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
Following the current docker-compose instructions from https://hub.docker.com/r/athou/commafeed, the server will be running as the root user. That's a security issue, and we should always avoid running processes as root.
It should run as its own user. Bonus points for having the UID/GID configurable.
Configurable UID:GID is needed if the person is mounting /commafeed/data as a volume, because it will match the permissions for that path. (By the way, this should be in the basic configuration example.)
Screenshots
$ docker compose topcommafeed-commafeed-1UID PID PPID C STIME TTY TIME CMDroot 637880 637860 9 08:53 ? 00:00:22 java -jar commafeed.jar server config.yml
Environment (please complete the following information):
CommaFeed version (or "commafeed.com"): latest
Browser [e.g. chrome, firefox]: N/A
Device [e.g. desktop, mobile]: N/A
Additional context
You could consider following the structure of the many other images from LinuxServer.IO. Those images always run as a configurable normal user and even have a configurable timezone.
If you go through that route, you can contribute your image to their project. Not only it will be easy to setup for most people, but also gives some exposure as something linked from and supported by LSIO.
The text was updated successfully, but these errors were encountered:
Describe the bug
Following the current docker-compose instructions from https://hub.docker.com/r/athou/commafeed, the server will be running as the
root
user. That's a security issue, and we should always avoid running processes as root.To Reproduce
Steps to reproduce the behavior:
docker-compose.yml
file following the instructions from https://hub.docker.com/r/athou/commafeed.docker compose up -d
htop
, search forcommafeed
; ordocker compose top
Expected behavior
It should run as its own user. Bonus points for having the UID/GID configurable.
Configurable UID:GID is needed if the person is mounting
/commafeed/data
as a volume, because it will match the permissions for that path. (By the way, this should be in the basic configuration example.)Screenshots
Environment (please complete the following information):
latest
Additional context
You could consider following the structure of the many other images from LinuxServer.IO. Those images always run as a configurable normal user and even have a configurable timezone.
If you go through that route, you can contribute your image to their project. Not only it will be easy to setup for most people, but also gives some exposure as something linked from and supported by LSIO.
The text was updated successfully, but these errors were encountered: