builds the vimeo/graphite-api-influxdb docker image, with graphite-api and graphite-influxdb using baseimage-docker which means you effectively get a full working linux system with an init system, logging, etc. So you can login if anything goes wrong.
- install docker on your system
- make a new directory and put your own Dockerfile in it, it looks like so:
FROM vimeo/graphite-api-influxdb
-
put a customized graphite-api.yaml in this directory, you can base yourself off the graphite-api.yaml in this repository
-
build!
docker build .
- run !
docker run -p 8000:8000 <image-id>
If you want, you can build with a name and run the container with this name:
docker build . -t <name>
docker run -p 8000:8000 <name>
on /render calls, you might get http 500 responses. unfortunately we can't simply log yet what happend (i.e. which exception) or display the errors in the http response. see brutasse/graphite-api#16 but you can make a free account on getsentry.com and use that, it works nicely. You can also try this patch for graphite-api brutasse/graphite-api#73 (comment) It works for some people (including yours truly)
This shouldn't happen to you as an end user, but may happen if you're tweaking this image. Try running in debug/standalone mode by running this script: https://github.com/brutasse/graphite-api/blob/master/bin/graphite