March 1, 201610 yr So today I noticed that 2 of my dockers weren't running (after an update). I tried to start them manually, nothing. When I clicked on edit and saved it, without changing anything. An exact copy of the original docker installed, but it was running. I tried the obvious solution: deleting the non-running docker. And what happens still amazes me: I don't know for sure which of the 2 versions got deleted, but the one that stayed won't run. Bringing me back to the original problem and keeping the vicious circle going. I thought removing the remaining docker that won't run and do a clean install would work, but I get an error when I try and it fails. Problem is with 2 dockers: Plex and PlexPy.
March 2, 201610 yr Hey, Try this: Settings > Docker > Enable Docker: No terminal into you docker image location and rename it from docker.img to dockerold.img start docker again. the containers that no longer run will show at the bottom of the list as a grey icon, remove them
March 2, 201610 yr Author A reboot or a new docker image would probably fix this. What's the error? Screenshot from iPad is to big in file size, so I copied the error when I try to delete the single not running docker. Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker rm -f plexpy Error response from daemon: no such id: plexpy Error: failed to remove containers: [plexpy] The command failed. Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker rmi 57653d36475e Error response from daemon: Conflict, cannot delete 57653d36475e because the container d592495c50b5 is using it, use -f to force Error: failed to remove images: [57653d36475e] The command failed.
March 2, 201610 yr Author Hey, Try this: Settings > Docker > Enable Docker: No terminal into you docker image location and rename it from docker.img to dockerold.img start docker again. the containers that no longer run will show at the bottom of the list as a grey icon, remove them Wont that affect my other working dockers? Or will they keep working as before when done?
March 3, 201610 yr this will not affect your working apps under docker. if it does, we can change dockerold.img back to docker.img
March 3, 201610 yr Author this will not affect your working apps under docker. if it does, we can change dockerold.img back to docker.img When i did what you proposed, all my dockers disappeared. But when I reverted the dockerold.img back, all my dockers where back and the non working became "unavailable", and this time deleting them worked. Thanks!
March 3, 201610 yr Yeah, for future reference, what I was trying to say to do was to: 1) Delete(or rename) the docker image. This will leave you with 0 dockers installed. This isn't a problem, because you should have your container configs on your array or cache drive, and the flash has templates of all of your most recent settings/mappings for each docker container you have ever installed 2) Create a new docker image 3) Add each container back. Go to the template drop down and select the containers you want to reinstall from the [templates-user] list Each container should reinstall just fine, and will be pointed to the config files you were using before. They should all work again like nothing happened. I have done this several times now.
March 3, 201610 yr Author Yeah, for future reference, what I was trying to say to do was to: 1) Delete(or rename) the docker image. This will leave you with 0 dockers installed. This isn't a problem, because you should have your container configs on your array or cache drive, and the flash has templates of all of your most recent settings/mappings for each docker container you have ever installed 2) Create a new docker image 3) Add each container back. Go to the template drop down and select the containers you want to reinstall from the [templates-user] list Each container should reinstall just fine, and will be pointed to the config files you were using before. They should all work again like nothing happened. I have done this several times now. Oh ok, I didn't know they would be still saved as a template. Good to know, thanks
March 5, 201610 yr Glad it worked! smashingtool's way of doing it would have been the proper way. I completly forgot to add the part where you just re add you containers in and it uses the same config files as they are stored in your array and not in the docker.img
Archived
This topic is now archived and is closed to further replies.