all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hilton Chain via Guix-patches via <guix-patches@gnu.org>
To: Brian Cully <bjc@spork.org>
Cc: Sam Lockart <sam@samlockart.com>, 64260@debbugs.gnu.org
Subject: [bug#64260] [PATCH] Use cgroups v2 file system
Date: Wed, 02 Aug 2023 12:39:35 +0800	[thread overview]
Message-ID: <87r0omoy60.wl-hako@ultrarare.space> (raw)
In-Reply-To: <87cz16gjxp.fsf@psyduck.jhoto.kublai.com>

Hi,

On Thu, 06 Jul 2023 04:52:34 +0800,
Brian Cully via Guix-patches via wrote:
>
> I've been running this patch for a few days with an elogind-based system
> and haven't had any issues. This patch also fixes rootless podman with
> elogind, which is very nice.
>
> -bjc

I'm not familiar with cgroup, but the current %control-groups is
a requirement for docker-shepherd-service:
--8<---------------cut here---------------start------------->8---
(shepherd-service
       (documentation "Docker daemon.")
       (provision '(dockerd))
       (requirement '(containerd
                      dbus-system
                      elogind
                      file-system-/sys/fs/cgroup/blkio
                      file-system-/sys/fs/cgroup/cpu
                      file-system-/sys/fs/cgroup/cpuset
                      file-system-/sys/fs/cgroup/devices
                      file-system-/sys/fs/cgroup/memory
                      file-system-/sys/fs/cgroup/pids
                      networking
                      udev))
--8<---------------cut here---------------end--------------->8---

Thanks




  reply	other threads:[~2023-08-02  4:41 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 [this message]
2023-08-08 15:08 ` bug#64260: " Ludovic Courtès

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=87r0omoy60.wl-hako@ultrarare.space \
    --to=guix-patches@gnu.org \
    --cc=64260@debbugs.gnu.org \
    --cc=bjc@spork.org \
    --cc=hako@ultrarare.space \
    --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 external index

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

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.