Your message dated Sat, 25 Oct 2025 14:50:02 -0400
with message-id <[email protected]>
and subject line Re: Bug#925115: docker: Error response from daemon: unable to 
find "systemd" in controller set: unknown.
has caused the Debian Bug report #925115,
regarding docker: Error response from daemon: unable to find "systemd" in 
controller set: unknown.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
925115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925115
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: docker.io
Version: 18.09.1+dfsg1-5+b10
Severity: important

Docker does not work out of the box.

$ sudo docker run  -it debian /bin/bash                                       
docker: Error response from daemon: unable to find "systemd" in controller set: 
unknown.


Workaround: do this once manually:

$ sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd


-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages docker.io depends on:
ii  adduser             3.118
ii  iptables            1.8.2-4
ii  libc6               2.28-8
ii  libdevmapper1.02.1  2:1.02.155-2
ii  libltdl7            2.4.6-10
ii  libnspr4            2:4.20-1
ii  libnss3             2:3.42.1-1
ii  libseccomp2         2.3.3-4
ii  libsystemd0         241-2
ii  lsb-base            10.2019031300
ii  runc                1.0.0~rc6+dfsg1-3
ii  tini                0.18.0-1

Versions of packages docker.io recommends:
ii  ca-bundle [ca-certificates]  20181220tarent1
pn  cgroupfs-mount               <none>
ii  git                          1:2.20.1-2
pn  needrestart                  <none>
ii  xz-utils                     5.2.4-1

Versions of packages docker.io suggests:
pn  aufs-tools           <none>
pn  btrfs-progs          <none>
ii  debootstrap          1.0.114
pn  docker-doc           <none>
ii  e2fsprogs            1.45.0-1
pn  rinse                <none>
pn  xfsprogs             <none>
pn  zfs-fuse | zfsutils  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 26.1.4+dfsg1-1

Thorsten Glaser <[email protected]> writes:

> Docker does not work out of the box.
>
> $ sudo docker run  -it debian /bin/bash                                       
> docker: Error response from daemon: unable to find "systemd" in controller 
> set: unknown.
>
>
> Workaround: do this once manually:
>
> $ sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd



From: Arnaud Rebillout <[email protected]>
>
> I did a quick search, there seem to be a bug opened upstream just a few
> days ago:
>
>  https://github.com/moby/moby/issues/38822
>
> Which links to:
>
> https://github.com/containerd/containerd/pull/3079
>


I concur. This has been fixed in a newer version of containerd. Closing
this issue accordingly.


-rt

--- End Message ---

Reply via email to