Bullseye+Docker - Cannot connect to the Docker daemon

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version:
    G_DIETPI_VERSION_CORE=9
    G_DIETPI_VERSION_SUB=4
    G_DIETPI_VERSION_RC=2
    G_GITBRANCH=‘master’
    G_GITOWNER=‘MichaIng’
    G_LIVE_PATCH_STATUS[0]=‘not applicable’

  • Distro version:
    bullseye

  • Kernel version:
    Linux DietPi 3.10.38 #22 SMP PREEMPT Fri Dec 22 10:45:41 IST 2017 armv7l GNU/Linux

  • Architecture:
    armhf

  • SBC model:
    Sparky SBC (armv7l)

Issue

Over the last few days, I’ve updated my dietpi version from Stretch to Buster and finally to Bullseye. Everything there went fine.

I was having trouble with Docker, so I unistalled completely and reinstalled (several times), but no mater what I try, I keep getting this msg:

docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

How should I go about debugging this issue? Thanks!

did you already checked if docker.socket is running

systemctl status docker.socket

I will try this as soon as I fix my ssh issue :slight_smile:

Okay, it looks like docker.socket is not running. Something about service start limit hit:

root@DietPi:~# systemctl status docker.socket
● docker.socket - Docker Socket for the API
Loaded: loaded (/lib/systemd/system/docker.socket; enabled; vendor preset: enabled)
Active: failed (Result: service-start-limit-hit) since Thu 2024-05-30 15:07:17 PDT; 3 days ago
Triggers: ● docker.service
Listen: /run/docker.sock (Stream)
May 30 14:17:05 DietPi systemd[1]: Starting Docker Socket for the API.
May 30 14:17:05 DietPi systemd[1]: Listening on Docker Socket for the API.
May 30 15:07:17 DietPi systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
root@DietPi:~#

Can you try to restart the socket

systemctl restart docker.socket

And check system logs

journalctl -u docker.socket

Here are the results:

root@DietPi:~# systemctl restart docker.socket
root@DietPi:~# journalctl -u docker.socket
Journal file /var/log/journal/725bae9f2861442597f0f0af07f7b3d0/system.journal is truncated, ignoring file.
-- Journal begins at Thu 2024-05-30 14:17:02 PDT, ends at Mon 2024-06-03 12:10:05 PDT. --
May 30 14:17:05 DietPi systemd[1]: Starting Docker Socket for the API.
May 30 14:17:05 DietPi systemd[1]: Listening on Docker Socket for the API.
May 30 15:07:17 DietPi systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
Jun 03 12:10:05 DietPi systemd[1]: Starting Docker Socket for the API.
Jun 03 12:10:05 DietPi systemd[1]: Listening on Docker Socket for the API.
root@DietPi:~#

Look like socket is working fine now

I think I’m back to where I started. I’ve been attempting to install Roon Extension Manager, but I alway end up with an error related to container creation. Initially, I had some Docker errors at the process crapped out almost immediately. Now, it takes quite awhile (~5min) before it fails. I’ve tried to install a few different ways, but the results are similar to this (very long) process:

root@DietPi:~# dietpi-software install 86
[  OK  ] DietPi-Software | Initialised database
[  OK  ] DietPi-Software | Reading database

 DietPi-Software
─────────────────────────────────────────────────────
 Mode: Automated install

[  OK  ] DietPi-Software | Installing Roon Extension Manager: manage extensions from within Roon
[  OK  ] DietPi-Software | DietPi-Userdata validation: /mnt/dietpi_userdata

 DietPi-Software
─────────────────────────────────────────────────────
 Step: Checking for conflicts and missing inputs


 DietPi-Software
─────────────────────────────────────────────────────
 Step: Checking for prerequisite software

