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
I am a docker newbie so please forgive me if these are stupid questions.
I am unable to bind volumes from host to container for graphite, elasticdata or supervisor logs. The crux seems to be permissions. The carbon and graphite run as www-data but if I start docker like your example. The host folder will only be writable by root (and the container docker user) not by www-data.
docker run -v /data/graphite:/var/lib/graphite/storage/whisper
-d nickstenning/graphite
How do you handle permissions for the container process users to write to the host volumes?
The text was updated successfully, but these errors were encountered:
Its tricky business, since docker build will run as root, we could insert a
step there chown the folders needed. Can you try that?
On Tue, Mar 18, 2014 at 12:05 AM, Torkel Ödegaard [email protected]:
I am a docker newbie so please forgive me if these are stupid questions.
I am unable to bind volumes from host to container for graphite,
elasticdata or supervisor logs. The crux seems to be permissions. The
carbon and graphite run as www-data but if I start docker like your
example. The host folder will only be writable by root (and the container
docker user) not by www-data.
docker run -v /data/graphite:/var/lib/graphite/storage/whisper
-d nickstenning/graphite
How do you handle permissions and the container process users and the host
volumes?
Reply to this email directly or view it on GitHubhttps://github.com//issues/1
.
I am a docker newbie so please forgive me if these are stupid questions.
I am unable to bind volumes from host to container for graphite, elasticdata or supervisor logs. The crux seems to be permissions. The carbon and graphite run as www-data but if I start docker like your example. The host folder will only be writable by root (and the container docker user) not by www-data.
docker run -v /data/graphite:/var/lib/graphite/storage/whisper
-d nickstenning/graphite
How do you handle permissions for the container process users to write to the host volumes?
The text was updated successfully, but these errors were encountered: