Bug 15321 - docker-engine now requires libseccomp by default
Summary: docker-engine now requires libseccomp by default
Status: RESOLVED FIXED
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: All Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-09 13:20 UTC by Dominique Tronche
Modified: 2023-03-12 20:09 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dominique Tronche 2023-02-09 13:20:03 UTC 
While trying to build our project which uses docker-engine on the master branch of buildroot which has integrated the major release 23.0.0, the following error message is diplayed when starting the docker containers:

Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: seccomp: config provided but seccomp not supported: unknown
Error: failed to start containers

From docker release note (https://docs.docker.com/engine/release-notes/23.0/) in section security, it seems docker is now always built with seccomp support

I think the libseccomp package is therefore now necessary and a select on that package should be added in a Config.in file.
It seems to be runc which is linked to the library