New stacks being created with root owner #89
Replies: 5 comments 1 reply
-
Yes please. This is a great piece of software and I'm so looking forward to fully swap Portainer with it, but I can't until it allows creating stacks as any other user than root (+1 for |
Beta Was this translation helpful? Give feedback.
-
For me a quick work around would be if the Group had write permission, that allows me to edit the stacks from within a browser. I only use Linux if that makes a difference. |
Beta Was this translation helpful? Give feedback.
-
Totally agree with this RichyHBM comment. |
Beta Was this translation helpful? Give feedback.
-
April 2024, still not a feature. Was excited to try this out, came across the stack being root immediately and it causes problems. Please fix! Someone has already done the work months ago and submitted a PR. 9f6a3ee |
Beta Was this translation helpful? Give feedback.
-
Just add a services:
dockge:
image: louislam/dockge:1
restart: unless-stopped
user: 1000:1000
group_add:
- '996'
ports:
# Host Port : Container Port
- 5001:5001
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ./data:/app/data
# If you want to use private registries, you need to share the auth file with Dockge:
# - /root/.docker/:/root/.docker
# Stacks Directory
# ⚠️ READ IT CAREFULLY. If you did it wrong, your data could end up writing into a WRONG PATH.
# ⚠️ 1. FULL path only. No relative path (MUST)
# ⚠️ 2. Left Stacks Path === Right Stacks Path (MUST)
- /opt/stacks:/opt/stacks
environment:
# Tell Dockge where is your stacks directory
- DOCKGE_STACKS_DIR=/opt/stacks As you can see, under |
Beta Was this translation helpful? Give feedback.
-
Hi, I have noticed that when creating a new stack, the owner of the stack/compose file is set to the container user, could we supply a user/group to assign it to maybe in the environment variables? It seems
PUID=1000 PGID=1000
seem to have become the standard env variables to use for thisBeta Was this translation helpful? Give feedback.
All reactions