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.

Why does Unraid randomly decide to delete my docker containers when changing their parameters?

Featured Replies

Hi, I'm new to Unraid so perhaps I'm missing something here. But I've noticed some extremely strange and frustrating behaviour. Its fairly easy to replicate. Just install a container like e.g. Sonarr, SABnzbd, EmbyServer etc (basically anything), then modify its parameters (e.g. delete some var variables or add some path variables etc) to customise the container to your requirements, then hit Apply and...poof! Your docker container evaporates into the nether, never to be seen again.


It doesn't happen all the time. So sometimes you can change the dockers parameters and apply and it works (i.e. the container gets updated and reboots correctly). Other times though...poof! Gone. Then you have to re-install it again.

This is on a brand new fresh install of 7.3.2 btw.

  • Community Expert

Because you entered something wrong and the container fails to build.

Can just hit back and correct, or go to apps->previous apps, select reinstall and correct before applying.

  • Community Expert

You can get back to the template by clicking the "Add Container" button on the docker page, and then selecting the template from the drop down menu.

But yes you are entering something incorrectly thus it cannot build/run and gets orphaned.

You should also tick the "advanced view" toggle on the docker page and make sure you dont have a bunch of orphaned containers taking up space. If you do, click on them and remove them.

Edited by MowMdown

  • Author
9 minutes ago, MowMdown said:


But yes you are entering something incorrectly thus it cannot build/run and gets orphaned.

I assume I must have I guess. But I honestly don't know what because I made the exact same changes each time and sometimes they would result in the container going poof and sometimes they didn't.

11 minutes ago, MowMdown said:

You should also tick the "advanced view" toggle on the docker page and make sure you dont have a bunch of orphaned containers taking up space. If you do, click on them and remove them.

Thanks for the tip. I did that too. Although I was also using the appdata cleanup plus plugin to scan for orphaned entries as well. That being said, it didn't seem to pickup all the orphaned containers. Only the advanced view you mentioned did.

  • Community Expert
30 minutes ago, DCCXVIII said:

But I honestly don't know what because I made the exact same changes each time and sometimes they would result in the container going poof and sometimes they didn't.

When it fails it'll tell you why in the output, look at it...

33 minutes ago, DCCXVIII said:

orphaned containers

They are orphaned images, not containers, i.e. images that have been downloaded but are not currently being used by any container.

34 minutes ago, DCCXVIII said:

appdata cleanup plus plugin to scan for orphaned entries as well

That only cares about the appdata folders, not containers or images.

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.