chronografEstimated reading time: 5 minutes
Chronograf is a visualization tool for time series data in InfluxDB.
GitHub repo: https://github.com/influxdata/influxdata-docker
Supported tags and respective
Where to file issues:
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
Chronograf is InfluxData’s open source web application. Use Chronograf with the other components of the TICK stack for infrastructure monitoring, alert management, data visualization, and database management.
Using this image
Running the container
Chronograf runs on port 8888. It can be run and accessed by exposing that port:
$ docker run -p 8888:8888 chronograf
Mounting a volume
The Chronograf image exposes a shared volume under
/var/lib/chronograf, so you can mount a host directory to that point to access persisted container data. A typical invocation of the container might be:
$ docker run -p 8888:8888 \ -v $PWD:/var/lib/chronograf \ chronograf
$PWD to the directory where you want to store data associated with the InfluxDB container.
You can also have Docker control the volume mountpoint by using a named volume.
$ docker run -p 8888:8888 \ -v chronograf:/var/lib/chronograf \ chronograf
Using the container with InfluxDB
The instructions here are very similar to the instructions when using
influxdb. These examples assume you are using Docker’s built-in service discovery capability. In order to do so, we’ll first create a new network:
$ docker network create influxdb
Next, we’ll start our InfluxDB container named
$ docker run -d --name=influxdb \ --net=influxdb \ influxdb
We can now start a Chronograf container that references this database.
$ docker run -p 8888:8888 \ --net=influxdb chronograf --influxdb-url=http://influxdb:8086
Try combining this with Telegraf to get dashboards for your infrastructure within minutes!
See the official docs for information on creating visualizations.
chronograf images come in many flavors, each designed for a specific use case.
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
This image is based on the popular Alpine Linux project, available in the
alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn’t have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
To minimize image size, it’s uncommon for additional related tools (such as
bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the
alpine image description for examples of how to install packages if you are unfamiliar).
View license information for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the
As for any pre-built image usage, it is the image user’s responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.library, sample, chronograf