From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15321] New: docker-engine now requires libseccomp by default
Date: Thu, 09 Feb 2023 13:20:03 +0000 [thread overview]
Message-ID: <bug-15321-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15321
Bug ID: 15321
Summary: docker-engine now requires libseccomp by default
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: dominique.tronche@atos.net
CC: buildroot@uclibc.org
Target Milestone: ---
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
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-02-09 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 13:20 bugzilla [this message]
2023-03-12 20:09 ` [Buildroot] [Bug 15321] docker-engine now requires libseccomp by default bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-15321-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.