Enhancement: Create additional nonroot user to avoid running as UID 0 #1147

Open
opened 2026-04-05 16:25:38 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @jiglesia3 on 3/8/2024

Is your feature request related to a problem? Please describe.
While the root user was removed in this earlier commit, this is still in violation of a common security policy where the container is running as UID 0 since another user was not explicitly added. Setting another user within a Dockerfile is a common practice we've seen from open-source tools, or including a separate field in the helm chart to run as a separate UID.

Describe the solution you'd like
Set an additional USER oneuptime - similar to this gist - and modify files and permissions as necessary.

Describe alternatives you've considered
None found at this time other than ignoring security violations in our environment.

Additional context
https://github.com/OneUptime/oneuptime/issues/1176

*Originally created by @jiglesia3 on 3/8/2024* **Is your feature request related to a problem? Please describe.** While the root user was removed in this earlier [commit](https://github.com/OneUptime/oneuptime/commit/519daba29490333246b729d82952ab8c8b6b8e66), this is still in violation of a common security policy where the container is running as UID 0 since another user was not explicitly added. Setting another user within a Dockerfile is a common practice we've seen from open-source tools, or including a separate field in the helm chart to run as a separate UID. **Describe the solution you'd like** Set an additional `USER oneuptime` - similar to this [gist](https://gist.github.com/avishayp/33fcee06ee440524d21600e2e817b6b7?permalink_comment_id=4348706) - and modify files and permissions as necessary. **Describe alternatives you've considered** None found at this time other than ignoring security violations in our environment. **Additional context** https://github.com/OneUptime/oneuptime/issues/1176
MrUnknownDE added the enhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancement labels 2026-04-05 16:25:40 +02:00
Sign in to join this conversation.
No Label enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#1147