/etc/services.d/jackett/run is no longer marked as executable, breaking s6 read-only root
Avamander opened this issue · 3 comments
Note: Quite a few linuxserver containers broke like this relatively recently
Expected Behavior
The file "/root/etc/services.d/jackett/run" is no longer marked executable in the container, configurations utilizing S6_READ_ONLY_ROOT and what mark the root read-only will fail. This is a regression compared to the previous builds.
Current Behavior
The ./run
file of the jackett service is rw-rw-r--
instead of rwxrw-r--
causing the following error message:
jackett | s6-supervise jackett (child): fatal: unable to exec run: Permission denied
jackett | s6-supervise jackett: warning: unable to spawn ./run - waiting 10 seconds
One chmod
in the container fixes that.
Steps to Reproduce
Add the snippet provided below to your compose file.
Similar symptoms or issues:
- kubeflow/kubeflow#5808 (comment)
- rocker-org/rocker#202
- containers/podman#3803
- Radarr/Radarr#5300
- linuxserver/docker-radarr#113
- just-containers/s6-overlay#158
- linuxserver/docker-homeassistant#54
- linuxserver/docker-radarr#181
Environment
OS: Ubuntu 22.04
CPU architecture: arm64
How docker service was installed: Official repos
Command used to create docker container
read_only: true
tmpfs:
- /run:rw,exec
- /tmp:rw,noexec,nosuid
environment:
- "S6_READ_ONLY_ROOT=1"
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Unstale.