go-graphite / docker-go-graphite Goto Github PK

We should migrate build to Github Actions (and maybe Github Docker repos) because Docker removed autobuilds.

Thanks for making these docker containers.

What is the recommended practice to change config files? Traditionally I've used the legacy 'bind' mount to point to files on the host managed by puppet.

docker run -it -v /etc/grafana/ldap.toml:/etc/grafana/ldap.toml gographite/go-graphite:1.0.4

However because this container uses the new volumes, I'm not able to use the older bind mounts.

https://docs.docker.com/storage/

If you mount a bind mount or non-empty volume into a directory in the container in which some files or directories exist, these files or directories are obscured by the mount, just as if you saved files into /mnt on a Linux host and then mounted a USB drive into /mnt. The contents of /mnt would be obscured by the contents of the USB drive until the USB drive were unmounted. The obscured files are not removed or altered, but are not accessible while the bind mount or volume is mounted.

Some people suggest using busybox to inject config files

https://stackoverflow.com/questions/37468788/what-is-the-right-way-to-add-data-to-an-existing-named-volume-in-docker

docker run -v my-jenkins-volume:/data --name helper busybox true
docker cp . helper:/data
docker rm helper

This feels unnecessarily complicated.

How do you recommend users change config files inside the docker container?

Hello,

First off, very good job, congratulations.

I am having some problems with the provision of the datasource. In some machines the provision is done properly and in other machines the provision fails and the datasource is not created.

I have been able to reproduce the problem by setting a lower sleep time in the Dockerfile grafana installation. If you set "sleep 1" instead of 5 you will see that grafana has not the datasource provisioned once it is up.

The Dockerfile copies the provision yaml to /etc/grafana/provisioning/datasources/carbonapi.yaml, but actually, once the grafana-server is started by the run script, the homepath is set to

--homepath=/usr/share/grafana/

And the configuration file says that the provisioning file should be in /usr/share/grafana/conf/provisioning/...

In order to make it work I made some changes. I have submitted those changes as a pull request, just in case you agree with them and want to merge them.

Thank you very much for sharing this, and BR.

If you run the docker image as provided it is shipped with Grafana.
However, you might want to use external grafana. In such case you won't be able to connect, even though the port 8081 is exported.

Migrate to Alpine + runit instead of phusion, similar to graphite-project/docker-graphite-statsd#66

Hello,
good job. Is it possible to upgrade grafana to version 5?

Best regards

The carbonapi port (8081) is exposed, but unreachable, even if mapped at runtime.

Mapping the port at runtime with -p 8081:8081 appears to work, but when you connect to the port, you get

connection reset by peer

The issue is that the carbonapi server binds to 127.0.0.1 instead of 0.0.0.0.

Please have carbonapi bind to 0.0.0.0 by default. This will enable mapping 8081 at runtime to work.

Is there any way to make tags work as expected?

I ingested data into graphite using the pickle format and here's what I get:

You can see that the metric names preserved ;..., which I think they shouldn't.

Clicking on seriesByTag in the screenshot above does nothing (the function dropdown gets deselected) and sometimes grafana displays a red rectangle with 404 not found

I even tried upgrading all dependencies. Same error.

Sidenote: I tried tweaking with the datasource settings inside Grafana. Still no luck.