unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Sam Lockart <sam@samlockart.com>
Cc: 64260-done@debbugs.gnu.org
Subject: bug#64260: [PATCH] Use cgroups v2 file system
Date: Tue, 08 Aug 2023 17:08:26 +0200	[thread overview]
Message-ID: <87leelr2qd.fsf@gnu.org> (raw)
In-Reply-To: <hC7GiiLV5qxJ0WSDTRmDmy4V2wsy6yraRPcoC4UC2WAhEyNCb69vCjBYKYVHmF1NS65HyWYD-jBliH_Gq5LwAO_2WPlhqq2ekBWI0FYyFxc=@samlockart.com> (Sam Lockart's message of "Sat, 24 Jun 2023 03:11:26 +0000")

Hello Sam,

Sam Lockart <sam@samlockart.com> skribis:

> cgroup v2 is the next generation of the control groups API.
> This patch replaces the cgroup v1 file system with the unified
> cgroup v2 file system.
>
> cgroup v2 allows for things like containerd/podman to run rootless containers and opens guix system up to running things like Kubernetes.
>
> * gnu/system/file-systems.scm: Use cgroups v2 file system

[...]

Hilton Chain <hako@ultrarare.space> skribis:

> I'm not familiar with cgroup, but the current %control-groups is
> a requirement for docker-shepherd-service:

Good point!  Finally applied, with the change Hilton suggested.

This passes just fine:

  make check-system TESTS="docker basic elogind"

Thanks,
Ludo’.




      parent reply	other threads:[~2023-08-08 15:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24  3:11 [bug#64260] [PATCH] Use cgroups v2 file system Sam Lockart
2023-07-05 20:52 ` Brian Cully via Guix-patches via
2023-08-02  4:39   ` Hilton Chain via Guix-patches via
2023-08-08 15:08 ` Ludovic Courtès [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87leelr2qd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=64260-done@debbugs.gnu.org \
    --cc=sam@samlockart.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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).