Hi,

Last week (03-30) I had an error where Docker failed to start.

I have attached the diagnostics from that date.

I tried to fix it myself and decided I would delete the docker.img file and add them all back via the Community Apps Previous Apps feature which was a huge pain since I had a ton of containers installed.

Today, I decided to reboot he server and when it came up, it shows "No Docker containers installed". So I first increased the image size and when that didn't work, I pulled the diagnostics and pasted it here.

Can anyone tell what is happening? I'm hoping to not have to install everything again and even if I do have to, I am worried there is a bigger issue that is causingthis to happen.

Thanks!

tower-diagnostics-20260330-1203.zip

tower-diagnostics-20260402-1644.zip

Edited April 2Apr 2 by RevelRob
Wrong file uploaded

There's a problem with this path: /mnt/user/real-debrid

Make sure you are not creating anything in /mnt/user, that is reserved.

To expand on the path issue: /mnt/user in Unraid is a FUSE union mount that merges all your array and pool shares into a single namespace. Creating directories directly under /mnt/user (like /mnt/user/real-debrid) instead of inside a proper share breaks things because those directories exist only in the FUSE layer and disappear or cause conflicts when the array restarts.

The fix: create a proper share through the Unraid WebGUI (Shares > Add Share), for example "real-debrid", and then reference it as /mnt/user/real-debrid in your Docker container path. The difference is subtle but important: a proper share has backing storage on a disk or pool, while a bare directory under /mnt/user is just a phantom.

For the Docker containers disappearing after reboot, the docker.img file is likely being recreated empty on each boot. Check Settings > Docker > Docker vDisk Location and make sure it points to a cache pool or a specific disk path, not to /mnt/user. If the Docker image sits on the array and the array takes too long to start, Docker gives up and creates a fresh empty image.

After fixing the path, you can reinstall containers from Community Apps > Previous Apps. To avoid this in the future, keep regular backups of your Docker template configurations with the CA Backup plugin. It saves all your container configs so reinstallation is just a click.