-
-
Notifications
You must be signed in to change notification settings - Fork 67
[BUG] Newer images require CAP_DAC_OVERRIDE or they get stuck #242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Do you get the same behaviour with It's the nightly tag so probably don't run it against your live install or you might not be able to go back to stable. |
No that seems to work (it starts up at least) |
OK TL;DR we made a change to fix a bug in our older base images, which seems to have surfaced this issue (it probably shouldn't have been working for months), our newer base (which that PR is using) doesn't use that code at all. The stable image should be updated in the next couple of weeks, depending on how busy we get. |
Awesome, appreciate the info/update! I'm just pinning all the versions for now and in a few weeks I'll check back and try the new versions. Thanks again! |
Just look for the Alpine 3.21 or Ubuntu Noble rebase entry in the readme changelog to know if they've been done or not. |
Is there an existing issue for this?
Current Behavior
Starting with 4.3.3 I get the following log entry and there are 2 processes that use 100% cpu and don't ever seem to terminate. Manually killing them doesn't seem to help (thought I'd try). I am running this via podman with reduced capabilities and after trying many combinations it appears that new linuxserver containers now require
CAP_DAC_OVERRIDE
in order to run. Ideally I would like to continue running these without that but I understand that it's a pretty niche setup so maybe you don't want to support that.There is probably a more appropriate repo to file this issue under since it appears to be affecting all newer
linuxserver
containers I use but I wasn't sure where so I just chose this one.rm: cannot remove '/usr/bin/with-contenv': Permission denied
bin/bash /command/with-contenv bash /etc/s6-overlay/s6-rc.d/init-migrations/run
/bin/bash /command/with-contenv bash /etc/s6-overlay/s6-rc.d/init-envfile/run
Expected Behavior
The container starts.
Steps To Reproduce
Hangs:
sudo podman run --rm --replace --name sab --security-opt=no-new-privileges --cap-drop all --cap-add setgid --cap-add sys_nice --cap-add setuid --cap-add chown --cap-add kill 'lscr.io/linuxserver/sabnzbd:4.3.3'
Works:
sudo podman run --rm --replace --name sab --security-opt=no-new-privileges --cap-drop all --cap-add setgid --cap-add sys_nice --cap-add setuid --cap-add chown --cap-add kill --cap-add dac_override 'lscr.io/linuxserver/sabnzbd:4.3.3'
Works (old version):
sudo podman run --rm --replace --name sab --security-opt=no-new-privileges --cap-drop all --cap-add setgid --cap-add sys_nice --cap-add setuid --cap-add chown --cap-add kill 'lscr.io/linuxserver/sabnzbd:4.3.2
Environment
Container logs
When failed: `rm: cannot remove '/usr/bin/with-contenv': Permission denied`
The text was updated successfully, but these errors were encountered: