From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: Christian Stewart <christian@aperture.us>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/docker-engine: fix runtime problem
Date: Tue, 20 Aug 2024 23:26:33 +0200 [thread overview]
Message-ID: <ZsUKCVcZheIlzo00@landeda> (raw)
In-Reply-To: <ZsS52zTjT0Ca9twG@waldemar-brodkorb.de>
Waldemar, All,
On 2024-08-20 17:44 +0200, Waldemar Brodkorb spake thusly:
> When starting a container you get:
> # docker run nginx
> docker0: port 1(veth7743781) entered blocking state
> docker0: port 1(veth7743781) entered disabled state
> veth7743781: entered allmulticast mode
> veth7743781: entered promiscuous mode
> docker0: port 1(veth7743781) entered disabled state
> veth7743781 (unregistering): left allmulticast mode
> veth7743781 (unregistering): left promiscuous mode
> docker0: port 1(veth7743781) entered disabled state
> docker: Error response from daemon: failed to create task for
> container: failed to create shim task: OCI runtime create failed:
> error opening file `/proc/self/uid_map`: No such file or directory: unknown.
>
> Add the missing kernel module to allow starting containers.
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> package/docker-engine/docker-engine.mk | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/docker-engine/docker-engine.mk b/package/docker-engine/docker-engine.mk
> index 268b851520..baec32d79d 100644
> --- a/package/docker-engine/docker-engine.mk
> +++ b/package/docker-engine/docker-engine.mk
> @@ -106,6 +106,7 @@ define DOCKER_ENGINE_LINUX_CONFIG_FIXUPS
> $(call KCONFIG_ENABLE_OPT,CONFIG_CGROUP_DEVICE)
> $(call KCONFIG_ENABLE_OPT,CONFIG_CGROUP_CPUACCT)
> $(call KCONFIG_ENABLE_OPT,CONFIG_NAMESPACES)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_USER_NS)
As far as I can see, this is an optional feature, and is not strictly
required:
https://github.com/moby/moby/blob/master/contrib/check-config.sh#L235
So I don't think we should forecfully enable it.
Regards,
Yann E. MORIN.
> $(call KCONFIG_ENABLE_OPT,CONFIG_UTS_NS)
> $(call KCONFIG_ENABLE_OPT,CONFIG_IPC_NS)
> $(call KCONFIG_ENABLE_OPT,CONFIG_PID_NS)
> --
> 2.30.2
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-20 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 15:44 [Buildroot] [PATCH] package/docker-engine: fix runtime problem Waldemar Brodkorb
2024-08-20 21:26 ` Yann E. MORIN [this message]
2024-08-20 21:32 ` Thomas Petazzoni via buildroot
2024-08-20 22:00 ` Yann E. MORIN
2024-08-21 6:18 ` TIAN Yuanhao
2024-08-21 7:12 ` Yann E. MORIN
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=ZsUKCVcZheIlzo00@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=wbx@openadk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox