helpermonkey

Members
  • Content Count

    203
  • Joined

Community Reputation

1 Neutral

About helpermonkey

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @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).
  2. 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?
  3. 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.
  4. I do have that set to yes ... here are all my settings:
  5. 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...
  6. @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/
  7. 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?
  8. 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_
  9. 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.
  10. okay so i disabled auto-update as detailed here: And there are two orphaned images and both Jackett & Plex have updates ready to apply ...