February 18, 20179 yr I went to change a path in my sab docker and when I applied it shows this. https://dl.dropboxusercontent.com/u/1548652/Forums/unRAID/dockerProblems/Screen%20Shot%202017-02-18%20at%2011.32.23%20AM.png[/img] Now the unraid ui is unresponsive, but all dockers are still running fine except sab. This seems to be a similar problem to this thread. https://lime-technology.com/forum/index.php?topic=39510.0 I tried the docker kill and it just sits there and doesn't work so it seems like the only way to fix this is to stop the array from the command line. Is this still the proper way to do that? https://lime-technology.com/forum/index.php?topic=6255.0 It is from 7 years ago so I just want to make sure before proceeding.
February 18, 20179 yr Something's messed up in the docker.img where its unable to stop or remove the container. Probably best course of action is to change /config/docker.cfg on the flash drive and set DOCKER_ENABLED to be "no" Then reboot powerdown -r After its back alive, delete the docker.img and re-add all your apps via the Add Container (my* templates) or via CA's previous Apps section
February 18, 20179 yr Author Something's messed up in the docker.img where its unable to stop or remove the container. Probably best course of action is to change /config/docker.cfg on the flash drive and set DOCKER_ENABLED to be "no" Then reboot powerdown -r After its back alive, delete the docker.img and re-add all your apps via the Add Container (my* templates) or via CA's previous Apps section Do I not need to stop the array first before rebooting?
February 18, 20179 yr Something's messed up in the docker.img where its unable to stop or remove the container. Probably best course of action is to change /config/docker.cfg on the flash drive and set DOCKER_ENABLED to be "no" Then reboot powerdown -r After its back alive, delete the docker.img and re-add all your apps via the Add Container (my* templates) or via CA's previous Apps section Do I not need to stop the array first before rebooting? Powerdown will do it all
February 18, 20179 yr Author Something's messed up in the docker.img where its unable to stop or remove the container. Probably best course of action is to change /config/docker.cfg on the flash drive and set DOCKER_ENABLED to be "no" Then reboot powerdown -r After its back alive, delete the docker.img and re-add all your apps via the Add Container (my* templates) or via CA's previous Apps section Do I not need to stop the array first before rebooting? Powerdown will do it all Well its been like 10 minutes and the server hasn't shutdown yet, all the dockers are still working. Time for a hard power down?
February 18, 20179 yr Something's messed up in the docker.img where its unable to stop or remove the container. Probably best course of action is to change /config/docker.cfg on the flash drive and set DOCKER_ENABLED to be "no" Then reboot powerdown -r After its back alive, delete the docker.img and re-add all your apps via the Add Container (my* templates) or via CA's previous Apps section Do I not need to stop the array first before rebooting? Powerdown will do it all Well its been like 10 minutes and the server hasn't shutdown yet, all the dockers are still working. Time for a hard power down? pretty much
Archived
This topic is now archived and is closed to further replies.