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
Is your feature request related to a problem? Please describe.
Any process that might not need to be run as root could be of a potential security risk.
Describe the solution you'd like
Following the principle of least privilege, I would suggest that the container could run as a newly created system user (in the Dockerfile):
RUN groupadd --system sal && useradd --system --shell /bin/false --gid sal sal
RUN chown -R sal:sal /home/app
USER sal
Of course there would still be issues with processes that need privileges to be addressed such as cron, supervisord etc. So the code above would be just a first step.
Describe alternatives you've considered
Isolating sal into its own VPC
Overwriting the original sal image with an additional docker layer (very hackish)
Additional context
There are lots of online resources you can find related to the importance of rootless containers.
I really appreciate sal and I know this request can be challenging to implement.
Thanks in advance! :)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Any process that might not need to be run as root could be of a potential security risk.
Describe the solution you'd like
Following the principle of least privilege, I would suggest that the container could run as a newly created system user (in the Dockerfile):
Of course there would still be issues with processes that need privileges to be addressed such as cron, supervisord etc. So the code above would be just a first step.
Describe alternatives you've considered
Additional context
There are lots of online resources you can find related to the importance of rootless containers.
I really appreciate sal and I know this request can be challenging to implement.
Thanks in advance! :)
The text was updated successfully, but these errors were encountered: