Hi,
I have a new Raspian Bullseye 32-bit lite build (updated and upgraded) on an old Pi v1 that I wanted to get a docker to run on for a simple application. However, when installing docker using the instructions for Raspian/Debian through using the repo at Install Docker Engine on Debian | Docker Documentation, there is an error when starting the service after the packages are unpacked:
Setting up containerd.io (1.6.10-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service → /lib/systemd/system/containerd.service.
Job for containerd.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status containerd.service" and "journalctl -xe" for details.
Setting up docker-compose-plugin (2.12.2~debian-bullseye) ...
Setting up libltdl7:armhf (2.4.6-15) ...
Setting up docker-ce-cli (5:20.10.21~3-0~debian-bullseye) ...
Setting up libslirp0:armhf (4.4.0-1+deb11u2) ...
Setting up docker-ce-rootless-extras (5:20.10.21~3-0~debian-bullseye) ...
Setting up slirp4netns (1.0.1-2) ...
Setting up docker-ce (5:20.10.21~3-0~debian-bullseye) ...
Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /lib/systemd/system/docker.service.
Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket.
A dependency job for docker.service failed. See 'journalctl -xe' for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: inactive (dead)
TriggeredBy: ● docker.socket
Docs: https://docs.docker.com
Dec 03 16:04:21 raspberrypi2 systemd[1]: Dependency failed for Docker Application Container Engine.
Dec 03 16:04:21 raspberrypi2 systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'.
Dec 03 16:40:33 raspberrypi2 systemd[1]: Dependency failed for Docker Application Container Engine.
Dec 03 16:40:33 raspberrypi2 systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'.
dpkg: error processing package docker-ce (--configure):
installed docker-ce package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u5) ...
Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
Checking the service, we see:
pi@raspberrypi2:~ $ systemctl status containerd.service
● containerd.service - containerd container runtime
Loaded: loaded (/lib/systemd/system/containerd.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: core-dump) since Sat 2022-12-03 16:42:21 GMT; 784ms ago
Docs: https://containerd.io
Process: 4253 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
Process: 4254 ExecStart=/usr/bin/containerd (code=dumped, signal=SEGV)
Main PID: 4254 (code=dumped, signal=SEGV)
CPU: 604ms
Dec 03 16:42:21 raspberrypi2 systemd[1]: containerd.service: Failed with result 'core-dump'.
Dec 03 16:42:21 raspberrypi2 systemd[1]: Failed to start containerd container runtime.
and the journal:
pi@raspberrypi2:~ $ journalctl -xe
░░ Subject: A stop job for unit containerd.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit containerd.service has finished.
░░
░░ The job identifier is 15282 and the job result is done.
Dec 03 16:44:08 raspberrypi2 systemd[1]: Starting containerd container runtime...
░░ Subject: A start job for unit containerd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit containerd.service has begun execution.
░░
░░ The job identifier is 15282.
Dec 03 16:44:09 raspberrypi2 systemd[1]: containerd.service: Main process exited, code=dumped, status=11/SEGV
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit containerd.service has exited.
░░
░░ The process' exit code is 'dumped' and its exit status is 11.
Dec 03 16:44:09 raspberrypi2 systemd[1]: containerd.service: Failed with result 'core-dump'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit containerd.service has entered the 'failed' state with result 'core-dump'.
Dec 03 16:44:09 raspberrypi2 systemd[1]: Failed to start containerd container runtime.
░░ Subject: A start job for unit containerd.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit containerd.service has finished with a failure.
░░
░░ The job identifier is 15282 and the job result is failed.
lines 7036-7072/7072 (END)
I tried to uninstall the docker components and reinstall, but I see the same issue.
I’m not sure if this is simply that a Pi v1 is not going to work with Docker, as Raspian Bullseye 32-bit is the underlying OS, I thought it would be fine.
Is there anything I’m missing?