Document how to store data outside of container about docker-grafana-graphite HOT 14 CLOSED

Oh, and another thing we did locally that we may want to document: If you're using collectd to report stats, you need to expose -p 2003:2003 for the graphite carbon port. I can open a separate issue for that but since I'm already in the README I'm happy to do it as part of this issue.

from docker-grafana-graphite.

Hello James! The paths look correct so yes, that should be enough to ensure data persistence. If you opt for sending the PR I would suggest you to also put a small note on optionally mounting the logs folder in a volume as well, to simplify troubleshooting. Thanks!

from docker-grafana-graphite.

Sounds good. What log paths would you suggest documenting? I see a few possibilities:

/var/log/elasticsearch
/opt/graphite/storage/log

Also, should users make the volumes they bridge to the container world-writeable? I ended up doing that but I'm not sure if that's strictly required.

from docker-grafana-graphite.

I'm having difficulties with permissions when storing the elasticsearch data outside of the container (whisper data works fine). It only works when I set write permissions to group and other on the mapped volumed data but I don't think it's a correct solution. Any ideas ?

from docker-grafana-graphite.

Yeah I made the directories world-writeable as well. It might work to chown the dir to the UID of elasticsearch. I didn't look at /etc/passwd in the container to see what UID that is though.

I've had similar issues with docker and external volumes.

from docker-grafana-graphite.

+1
Makes a lot of sense to have this configuration in the README

from docker-grafana-graphite.

I think /opt/grafana/data should also be persisted, or you lose your dashboards.

from docker-grafana-graphite.

Yes you need to add this to readme =) Thanks coopernurse

from docker-grafana-graphite.

Created a pull request: #60 which encapsulates the advise from this thread.

from docker-grafana-graphite.

I have a question regarding the persistence of the data. I am trying to use data volume container however it does not seem to work with following commands - can someone tell me what is wrong in that

docker create --name grafanadata \
  -v /opt/graphite/storage/whisper \
  -v /var/lib/elasticsearch \
  -v /opt/grafana/data \
  -v /opt/graphite/webapp
  -v /opt/graphite/storage/log \
  -v /var/log/elasticsearch \
  kamon/grafana_graphite /bin/true

docker run \
  --detach \
  --volume-from grafanadata \
   --publish=80:80 \
   --publish=81:81 \
   --publish=8125:8125/udp \
   --publish=8126:8126 \
   --name grafana-dashboard \
   kamon/grafana_graphite

I get this
flag provided but not defined: --volume-from

from docker-grafana-graphite.

@mohdaliiqbal It should be

 --volumes-from

Plural. :)

from docker-grafana-graphite.

FML!

@joshrivers - Thanks dude.

from docker-grafana-graphite.

I think /src/dashboards also needs to be persisted or at least documented better in README as I've lost configured dashboards because of it twice :/ Looking at the Dockerfile and scripts, there is a dashboard-loader tool that runs under supervisor which imports dashboard JSON files from that directory and basically overwrites anything that existed. In my case, I had reconfigured the system metrics dashboard and on container launch all changes get overwritten.

from docker-grafana-graphite.

Lots of done work here - maybe the issue can be closed?

@rholloway 's issue is probably a completely separate one

@coopernurse I'd like to see a simple way to also feed stats to the Docker be explained in the README. Using collectd could be exactly this.

from docker-grafana-graphite.