8
Deployment vaultwarden (in cluster main) violates 'Process with UID 0' Policy
Source: dani-garcia/vaultwarden#4358 · opened by @gecube
Good day!
I'd like to ask to build a docker image with a non-privileged user. I don't see any reason why we should to use root (uid 0) user for running Vaultwarden service. It is critical when running Vaultwarden in strict and regulated environments.
The change could be breaking in case if Vaultwarden is running inside of k8s pod and stores data in a local file.
<img width="704" alt="Screenshot 2024-02-16 at 11 56 36" src="
I'd like to ask to build a docker image with a non-privileged user. I don't see any reason why we should to use root (uid 0) user for running Vaultwarden service. It is critical when running Vaultwarden in strict and regulated environments.
The change could be breaking in case if Vaultwarden is running inside of k8s pod and stores data in a local file.
<img width="704" alt="Screenshot 2024-02-16 at 11 56 36" src="
No pledges yet. Be the first to back this.
Comments
Similar requests
Re-License of Vaultwarden to AGPLv3
26 votes · 0 comments
Migration to organization
1 vote · 0 comments
Utilize checksum on vaultwarden.css
1 vote · 0 comments
Update Podman documentation to use Quadlet for systemd deployment
5 votes · 0 comments
[Security] Default Port Should be 443
1 vote · 0 comments
No comments yet.