This repository has been archived by the owner on Sep 7, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 380
Allow custom user to be specified #102
Comments
micheljung
added a commit
to FAForever/faf-stack
that referenced
this issue
Sep 15, 2017
Sounds like a reasonable solution. A PR would be appreciated. |
I'm a bit confused. In run.sh, the owner of directories is changed to Update turns out the user is being created by the .deb package, so it's basically baked into the image and can not be changed. It looks like there's no solution to this. Maybe I need to Isolate containers with a user namespace instead. |
micheljung
added a commit
to micheljung/grafana-docker
that referenced
this issue
Oct 2, 2017
micheljung
added a commit
to micheljung/grafana-docker
that referenced
this issue
Oct 2, 2017
On my host system the grafana-server is run as user |
Merged
This will be resolved when we release Grafana 5.1 with the update image tracked in #146. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, this docker image uses a hard coded user and group
grafana
within the container. The problem with this, when using volumes, is that all files created bygrafana:grafana
inside the container belong to some "random" user on the host.In my case, the files created by
grafana:grafana
belong the the usersyslog:crontab
on the host.Now, unless someone knows how to map container users to host users, it would good if the user/group could be specified as environment variables which would be used like so:
Alternatively, you could define
USER grafana
in the Dockerfile. This can then be overridden by the user. I'm no Docker pro, but I read running containers as root is bad practice. Not sure this applies as well if you change users inside the container.The text was updated successfully, but these errors were encountered: