As posted here (https://forums.docker.com/t/docker-daemon-failed-to-start/116007) and here (https://www.reddit.com/r/artixlinux/comments/xf7n77/docker_daemon_fails_to_start_after_reboots/)...
I use an Artix OpenRC VM to run Docker containers (installed from stable ISO). After every shutdown, I have to reinstall Docker (uninstall Docker, restart the VM, install Docker) to get it working again. I've also had random times where ConnMan's tray icon looks like an unplugged cable (no network connection). I usually have to restart connman daemon to get my network config working again. It's been this way for a while now. Newer ISO builds don't appear to have this issue, and no one I've worked with has been able to replicate this. During one of the troubleshooting sessions (working with someone who knows more about Linux than me), we ended up checking to see if overlayfs wasn't loading in time. But, that ended up not being the case. The current theory is that Docker is attempting to start before networking (connman) is ready. However, any attempts to make Docker delay or wait until connman (eth0) is ready have ended in failure. I'm not sure why this issue is present, but I would like to forgo having to reinstall Docker after shutdowns and reboots. Has anyone else encountered this? Is this something that can be resolved?
I installed Artix from artix-xfce-openrc-20220713-x86_64.iso. I ran
pacman -Syu
and updated, rebooted, and installed docker with pacman.
I've never used openrc before, but learned that running
rc-service -l
should list available services. Docker isn't listed, but I believe it should be.
I was able to start the docker daemon by running
sudo dockerd
.
So basically, I'm reporting a suspected bug in this possibly-related thread.
Other than that, Artix seems cool so far. Trying it in a VM. Just heard about it earlier tonight (end intro).
Did you install
docker-openrc along with the
docker package?
That worked! Thanks!
I may have to try a clean-install at some point in the future if no solution is in sight...