InfluxDB is an open source time-series database. It is designed to handle large write and read loads in real-time. It is a core component of the TICK (Telegraf, InfluxDB, Chronograf, Kapacitor) stack.

$ docker run --name influxdb bitnami/influxdb:latest

$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-influxdb/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d

• Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
• With Bitnami images the latest bug fixes and features are available as soon as possible.
• Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
• All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading linux distribution.
• All Bitnami images available in Docker Hub are signed with Docker Content Trust (DTC). You can use DOCKER_CONTENT_TRUST=1 to verify the integrity of the images.
• Bitnami container images are released daily with the latest distribution packages available.

This CVE scan report contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.

Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami InfluxDB Chart GitHub repository.

Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.

NOTE: Debian 8 images have been deprecated in favor of Debian 9 images. Bitnami will not longer publish new Docker images based on Debian 8.

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

• 1-ol-7, 1.7.9-ol-7-r58 (1/ol-7/Dockerfile)
• 1-debian-9, 1.7.9-debian-9-r33, 1, 1.7.9, 1.7.9-r33, latest (1/debian-9/Dockerfile)

Subscribe to project updates by watching the bitnami/influxdb GitHub repo.

The recommended way to get the Bitnami InfluxDB Docker Image is to pull the prebuilt image from the Docker Hub Registry.

$ docker pull bitnami/influxdb:latest

To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.

$ docker pull bitnami/influxdb:[TAG]

If you wish, you can also build the image yourself.

$ docker build -t bitnami/influxdb:latest 'https://github.com/bitnami/bitnami-docker-influxdb.git#master:1/debian-9'

If you remove the container all your data will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.

For persistence you should mount a directory at the /bitnami/influxdb path. If the mounted directory is empty, it will be initialized on the first run.

$ docker run \
    --volume /path/to/influxdb-persistence:/bitnami/influxdb \
    --env INFLUXDB_HTTP_AUTH_ENABLED=false \
    bitnami/influxdb:latest

You can also do this with a minor change to the docker-compose.yml file present in this repository:

InfluxDB:
  ...
  volumes:
    - /path/to/influxdb-persistence:/bitnami/influxdb
  ...

Using Docker container networking, a different server running inside a container can easily be accessed by your application containers and vice-versa.

Containers attached to the same network can communicate with each other using the container name as the hostname.

In this example, we will create a InfluxDB client instance that will connect to the server instance that is running on the same docker network as the client.

$ docker network create my-network --driver bridge

Use the --network <NETWORK> argument to the docker run command to attach the container to the my-network network.

$ docker run -d --name influxdb-server \
  --network my-network \
  --env INFLUXDB_HTTP_AUTH_ENABLED=false \
  bitnami/influxdb:latest

Finally we create a new container instance to launch the InfluxDB client and connect to the server created in the previous step:

$ docker run -it --rm \
    --network my-network \
    bitnami/influxdb:latest influx -host influxdb-server

When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new bridge network named my-network. In this example we assume that you want to connect to the InfluxDB server from your own custom application image which is identified in the following snippet by the service name myapp.

version: '2'

networks:
  my-network:
    driver: bridge

services:
  influxdb:
    image: bitnami/influxdb:latest
    environment:
      - INFLUXDB_HTTP_AUTH_ENABLED=false
    networks:
      - my-network
  myapp:
    image: 'YOUR_APPLICATION_IMAGE'
    networks:
      - my-network

IMPORTANT:

1. Please update the YOUR_APPLICATION_IMAGE placeholder in the above snippet with your application image
2. In your application container, use the hostname influxdb to connect to the InfluxDB server

Launch the containers using:

$ docker-compose up -d

InfluxDB can be configured via environment variables (prefixed with INFLUXDB_) or using a configuration file (influxdb.conf). If a configuration option is not specified in either the configuration file or in an environment variable, InfluxDB uses its internal default configuration.

Note: The settings at the environment variables override the equivalent options in the configuration file."

Find more information about all the available configuration options in the official documentation.

The configuration can easily be setup by mounting your own configuration file (influxdb.conf) on the directory /opt/bitnami/influxdb/etc/:

$ docker run --name influxdb \
    --volume /path/to/influxdb.conf:/opt/bitnami/influxdb/etc/influxdb.conf:ro \
    bitnami/influxdb:latest

or using Docker Compose:

version: '2'

services:
  influxdb:
    image: bitnami/influxdb:latest
    volumes:
      - /path/to/influxdb.conf:/opt/bitnami/influxdb/etc/influxdb.conf:ro

When the container is executed for the first time, it will execute the files with extensions .sh, and .txt located at /docker-entrypoint-initdb.d.

In order to have your custom files inside the docker image you can mount them as a volume.

