November 5, 20169 yr Hello, Today I've updated UNRAID to version 6.2.3.The update asked for a system reboot. After the reboot something strange happened. The DOCKER tab is missing. On Settings another strange thing. When I choose settings\docker I can see that docker is not started. It shows an error message: "Before you can start the Docker service for the first time, please specify an image file for Docker to install to. Once started, Docker will always automatically start after the array has been started." But there's no way to chose again the image file for docker (please see attached print screen). Can you please help? I've attached the diagnostics file. System Information Model: N/A M/B: - CPU: AMD Turion™ II Neo N54L Dual-Core @ 2200 HVM: Enabled IOMMU: Disabled Cache: 256 kB, 2048 kB Memory: 4 GB (max. installable capacity 8 GB) Network: eth0: 1000 Mb/s, full duplex, mtu 1500 Kernel: Linux 4.4.30-unRAID x86_64 OpenSSL: 1.0.2j bianiniserver-diagnostics-20161106-0036.zip
November 6, 20169 yr The system knows where your image is, but is having trouble with mounting it. It *believes* that its 100% full. Whether this is true or not, your only choice here is to hit advanced on the settings - docker settings screen. Set Use Docker to No, Delete the image if its there, then recreate it, and add the apps back in via CA's previous apps section.
November 6, 20169 yr Community Expert What version did you upgrade from? I think from 6.0.9 Did you read what the 6.2.3 announcement post said about upgrading 6.1 or earlier?
November 6, 20169 yr Author The system knows where your image is, but is having trouble with mounting it. It *believes* that its 100% full. Whether this is true or not, your only choice here is to hit advanced on the settings - docker settings screen. Set Use Docker to No, Delete the image if its there, then recreate it, and add the apps back in via CA's previous apps section. Thank you!! I'm now trying to reinstall all the containers and see if nothing was lost!
November 6, 20169 yr Author What version did you upgrade from? I think from 6.0.9 Did you read what the 6.2.3 announcement post said about upgrading 6.1 or earlier? Unfortunetly not. What did it said?
November 6, 20169 yr As listed in the release notes of 6.2.0, and linked from the release notes of every release since: http://lime-technology.com/forum/index.php?topic=51874.0
November 6, 20169 yr The release notes actually aren't very good at explaining the "one time procedure" in updating the docker apps. It explicitly forgets to mention that its an entirely automatic procedure with nothing to be done by the user at all. Since the docker.log is complaining about the image being full, my suggestion a few posts up is still the (only) way to go.
November 6, 20169 yr Author I've done what Squid told: I've renamed the old img file from docker and created a new one (this time with 30GB - hope that's enough). Meanwhile I've reinstalled all the containers needed and everything was ok. Today I updated to 6.2.4 and everything remains ok...
Archived
This topic is now archived and is closed to further replies.