all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sergiu Ivanov <sivanov@colimite.fr>
To: 65614@debbugs.gnu.org
Subject: bug#65614: cgroups increase to 65555 preventing docker to start
Date: Sat, 02 Sep 2023 22:25:43 +0200	[thread overview]
Message-ID: <87fs3wiaf0.fsf@colimite.fr> (raw)
In-Reply-To: <87msy9sz6j.fsf@web.de>

Hello,

I have a similar issue, related to cgroups as well: after a recent
update, I cannot start my LXC containers anymore.

This is how I generally start one of my LXC containers, called arch:

# lxc-start -n arch

I add the -F switch to get the following more detailed error log:


lxc-start: arch: cgroups/cgfsng.c: cg_legacy_set_data: 2678 No such file or directory - Failed to setup limits for the "devices" controller. The controller seems to be unused by "cgfsng" cgroup driver or not enabled on the cgroup hierarchy
lxc-start: arch: cgroups/cgfsng.c: cgfsng_setup_limits_legacy: 2745 No such file or directory - Failed to set "devices.deny" to "a"
lxc-start: arch: start.c: lxc_spawn: 1896 Failed to setup legacy device cgroup controller limits
lxc-start: arch: start.c: __lxc_start: 2074 Failed to spawn container "arch"
lxc-start: arch: tools/lxc_start.c: main: 306 The container failed to start
lxc-start: arch: tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options


I tried tinkering a little with the cgroups-related options in my
container configuration, but that had zero impact on the error message.

-
Sergiu




      reply	other threads:[~2023-09-02 20:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30  8:31 bug#65614: cgroups increase to 65555 preventing docker to start Dr. Arne Babenhauserheide
2023-09-02 20:25 ` Sergiu Ivanov [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

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

  git send-email \
    --in-reply-to=87fs3wiaf0.fsf@colimite.fr \
    --to=sivanov@colimite.fr \
    --cc=65614@debbugs.gnu.org \
    /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.