-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Is there any plan to run container as non root user? #1447
Comments
Yes, but it hasn't been a priority. If you are willing to help, he first step would be to upgrade the s6 overlay to v3, which does allow running as non-root. Once that is done, switching to non-root would be a next step. |
@saghul is it gonna be a priority this year? |
I don't have any indication to believe it will be. As I mentioned earlier (#1447 (comment)) migrating to S6 v3 is a pre-requisite to that. |
@saghul I have successfully migrated docker-jitsi-meet's base image to the latest version of s6-overlay (v3.1.5.0). After a few days of refactoring some of the cont-init and services.d and of course, some changes in Dockerfiles, seems like all the services are now running error-free with the new base. |
This is awesome, thank you! |
No description provided.
The text was updated successfully, but these errors were encountered: