library/influxdbMaintained by:
InfluxData
Where to get help:
InfluxDB Discord Server (preferred for InfluxDB 3 Core, InfluxDB 3 Enterprise), InfluxDB Community Slack *(preferred for InfluxDB v2, v1)*
Dockerfile linksWhere to file issues:
https://github.com/influxdata/influxdata-docker/issues
Published image artifact details:
repo-info repo’s repos/influxdb/ directory (history)
(image metadata, transfer size, etc)
Image updates:
official-images repo’s library/influxdb label
official-images repo’s library/influxdb file (history)
Source of this description:
docs repo’s influxdb/ directory (history)
InfluxDB is the time series database platform designed to collect, store, and process large amounts of event and time series data. Ideal for monitoring (sensors, servers, applications, networks), financial analytics, and behavioral tracking.
… via docker compose
Example compose.yaml for influxdb:
# compose.yaml
name: influxdb3
services:
influxdb3-core:
container_name: influxdb3-core
image: influxdb:3-core
ports:
- 8181:8181
command:
- influxdb3
- serve
- --node-id=node0
- --object-store=file
- --data-dir=/var/lib/influxdb3/data
- --plugin-dir=/var/lib/influxdb3/plugins
volumes:
- type: bind
source: ~/.influxdb3/core/data
target: /var/lib/influxdb3/data
- type: bind
source: ~/.influxdb3/core/plugins
target: /var/lib/influxdb3/plugins
Alternatively, you can use the following command to start InfluxDB 3 Core:
docker run --rm -p 8181:8181 \
-v $PWD/data:/var/lib/influxdb3/data \
-v $PWD/plugins:/var/lib/influxdb3/plugins \
influxdb:3-core influxdb3 serve \
--node-id=my-node-0 \
--object-store=file \
--data-dir=/var/lib/influxdb3/data \
--plugin-dir=/var/lib/influxdb3/plugins
InfluxDB 3 Core starts with:
/var/lib/influxdb3/data8181After starting your InfluxDB 3 server, follow the Get Started guide to create an authorization token and start writing, querying, and processing data via the built-in influxdb3 CLI or the HTTP API.
Use the following tools with InfluxDB 3 Core:
Customize your instance with available server options:
docker run --rm influxdb:3-core influxdb3 serve --help
influxdb:3-core - Latest InfluxDB OSS (InfluxDB 3 Core)influxdb:2 - Previous generation OSS (InfluxDB v2)influxdb:1.11 - InfluxDB v1influxdb:3-core) - Latest OSSinfluxdb:2)influxdb:1.11)influxdb:3-enterprise)Adds unlimited data retention, compaction, clustering, and high availability to InfluxDB 3 Core.
For setup instructions, see the InfluxDB 3 Enterprise installation documentation.
influxdb:1.11-data - Data nodes for clusteringinfluxdb:1.11-meta - Meta nodes for cluster coordination (port 8091)For setup instructions, see the InfluxDB v1 Enterprise Docker documentation.
To migrate from v1 or v2 to InfluxDB 3:
InfluxDB v2 is a previous version. Consider InfluxDB 3 Core for new deployments.
Enter the following command to start InfluxDB v2 initialized with custom configuration:
docker run -d -p 8086:8086 \
-v $PWD/data:/var/lib/influxdb2 \
-v $PWD/config:/etc/influxdb2 \
-e DOCKER_INFLUXDB_INIT_MODE=setup \
-e DOCKER_INFLUXDB_INIT_USERNAME=my-user \
-e DOCKER_INFLUXDB_INIT_PASSWORD=my-password \
-e DOCKER_INFLUXDB_INIT_ORG=my-org \
-e DOCKER_INFLUXDB_INIT_BUCKET=my-bucket \
influxdb:2
After the container starts, visit http://localhost:8086 to view the UI.
For detailed instructions, see the InfluxDB v2 Docker Compose documentation.
InfluxDB v1 is a previous version. Consider InfluxDB 3 Core for new deployments.
docker run -d -p 8086:8086 \
-v $PWD:/var/lib/influxdb \
influxdb:1.11
This starts InfluxDB v1 with:
For more information, see the InfluxDB v1 Docker documentation. For v1 Enterprise installation, see the InfluxDB Enterprise v1 documentation.
The influxdb images come in many flavors, each designed for a specific use case.
influxdb:<version>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.
influxdb:<version>-alpineThis 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 useful when final image size being as small as possible is your primary concern. The main caveat to note is that it does use musl libc instead of glibc and friends, so software will often run into issues depending on the depth of their libc requirements/assumptions. 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 git or 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 repo-info repository’s influxdb/ directory.
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.