Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

7.3.0 - Docker containers not starting, container name already in use error

Featured Replies

  • 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 by adammerkley

Solved by Kilrah

  • adammerkley changed the title to 7.3.0 - Docker containers not starting, container name already in use error
  • Community Expert
  • Solution

Do you have the RAM-Disk for Docker logs plugin installed? if so try removing it temporarily

  • Author
  • Community Expert
10 minutes ago, Kilrah said:

Do you have the RAM-Disk for Docker logs plugin installed? if so try removing it temporarily

I thought you were on to something but I've removed the plug-in and rebooted and am getting the same error (

  • 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 by adammerkley

  • 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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.