for a good while I have to increase my docker .img  several times I am currently up to 150GB. but what I have found is a lot of orphan images under the docker /advance with only IDS. so I delete a couple and my image size decreased .I can I find where they are coming from and a easy way to delete .thanks 

Orphan images come from when there is an error starting the container.

 

Delete them all, then on the UI, post up a screen shot of "Container Size".  There's something else wrong if you need to go to 150GB

is there a quick way to delete them all

7 minutes ago, Squid said:

There's something else wrong if you need to go to 150GB

 I always tell people if they need more than 20G they have something misconfigured. Making it larger will just make it take longer to fill, it won't fix anything.

 

There is a whole section (Docker Image Filling Up) of the Docker FAQ devoted to this:

 

https://forums.unraid.net/topic/57181-real-docker-faq/

 

6 minutes ago, kcmccombs said:

is there a quick way to delete them all

Yes and this is what you should do anyway.

 

Go to Settings - Docker, disable the docker service, delete the docker image, and recreate it at the more reasonable size of 20G.

 

You could then go to Apps and use the Previous Apps feature to reinstall them exactly as they were before, but in your case you don't want them exactly as before because they aren't setup correctly.

 

The likely cause of filling up an image as large as what you had is one or more applications writing a lot of data, such as downloads, to some path that isn't in one of the container volume mappings. You need to take a look at the settings within the apps themselves. Common mistakes are not using the same upper/lower case as in the volume mappings, or using a relative instead of an absolute path (must begin with / character).

 

 

 

ok thanks 

But post the screenshot I asked for first

Sent via telekinesis

2 minutes ago, kcmccombs said:

ok thanks 

also  if I have something misconfigured do I need to reinstall unraid and start over just keep my data sets and parity intact.

3 minutes ago, Squid said:

But post the screenshot I asked for first

Sent via telekinesis
 

is there a fast way to delete them at once

Just now, kcmccombs said:

do I need to reinstall unraid

No. Unraid does a clean install of itself each time you boot.

 

The Unraid OS is in RAM. When you boot, the OS is unpacked fresh from the archives on flash into RAM, then it applies any settings you have made. It is the settings you need to fix, the OS is fine.

 

The only time it ever makes sense to reinstall to the flash is when the flash fails for some reason.

2 minutes ago, kcmccombs said:

is there a fast way to delete them at once

I already answered this

12 minutes ago, trurl said:

Go to Settings - Docker, disable the docker service, delete the docker image, and recreate it at the more reasonable size of 20G.

 

6 minutes ago, Squid said:

But post the screenshot I asked for first

okay got it done.

You didn't do this

13 minutes ago, Squid said:

But post the screenshot I asked for first

and now it's too late

The screenshot Squid asked for might have given some clue which docker(s) was the (main) culprit. You will just have to work through each of them, which you probably needed to anyway.

i guess i misunderstood what he want a pick of where is this at

On the Dockers page, a button at lower right says Container Size.

ok. is there away to find out what size each docker should be .thanks

7 minutes ago, kcmccombs said:

ok. is there away to find out what size each docker should be .thanks

I'm pretty sure nobody has ever compiled a list of approximately how large each docker will typically be. There are very many available dockers.

 

If you set them up correctly, you shouldn't have to worry about it.

 

Which dockers are you interested in?

i think plex or nzbsabd was the issue these are the ones i need to make sure they right

When you look at that popup, Container Size won't particularly change.  It's the "Writable Size", and "Log Size"  You'll know what's wrong just by looking at it.

ok thanks

6 minutes ago, kcmccombs said:

i think plex or nzbsabd was the issue these are the ones i need to make sure they right

Plex doesn't write enough data to fill 150G. Well, maybe it would if you used the DVR feature.

 

The other one you mentioned sounds like a downloading application, but I don't think you got the name exactly right. That would be a good suspect, but if you have any others involved with post-processing your downloads, for example, they would also be something to look at.

what about plex trans coding

Just now, kcmccombs said:

what about plex trans coding

The default transcoding would go to a subfolder in your plex library, which would be in appdata. If you aren't using the default then you could easily make some mistake like I mentioned and that would also fill docker image.

 

Every application must only write to paths that are in mapped volumes, it's as simple as that. And you must get the paths exactly right.