Are you automatically updating dockers? If so try disabling the automatic update of your dockers then you can manually update as necessary and catch the output to see if orphans are created without being deleted.

3 hours ago, trurl said:

Are you automatically updating dockers? If so try disabling the automatic update of your dockers then you can manually update as necessary and catch the output to see if orphans are created without being deleted.

yes - i am automatically updating them using the autoupdate plugin. I will disable all of those and post a reply once i have a chance to test with a new version release. I'm going to assume that orphans would be created when i hit "apply update"?

5 minutes ago, helpermonkey said:

orphans would be created when i hit "apply update"?

When you update or edit a container, it gets recreated. The old container becomes an orphan, but normally it gets deleted automatically.

1 minute ago, trurl said:

When you update or edit a container, it gets recreated. The old container becomes an orphan, but normally it gets deleted automatically.

gotcha - thanks much. more to follow.

19 hours ago, trurl said:

When you update or edit a container, it gets recreated. The old container becomes an orphan, but normally it gets deleted automatically.

 

okay so i disabled auto-update as detailed here:

 

 

And there are two orphaned images and both Jackett & Plex have updates ready to apply ...

 

 

 

Did those orphans already exist before you disabled autoupdate?

7 hours ago, trurl said:

Did those orphans already exist before you disabled autoupdate?

nope.

Have you tried manually updating any dockers? Be sure to capture the output.

 

Have you done memtest?

4 hours ago, trurl said:

Have you tried manually updating any dockers? Be sure to capture the output.

 

Have you done memtest?

I have not applied the updates yet - should i do that before or after deleting the orphans? When you say capture the output i presume you mean the dockerrun - if not let me know what that is. I have not run memtest - my understanding is that you have to do it at startup but I don't have a monitor anymore - so not sure if that's a problem here or not.

delete the orphans first then yes I mean the docker run

Just now, trurl said:

delete the orphans first then yes I mean the docker run

Here ya go:

 

PLEX
 

Pulling image: linuxserver/plex:latest

IMAGE ID [1008960680]: Pulling from linuxserver/plex.
Status: Image is up to date for linuxserver/plex:latest

TOTAL DATA PULLED: 0 B

Stopping container: plex

Successfully stopped container 'plex'

Removing container: plex

Successfully removed container 'plex'

Command:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex' --net='host' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'VERSION'='latest' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'TCP_PORT_32400'='32400' -e 'TCP_PORT_3005'='3005' -e 'TCP_PORT_8324'='8324' -e 'TCP_PORT_32469'='32469' -e 'UDP_PORT_1900'='1900' -e 'UDP_PORT_32410'='32410' -e 'UDP_PORT_32412'='32412' -e 'UDP_PORT_32413'='32413' -e 'UDP_PORT_32414'='32414' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/Videos/Films/':'/movies':'rw' -v '/mnt/user/Videos/TV/':'/tv':'rw' -v '/mnt/user/Music/':'/music':'rw' -v '':'/transcode':'rw' -v '/mnt/user/Videos/Stand-Up/':'/stand-up':'rw' -v '/mnt/user/Videos/Trailers/':'/Trailers':'rw' -v '/mnt/user/Videos/Documentaries/':'/documentaries/':'rw' -v '/mnt/user/Videos/Sports/':'/sports':'rw' -v '/mnt/user/appdata/plexmediaserver':'/config':'rw' 'linuxserver/plex'

e151a5ff03fa1baa766e27264c11ea2e1c65b36babce67931be1e9d8bd3faaf9

The command finished successfully!

 

Jackett
 

Pulling image: linuxserver/jackett:latest

IMAGE ID [166390777]: Pulling from linuxserver/jackett.
Status: Image is up to date for linuxserver/jackett:latest

TOTAL DATA PULLED: 0 B

Stopping container: jackett

Successfully stopped container 'jackett'

Removing container: jackett

Successfully removed container 'jackett'

