-
Notifications
You must be signed in to change notification settings - Fork 70
Run Bitwarden-selfhosted as non-root container on the read-only filesystem #247
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
Comments
I did a trivial PR for this issue. |
Hi there, This issue has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks! |
Much needed feature to get this working on Azure AppService / Container Apps! |
/etc/supervisor.d is mostly where systemd stores content. Don't try to outsmart systemd: Rather than using "bitwarden.sh" directly, create a systemd for bitwarden and enable the designated service user to start or stop that, with the escalations built into systemd. |
I am running a Bitwarden instance in Kubernetes and want to harden it, because to it contains vital secrets. However, if I try as a start to set:
I am getting several errors from the entrypoint.sh:
and
This happens due to the entrypoint.sh:
Useradd, groupadd could be easily moved in the Dockerfile, as well as the permissions/group ownership. Seems like "Enable/Disable services" also should be rather in the Dockerfile. /etc/bitwarden that is altered by the entrypoint.sh should be a persistent volume, since we want to keep instance identity on restarts, it's not a problem.
The text was updated successfully, but these errors were encountered: