Skip to content
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

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

Closed
Avamander opened this issue Jul 19, 2022 · 3 comments · Fixed by #130
Closed

Comments

@Avamander
Copy link

Avamander commented Jul 19, 2022

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:

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
Copy link

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

@github-actions
Copy link

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
Copy link
Author

Unstale.

@thespad thespad linked a pull request Nov 1, 2022 that will close this issue
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant