Hi,

I've been trying to update to 7.3.4 from 7.2.4 last night, but after the update, half of my docker containers were deleted, resulting with orphaned images. I had to revert back to 7.2.4 for the time being. Is there a way to prevent this behaviour ?

Thank you for your help.

Please post the diagnostics

Thank you, here it is. Diagnostics after the update.

monalisa-diagnostics-20261023-1209.zip

This doesn't appear to have been caused by the update itself, but by the RAM-DISK-Dockerlog plugin. Your appdata and container templates should be fine, so everything can be recovered.

The plugin keeps Docker's container information on a RAM disk and keeps a copy in appdata/containers_backup. On 7.3.4 Docker loaded an old copy of that information. That is why some current containers are missing (their images now show as orphaned), the old entries fail with "RWLayer ... is unexpectedly nil", and older containers like overseerr and paperless-ng came back. Another user had the same problem on 7.3.4 with the latest plugin version (2026.10.09a), so updating the plugin is not enough. For now I recommend removing it.

If you are back on 7.2.4 and your containers work there:

1. Remove the RAM-DISK-Dockerlog plugin and reboot.

2. Delete the folder /mnt/cache/appdata/containers_backup.

3. Update to 7.3.4.

If you are on 7.3.4 with missing containers (or if they are also missing after you revert):

1. Remove the RAM-DISK-Dockerlog plugin and reboot.

2. Go to Settings → Docker, set Enable Docker to No, and delete the Docker vDisk.

3. Delete the folder /mnt/cache/appdata/containers_backup.

4. Create a new Docker vDisk (keep it as a btrfs docker.img in the system share) and enable Docker.

5. Recreate your user-defined Docker networks before the next step, for example media and privatedb_isolated, because they are stored inside the vDisk. Also check that br0.30 and br0.40 are available.

6. Go to Apps → Previous Apps, select your containers, and install them. They use the same templates and appdata, so your settings and data are kept. Containers deployed outside the Docker page, for example with Portainer or compose, must be deployed again from their own definitions.

Yes I had seen your previous answer. So I tried the following procedure :

1) Downgrade to 7.2.4. All containers are present and working.

2) Remove the RAM-DISK-Dockerlog plugin.

3) Remove the ram disk section added in /boot/config/go~ and reboot.

4) Delete the folder /mnt/cache/appdata/containers_backup.

5) Update to 7.3.4.

But unfortunately, containers are still missing...

monalisa-diagnostics-20261023-1417.zip

Had the same issue, you can do a

docker container rm 55e202a76 ac3d0872d 67005eb58 ed2b8d87b a5997ca85 1614f6f71 fc47760df 4d58b3096 89e0a6c12 f2a43dfcf 7625586fc e1b73a6a4 f5740dce3 af43ac462 4e29b8bb0 0f0f588e2 caaa01b20 85d86490f be7eb8b2b 6656e56a8 a50313426 1de8a9af6 55a83fe73 80bfdd8f2 9f2accb82 ed47915f0 b180f0059 86d7b24d4 c861931f0 

(the whole list of containers that have the RWLayer error)

then reinstall those from apps->previous apps. Will be a lot faster than recreating the whole docker image.

Following my investigations, something is weird : the missing containers are not the same between each reboot in 7.3.4. Sometimes Plex starts, the next reboot it is an orphaned image.

The plugin is gone now, but it left old container entries inside the Docker vDisk itself. Deleting containers_backup does not remove those. 7.2.4 hides them, which is why everything looks fine there. On 7.3.4 they are loaded again, so old versions of some containers (for example overseerr and paperless-ng) come back. Because they use the same names as the current containers, which ones show up can change after each reboot.

Do this on 7.3.4. These entries are hidden on 7.2.4, so they cannot be removed there.

1. Remove the broken entries, as Kilrah suggested. You can do it in one command:

grep -o 'RWLayer of container [0-9a-f]*' /var/log/syslog | awk '{print $4}' | sort -u | xargs docker container rm

2. Go to Settings → Docker, set Enable Docker to No, then set it back to Yes.

3. On the Docker page, remove any old containers you no longer use, for example overseerr and paperless-ng, if they still show up.

4. Reinstall any missing containers from Apps → Previous Apps. They use the same templates and appdata, so your settings and data are kept.

5. Reboot once and check that the same set of containers is there.

If anything is still wrong after that, delete the Docker vDisk and recreate it as I described earlier. That shoudl clear everything for sure.

Containers get orphaned when a container template variable is no longer valid.

You will need to investigate the templates and make sure everything is entered correctly and when you hit save the docker run output says success and not failed.

So it did the trick. I removed the old entries (I had to do it multiple times..) and added back four missing containers, after a reboot some other container went missing. Each reboot presented new faulty containers... I followed your procedure as long as orphan images appeared, it seems okay now! Thank you for your help.

Edited 13 hours ago13 hr by potjoe