Hello,

For some time now I am experiencing a weird behavior with my containers. I'm running on 7.3.1 but the problem existet also on 7.3.0 or even before. And I'm using FolderView3.

The Problem: I have now experienced lots of containers disapearing and some times reapearing again. Most of the time after a reboot I get missing containers and some orphaned ones. Also some times after a "bulk"-Update in Folderview3 (Update all) I get orphaned images afterwards.

Notice in the sreenshot that it shows 4/6 started, but it shows only 4. The missing ones will probably be Immich-redis and the second one I'm not to shure right now which one it should be.

Also notice the docker folder showing 3/5 started, but only 3 container showed. One of the missing ones will be this one:

And there are more orphans by the way:

Whai I wxperience now for the first time is that the first 2 of them don't even show the name anymore, so I have no idea which ones are missing.

I can now delete the orphans and reinstall them, but I allways get an error:

docker: Error response from daemon: Conflict. The container name "/PortainerCE" is already in use by container "5d1124ae90bacea5f5725436caa80045b1e40cb755179f1ead0639029dfde56c". You have to remove (or rename) that container to be able to reuse that name.

Run 'docker run --help' for more information

The command failed.

I can now rename and install it as PortainerCE1, but then it is not in the correct Folder anymore and so on...

And sometimes a "lost" Container magicly reapears again after a restart, so it hapened with Luckybackup, of which I duddenly had 2, Luckibackup and Luckibackup1 (but normally I get more orphans after a reboot).

Any idea what is going wrong and how I can solve it? That is getting a little annoying...

unraid-diagnostics-20260623-2143.zip

Please be aware that errors concerning Ip-Adresses (especially 192.168.1.x and 10.10.10.x ) have to do with the fact that I had to change from the 192. -net to the 10. -net. last week/weekend, so ther may still be problems there I have to figure out, but the here decribed problems existed way before but have become more apparently because I had to restart the Unraid server a few times. Btw, for me no signs of an unclean shutdown or reboot so far...

Thank you

Docker folder with native zfs driver is not recommended and known to have multiple issues, I would recommend recreating that as a docker image, even other docker folders can have strange issues in my experience, but if you prefer to keep the folder, recreate it using the overlay2 driver.

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-file

Then:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applications

Also see below if you have any custom docker networks:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks