We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Cron cannot start in rootless mode and the app loops on
scrutiny | starting cron scrutiny | seteuid: Operation not permitted scrutiny | cron exiting s6-svscanctl -t /var/run/s6/services
Expected behavior Using user: 1000:100 in the docker compose file (to alleviate file access permissions) but still getting access to cron
user: 1000:100
If someone could help, it would be great. Thanks in advance :)
The text was updated successfully, but these errors were encountered:
+1 Any solution?
Sorry, something went wrong.
Just looking at the error, you likely need to add --cap-add CAP_SETUID in the docker command.
--cap-add CAP_SETUID
No branches or pull requests
Describe the bug
Cron cannot start in rootless mode and the app loops on
Expected behavior
Using
user: 1000:100
in the docker compose file (to alleviate file access permissions) but still getting access to cronIf someone could help, it would be great. Thanks in advance :)
The text was updated successfully, but these errors were encountered: