Squid Posted December 20, 2015 Share Posted December 20, 2015 Was trying to add a container, that sort of got stuck doing nothing. And I couldn't even access web ui. So I rebooted from command (have powerdown script installed). After reboot, docker tab went missing. So I followed the steps in this thread, in that I disabled docker from settings, and re enabled using a larger docker image size. Now all except 2 of my docker containers are showing as orphaned! How to salvage the situation? While it got "stuck", the container was trying to autoupdate. Net result is that the docker.img wound up getting corrupted. Either delete docker.img, or (since it looks like its working ok on the 2 images) delete those 2 orphaned images, then re-add the containers using the my* templates, and you'll be back up and running the same as before Quote Link to comment
extremeaudio Posted December 20, 2015 Share Posted December 20, 2015 Sounds reasonable. Will try that and post back. Thank you. BTW, these my-templates are a boon for jumpy fellas like me! Quote Link to comment
extremeaudio Posted July 27, 2016 Share Posted July 27, 2016 Docker tab went missing again. Deleted the docker image completely. Created a new larger one. Started adding "my" dockers one by one. First one downloaded a lot of stuff and added fine. Second one gave a message like "already exists" and got over in a hurry and gave the message "command successfully finished". But the docker is stopped on the dockers page and I can't get it to start. Quote Link to comment
Squid Posted July 27, 2016 Share Posted July 27, 2016 Docker tab went missing again. Deleted the docker image completely. Created a new larger one. Started adding "my" dockers one by one. First one downloaded a lot of stuff and added fine. Second one gave a message like "already exists" and got over in a hurry and gave the message "command successfully finished". But the docker is stopped on the dockers page and I can't get it to start. unRaid 6.1.x has a nasty habit of saying command finished successfully when in actuality there is an error message above it. You really have to post the screen shot of that, and possibly the diagnostics Quote Link to comment
extremeaudio Posted July 27, 2016 Share Posted July 27, 2016 Never mind, I went to the cache share and saw that it had not created a docker.img at all in it. So I created it again and it works now. Strange that I even got to the point where the docker tab existed and it let me install some "ghost" containers. Quote Link to comment
RobJ Posted September 7, 2016 Share Posted September 7, 2016 I am strongly considering moving this thread to Docker support (Docker Engine), because it doesn't really fit here, any more. Any comments or objections? Quote Link to comment
trurl Posted September 7, 2016 Share Posted September 7, 2016 I am strongly considering moving this thread to Docker support (Docker Engine), because it doesn't really fit here, any more. Any comments or objections? Certainly never clear there was a defect, it was for an old beta, and the followup posts seemed to go off in different directions. Whether it should be moved or just marked solved and locked I don't know. Quote Link to comment
RobJ Posted September 7, 2016 Share Posted September 7, 2016 It was tempting (to mark it solved and locked), but at least one user is still posting, so I'm moving it to Support. 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.