[ INFO ] DietPi-Software | Docker will be reinstalled
[  OK  ] DietPi-Software | mkdir -p /mnt/dietpi_userdata/Music /mnt/dietpi_userdata/Pictures /mnt/dietpi_userdata/Video /mnt/dietpi_userdata/downloads /var/www /opt /usr/local/bin
[  OK  ] DietPi-Software | chown dietpi:dietpi /mnt/dietpi_userdata/Music /mnt/dietpi_userdata/Pictures /mnt/dietpi_userdata/Video /mnt/dietpi_userdata/downloads
[  OK  ] DietPi-Software | chmod 0775 /mnt/dietpi_userdata/Music /mnt/dietpi_userdata/Pictures /mnt/dietpi_userdata/Video /mnt/dietpi_userdata/downloads
[ SUB1 ] DietPi-Services > stop 
[  OK  ] DietPi-Services | stop : cron
[  OK  ] DietPi-Services | stop : docker
[  OK  ] DietPi-Services | stop : netdata
[  OK  ] DietPi-Services | stop : roon-extension-manager
[  OK  ] DietPi-Services | stop : roonbridge
[  OK  ] DietPi-Services | stop : networkaudiod
[  OK  ] DietPi-Services | stop : gmediarender
[  OK  ] DietPi-Services | stop : squeezelite
[  OK  ] DietPi-Services | stop : shairport-sync
[  OK  ] DietPi-Services | stop : mpd
[  OK  ] DietPi-Services | stop : lighttpd
[  OK  ] DietPi-Services | stop : php7.4-fpm
[  OK  ] DietPi-Services | stop : mariadb
[  OK  ] DietPi-Services | stop : smbd
[  OK  ] DietPi-Services | stop : nmbd
[  OK  ] DietPi-Services | stop : avahi-daemon
[ INFO ] DietPi-Software | APT update, please wait...
Hit:1 http://ftp.debian.org/debian bullseye InRelease
Hit:2 http://ftp.debian.org/debian bullseye-updates InRelease
Hit:3 https://download.docker.com/linux/debian bullseye InRelease
Hit:4 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:5 https://dietpi.com/apt bullseye InRelease
Hit:6 https://dietpi.com/apt all InRelease
Reading package lists...
[  OK  ] DietPi-Software | APT update

 DietPi-Software
─────────────────────────────────────────────────────
 Step: Installing Docker: Build, ship, and run distributed applications

[  OK  ] DietPi-Software | Checking URL: https://download.docker.com/linux/debian/gpg
[  OK  ] DietPi-Software | eval curl -sSfL 'https://download.docker.com/linux/debian/gpg' | gpg --dearmor -o /etc/apt/trusted.gpg.d/dietpi-docker.gpg --yes
[  OK  ] DietPi-Software | eval echo 'deb https://download.docker.com/linux/debian bullseye stable' > /etc/apt/sources.list.d/docker.list
[ INFO ] DietPi-Software | APT update, please wait...
Hit:1 http://ftp.debian.org/debian bullseye InRelease
Hit:2 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:3 https://download.docker.com/linux/debian bullseye InRelease
Hit:4 http://ftp.debian.org/debian bullseye-updates InRelease
Hit:5 https://dietpi.com/apt bullseye InRelease
Hit:6 https://dietpi.com/apt all InRelease
Reading package lists...
[  OK  ] DietPi-Software | APT update
[  OK  ] DietPi-Software | systemctl mask --now docker
[ INFO ] DietPi-Software | APT install docker-ce, please wait...
Reading package lists...
Building dependency tree...
Reading state information...
docker-ce is already the newest version (5:26.1.3-1~debian.11~bullseye).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[  OK  ] DietPi-Software | APT install docker-ce
[  OK  ] DietPi-Software | systemctl unmask docker
[  OK  ] DietPi-Software | systemctl start docker.socket
[  OK  ] DietPi-Software | mkdir -p /lib/systemd/system/docker.service.d
[  OK  ] DietPi-Software | eval echo -e '[Service]\nType=simple' > /lib/systemd/system/docker.service.d/dietpi-simple.conf
[  OK  ] DietPi-Software | mkdir -p /mnt/dietpi_userdata/docker-data
[  OK  ] DietPi-Software | Current setting in /etc/docker/daemon.json will be preserved:     "data-root": "/mnt/dietpi_userdata/docker-data",
[  OK  ] DietPi-Software | Current setting in /etc/docker/daemon.json will be preserved:     "log-driver": "journald",
[  OK  ] DietPi-Software | Current setting in /etc/docker/daemon.json will be preserved:     "log-level": "warn",
[  OK  ] DietPi-Software | Current setting in /etc/docker/daemon.json will be preserved:     "debug": false
[  OK  ] DietPi-Software | Desired setting in /etc/containerd/config.toml was already set: [debug]
[  OK  ] DietPi-Software | Current setting in /etc/containerd/config.toml will be preserved:   level = "warn"
[  OK  ] DietPi-Software | update-alternatives --set iptables /usr/sbin/iptables-legacy
[  OK  ] DietPi-Software | update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy

 DietPi-Software
─────────────────────────────────────────────────────
 Step: Installing Roon Extension Manager: manage extensions from within Roon

