September 26, 20169 yr I just updated from unRAID 6.1.9 to unRAID 6.2 and my docker service doesn't start. Here is the error in the log file: --- Code: ---Sep 25 18:21:34 Tower emhttp: shcmd (233): /etc/rc.d/rc.docker start |& logger Sep 25 18:21:35 Tower root: starting docker ... Sep 25 18:21:36 Tower emhttp: shcmd (246): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/cache/docker.img' /var/lib/docker 10 |& logger Sep 25 18:21:36 Tower root: /mnt/cache/docker.img is in-use, cannot mount Sep 25 18:21:36 Tower emhttp: shcmd: shcmd (246): exit status: 1
September 26, 20169 yr I just updated from unRAID 6.1.9 to unRAID 6.2 and my docker service doesn't start. Here is the error in the log file: --- Code: ---Sep 25 18:21:34 Tower emhttp: shcmd (233): /etc/rc.d/rc.docker start |& logger Sep 25 18:21:35 Tower root: starting docker ... Sep 25 18:21:36 Tower emhttp: shcmd (246): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/cache/docker.img' /var/lib/docker 10 |& logger Sep 25 18:21:36 Tower root: /mnt/cache/docker.img is in-use, cannot mount Sep 25 18:21:36 Tower emhttp: shcmd: shcmd (246): exit status: 1 Try settings - docker settings, delete the image, then recreate it. Then hit CA's previous apps section and re-add your old apps. They will already be filled out with all your paths, etc and you won't notice a difference. Most users from 6.1.9 wind up having to do this anyways because dockerHub changed some things around and the image and apps half the time won't update without an error...
September 27, 20169 yr Author I posted a screenshot of my docker settings and I don't see an option to delete the image. Is there another way to delete the docker image?
September 27, 20169 yr Author Squid, the docker service is stopped. In fact, the array isn't even online. P.s. If I try to start the array, I still get start the docker service because of the error I posted above.
September 27, 20169 yr Community Expert Squid, the docker service is stopped. In fact, the array isn't even online. P.s. If I try to start the array, I still get start the docker service because of the error I posted above. In the screenshot you posted, change Enable Docker to No. Then it will let you delete.
October 21, 20169 yr Most users from 6.1.9 wind up having to do this anyways Aaaaand thanks to lime tech for the release notes advising my upgrade / patching is now a morning of recreating a heap of custom docker containers.
October 22, 20169 yr Most users from 6.1.9 wind up having to do this anyways Aaaaand thanks to lime tech for the release notes advising my upgrade / patching is now a morning of recreating a heap of custom docker containers. Your templates are saved, so it's not as much work as you think. Took me 10 minutes for over 20 containers. If however your changes are within the docker container itself, then yeah, you may have some work to do, which is why if you're going to do that you're better off pushing your custom images to the hub.
June 14, 20179 yr deleting the docker image file worked for me in the above scenario. upgraded from 6.0-ish to 6.3.5 and ran into this issue. Deleted image file and re added containers. Everything is back up and running as usual.
June 14, 20179 yr It is mentioned in the release notes that the Docker image file needs to be recreated due to changes in Docker itself. From unRAID 6.1 a newer version of Docker is being used. As CHBMB mentioned it takes very little time and effort afterwards to re-install the containers.
Archived
This topic is now archived and is closed to further replies.