linuxserver/docker-homeassistant

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

Avamander opened this issue · 4 comments

Avamander commented

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 commented

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

github-actions commented

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 commented

Still relevant.

aptalca commented

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