I’ll preface this with I’m a Linux novice and kind of pieced this all together. My perms had been the 1 thing that I wanted to try and fix as I know they weren’t set correctly.
I have been running Radarr, Sonarr, Plex, Jackett as containers (using Portainer) for the best part of the last year without issue. Yesterday I went to update Radarr, Sonarr and Plex and since then I’ve found that I get the refused connection error.
The weird thing is that Jackett has stopped as well and I didn’t try to update that.
For these I’m getting:
s6-applyuidgid: fatal: unable to exec mono: Permission denied
I have another docker which I updated and works (non-LinuxServer image) and 1 other that has also stopped working - qBitTorrentVPN (non-LinuxServer image). I can’t be sure if this stopped at the same time or prior but I get different errors with that one.
Why would pulling down the images again break this?
I’ll start with saying, we do not support or recommend deploying our containers with portainer, nor do the ARR team (radarr/sonarr/etc)
for support with our containers only, we would need your docker run or docker compose and the full container logs which begin with our ascii logo. Helpful information is also the output of docker -v && uname -mr
What’s the issue with Portainer? Given I use a QNAP NAS - is Container Station any better since it’s the default? Or strictly docker compose?
docker -v && uname -mr
Docker version 20.10.27-qnap1, build 662936b 5.10.60-qnap x86_64
Sample from the Radarr stack - it just repeats this, nothing changes - it’s the same for Radarr, Sonarr, Jackett using linuxserver image - tested hotio\radarr and it worked:
[migrations] started
[migrations] no migrations found
───────────────────────────────────────
██╗ ███████╗██╗ ██████╗
██║ ██╔════╝██║██╔═══██╗
██║ ███████╗██║██║ ██║
██║ ╚════██║██║██║ ██║
███████╗███████║██║╚██████╔╝
╚══════╝╚══════╝╚═╝ ╚═════╝
Brought to you by linuxserver.io
───────────────────────────────────────
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID: 1000
User GID: 1000
───────────────────────────────────────
[custom-init] No custom files found, skipping…
s6-applyuidgid: fatal: unable to exec /app/radarr/bin/Radarr: Permission denied
s6-applyuidgid: fatal: unable to exec /app/radarr/bin/Radarr: Permission denied
s6-applyuidgid: fatal: unable to exec /app/radarr/bin/Radarr: Permission denied
s6-applyuidgid: fatal: unable to exec /app/radarr/bin/Radarr: Permission denied
s6-applyuidgid: fatal: unable to exec /app/radarr/bin/Radarr: Permission denied
s6-applyuidgid: fatal: unable to exec /app/radarr/bin/Radarr: Permission denied
s6-applyuidgid: fatal: unable to exec /app/radarr/bin/Radarr: Permission denied
without going too deep, unless you’re a portainer expert it hides functions, can use broken or eol versions of libcompose rather than docker compose, breaks container pathing (as a feature), and many other things. Our recommendation would be docker compose, not docker compose in any UI.
i dont even know where to start with that, the latest 20.10 release officially is 20.10.24, so ill just ignore this and pretend qnap knows what they’re doing. – disregard this, i see that (as usual) docker’s release info just isn’t updated and 20.10.27 is valid, from github
is /share/Portainer/Files/AppData/Config/Radarr local storage or remote?
what is the output of ls -lan /share/Portainer/Files/AppData/Config/Radarr
There is always the possibility qnap is doing weird acl stuff like synology does, but we can start with the basics.
No worries, thanks. Perhaps I should just look at starting again using docker compose rather than waste your time and then raise another post should the issues continue.
is /share/Portainer/Files/AppData/Config/Radarr local storage or remote?
This is local on the NAS
what is the output of `ls -lan /share/Portainer/Files/AppData/Config/Radarr’
so your initial items all look good, local storage, the puid/pgid you set owns all the folders properly, your kernel and docker version are up to date… you could definitely try with compose, i mean… you already have the data for it. As a note, you can still use portainer to VIEW stuff, just don’t use it (if you’re following our support policy) to deploy stuff.
It might be better to come on our discord for support from the community. i dont use qnap, but we have users that do
I’ll take a look at moving over to compose though it’s going to take it’s time to get to that stage as I have a few things coming up over the next couple of weeks.
I’ll also look at Discord too, thanks for the advice.