Chuck

Thank you for this info. I'll be of great help. I'll make time this weekend to update. As for your version, I have a few suggestions. 1. Don't `kill` (default...

@binhex Can we chat somewhere ? We have an issue to resolve.

@AppliedEllipsis Cool. Thank you for letting me know. I'll update right away. Expect an update (Aug 28/29)

@Chaotic 1. Yes, put the script (`DBRepair.sh`) adjacent to `/config` 2. This way, when you enter the container, you can then `/DBRepair.sh stop auto start exit` (or whatever you want...

@AppliedEllipsis I just created a new LSIO plex container. This is what I see: ``` root@lsioplex:/# ls /var/run/service s6-linux-init-shutdownd s6rc-fdholder s6rc-oneshot-runner svc-cron svc-plex root@lsioplex:/# ``` Given you state /run versus...

The full sequence: ```Error response from daemon: No such container: lsioplex Error response from daemon: No such container: lsioplex Unable to find image 'lscr.io/linuxserver/plex:latest' locally latest: Pulling from linuxserver/plex 6e8bf31012d1:...

@AppliedEllipsis @Chaotic I've updated the general path testing to look at both older and newer (?) path -- which I can't yet confirm in my own new container. Please test...

1, Yes, I forgot to close that with `fi` 2. If both paths exist in the container, how can we determine which one is the correct one to use ?...

Well isn't this problematic :smile: For the life of me, I cannot figure out why these lines, which have worked for a long time now, suddenly fail. ``` # Miscellaneous...

@drumtechphoto I'm glad it helped. There are a couple here which help me with this monster I've created. ( I had no idea it would be like this when started)...