The admin user and password can easily be setup with the Bitnami InfluxDB Docker image using the following environment variables:

• INFLUXDB_ADMIN_USER: The database admin user. Defaults to admin.
• INFLUXDB_ADMIN_USER_PASSWORD: The database admin user password. No defaults.

Passing the INFLUXDB_ADMIN_USER_PASSWORD environment variable when running the image for the first time will set the password of the INFLUXDB_ADMIN_USER user to the value of INFLUXDB_ADMIN_USER_PASSWORD.

$ docker run --name influxdb -e INFLUXDB_ADMIN_USER_PASSWORD=password123 bitnami/influxdb:latest

or by modifying the docker-compose.yml file present in this repository:

services:
  influxdb:
  ...
    environment:
      - INFLUXDB_ADMIN_USER_PASSWORD=password123
  ...

Warning In case you want to allow users to access the database without credentials, set the environment variable INFLUXDB_HTTP_AUTH_ENABLED=false. This is recommended only for development.

By default the InfluxDB image expects all the available passwords to be set. In order to allow empty passwords, it is necessary to set the INFLUXDB_HTTP_AUTH_ENABLED=false env variable. This env variable is only recommended for testing or development purposes. We strongly recommend specifying the INFLUXDB_ADMIN_USER_PASSWORD for any other scenario.

$ docker run --name influxdb --env INFLUXDB_HTTP_AUTH_ENABLED=false bitnami/influxdb:latest

or by modifying the docker-compose.yml file present in this repository:

services:
  influxdb:
  ...
    environment:
      - INFLUXDB_HTTP_AUTH_ENABLED=false
  ...

By passing the INFLUXDB_DB environment variable when running the image for the first time, a database will be created. This is useful if your application requires that a database already exists, saving you from having to manually create the database using the InfluxDB client.

$ docker run --name influxdb \
    -e INFLUXDB_ADMIN_USER_PASSWORD=password123 \
    -e INFLUXDB_DB=my_database \
    bitnami/influxdb:latest

or by modifying the docker-compose.yml file present in this repository:

services:
  influxdb:
  ...
    environment:
      - INFLUXDB_ADMIN_USER_PASSWORD=password123
      - INFLUXDB_DB=my_database
  ...

You can create a restricted database user that only has permissions for the database created with the INFLUXDB_DB environment variable. To do this, provide the INFLUXDB_USER environment variable and to set a password for the database user provide the INFLUXDB_USER_PASSWORD variable.

$ docker run --name influxdb \
  -e INFLUXDB_ADMIN_USER_PASSWORD=password123 \
  -e INFLUXDB_USER=my_user \
  -e INFLUXDB_USER_PASSWORD=my_password \
  -e INFLUXDB_DB=my_database \
  bitnami/influxdb:latest

or by modifying the docker-compose.yml file present in this repository:

services:
  influxdb:
  ...
    environment:
      - INFLUXDB_ADMIN_USER_PASSWORD=password123
      - INFLUXDB_USER=my_user
      - INFLUXDB_USER_PASSWORD=my_password
      - INFLUXDB_DB=my_database
  ...

You can also create users with restricted privileges in the database in a very similar way. To do so, user the environment variables below:

• INFLUXDB_READ_USER: Specify the user with "read" privileges in the database.
• INFLUXDB_READ_USER_PASSWORD: Specify the password of the INFLUXDB_READ_USER user.
• INFLUXDB_WRITE_USER: Specify the user with "write" privileges in the database.
• INFLUXDB_WRITE_USER_PASSWORD: Specify the password of the INFLUXDB_WRITE_USER user.

The Bitnami InfluxDB Docker image sends the container logs to stdout. To view the logs:

$ docker logs influxdb

You can configure the containers logging driver using the --log-driver option if you wish to consume the container logs differently. In the default configuration docker uses the json-file driver.

Bitnami provides up-to-date versions of InfluxDB, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.

$ docker pull bitnami/influxdb:latest

or if you're using Docker Compose, update the value of the image property to bitnami/influxdb:latest.

Stop the currently running container using the command

$ docker stop influxdb

or using Docker Compose:

$ docker-compose stop influxdb

Next, take a snapshot of the persistent volume /path/to/influxdb-persistence using:

$ rsync -a /path/to/influxdb-persistence /path/to/influxdb-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)

$ docker rm -v influxdb

or using Docker Compose:

$ docker-compose rm -v influxdb

Re-create your container from the new image.

$ docker run --name influxdb bitnami/influxdb:latest

or using Docker Compose:

$ docker-compose up influxdb

We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.

If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:

• Host OS and version
• Docker version (docker version)
• Output of docker info
• Version of this container
• The command you used to run the container, and any relevant output you saw (masking any sensitive information)

Copyright (c) 2019 Bitnami

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.