Good morning.

with the new updates 7.2.7 and 7.3.0 i got the same problem.

Many of my Docker Containers are missing after update... if i interpret it correctly, my custom user bridge "proxy-net" (the custom user bridge from many SWAG user-guides), is missing and not created with the new updates.

Diagnostic is attached.

unraid-1-diagnostics-20260522-0639.zip

Try recreating the Docker folder as a Docker image, and with a different storage driver, XFS

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

here is also a diagnostic from 7.3.0 just for the case.unraid-1-diagnostics-20260522-0834.zip

45 minutes ago, JorgeB said:

Try recreating the Docker folder as a Docker image, and with a different storage driver, XFS

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

dont get me wrong... but this doesn't sound really like addressing the problem. i can went back to 7.2.6 without any problem, so the "image" isn't corrupt.

Edited May 22May 22 by sonic6

47 minutes ago, JorgeB said:

and with a different storage driver, XFS

also my cache, where the docker folder is located is on a btrfs cache... why should i use a different storage driver?

This appears to be related to the Docker engine upgrade, but it only affects a very small number of users, and AFAIK, the issue was resolved for all after changing the Docker storage driver.

3 hours ago, sonic6 said:

also my cache, where the docker folder is located is on a btrfs cache... why should i use a different storage driver?

If you are using a docker .img file then the format inside that image is independent of the format of the drive on which it is stored.

@JorgeB thank you for clarification.

1 hour ago, itimpi said:

If you are using a docker .img file then the format inside that image is independent of the format of the drive on which it is stored.

i dont use the docker image, i am using Docker directory... so does the driver change had any impact, when i am using Docker directory?

Edited May 22May 22 by sonic6

i am not 100% sure, but if i am remeber right, i was told, that the docker storage driver option, dosen't had any impact to my setup, becaus i am using docker directory, instead of the docker image.

so the problem must be somewhere else...

1 hour ago, sonic6 said:

so does the driver change had any impact, when i am using Docker directory?

Yep, you are using the btrfs native driver with a folder, hence my suggestion to try with an XFS docker image

so, sorry for that delay:

On 5/22/2026 at 3:55 PM, JorgeB said:

Yep, you are using the btrfs native driver with a folder, hence my suggestion to try with an XFS docker image

i woulnd't use docker image... don't see any point to switch, when docker "Docker directory" is an official feature.

but i followed your suggestion, deleted my docker directory and started with a new one.

to keep my custom networks i just saved /mnt/user/system/docker/container/network/files/local-kv.db and moved it back after the new directory was created.

@JorgeB @itimpi thank you both for you help.

If you created a new Docker folder, I recommend using overlay2 as the storage driver; it tends to be more reliable than btrfs with Docker.