From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/systemd: hybrid cgroupfs hierarchy for docker compatibility
Date: Mon, 11 Nov 2019 16:29:44 +0100 [thread overview]
Message-ID: <20191111162944.5529d1b2@windsurf.home> (raw)
In-Reply-To: <20191111083348.3964650-1-christian@paral.in>
On Mon, 11 Nov 2019 00:33:48 -0800
Christian Stewart <christian@paral.in> wrote:
> Docker fails to start with "Devices cgroup isn't mounted" as of systemd 243.
> According to the systemd documentation:
>
> systemd now defaults to the "unified" cgroup hierarchy setup during
> build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default.
> Previously, -Ddefault-hierarchy=hybrid was the default. [...] Downstream
> production distributions might want to continue to use
> -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately
> the popular container managers have not caught up with the kernel API changes.
>
> Changing this option to "hybrid" or "legacy" fixes the Docker startup.
>
> Reference: https://github.com/opencontainers/runc/issues/654
>
> Signed-off-by: Christian Stewart <christian@paral.in>
> ---
> package/systemd/systemd.mk | 1 +
> 1 file changed, 1 insertion(+)
Applied to master, thanks. It would be nice to have some runtime tests
around Docker, to verify that it is still working properly at runtime,
so that we can catch this kind of issues.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-11-11 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 8:33 [Buildroot] [PATCH 1/1] package/systemd: hybrid cgroupfs hierarchy for docker compatibility Christian Stewart
2019-11-11 9:04 ` James Hilliard
2019-11-11 10:09 ` Jérémy ROSEN
2019-11-11 14:39 ` Thomas Petazzoni
2019-11-11 14:56 ` Jérémy ROSEN
2019-11-11 15:01 ` Thomas Petazzoni
2019-11-11 15:29 ` Thomas Petazzoni [this message]
2019-11-11 20:27 ` Christian Stewart
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=20191111162944.5529d1b2@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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