Which UID and GID does Crosswatch use in the docker container? #28
-
|
Nice looking solution and good documentation. One thing I couldn't find in the doc, discussions, or issues is which UID and GID Crosswatch uses in the docker container. I like to put my containers' configs and data on my NAS. The container won't start due to a UID/GID mismatch permission denied error while trying to mkdir /config/sync_reports. Please tell me which UID and GID Crosswatch uses in the docker container so I can adjust my mount point to use the same UID/GID. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
UID/GID used for the app user inside the container Can be changed in the contrainer ENV. appuser:x:1000:1000::/home/appuser:/bin/bash https://github.com/cenodude/CrossWatch/wiki/Getting-Started Optional environment variablesYou normally only need
|
Beta Was this translation helpful? Give feedback.
UID/GID used for the app user inside the container
APP_UID: "1000"
APP_GID: "1000"
Can be changed in the contrainer ENV.
appuser:x:1000:1000::/home/appuser:/bin/bash
https://github.com/cenodude/CrossWatch/wiki/Getting-Started
Optional environment variables
You normally only need
TZ, but you can override these:CONFIG_BASE— base path forconfig.json,state.json,statistics.json, etc.Default:
/configWEB_HOST— bind address for the web UI inside the container.Default:
0.0.0.0WEB_PORT— port for the web UI inside the container.Default:
8787APP_USER— username created inside the container that runs CrossWatch.Default:
appuserAPP_GROUP— group name created inside the container.Default: