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/homeassistant/run is no longer marked as executable, breaking s6 read-only root #54

Closed
Avamander opened this issue Jul 19, 2022 · 4 comments

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/homeassistant/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 homeassistant service is rw-rw-r-- instead of rwxr--r-- causing the following error message:

homeassistant     | s6-supervise homeassistant (child): fatal: unable to exec run: Permission denied
homeassistant     | s6-supervise homeassistant: 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

Still relevant.

@aptalca
Copy link
Member

aptalca commented Sep 28, 2022

No, it's not. That file is no longer used in the images.

@aptalca aptalca closed this as completed Sep 28, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants