linuxserver / docker-transmission

GNU General Public License v3.0
577 stars 179 forks source link

[BUG] <title> #273

Closed mcepl closed 6 months ago

mcepl commented 6 months ago

Is there an existing issue for this?

Current Behavior

I am using this podman/quadlet .container file (with podman 4.9.2 on openSUSE/MicroOS, essentially Tumbleweed, our rolling distro):

[Unit]
Description=Podman container-transmission.service
Documentation=https://github.com/linuxserver/docker-transmission/blob/master/README.md
Wants=network-online.target
After=network-online.target

[Container]
Image=docker.io/linuxserver/transmission
ContainerName=transmission
Label=io.containers.autoupdate=registry
Environment=PUID=1000 PGID=100 SEED_RATIO=1.3 TZ=Europe/Prague
Volume=/home/matej/.config/transmission:/config
Volume=/home/matej/Videa/2BSeen:/downloads
PublishPort=127.0.0.1:9091:9091
PublishPort=127.0.0.1:51413:51413
PublishPort=127.0.0.1:51413:51413/udp
UserNS=keep-id:uid=1000,gid=100
PodmanArgs=--hostname my-transmission --privileged

[Service]
Restart=on-failure

[Install]
WantedBy=default.target

I get plenty of errors in podman logs:

mitmanek:systemd $ podman logs -f transmission
/run/s6/basedir/scripts/rc.init: line 26: /docker-mods: Permission denied
/run/s6/basedir/scripts/rc.init: warning: hook /docker-mods exited 126
[migrations] started
[migrations] no migrations found
groupmod: /etc/group.73: Permission denied
groupmod: cannot lock /etc/group; try again later.
usermod: /etc/passwd.74: Permission denied
usermod: cannot lock /etc/passwd; try again later.
───────────────────────────────────────
  _____ __ __ _____ _____ _____ _____ 
 |     |  |  |   __|_   _|     |     |
 |   --|  |  |__   | | | |  |  | | | |
 |_____|_____|_____| |_| |_____|_|_|_|
       _____ __ __ _ __    ____  
      | __  |  |  | |  |  |    \ 
      | __ -|  |  | |  |__|  |  |
      |_____|_____|_|_____|____/ 

  Based on images from linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    911
User GID:    1001
───────────────────────────────────────

/etc/s6-overlay/s6-rc.d/init-adduser/run: line 44: lsiown: command not found
/etc/s6-overlay/s6-rc.d/init-adduser/run: line 45: lsiown: command not found
/etc/s6-overlay/s6-rc.d/init-adduser/run: line 46: lsiown: command not found
s6-rc: warning: unable to start service init-adduser: command exited 127

It seems to me that missing programs must be a problem in the container itself, mustn’t it?

Also, my browser cannot connect to http://127.0.0.1:9091/transmission/web/.

Expected Behavior

The container should start without errors in logs and waiting for the connection via a browser.

Steps To Reproduce

see above

Environment

- OS: openSUSE/MicroOS (based on Tumbleweed)
- How docker service was installed: see above, using podman/systemd/quadlet combo.

CPU architecture

x86-64

Docker creation

see above

Container logs

see above
github-actions[bot] commented 6 months ago

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

Roxedus commented 6 months ago

/run/s6/basedir/scripts/rc.init: line 26: /docker-mods: Permission denied We do not target, nor support rootless runtimes with usernamespace mappings.

mcepl commented 6 months ago

On Thu Feb 8, 2024 at 1:43 PM CET, Roxedus wrote:

/run/s6/basedir/scripts/rc.init: line 26: /docker-mods: Permission denied We do not target, nor support rootless runtimes with usernamespace mappings.

OK, thank you. You can close this ticket then, and I will find my container somewhere else (or I will create my own).