You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not really a bug: just to point out that some runtimes (podman, may be dependent on host OS?) mount /run with the noexec flag preventing /run/s6/services/*/run scripts from starting up.
I noticed that /var/run/s6/services is hardcoded in the init scripts, perhaps one could consider making it a parameter of the container image?
Alternatively, document that scripts are run from /run and that the container should be created with the equivalent of
--tmpfs /run:rw,nosuid,nodev,mode=755
i.e., make sure your runtime doesn't create /run mounted noexec
The text was updated successfully, but these errors were encountered:
Not really a bug: just to point out that some runtimes (podman, may be dependent on host OS?) mount
/run
with thenoexec
flag preventing/run/s6/services/*/run
scripts from starting up.I noticed that
/var/run/s6/services
is hardcoded in the init scripts, perhaps one could consider making it a parameter of the container image?Alternatively, document that scripts are run from
/run
and that the container should be created with the equivalent ofi.e., make sure your runtime doesn't create
/run
mountednoexec
The text was updated successfully, but these errors were encountered: