-
-
Notifications
You must be signed in to change notification settings - Fork 254
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
[BUG] s6-rc: warning: unable to start service init-permissions: command exited 1 #535
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Issues with your file system? Full disk? |
They're bind mounting a bunch of individual config files as read only, which is something we do not support. Config folder belongs to the container and needs to be writeable by the container. |
This comment has been minimized.
This comment has been minimized.
Your issue is unrelated to OP and is due to #514 |
Solved by following @aptalca suggestion: mounted the entire nginx configuration directory instead of single files. Thank you. |
Is there an existing issue for this?
Current Behavior
Service keeps restarting ending with error related to init-permissions unable to start.
Expected Behavior
No response
Steps To Reproduce
lscr.io/linuxserver/swag:3.0.1-ls347
Environment
CPU architecture
arm64
Docker creation
The text was updated successfully, but these errors were encountered: