mwoods98 Posted January 30, 2023 Share Posted January 30, 2023 I was doing some regular updating this morning and I stumbled upon this error this morning. Normally I check to see what needed to be updated and then take care of it. I was trying to get a docker updated when I got this message. Diags also included. Thanks in advance. tower-diagnostics-20230130-1043.zip Quote Link to comment
Solution trurl Posted January 30, 2023 Solution Share Posted January 30, 2023 Corrupt docker.img, Delete, recreate, reinstall previous apps https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications Quote Link to comment
mwoods98 Posted January 30, 2023 Author Share Posted January 30, 2023 11 minutes ago, trurl said: Corrupt docker.img, Delete, recreate, reinstall previous apps https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications Thanks, this looks easy enough but I want to make sure I take my time and re do this with off the docker images I have installed so I won't lose anything. Thanks for this. Quote Link to comment
trurl Posted January 30, 2023 Share Posted January 30, 2023 Your docker.img is larger than is usually necessary. Have you had problems filling it? Quote Link to comment
mwoods98 Posted January 30, 2023 Author Share Posted January 30, 2023 Just now, trurl said: Your docker.img is larger than is usually necessary. Have you had problems filling it? No, I recently expanded it when it was getting close to running out of space. Quote Link to comment
trurl Posted January 30, 2023 Share Posted January 30, 2023 Still larger than usually necessary and it shouldn't be growing. The usual cause of filling docker.img is an application writing to a path that isn't mapped. Quote Link to comment
mwoods98 Posted January 31, 2023 Author Share Posted January 31, 2023 Update: I did what was suggested, turned off docker, deleted the image restarted docker and reinstalled the images using the community apps way. (mostly followed Space Invaders guide he has on you tube) However it got down to containers that stated with 'Y' and seemed to get stuck. I'm going to let it run overnight but it doesn't appear to be moving. If it hasn't moved by the AM, any suggestions? Quote Link to comment
mwoods98 Posted January 31, 2023 Author Share Posted January 31, 2023 12 minutes ago, mwoods98 said: Update: I did what was suggested, turned off docker, deleted the image restarted docker and reinstalled the images using the community apps way. (mostly followed Space Invaders guide he has on you tube) However it got down to containers that stated with 'Y' and seemed to get stuck. I'm going to let it run overnight but it doesn't appear to be moving. If it hasn't moved by the AM, any suggestions? Also tower-diagnostics-20230130-2321.zip Quote Link to comment
klippertyk Posted March 4 Share Posted March 4 I'm having the same issue - my docker.img is 42.9gb. I've had this error for a while actually and only got around to invesitgating the problem recently. Can I please ask - are there updated links for your articles above? They appear to be out of date. My primary concern is losing my config, my containers took hours to setup - i'm curious as to what is writing to the docker.img though - any tips to investigate that? Quote Link to comment
klippertyk Posted March 4 Share Posted March 4 for others... https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications I am new to this, so any advice apprciated - pre-req checks or gotchas would be useful. Quote Link to comment
napalmyourmom Posted May 4 Share Posted May 4 I suddenly am unable to Unable to Update, Modify, or Delete Docker containers. No recent system updates/changes to correlate it with. "Error response from daemon: Conflict. The container name "movies" is already in use by container "7b9c21616f4b5619fdb54690c9ae378067f7d6e2815e0a0e71123d2bc6ab38b2". You have to remove (or rename) that container to be able to reuse that name." The container ID correlates with the existing container that I am trying to update. I see no orphaned containers. I have found other threads suggesting to delete the docker.img and recreate all containers. Before doing so, I was hoping you brilliant ladies and gentlemen could look at my diagnostics to see if there is another route to take. Diagnostics attached. tower-diagnostics-20240502-2218.zip Quote Link to comment
trurl Posted May 6 Share Posted May 6 Looks like docker.img corruption. Why do you have 100G docker.img? Have you had problems filling it? Default 20G is often more than enough. The usual cause of filling docker.img is an application writing to a path that isn't mapped. Also, your system share has files on the array. SInce docker.cfg specifies cache, maybe libvirt.img is on the array unless you have an old docker.img on the array. Dynamix File Manager plugin might be the easiest way to clean that up. Nothing can move or delete open files so you have to disable Docker and/or VM Manager before you could work with those. To fix the docker.img you will have to delete, recreate, reinstall containers. Looks like 30G should be enough for your docker.img https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications Quote Link to comment
Recommended Posts
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.