Install InfluxDB 3 Core

Upgrade to InfluxDB 3 Enterprise

If you want to upgrade from InfluxDB 3 Core to InfluxDB 3 Enterprise for features like high availability, read replicas, and historical query capability, see Upgrade to Enterprise.

System Requirements

Operating system

InfluxDB 3 Core runs on Linux, macOS, and Windows.

Object storage

A key feature of InfluxDB 3 is its use of object storage to store time series data in Apache Parquet format. You can choose to store these files on your local file system. Performance on your local filesystem will likely be better, but object storage has the advantage of not running out of space and being accessible by other systems over the network. InfluxDB 3 Core natively supports Amazon S3, Azure Blob Storage, and Google Cloud Storage. You can also use many local object storage implementations that provide an S3-compatible API, such as Minio.

Install

InfluxDB 3 Core runs on Linux, macOS, and Windows.

Choose one of the following methods to install InfluxDB 3 Core:

Quick install for Linux and macOS

To install InfluxDB 3 Core on Linux or macOS, download and run the quick installer script for InfluxDB 3 Core–for example, using curl to download the script:

curl -O https://www.influxdata.com/d/install_influxdb3.sh \
&& sh install_influxdb3.sh

The quick installer script is updated with each InfluxDB 3 Core release, so it always installs the latest version.

Production deployment

For production deployments, use Linux DEB or RPM for built-in systemd sandboxing, or Docker with your own container security configuration.

For detailed security options, see Manage security.

Download and install the latest build artifacts

You can also download and install InfluxDB 3 Core build artifacts directly:

macOS binaries

Pull the Docker image

Run the following command to pull the influxdb:3-core image, available for x86_64 (AMD64) and ARM64 architectures:

docker pull influxdb:3-core

Docker automatically pulls the appropriate image for your system architecture.

Pull for a specific system architecture

Pin to a specific version

Linux DEB or RPM

When installed via DEB or RPM on a systemd-enabled system, InfluxDB 3 Core runs in a sandboxed environment. The included systemd unit file configures the environment to provide security isolation for typical deployments. For more information, see Manage security.

DEB and RPM installation is recommended for non-Docker production deployments due to built-in systemd sandboxing.

DEB-based systems

RPM-based systems

TOML configuration (Linux)

After you install the DEB or RPM package, the InfluxDB 3 Core TOML configuration file is located at /etc/influxdb3/influxdb3-core.conf and contains the following settings:

Run as a system service (Linux)

InfluxDB 3 Core DEB and RPM installs include service files for running as a managed system service on Linux:

  • systemd: For modern Linux distributions
  • SysV init: For legacy system compatibility
Run using systemd

On systemd systems, the influxdb3-core unit file is enabled on install, but the unit is not started in order to allow configuration.

Start, stop, and restart

The following examples use sudo for systems that require elevated privileges. On some systems (such as Amazon Linux or other RHEL-based distributions where you may already be running as root), you can omit sudo from the commands.

# Start the service
sudo systemctl start influxdb3-core

# Stop the service
sudo systemctl stop influxdb3-core

# Restart the service (use after configuration changes)
sudo systemctl restart influxdb3-core
Check status and logs
# Check status (sudo to ensure full journal output)
sudo systemctl status influxdb3-core

# Quick state checks (no sudo needed)
systemctl is-enabled influxdb3-core
systemctl is-active  influxdb3-core

# Recent logs
sudo journalctl --unit influxdb3-core -n 200 --no-pager

# Follow logs
sudo journalctl --unit influxdb3-core -f
Inspect the packaged unit

The packaged unit configures security sandboxing for typical deployments (see Manage security). To inspect the packaged unit and its resolved properties:

# Show the unit file
systemctl cat influxdb3-core

# Show all resolved properties (paths, environment, sandboxing options)
systemctl show influxdb3-core
Apply configuration changes

Edit the TOML configuration file and restart the service to apply changes:

sudoedit /etc/influxdb3/influxdb3-core.conf
sudo systemctl restart influxdb3-core
sudo systemctl status  influxdb3-core
sudo journalctl --unit influxdb3-core -n 100 --no-pager

influxdb3 serve does not support configuration reload; a restart is required after editing the TOML file or changing environment variables.

The TOML file is read by the systemd launcher and converted to INFLUXDB3_* environment variables before influxdb3 serve runs; CLI flags still override values from the TOML file. For details, see TOML configuration files.

Run using SysV

On SysV init systems, influxdb3-core is disabled on install and can be enabled by adjusting /etc/default/influxdb3-core to contain ENABLED=yes.

To start the database, enter the following commands:

# Start the database
/etc/init.d/influxdb3-core start

# View status
/etc/init.d/influxdb3-core status

# View logs
tail -f /var/lib/influxdb3/influxdb3-core.log

Verify the installation

After installing InfluxDB 3 Core, enter the following command to verify that it installed successfully:

influxdb3 --version

If your system can’t locate influxdb3 following a quick install, source the configuration file (for example, .bashrc, .zshrc) for your shell–for example:

source ~/.zshrc

Was this page helpful?

Thank you for your feedback!