Install and run InfluxDB 3 Explorer with Docker

  • InfluxDB 3 Core and Enterprise

How you install Explorer depends on your InfluxDB 3 server

Starting with InfluxDB 3 Enterprise v3.11, Explorer is included with the server and runs as WebAssembly (WASM)–there’s no separate container to install. Docker is required for InfluxDB 3 Core and Enterprise earlier than v3.11, and remains an option for later Enterprise releases. See Install Explorer to find the instructions for your server.

Use Docker to install and run InfluxDB 3 Explorer as a standalone container with InfluxDB 3 Core or InfluxDB 3 Enterprise, including Enterprise v3.11 and later. Starting with Enterprise v3.11, Explorer is also available as an integrated WebAssembly (WASM) component of the server. See Use the integrated Explorer UI if you run Enterprise v3.11 or later and don’t need a separate container.

Control who can reach Explorer

Anyone who can reach the Explorer port can use the InfluxDB connection that you configure in Explorer, with that token’s permissions. By default, Docker publishes a container port on all network interfaces (0.0.0.0) and adds its own firewall rules, which can take effect even when a host firewall (such as ufw or firewalld) is set to block the port.

The examples in this guide publish Explorer on the loopback interface (127.0.0.1) so it’s reachable only from the same machine. Before you make Explorer reachable from other hosts, see Network exposure and access control.

Quick start

Get InfluxDB 3 Explorer running in minutes:

  1. Run the Explorer container:

    docker run --detach \
  --name influxdb3-explorer \
  --publish 127.0.0.1:8888:8080 \
  influxdata/influxdb3-ui:1.11.0