Skip to content
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

Run gateway image as non-root user #1198

Open
LECZYF opened this issue Aug 5, 2020 · 1 comment · May be fixed by #1199
Open

Run gateway image as non-root user #1198

LECZYF opened this issue Aug 5, 2020 · 1 comment · May be fixed by #1199
Assignees
Labels
enhancement New feature or request

Comments

@LECZYF
Copy link

LECZYF commented Aug 5, 2020

The problem faced currently?

Currently all files needed to run gateway image are owned by root user.
Also the mission-control package is unpacked into /root directory.

This setup makes it impossible to run gateway image on k8s clusters with tight security restrictions like:

  • containers cannot be run as root ( non root user cannot create config file in /app dir and access mission-control files)
  • container don't have access to internet (container cannot download mission-control after failing to read one in root dir)

How can we solve it?

To overcome this, dedicated user should be created in the dockerfile and set as default user in the container. This user should own all the files and directories needed to run the application.

Happy to issue a PR if this gets and OK. Such improvement could improve and adoption of space cloud as most enterprise k8s clusters (and OpenShift by default) have such security requirements in place.

@YourTechBud
Copy link
Collaborator

@LECZYF that's a great recommendation. Happy to assign this issue to you!

@YourTechBud YourTechBud added the enhancement New feature or request label Aug 5, 2020
@LECZYF LECZYF linked a pull request Aug 5, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants