Public | Automated Build

Last pushed: a year ago
Short Description
Legacy Influxdb 0.8 image for those poor souls out there, that still need to use it!
Full Description

Supported tags and respective Dockerfile links

What is it?

TimeSeriesAwesomeStuff -> InfluxDB and basically the legacy 0.8 line that is no longer supported. Currently we use this image in-house and there are no plans, to ever upgrade to 0.9 / 1.0+; for this you should use the upcoming official influxdb image or for the time being tutum/influxdb/.

How to use this image

Start a influxdb instance

Starting an Influxdb instance is simple:

$ docker run --name some-influxdb -d zalari/influxdb:tag

... where some-influxdb is the name you want to assign to your container. The default admin / password is always: root:root.

Connect to InfluxDB from an application in another Docker container

This image exposes the standard API port (8086) and the WebUI (8083), so container linking makes the influxdb instance available to other application containers. Start your application container like this in order to link it to the InfluxDB container:

$ docker run --name some-app --link some-influxdb:influxdb -d application-that-uses-influxdb

Container shell access and viewing InfluxDB logs

The docker exec command allows you to run commands inside a Docker container. The following command line will give you a bash shell inside your influxdb container:

    $ docker exec -it some-influxdb bash

The influxdb Server log is available through Docker's container log:

$ docker logs some-influxdb

Where to Store Data

Important note: There are several ways to store data used by applications that run in Docker containers. We encourage users of the influxdb images to familiarize themselves with the options available, including:

  • Let Docker manage the storage of your database data by writing the database files to disk on the host system using its own internal volume management. This is the default and is easy and fairly transparent to the user. The downside is that the files may be hard to locate for tools and applications that run directly on the host system, i.e. outside containers.
  • Create a data directory on the host system (outside the container) and mount this to a directory visible from inside the container. This places the database files in a known location on the host system, and makes it easy for tools and applications on the host system to access the files. The downside is that the user needs to make sure that the directory exists, and that e.g. directory permissions and other security mechanisms on the host system are set up correctly.

The Docker documentation is a good starting point for understanding the different storage options and variations, and there are multiple blogs and forum postings that discuss and give advice in this area. We will simply show the basic procedure here for the latter option above:

  1. Create a data directory on a suitable volume on your host system, e.g. /my/own/datadir.
  2. Start your influxdb container like this:

    $ docker run --name some-influxdb -v /my/own/datadir:/opt/influxdb/shared/data -d influxdb:0.8

The -v /my/own/datadir:/opt/influxdb/shared/data part of the command mounts the /my/own/datadir directory from the underlying host system as /opt/influxdb/shared/data inside the container, where influxdb by default will write its data files.

Note that users on host systems with SELinux enabled may see issues with this. The current workaround is to assign the relevant SELinux policy type to the new data directory so that the container will be allowed to access it:

$ chcon -Rt svirt_sandbox_file_t /my/own/datadir

Supported Docker versions

This image is has been tested with Docker Engine 1.9+.

Please see the Docker installation documentation for details on how to upgrade your Docker daemon.

Docker Pull Command
Source Repository

Comments (0)