[  OK  ] DietPi-Software | mkdir -p /mnt/dietpi_userdata/roon-extension-manager
[  OK  ] DietPi-Software | systemctl stop roon-extension-manager
[  OK  ] DietPi-Software | rm /etc/systemd/system/roon-extension-manager.service
[  OK  ] DietPi-Software | usermod -aG docker -d /mnt/dietpi_userdata/roon-extension-manager -s /bin/dash roon-extension-manager
[  OK  ] DietPi-Software | chown -R roon-extension-manager:root /mnt/dietpi_userdata/roon-extension-manager
[  OK  ] DietPi-Software | cd /tmp/DietPi-Software
[  OK  ] DietPi-Software | Checking URL: https://raw.githubusercontent.com/TheAppgineer/roon-extension-manager/v1.x/rem-setup.sh
[ INFO ] DietPi-Software | G_THREAD_START_0 | curl -sSfL https://raw.githubusercontent.com/TheAppgineer/roon-extension-manager/v1.x/rem-setup.sh -o rem-setup.sh
[ INFO ] DietPi-Software | APT install wget, please wait...
Reading package lists...
Building dependency tree...
Reading state information...
wget is already the newest version (1.21-1+deb11u1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[  OK  ] DietPi-Software | APT install wget
[  OK  ] DietPi-Software | G_THREAD: All threads finished
[  OK  ] DietPi-Software | mv rem-setup.sh /mnt/dietpi_userdata/roon-extension-manager/rem-setup.sh
[  OK  ] DietPi-Software | cd /mnt/dietpi_userdata/roon-extension-manager
[  OK  ] DietPi-Software | chmod +x rem-setup.sh
[ INFO ] DietPi-Software | ./rem-setup.sh, please wait...
Roon Extension Manager setup script - version 1.0.0

Checking for root privileges...		[ OK ]
Checking for Docker socket...		[ OK ]
Downloading shell script...		[ OK ]
Detecting timezone...			[ OK ]
Setting up service...			[ OK ]
Starting service...			[ OK ]
Waiting for container creation...	[FAIL]
[FAILED] DietPi-Software | ./rem-setup.sh

Socket is not working again?

Correct :frowning:

root@DietPi:~# systemctl status docker.socket
● docker.socket - Docker Socket for the API
Loaded: loaded (/lib/systemd/system/docker.socket; enabled; vendor preset:
enabled)
Active: failed (Result: service-start-limit-hit) since Tue 2024-
06-04 08:02:40 PDT; 5min ago
Triggers: ● docker.service
Listen: /run/docker.sock (Stream)
Jun 04 08:02:08 DietPi systemd[1]: Starting Docker Socket for the API.
Jun 04 08:02:08 DietPi systemd[1]: Listening on Docker Socket for the API.
Jun 04 08:02:40 DietPi systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
root@DietPi:~#

I did another systemctl restart docker.socket and continue to see this log:

docker.socket: Failed with result 'service-start-limit-hit'.

And in status, Triggers: docker.service still has a red dot, which I assume is an error.

the system has been rebooted already, right?

some further tips from the web docker.socket failed with result service-start-limit-hit | Troubleshooting tip

Yes, I’ve rebooted several times too. I’ll check out the link you shared and see where that takes me.

Thank you!

I think, the activation socket is not the issue, but the Docker daemon itself failing to start or taking too long. And I think the reason is that Linux 3.10 is too old for recent Docker versions to function.

Check the logs:

journalctl -u docker -u containerd

Ah! Here’s the output:

root@DietPi:~# journalctl -u docker -u containerd
Journal file /var/log/journal/725bae9f2861442597f0f0af07f7b3d0/system.journal is truncated, ignoring file.
-- Journal begins at Tue 2024-06-04 11:18:15 PDT, ends at Tue 2024-06-04 11:41:18 PDT. --
Jun 04 11:18:19 DietPi systemd[1]: Starting containerd container runtime...
Jun 04 11:18:19 DietPi modprobe[987]: modprobe: FATAL: Module overlay not found in directory /lib/modules/3.10.38
Jun 04 11:18:22 DietPi containerd[1003]: time="2024-06-04T11:18:22-07:00" level=
warning msg="containerd config version `1` has been deprecated and will be converted on each startup in containerd v2.0, use `containerd config migrate` after upgrading to containerd 2.0 to avoid conversion on startup"
Jun 04 11:18:23 DietPi containerd[1003]: time="2024-06-04T11:18:23.210933834-07:
00" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.devmapper" error="devmapper not configured"
Jun 04 11:18:23 DietPi containerd[1003]: time="2024-06-04T11:18:23.217987250-07:
00" level=warning msg="could not use snapshotter devmapper in metadata plugin" error="devmapper not configured"
Jun 04 11:18:23 DietPi systemd[1]: Started containerd container runtime.
Jun 04 11:18:23 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:18:29 DietPi dockerd[1104]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:18:29 DietPi systemd[1]: **docker.service: Main process exited, code=exited, status=1/FAILURE**
Jun 04 11:18:29 DietPi systemd[1]: **docker.service: Failed with result 'exit-code'.**
Jun 04 11:18:32 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 1.
Jun 04 11:18:32 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:18:32 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:18:33 DietPi dockerd[1348]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:18:33 DietPi systemd[1]: **docker.service: Main process exited, code=exited, status=1/FAILURE**
Jun 04 11:18:33 DietPi systemd[1]: **docker.service: Failed with result 'exit-code'.**
Jun 04 11:18:35 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 2.
Jun 04 11:18:35 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:18:35 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:18:36 DietPi dockerd[1514]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:18:36 DietPi systemd[1]: **docker.service: Main**
**process exited, code=exited, status=1/FAILURE**
Jun 04 11:18:36 DietPi systemd[1]: **docker.service: Failed with result 'exit-code'.**
Jun 04 11:18:39 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Jun 04 11:18:39 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:18:39 DietPi systemd[1]: **docker.service: Start request repeated too quickly.**
Jun 04 11:18:39 DietPi systemd[1]: **docker.service: Failed with result 'exit-code'.**
Jun 04 11:18:39 DietPi systemd[1]: **Failed to start Docker Application Container Engine.**
Jun 04 11:19:51 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:19:52 DietPi dockerd[2450]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:19:52 DietPi systemd[1]: **docker.service: Main**
**process exited, code=exited, status=1/FAILURE**
Jun 04 11:19:52 DietPi systemd[1]: **docker.service: Failed with result 'exit-code'.**
Jun 04 11:19:54 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 1.
Jun 04 11:19:54 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:19:54 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:19:55 DietPi dockerd[2478]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:19:55 DietPi systemd[1]: **docker.service: Main**
**process exited, code=exited, status=1/FAILURE**
Jun 04 11:19:55 DietPi systemd[1]: **docker.service: Failed with result 'exit-code'.**
Jun 04 11:19:57 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 2.
Jun 04 11:19:57 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:19:57 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:19:57 DietPi dockerd[2502]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:19:57 DietPi systemd[1]: **docker.service: Main**
**process exited, code=exited, status=1/FAILURE**
Jun 04 11:19:57 DietPi systemd[1]: **docker.service: Failed with result 'exit-code'.**
Jun 04 11:19:59 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Jun 04 11:19:59 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:19:59 DietPi systemd[1]: **docker.service: Start request repeated too quickly.**
Jun 04 11:19:59 DietPi systemd[1]: **docker.service: Failed with result 'exit-code'.**
Jun 04 11:19:59 DietPi systemd[1]: **Failed to start Docker Application Container Engine.**
Jun 04 11:21:15 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:21:15 DietPi dockerd[2611]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:21:15 DietPi systemd[1]: **docker.service: Main process exited, code=exited, status=1/FAILURE**
Jun 04 11:21:15 DietPi systemd[1]: **docker.service: Failed with result 'exit-code'.**
Jun 04 11:21:18 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 1.
Jun 04 11:21:18 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:21:18 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:21:18 DietPi dockerd[2634]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:21:18 DietPi systemd[1]: **docker.service: Main**
**process exited, code=exited, status=1/FAILURE**
Jun 04 11:21:18 DietPi systemd[1]: **docker.service: Failed with result 'exit-code'.**
Jun 04 11:21:20 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 2.
Jun 04 11:21:20 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:21:20 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:21:21 DietPi dockerd[2657]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:21:21 DietPi systemd[1]: **docker.service: Main process exited, code=exited, status=1/FAILURE**
Jun 04 11:21:21 DietPi systemd[1]: **docker.service: Failed with result 'exit-code'.**
Jun 04 11:21:23 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Jun 04 11:21:23 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:21:23 DietPi systemd[1]: **docker.service: Start request repeated too quickly.**
Jun 04 11:21:23 DietPi systemd[1]: **docker.service: Failed with result 'exit-code'.**
Jun 04 11:21:23 DietPi systemd[1]: **Failed to start Docker Application Container Engine.**
**root@DietPi**:**~**#

Uhhh I overlooked that one. Yes kernel 3.x is quite to old for running Docker.

Right, Docker requires cgroup v2, introduced with Linux 3.16.

But can you try the following:

G_CONFIG_INJECT '"exec-opts":' '    "exec-opts": ["native.cgroupdriver=cgroupfs"],' /etc/docker/daemon.json '^\{([[:space:]]|$)'
systemctl restart docker
sleep 5
journalctl -u docker

This should make Docker use its internal cgroup management, instead of cgroup v2. Let’s see whether this helps.

Okay, here’s the output after following these instructions:

G_CONFIG_INJECT '"exec-opts":' '    "exec-opts": ["native.cgroupdriver=cgroupfs"], /etc/docker/daemon.json '^\{([[:space:]]|$)'
systemctl restart docker
sleep 5
journalctl -u docker

Output:

root@DietPi:~# journalctl -u docker
Journal file /var/log/journal/725bae9f2861442597f0f0af07f7b3d0/system.journal is truncated, ignoring file.
-- Journal begins at Tue 2024-06-04 11:18:15 PDT, ends at Tue 2024-06-04 12:34:3
3 PDT. --
Jun 04 11:18:23 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:18:29 DietPi dockerd[1104]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:18:29 DietPi systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jun 04 11:18:29 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 04 11:18:32 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 1.
Jun 04 11:18:32 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:18:32 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:18:33 DietPi dockerd[1348]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:18:33 DietPi systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jun 04 11:18:33 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 04 11:18:35 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 2.
Jun 04 11:18:35 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:18:35 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:18:36 DietPi dockerd[1514]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:18:36 DietPi systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jun 04 11:18:36 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 04 11:18:39 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Jun 04 11:18:39 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:18:39 DietPi systemd[1]: docker.service: Start request repeated too quickly.
Jun 04 11:18:39 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 04 11:18:39 DietPi systemd[1]: Failed to start Docker Application Container Engine.
Jun 04 11:19:51 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:19:52 DietPi dockerd[2450]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:19:52 DietPi systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jun 04 11:19:52 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 04 11:19:54 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 1.
Jun 04 11:19:54 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:19:54 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:19:55 DietPi dockerd[2478]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:19:55 DietPi systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jun 04 11:19:55 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 04 11:19:57 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 2.
Jun 04 11:19:57 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:19:57 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:19:57 DietPi dockerd[2502]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:19:57 DietPi systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jun 04 11:19:57 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 04 11:19:59 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Jun 04 11:19:59 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:19:59 DietPi systemd[1]: docker.service: Start request repeated too quickly.
Jun 04 11:19:59 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 04 11:19:59 DietPi systemd[1]: Failed to start Docker Application Container Engine.
Jun 04 11:21:15 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:21:15 DietPi dockerd[2611]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:21:15 DietPi systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILUREe--
Jun 04 11:21:15 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 04 11:21:18 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 1.
Jun 04 11:21:18 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:21:18 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:21:18 DietPi dockerd[2634]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:21:18 DietPi systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILUREe--
Jun 04 11:21:18 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 04 11:21:20 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 2.
Jun 04 11:21:20 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:21:20 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 11:21:21 DietPi dockerd[2657]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 11:21:21 DietPi systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILUREe--
Jun 04 11:21:21 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 04 11:21:23 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Jun 04 11:21:23 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 11:21:23 DietPi systemd[1]: docker.service: Start request repeated too quickly.
Jun 04 11:21:23 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 04 11:21:23 DietPi systemd[1]: Failed to start Docker Application Container Engine.
Jun 04 12:34:25 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 12:34:26 DietPi dockerd[3774]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 12:34:26 DietPi systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILUREe--
Jun 04 12:34:26 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 04 12:34:28 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 1.
Jun 04 12:34:28 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 12:34:28 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 12:34:28 DietPi dockerd[3798]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 12:34:28 DietPi systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILUREe--
Jun 04 12:34:28 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 04 12:34:30 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 2.
Jun 04 12:34:30 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 12:34:30 DietPi systemd[1]: Started Docker Application Container Engine.
Jun 04 12:34:31 DietPi dockerd[3822]: failed to start daemon: Devices cgroup isn't mounted
Jun 04 12:34:31 DietPi systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILUREe--
Jun 04 12:34:31 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.m
Jun 04 12:34:33 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Jun 04 12:34:33 DietPi systemd[1]: Stopped Docker Application Container Engine.
Jun 04 12:34:33 DietPi systemd[1]: docker.service: Start request repeated too quickly.
Jun 04 12:34:33 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.m
Jun 04 12:34:33 DietPi systemd[1]: Failed to start Docker Application Container Engine.

root@DietPi:~#

I guess my final questions are:

  1. Is it possible/worthwhile to update my linux kernel?
  2. Is there an older Docker version that will run on my existing setup?
  3. Would I need to downgrade to Buster, etc to do either?

Thanks again for all your help!

probably not

probably yes. But I’m not sure which one would work

can be done if you would have a backup from before doing the Debian upgrade

1 Like