Hi, I shutdown my server yesterday and booted it up today just to find all, except 3, containers are gone. I can't really tell what went wrong.

 

Before I tried all my best to fix this:

I could start the 3 left container but they had errors, for example Redis:

Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf

 

If I tried to install a container that I previous had, following error occur:

failed to register layer: rename /var/lib/docker/image/btrfs/layerdb/tmp/write-set-794137828 /var/lib/docker/image/btrfs/layerdb/sha256/ba79b2c0127890636a791eb3ec3993cce08a50cc01fcb1513f0e8fbae41977af: file exists

But the folder /var/lib/docker/image/btrfs/layerdb/tmp/ is empty

If I tried to install a container I never had before, the same error was showed.

 

Diagnostics before I did something:

homelab-diagnostics-20241118-1057.zip

 

 

 

After I tried all my best to fix this:

If I try to install an App I previously had (even if I click remove from previous owned apps) the following error occurs now:

The same error occurs. But I can install container that I didn't had installed prior to my accident.

 

Diagnostics after I did something:

homelab-diagnostics-20241118-1224.zip

 

 

Things that had been done:

- docker system prune -a (removed all dockers that were left)

- i deleted the docker.img under system

- tried to restart

 

Everything else seems to work normal in Unraid, all addons, all tools etc just work fine.

I have made backups with the addon Appdata Backup. Could I just reset the whole docker thing on Unraid an just reinstall all container and than restore the backup?

 

I don't even know what caused the error, maybe some of you can help me, thank you!

 

Try recreating the docker as an image, not a folder.

Did you mean the "Docker data-root:" setting right here or did I misunderstand you?

Yes.

This did indeed work, thank you. But do you maybe have little background why my dockers died on me?

Difficult to say, there wasn't anything obvious logged, but docker folders are known to sometimes cause strange issues, recommend always using an image.