Portainer Templates logo

Portainer Templates

Influxdb Influxdb

Stack

Database

InfluxDB is an open source time series database for recording metrics, events, and analytics.

Configuration

Type
Compose
Platform
linux
Source
Repo

Template by xneo1·Source

Services

influxdb

Configuration

Image
influxdb:latest
Ports
8086:8086
Volumes
/var/lib/influxdb2 : /portainer/Files/AppData/Config/influxdb2

Image details

Pulls: 1.1B
User: library
Created: May 12, 2016
Updated: 1 day ago
Status: active

influxdb_cli

Configuration

Image
influxdb:latest
Entrypoint
./entrypoint.sh
Volumes
/var/lib/influxdb2 : /portainer/Files/AppData/Config/influxdb2/etc/ssl/influxdb-selfsigned.crt : /portainer/Files/AppData/Config/influxdb2/ssl/influxdb-selfsigned.crt/etc/ssl/influxdb-selfsigned.key : /portainer/Files/AppData/Config/influxdb2/ssl/influxdb-selfsigned.key
Env vars
DOCKER_INFLUXDB_INIT_MODE=setupDOCKER_INFLUXDB_INIT_USERNAME=myusernameDOCKER_INFLUXDB_INIT_PASSWORD=passwordpasswordpasswordDOCKER_INFLUXDB_INIT_ORG=myorgDOCKER_INFLUXDB_INIT_BUCKET=mybucketDOCKER_INFLUXDB_INIT_ADMIN_TOKEN=mytokenINFLUXD_TLS_CERT=/etc/ssl/influxdb-selfsigned.crtINFLUXD_TLS_KEY=/etc/ssl/influxdb-selfsigned.key
Restart
on-failure:10

Image details

Pulls: 1.1B
User: library
Created: May 12, 2016
Updated: 1 day ago
Status: active

Standalone Install

Select an install method, to see config/commands for deploying Influxdb

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Influxdb, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

services:
  influxdb:
    image: influxdb:latest
    volumes:
      # Mount for influxdb data directory and configuration
      - /portainer/Files/AppData/Config/influxdb2:/var/lib/influxdb2:rw
    ports:
      - "8086:8086"
  # Use the influx cli to set up an influxdb instance. 
  influxdb_cli:
    links:
      - influxdb
    image: influxdb:latest
    volumes:
      # Mount for influxdb data directory and configuration
      - /portainer/Files/AppData/Config/influxdb2:/var/lib/influxdb2:rw
      - /portainer/Files/AppData/Config/influxdb2/ssl/influxdb-selfsigned.crt:/etc/ssl/influxdb-selfsigned.crt:rw
      - /portainer/Files/AppData/Config/influxdb2/ssl/influxdb-selfsigned.key:/etc/ssl/influxdb-selfsigned.key:rw
    environment: 
      - DOCKER_INFLUXDB_INIT_MODE=setup
      - DOCKER_INFLUXDB_INIT_USERNAME=myusername
      - DOCKER_INFLUXDB_INIT_PASSWORD=passwordpasswordpassword
      - DOCKER_INFLUXDB_INIT_ORG=myorg
      - DOCKER_INFLUXDB_INIT_BUCKET=mybucket
      - DOCKER_INFLUXDB_INIT_ADMIN_TOKEN=mytoken
      - INFLUXD_TLS_CERT=/etc/ssl/influxdb-selfsigned.crt
      - INFLUXD_TLS_KEY=/etc/ssl/influxdb-selfsigned.key
    entrypoint: ["./entrypoint.sh"]
    restart: on-failure:10
    depends_on:
      - influxdb

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/influxdb2.yml up -d

More install options in our documentation.

Container Documentation

influxdb Documentation

InfluxDB is the open source time series database built for real-time analytic workloads.

influxdb_cli Documentation

InfluxDB is the open source time series database built for real-time analytic workloads.

Serve Influxdb on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying influxdb.example.com to http://influxdb:8086

Add this to your Caddyfile

influxdb.example.com {
	reverse_proxy http://influxdb:8086
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:8086 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :8086
  • Stop the other service, or pick a different host port. In 8086:8086 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:8086. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, influxdb2 can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 8086

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/influxdb2 (and the same for the other mapped folders)

Image won't pull

Test the pull directly on the host: docker pull influxdb:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Influxdb is a Compose stack, a set of containers (2 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.

The services

This stack is built from 2 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:

  • influxdb runs influxdb:latest
  • influxdb_cli runs influxdb:latest, starts after influxdb

Ports

A port is the door the app answers on. A mapping like 8086:8086 means it's reachable on port 8086 of your server, where the left number is yours to change and the right one belongs to the app. It opens:

  • 8086:8086

Volumes

A volume is where Influxdb keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /var/lib/influxdb2 from /portainer/Files/AppData/Config/influxdb2 on the host
  • /etc/ssl/influxdb-selfsigned.crt from /portainer/Files/AppData/Config/influxdb2/ssl/influxdb-selfsigned.crt on the host
  • /etc/ssl/influxdb-selfsigned.key from /portainer/Files/AppData/Config/influxdb2/ssl/influxdb-selfsigned.key on the host

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Influxdb takes 8 of them, all with defaults you can leave alone or tweak:

  • DOCKER_INFLUXDB_INIT_MODE, defaults to setup
  • DOCKER_INFLUXDB_INIT_USERNAME, defaults to myusername
  • DOCKER_INFLUXDB_INIT_PASSWORD, defaults to passwordpasswordpassword
  • DOCKER_INFLUXDB_INIT_ORG, defaults to myorg
  • DOCKER_INFLUXDB_INIT_BUCKET, defaults to mybucket
  • DOCKER_INFLUXDB_INIT_ADMIN_TOKEN, defaults to mytoken
  • INFLUXD_TLS_CERT, defaults to /etc/ssl/influxdb-selfsigned.crt
  • INFLUXD_TLS_KEY, defaults to /etc/ssl/influxdb-selfsigned.key

Restart policy

The restart policy here is on-failure:10, so Influxdb won't come back on its own after a crash or reboot. You bring it up again whenever you're ready. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Portainer puts these services on one shared private network, so they can find each other by name (like influxdb) while only the ports above are open to you.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Influxdb up. Add the template list to Portainer once, then deploying Influxdb is a click rather than a wall of config.