Command:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='jackett' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/Downloads/':'/downloads':'rw' -v '/mnt/user/appdata/jackett':'/config':'rw' --net=container:binhex-delugevpn 'linuxserver/jackett'

d60dce3d0f7f7c0fcd12e0f48a1da6711428a7e09501dd3f05c579d275d2bbdb

The command finished successfully!

 

And I presume you have no orphans as a result of those updates.

3 minutes ago, trurl said:

And I presume you have no orphans as a result of those updates.

i do not.

I'm beginning to wonder if some hacker isn't trying and failing to create containers on your system.

1 minute ago, trurl said:

I'm beginning to wonder if some hacker isn't trying and failing to create containers on your system.

i would obviously say anything is possible but i don't have any reason to believe that to be the case either... how would i "test" for that?

@trurl

okay so some more information for you - i logged into my server a few minutes ago and saw that there were again 2 new orphan images. I then compared the ids to the ones from the screenshot a few back and they are indeed different (not sure if that's surprising or not). I then ran "check for updates" - and found that two of the containers needed to be updated ... so perhaps this is not a hacker and is in fact tied to some sort of "bug" in my system???

 

Here are the docker runs:

Pulling image: linuxserver/duckdns:latest

IMAGE ID [1600041090]: Pulling from linuxserver/duckdns.
Status: Image is up to date for linuxserver/duckdns:latest

TOTAL DATA PULLED: 0 B

Stopping container: duckdns

Successfully stopped container 'duckdns'

Removing container: duckdns

Successfully removed container 'duckdns'

Command:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='duckdns' --net='host' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'SUBDOMAINS'='REMOVEDBYME' -e 'TOKEN'='REMOVEDBYME' -e 'PUID'='99' -e 'PGID'='100' 'linuxserver/duckdns'

cddcf69994f595a1ce33e8d26098396b65978d772d49307284c96adf864282cf

The command finished successfully!

and the other one was jackett which updated last night too so i don't see much having changed there 🙂

 

22 minutes ago, helpermonkey said:

some sort of "bug" in my system???

If it is a bug it hasn't been reported by anyone else. I wonder if searching outside in the larger world of docker would find anything. 

1 hour ago, trurl said:

If it is a bug it hasn't been reported by anyone else. I wonder if searching outside in the larger world of docker would find anything. 

Yeah, i am all about using google and forum search to turn up stuff but if you don't know what to input - it can severely limit what i'm able to turn up. Is it possible this is tied to a plugin that is somehow checking for updates surreptitiously? Here are my plugins...

Do you have CA Backup plugin configured to update applications on restart? Or to NOT stop some of your dockers when backing up?

42 minutes ago, trurl said:

Do you have CA Backup plugin configured to update applications on restart? Or to NOT stop some of your dockers when backing up?

I do have that set to yes ... here are all my settings:

Do the orphans get created when the backup runs?

9 hours ago, trurl said:

Do the orphans get created when the backup runs?

they don't appear to be. okay so interestingly enough - i just checked - a new orphan had appeared - i ran "check for updates" and Jackett had an update ... is it normal for a docker to have an update 3 consecutive days? here's the docker run from that install....

This is really strange and i appreciate your continued help on it.

okay so when i logged in today - you will notice that i had 3 orphans and one image saying it needed to be updated:

 

 

After hitting check for updates - there were indeed 3 that had updates ready.

 

I deleted the orphan images, applied the updates and took this screen cap of the docker run for calibre web...

 

I'm guessing it's tied to the way my containers are updating - i haven't changed any settings and have tried to show in previous posts all the configurations. Any suggestions?

@trurl

would you have any thoughts on this? was hoping some others might help take the weight of your shoulders.

 

I left the server alone for a few days - came back today and there were 7 orphans with 5 images needing updates applied. I'm curious that the Total Data Pulled is always 0 B for any docker.... is this unrelated to the size of the file or is it because the data is downloaded ahead of time and then the update is applied so the dockder run doesn't show the download? (or something else? again out of my depth here).

I'm out of ideas for now