Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: Romain Naour <romain.naour@smile.fr>,
	"Arnout Vandecappelle \(Essensium/Mind\)" <arnout@mind.be>,
	Christian Stewart <christian@aperture.us>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/docker-engine: prefer cgroup v2 with kernel >=5.4 and no systemd
Date: Tue, 26 Aug 2025 12:18:51 +0200	[thread overview]
Message-ID: <20250826121851.06ec731e@windsurf> (raw)
In-Reply-To: <17c60c20-55aa-4864-b838-45751b67210e@gmx.de>

On Mon, 25 Aug 2025 12:24:27 +0200
Fiona Klute <fiona.klute@gmx.de> wrote:

> It looks like the "kernel too old for toolchain" problem appeared 
> before, in commit 521b6f85508ee9ab848b0b2ea1d36edaf1701bc1 that was the 
> reason to use the "stable" Bootlin toolchain instead of "bleeding-edge". 
> Earlier this year the stable toolchain was updated with headers 5.4 
> (commit 947dbc92a20c5acea7882166cae7893e6ea661e1), so I think the 
> reasonable solution here is to update the kernel. Looks like the kernel 
> config needs to be adjusted for 5.4.x, I'll send a patch when I have the 
> tests passing.

Indeed, now that the stable Bootlin toolchains use 5.4 headers, all
tests should use >= 5.4 kernel versions.

> Another question is if it still makes sense to claim support for kernel 
> versions < 5.4 and cgroup v1. Maybe it'd be better to simplify things 
> and have "depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_4" for all the 
> Docker packages, or even remove package/cgroupfs-mount entirely and 
> require all packages that need cgroups to use v2? There aren't that 
> many, grepping for BR2_PACKAGE_CGROUPFS_MOUNT (other than Docker and 
> Podman, which already works with either) there are package/moby-buildkit 
> (definitely supports cgroupv2), package/libvirt (haven't checked, but 
> I'd be extremely surprised if not), and package/balena-engine (no idea, 
> this is the first time I've heard of it).

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

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-08-26 10:19 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 [this message]
2025-08-27 15:22         ` Romain Naour via buildroot
2025-08-28  9:11           ` Peter Korsgaard
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=20250826121851.06ec731e@windsurf \
    --to=buildroot@buildroot.org \
    --cc=arnout@mind.be \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox