You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's considered bad practice to run a container's processes as the root user.
Two possible solutions:
Give the user the ability to set the container process user and group on container creation
Run the process as a non-privileged default user. See linuxserver's implementation where the processes run as user "abc" and the mounted file permissions can be set with environment variables PUID and PGID: https://github.com/linuxserver/docker-plex
Setting the user in a compose file like user: "1068:100" does not work. The container fails to start.
👟 Reproduction steps
n/a
👀 Expected behavior
Don't run process as root
😓 Actual Behavior
Process is running as root
🐻 Uptime-Kuma Version
1.18.0
💻 Operating System and Arch
docker
🌐 Browser
n/a
🐋 Docker Version
20.10.3
🟩 NodeJS Version
n/a
📝 Relevant log output
No response
The text was updated successfully, but these errors were encountered:
🛡️ Security Policy
Description
It's considered bad practice to run a container's processes as the root user.
Two possible solutions:
Setting the user in a compose file like
user: "1068:100"
does not work. The container fails to start.👟 Reproduction steps
n/a
👀 Expected behavior
Don't run process as root
😓 Actual Behavior
Process is running as root
🐻 Uptime-Kuma Version
1.18.0
💻 Operating System and Arch
docker
🌐 Browser
n/a
🐋 Docker Version
20.10.3
🟩 NodeJS Version
n/a
📝 Relevant log output
No response
The text was updated successfully, but these errors were encountered: