Docker container list contains unwanted versions

[Raidersan]

I am enjoying fantastic containers for Plex, Deluge, Crashplan but something is bothering me trying to manage them. My list of containers (6 genuine containers) is filled with what I assume is Github versions of the original containers. They are all marked as not available but it does mean I need to scroll through 3 pages of containers to find the ones I run. Is this a configuration option I have missed or is there something I can do to avoid this?

Many thanks!

[CHBMB]

Not quite with you, can you post a screenshot.  I think I know what you're alluding to, but want to be sure before I tell you to nuke stuff.. 

[Raidersan]

Here it is. I can delete them but when I do the list seem to be growing back

[CHBMB]

Ok, that's weird, never seen that before, so are you saying each time you upgrade a container you get an old version left behind?

[BRiT]

Delete the docker.img and start adding bacck from the My-templates the ones you use.

[CHBMB]

Delete the docker.img and start adding bacck from the My-templates the ones you use.

 

Any idea why it happened Brit?

[Raidersan]

Delete the docker.img and start adding bacck from the My-templates the ones you use.

 

What will happen to my configurations?

[scottc]

Delete the docker.img and start adding bacck from the My-templates the ones you use.

 

What will happen to my configurations?

 

As long as your container mappings are correct you will not loose any of your configurations

[Squid]

Here it is. I can delete them but when I do the list seem to be growing back

Those are orphaned images (with the interesting names chosen by docker itself)...  The only time I've seen them (since the original days of unRaid and docker before dockerMan) was if I interrupt a download / install of a container.

 

If that's not happening, then I'd agree that toasting your image file is the best way forward.

 

[Raidersan]

I will do this but I am trying to understand what is going on, and I cannot find an explanation on this in the FAQ and tutorial sections.

When I select an image, let's say needo:Plex, am I supposed to then re-select the equivalent under "My user-defined templates", such as my-PlexMediaServer?

Is that cutting me off any future updates?

Why the need for the user-defined version of the container?

 

I am sorry if I missed this from the docs but it was not obvious to me if it is explained somewhere in the doc

[BRiT]

The only thing the My-itemname has is YOUR SETTINGS that you last used. That is the only difference.

[Raidersan]

Ok that is clear, thanks.

Will it still get the update from the original container?

[BRiT]

Yes.

[Raidersan]

One last question! Did I do something wrong or has something gone wrong with my image? If not, why are they not more people with the same issue?

Many thanks!

[Squid]

Easiest thing to blame is that your docker image filled up to 100%.  What size are you using?

[Raidersan]

It used to be 5Gb, I re-created it a month ago to 20Gb, it is now reporting 7Gb used.

That is why I was surprised I would need to re-create it again, having done this not long ago and those strange versions appearing pretty much from the beginning.

So I understand this is not normal, but would a normal behaviour still warrant the usage of the "my-xxx-container" instead of the original? If not, when/why would you use those my-xxx-containers? Are those containers documented anywhere? I could not find anything on them

[CHBMB]

 

The "My" containers are actually just templates that your machine has saved to your flash with your folder and port mappings saved.  So yes, use them, unless you have a burning desire to make your life more difficult.