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

Allow run as non root #138

Open
1 task done
TheKangaroo opened this issue May 7, 2024 · 2 comments
Open
1 task done

Allow run as non root #138

TheKangaroo opened this issue May 7, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@TheKangaroo
Copy link

Steps To Reproduce

I do not think it is currently possible to deploy the bitwarden helm chart in a cluster that requires pods to run without root.
There is an option to provide security context to some pods, but not all.
My installation on a security hardened cluster (no root containers allowed) failed as soon as I tried to deploy the bitwarden-db-pre-upgrade job. This job has no configurable security context, so I couldn't get any further.

It would be great if running as non-root was the default for a security oriented tool like bitwarden.
As an alternative, I would like to see the option to run bitwarden as non-root with a custom values configuration.

Expected Result

It was possible to run in a hardened cluster

Actual Result

It is not possible at the moment

Screenshots or Videos

No response

Additional Context

No response

Chart Version

self-host-2024.4.0

Environment Details

No response

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@TheKangaroo TheKangaroo added the bug Something isn't working label May 7, 2024
@cfis
Copy link

cfis commented Jul 11, 2024

I would also like to have this. Note when I set runAsUser and runAsGroup then bitwarden breaks with an error message:

invalid user: "bitwarden:bitwarden"

It looks like that user is hardcoded to id 1000/1000 here:

It would be nice if that could be changed to use runAsUser and runAsGroup settings.

@TheKangaroo
Copy link
Author

@cfis I think the entrypoint of the containers need to run as root right now and drop down to bitwarden user once started. Thats something that needs to be fixed in the container images, but thats on the bitwarden side to fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants