Your message dated Sat, 25 Oct 2025 15:33:56 -0400 with message-id <[email protected]> and subject line Re: Bug#939539: docker.io: Failed to start Docker Application Container Engine. has caused the Debian Bug report #939539, regarding docker.io: Failed to start Docker Application Container Engine. 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.) -- 939539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939539 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: docker.io Version: 18.09.5+dfsg1-1 Severity: important Dear Maintainer, After a recent upgrade to linux-image-5.2.0-2-amd64 docker no longer starts with the following reported by systemd: ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-09-05 23:13:28 MST; 4min 58s ago Docs: https://docs.docker.com Process: 123443 ExecStart=/usr/sbin/dockerd -H fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE) Main PID: 123443 (code=exited, status=1/FAILURE) CPU: 154ms Sep 05 23:13:28 life systemd[1]: docker.service: Failed with result 'exit-code'. Sep 05 23:13:28 life systemd[1]: Failed to start Docker Application Container Engine. Sep 05 23:13:28 life systemd[1]: docker.service: Service RestartSec=100ms expired, scheduling restart. Sep 05 23:13:28 life systemd[1]: docker.service: Scheduled restart job, restart counter is at 3. Sep 05 23:13:28 life systemd[1]: Stopped Docker Application Container Engine. Sep 05 23:13:28 life systemd[1]: docker.service: Start request repeated too quickly. Sep 05 23:13:28 life systemd[1]: docker.service: Failed with result 'exit-code'. Sep 05 23:13:28 life systemd[1]: Failed to start Docker Application Container Engine. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages docker.io depends on: ii adduser 3.118 ii iptables 1.8.3-2 ii libc6 2.29-0experimental1 ii libdevmapper1.02.1 2:1.02.155-3 ii libltdl7 2.4.6-11 ii libnspr4 2:4.21-2 ii libnss3 2:3.45-1 ii libseccomp2 2.4.1-2 ii libsystemd0 243~rc2-1 ii lsb-base 11.1.0 ii runc 1.0.0~rc6+dfsg1-3 ii tini 0.18.0-1+b1 Versions of packages docker.io recommends: ii ca-certificates 20190110 ii cgroupfs-mount 1.4 ii git 1:2.23.0-1 ii needrestart 3.4-5 ii xz-utils 5.2.4-1+b1 Versions of packages docker.io suggests: pn aufs-tools <none> pn btrfs-progs <none> ii debootstrap 1.0.115 pn docker-doc <none> ii e2fsprogs 1.45.3-4 pn rinse <none> pn xfsprogs <none> pn zfs-fuse | zfsutils <none> -- no debconf information
--- End Message ---
--- Begin Message ---> Just to finalize, it was NOT necessary to modify the GRUB_CMDLINE_LINUX > value in /etc/default/grub but it IS necessary to manually run the > script from here after each reboot: > https://github.com/moby/moby/issues/8791#issuecomment-60874893. this is done in the docker.io init script: https://sources.debian.org/src/docker.io/20.10.5%2Bdfsg1-1/debian/docker.io.docker.init#L54-L81 > It appears that even though cgroupfs-mount is required by the docker.io > package, either the cgroupfs-mount package or else the docker.io package > is not setting things up properly with the cgroup system mounts and they > are not getting mounted at boot time. Fresh Debian installations setup cgroupfs properly out of the box. This is not something that can be fixed in the docker.io package. As such, I'm closing this bug with this email.
--- End Message ---
