bitwarden/server

Container should not run as root

Open

#2,903 创建于 2023年5月3日

在 GitHub 查看
 (6 评论) (7 反应) (0 负责人)C# (18,588 star) (1,575 fork)batch import
bugbw-lite-deployhelp wanted

描述

Steps To Reproduce

  1. Install per the instructions as written at https://bitwarden.com/help/install-and-deploy-unified-beta/ that has a restrictive policy like SELinux

Expected Result

The container should run as a non-root user

Actual Result

The container cannot run in a restrictive environment where root users are not permitted or are highly restricted like in SELinux environments or Kubernetes platforms that enforce a restrictive policy like VMware Tanzu or OpenShift.

Screenshots or Videos

No response

Additional Context

I have attempted to set the running user via policy, but the image is trying to change permissions on startup and is not allowed to.

Githash Version

NA - container does not run

Environment Details

  • Operating System: Photon Linux
  • Platform: Kubernetes (Tanzu)
  • Kubernetes API: 1.21

Database Image

sqlite

Issue-Link

https://github.com/bitwarden/server/issues/2480

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.

贡献者指南

技术栈
csharpdocker
领域
securitydevopscloud
议题类型
security
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Dockerfile basicsLinux user permissions
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
Investigate the Dockerfile in the repository (e.g., Dockerfile or docker compose files) to determine how the container user is configured. The issue requires adding a non root user directive (USER) and ensuring that all necessary file permissions are adjusted for volumes and startup scripts. Review the linked issue #2480 for previous discussion. Test the changes in a SELinux or Kubernetes environment to confirm compliance. Consider using a tool like 'docker run user' or modifying the image entrypoint.