I have some containers created and built with
docker-compose -f <file> up --build with
restart: always. These containers are set to start with the system, however one or two containers will randomly fail to start and I’ve no idea why.
I’m running an Ubuntu Server 20.04 VM with
Docker version 20.10.5, build 55c4c88. Viewing the Docker logs with
journalctl -fu docker.service I can see a reference to one of the containers that failed to start:
level=error msg="stream copy error: reading from a closed fifo" level=error msg="stream copy error: reading from a closed fifo" level=error msg="8d36ccc6189e54e27c633227e247f3c69462340cba2baa2b47eec7a6edc33192 cleanup: failed to delete container from containerd: no such container" level=error msg="failed to start container" container=8d36ccc6189e54e27c633227e247f3c69462340cba2baa2b47eec7a6edc33192 error="OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused:: unknown"
But even this error is not very helpful! Could this be related to a recent version of Docker? It seems to be happening after I ran an
apt update and
apt upgrade on the system.
I’m able to run the containers manually with
docker container start <id> without any problems.
When I restart the VM the containers all start up fine, when I restart the host the containers all start up fine, when I shutdown, turn off at the wall, and power everything back on that’s when my containers randomly don’t start properly.
What could be causing this problem and how could I fix it?
Thanks in advance!