May 20, 20251 yr So this past weekend I upgraded to 7.1.2 and working okay. I rebooted and when the server came back online I received a Docker Service Failed to Start message and none of the dockers are working. After reading some of the same problems of other with Docker failed to start, none of those really pertain to my situation. Drives are not full, cache drives, parity drives and all disks are good and healthy etc. Running Fix common problems does not yield any errors. I have included my diags and I see where the docker service does not start but no clue as to why it won't start. Vm's and shared drives working fine. server-diagnostics-20250519-1743.zip Edited May 20, 20251 yr by mbppg
May 20, 20251 yr Author Solution Well I feel a little dumb. I just looked at the Docker image size and it was pretty full. I upped it from 40 gig to 70 gig, Docker started right up. I guess that make sense that some docker updates where taking a while and some I had to manually update. At least I am relearning new things, getting old and I forget to look a little harder.
May 20, 20251 yr Community Expert So you have a LOT of docker containers installed (or particularly large ones). Just asking as commonest reason for running out of space in the docker.img file is having a container misconfigured so it is writing files internally to a location inside the docket.img file that should really be configured to be written externally to storage on the Unraid host.
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.