jason-wilson
commented
1 year ago After a lot of digging (sorry should have dug more) found a script as part of install called: /etc/cont-init.d/10-init-users.sh from the base image jlesage/baseimage-gui:alpine-3.16-v4.4.2 In this script there is this line: echo ${SUP_GROUP_IDS:-},${SUP_GROUP_IDS_INTERNAL:-} | tr ',' '\n' | grep -v '^$' | grep -v '^0$' | grep -vw "$GROUP_ID" | sort -nub | while read GID
Which does add to groups, unless the gid happens to be '0' - which in my case it is. If I instead try SUP_GROUP_IDS=42 (only other group available) then it works and app gets added to group and Crashplan runs with this group added.
Assume there a reason why gid of 0 is forbidden - will work out a different way to add to group
jlesage
Current Behavior
Setting SUP_GROUP_IDS in the docker environment, but does not seem to do anything
Expected Behavior
Expect the running application to be placed into the group. Possibly user 'app' gets added to /etc/group. Only references to SUP_GROUP_IDS I can find are in the README.md and in appdefs.yml - cannot see any references to this variable anywhere to see how it is trying to be setup/used.
Steps To Reproduce
Add SUP_GROUP_IDS=0 to docker-compose.yml
docker compose up -d
docker exec crashplantest-crashplan-pro-1 groups app
app
docker exec crashplantest-crashplan-pro-1 ps | grep CrashPlanService
695 app 0:29 /usr/local/crashplan/bin/CrashPlanService
docker exec crashplantest-crashplan-pro-1 grep Groups /proc/695/status
Groups:
Environment
Container creation
Using docker-compose.yml docker compose up -d
Container log
Container inspect
Anything else?
docker-compose.yml: version: '3'
services: crashplan-pro: image: jlesage/crashplan-pro