May 13May 13 Community Expert Just upgraded to 7.3.0 from 7.2.6. Many of my Docker containers didn't auto start and were missing on the docker page. Trying to re-add the container from template results in the following error:docker: Error response from daemon: Conflict. The container name "/redis" is already in use by container "55e3df3eac0373e6d7df884f1cae5b83246d05c80b9f8cc291e8546c5a31cf40". You have to remove (or rename) that container to be able to reuse that name.In an effort to mitigate I deleted docker.img using the toggle on the Docker settings page. I then had docker.img recreated. Now the containers that were launching post upgrade are getting the same error when trying to recreate from template. I have also restarted but continue to get the error. Diagnostics attached.tower-diagnostics-20260513-1213.zip Edited May 13May 13 by adammerkley
May 13May 13 Community Expert Solution Do you have the RAM-Disk for Docker logs plugin installed? if so try removing it temporarily
May 13May 13 Author Community Expert 10 minutes ago, Kilrah said:Do you have the RAM-Disk for Docker logs plugin installed? if so try removing it temporarilyI thought you were on to something but I've removed the plug-in and rebooted and am getting the same error
May 13May 13 Author Community Expert UPDATE: Removing Docker.img one more time, then restarting, then recreating Docker.img finally allowed my containers to launch. I'm certain @Kilrah was correct and the issue was with the RAM-Disk for Docker Logs plugin after all. Edited May 13May 13 by adammerkley
May 13May 13 Community Expert 16 minutes ago, adammerkley said:I'm certain @Kilrah was correct and the issue was with thr RAM-Disk for Docker Logs plugin after all.Delete the containers_backup folder in your appdata share, then you should be able to install it again.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.