January 29, 20251 yr I'm running Unraid 7.0.0 Recently had an issue with it seems my Docker.img was corrupted and had to do a deletion of the image and a reinstall of all my containers. I had forgotten to turn off some mover logging which filled up my sys log making my logging get stuck so I added some info to my go file to expand the log capacity a little bit. # Enlarge the LOG partition (because Dynamix System Stats needs at least 186Mb, default LOG is 128Mb) mount -o remount,size=384m /var/log Turned off the more verbose logging for Mover and rebooted. When it came back up everything started up seemingly fine except I no longer had any Docker containers. diagnostics attached. TIA Edit: I removed the additional parameters from the Go file just in case but it seems to have had zero effect. I double checked that the docker setting pointed to the correct location for the image and my appdata share looks to have all the container folders present. snuts-diagnostics-20250129-0921.zip Edited January 29, 20251 yr by DontWorryScro
January 29, 20251 yr Community Expert A new docker image was just created on boot, you can restore the apps from previous apps on CA.
January 29, 20251 yr Author Just now, JorgeB said: A new docker image was just created on boot, you can restore the apps from previous apps on CA. Do we know why a new docker image was created on boot? is it going to do this every time i reboot now? Is there some setting somewhere that I have overlooked that nuked my last docker image?
January 29, 20251 yr Community Expert 2 minutes ago, DontWorryScro said: Do we know why a new docker image was created on boot? It's only created if one doesn't exist on the set path.
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.