All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	 Fiona Klute <fiona.klute@gmx.de>,
	 Christian Stewart <christian@aperture.us>,
	buildroot@buildroot.org,
	 "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
Subject: Re: [Buildroot] [PATCH 1/1] package/docker-engine: prefer cgroup v2 with kernel >=5.4 and no systemd
Date: Thu, 28 Aug 2025 11:11:16 +0200	[thread overview]
Message-ID: <875xe7lsjv.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <f6d95d33-d134-4390-be7f-ee1a674b25ee@smile.fr> (Romain Naour's message of "Wed, 27 Aug 2025 17:22:30 +0200")

>>>>> "Romain" == Romain Naour <romain.naour@smile.fr> writes:

Hi,

 >> Totally fine with this idea. I think it's OK to require a 5.4 kernel
 >> if you want to run Docker.

 > Agree. If we really want to keep cgroupv1, we must at least add a specific test
 > to check if other packages (like docker) are still working with only cgroupv1.

 > I'm not sure it's worth the effort.

I doubt it as well. Recently, systemd has also dropped cgroupv1 support:

https://mastodon.social/@pid_eins/115088165140443645

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-08-28  9:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 13:24 [Buildroot] [PATCH 1/1] package/docker-engine: prefer cgroup v2 with kernel >=5.4 and no systemd Fiona Klute via buildroot
2025-08-19  3:53 ` Christian Stewart via buildroot
2025-08-24  9:33   ` Romain Naour via buildroot
2025-08-25 10:24     ` Fiona Klute via buildroot
2025-08-26 10:18       ` Thomas Petazzoni via buildroot
2025-08-27 15:22         ` Romain Naour via buildroot
2025-08-28  9:11           ` Peter Korsgaard [this message]
2025-08-29  9:15             ` Fiona Klute via buildroot

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=875xe7lsjv.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=christian@aperture.us \
    --cc=fiona.klute@gmx.de \
    --cc=romain.naour@smile.fr \
    --cc=thomas.petazzoni@bootlin.com \
    /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.