June 9, 20242 yr So for some reason, docker is failing to start. I get the following errors: Jun 8 21:48:55 Alexandria unraid-api[14239]: ✔️ UNRAID API started successfully! Jun 8 21:48:55 Alexandria unraid-api[14239]: ⚠️ Caught exception: connect ECONNREFUSED /var/run/docker.sock Jun 8 21:48:55 Alexandria unraid-api[14239]: ⚠️ UNRAID API crashed with exit code 1 I have wiped my cache drive, reformatted it and rebooted but still no luck. Any suggestions? alexandria-diagnostics-20240608-2139.zip
June 9, 20242 yr Community Expert * disable the docker service * re-enable the docker service This should create the needed subdirectories and re-download libvirt cross your fingers 😁
June 9, 20242 yr Author 11 minutes ago, MAM59 said: * disable the docker service * re-enable the docker service This should create the needed subdirectories and re-download libvirt cross your fingers 😁 Sadly this was the first thing I tried, along with reboots.
June 9, 20242 yr Community Expert 4 hours ago, vonarstonehelm said: Sadly this was the first thing I tried, along with reboots. Too bad. I assume you have entered a valid path to appdata and docker and use ipvlan with bridgeing ?
June 9, 20242 yr Community Expert Solution Try recreating the docker image: https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks
June 9, 20242 yr Community Expert As an aside, why do you have 150GB allocated to the docker.img file? The default of 20GB is enough for most people as when properly set up this only holds the binaries for docker containers. If you increased the size because you run out of space it is typically because there is a path not mapped correctly for at least one container so files are being written internally to the image rather than to a location on the host.
June 9, 20242 yr Author 1 hour ago, JorgeB said: Try recreating the docker image: https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks Thank you! This did the trick. Now I am curious what caused it to begin with
June 9, 20242 yr Author 1 hour ago, itimpi said: As an aside, why do you have 150GB allocated to the docker.img file? The default of 20GB is enough for most people as when properly set up this only holds the binaries for docker containers. If you increased the size because you run out of space it is typically because there is a path not mapped correctly for at least one container so files are being written internally to the image rather than to a location on the host. Is there an easy way to figure out what caused this issue? I did increase it because it was filling up, but I am not sure what went wrong or where
June 9, 20242 yr Community Expert 3 hours ago, vonarstonehelm said: Is there an easy way to figure out what caused this issue? Check the mappings for all container paths, that's the most common reason for this.
June 9, 20242 yr Container Size on the docker tab will show you where the space is being taken up after you see the size utilized growing in the dashboard for docker
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.