From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: 65614@debbugs.gnu.org
Subject: bug#65614: cgroups increase to 65555 preventing docker to start
Date: Wed, 30 Aug 2023 10:31:36 +0200 [thread overview]
Message-ID: <87msy9sz6j.fsf@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]
Hi,
when I try to start a docker container, I get the erro
docker: Error response from daemon: failed to create shim task: OCI
runtime create failed: runc create failed: unable to start container
process: unable to apply cgroup configuration: mkdir
/sys/fs/cgroup/docker/dac0a619a2d6f980095c74a6a2b82a31bbfef721d5bc80fe9a9fb94fe48cfa37:
no space left on device: unknown.
Checking the number of cgroups shows that it’s at the limit (if I read
it right, no guarantees for that, cgroups isn’t my strong side), but
this is after only a few days of uptime:
$ find /sys/fs/cgroup/ -type d | wc -l
65534
$ cat /proc/cgroups
#subsys_name hierarchy num_cgroups enabled
cpuset 0 65536 1
cpu 0 65536 1
cpuacct 0 65536 1
blkio 0 65536 1
memory 0 65536 1
devices 0 65536 1
freezer 0 65536 1
net_cls 0 65536 1
perf_event 0 65536 1
net_prio 0 65536 1
hugetlb 0 65536 1
pids 0 65536 1
misc 0 65536 1
Is Guix using cgroups for building?
Is something broken in Guix or do I have to hunt elsewhere for fixes?
Other people seem to have similar problems, but only after massive
docker usage:
https://github.com/AlexiaChen/rocker/issues/3#issuecomment-1128946114
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next reply other threads:[~2023-08-30 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 8:31 Dr. Arne Babenhauserheide [this message]
2023-09-02 20:25 ` bug#65614: cgroups increase to 65555 preventing docker to start Sergiu Ivanov
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=87msy9sz6j.fsf@web.de \
--to=arne_bab@web.de \
--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.