I have read the other issue making it clear not to run this containor as root, but whether i use podman run command or a docker-compose.yml, the container never recognises my PUID/PGID and tries to run as 0.
id -u
id -g
1040
1040
podman run \
--name lidarr-on-steroids \
--replace \
-p 30530:8686 \
-p 30531:6595 \
-v /home/novafeels/.config/Radarr:/config \
-v /home/novafeels/.config/deemix:/config_deemix \
-v /home/novafeels/files/lidarr:/downloads \
-v /home/novafeels/media/music:/music \
-e AUTOCONFIG=true \
-e PUID=1040 \
-e PGID=1040 \
--restart unless-stopped \
youegraillot/lidarr-on-steroids
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-perms: starting
s6-rc: info: service init-perms successfully started
s6-rc: info: service init-secrets: starting
s6-rc: info: service init-secrets successfully started
s6-rc: info: service init-setup: starting
----------------------------------------------------------------------
ENVIRONMENT
----------------------------------------------------------------------
PUID=0
PGID=0
UMASK=002
TZ=Etc/UTC
----------------------------------------------------------------------
Running as root is not supported, please fix your PUID and PGID!
s6-rc: warning: unable to start service init-setup: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service init-secrets: stopping
s6-rc: info: service init-secrets successfully stopped
s6-rc: info: service init-perms: stopping
s6-rc: info: service init-perms successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
I have read the other issue making it clear not to run this containor as root, but whether i use podman run command or a docker-compose.yml, the container never recognises my PUID/PGID and tries to run as 0.