/etc/services.d/jackett/run is no longer marked as executable, breaking s6 read-only root

[Avamander]

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:

• https://github.com/kubeflow/kubeflow/issues/5808#issuecomment-1083558197
• https://github.com/rocker-org/rocker/issues/202
• https://github.com/containers/podman/issues/3803
• https://github.com/Radarr/Radarr/issues/5300
• https://github.com/linuxserver/docker-radarr/issues/113
• https://github.com/just-containers/s6-overlay/issues/158
• https://github.com/linuxserver/docker-homeassistant/issues/54
• https://github.com/linuxserver/docker-radarr/issues/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"

[github-actions[bot]]

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

[github-actions[bot]]

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.

[Avamander]

Unstale.