--- title: Install InfluxDB OSS v2 description: Download, install, and set up InfluxDB OSS. url: https://docs.influxdata.com/influxdb/v2/install/ estimated_tokens: 15728 product: InfluxDB OSS v2 version: v2 --- # Install InfluxDB OSS v2 This page documents an earlier version of InfluxDB OSS. [InfluxDB 3 Core](/influxdb3/core/) is the latest stable version. #### API token hashing is enabled by default in InfluxDB OSS 2.9.0 Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — **capture any plaintext tokens you still need before you upgrade**. For more information, see [Token hashing](/influxdb/v2/admin/tokens/#token-hashing). The InfluxDB v2 time series platform is purpose-built to collect, store, process and visualize metrics and events. - [Download and install InfluxDB v2](#download-and-install-influxdb-v2) - [Start InfluxDB](#start-influxdb) - [Download, install, and configure the `influx` CLI](#download-install-and-configure-the-influx-cli) ## Download and install InfluxDB v2 Recommended:: Before you open and install packages and downloaded files, use SHA checksum verification and GPG signature verification to ensure the files are intact and authentic. InfluxDB installation instructions for some OS versions include steps to verify downloaded files before you install them. For more information about SHA and GPG verifications, see the following: [](#choose-the-influxdata-key-pair-for-your-os-version) Choose the InfluxData key-pair for your OS version *Before running the installation steps, substitute the InfluxData key-pair compatible with your OS version:* For newer releases (for example, Ubuntu 20.04 LTS and newer, Debian Buster and newer) that support subkey verification: - GPG key file: [`influxdata-archive.key`](https://repos.influxdata.com/influxdata-archive.key) - Primary key fingerprint: `24C975CBA61A024EE1B631787C3D57159FC2F927` For older versions (for example, CentOS/RHEL 7, Ubuntu 18.04 LTS, or Debian Stretch) that don’t support subkeys for verification: - GPG key file: [`influxdata-archive_compat.key`](https://repos.influxdata.com/influxdata-archive_compat.key) - Signing key fingerprint: `9D539D90D3328DC7D6C8D3B9D8FF8E1F7DF8B07E` [](#verify-download-integrity-using-sha-256) Verify download integrity using SHA-256 For each released binary, InfluxData publishes the SHA checksum that you can use to verify that the downloaded file is intact and hasn’t been corrupted. To use the SHA checksum to verify the downloaded file, do the following: 1. In the [downloads page](https://www.influxdata.com/downloads), select the **Version** and **Platform** for your download, and then copy the **SHA256:** checksum value. 2. Compute the SHA checksum of the downloaded file and compare it to the published checksum–for example, enter the following command in your terminal: ```bash # Use 2 spaces to separate the checksum from the filename echo "8d7872013cad3524fb728ca8483d0adc30125ad1af262ab826dcf5d1801159cf influxdb2-2.9.1_linux_amd64.tar.gz" \ | sha256sum --check - ``` Replace the following: - `8d7872013cad3524fb728ca8483d0adc30125ad1af262ab826dcf5d1801159cf`: the **SHA256:** checksum value that you copied from the downloads page If the checksums match, the output is the following; otherwise, an error message. ``` influxdb2-2.9.1_linux_amd64.tar.gz: OK ``` [](#verify-file-integrity-and-authenticity-using-gpg) Verify file integrity and authenticity using GPG InfluxData uses [GPG (GnuPG)](https://www.gnupg.org/software/) to sign released software and provides public key and encrypted private key (`.key` file) pairs that you can use to verify the integrity of packages and binaries from the InfluxData repository. Most operating systems include `gpg` by default. *If `gpg` isn’t available on your system, see [GnuPG download](https://gnupg.org/download/) and install instructions.* The following steps guide you through using GPG to verify InfluxDB binary releases: 1. [Choose the InfluxData key-pair for your OS version](#choose-the-influxdata-key-pair-for-your-os-version). 2. Download and import the InfluxData public key. `gpg --import` outputs to stderr. The following example shows how to import the key, redirect the output to stdout, and then check for the expected key name: ```sh curl --silent --location https://repos.influxdata.com/influxdata-archive.key \ | gpg --import - 2>&1 \ | grep 'InfluxData Package Signing Key ' ``` Replace the following: - `https://repos.influxdata.com/influxdata-archive.key`: the InfluxData private key file compatible with your OS version If successful, the output is the following: ``` gpg: key 7C3D57159FC2F927: public key "InfluxData Package Signing Key " imported ``` 3. Download the signature file for the release by appending `.asc` to the download URL, and then use `gpg` to verify the download signature–for example, enter the following in your terminal: ```sh curl --silent --location \ https://download.influxdata.com/influxdb/releases/v2.9.1/influxdb2-2.9.1_darwin_amd64.tar.gz.asc \ | gpg --verify - ~/Downloads/influxdb2-2.9.1_darwin_amd64.tar.gz \ 2>&1 | grep 'InfluxData Package Signing Key ' ``` - `curl --silent --location`: Follows any server redirects and fetches the signature file silently (without progress meter). - `gpg --verify -`: Reads the signature from stdin and uses it to verify the the downloaded `influxdbv2` binary. If successful, the output is the following: ``` gpg: Good signature from "InfluxData Package Signing Key " [unknown] ``` *For security, InfluxData periodically rotates keys and publishes the new key pairs.* The following instructions include steps for downloading, verifying, and installing InfluxDB: **macOS:** To install InfluxDB, do one of the following: - [Install using Homebrew](#install-using-homebrew) - [Manually download and install for macOS](#manually-download-and-install-for-macos) We recommend using [Homebrew](https://brew.sh/) to install InfluxDB v2 on macOS. #### InfluxDB and the influx CLI are separate packages The InfluxDB server ([`influxd`](/influxdb/v2/reference/cli/influxd/)) and the [`influx` CLI](/influxdb/v2/reference/cli/influx/) are packaged and versioned separately. *You’ll install the `influx CLI` in a [later step](#download-install-and-configure-the-influx-cli).* ### Install using Homebrew ```sh brew update brew install influxdb ``` ### Manually download and install for macOS 1. In your browser or your terminal, download the InfluxDB package. [InfluxDB v2 (macOS)](https://download.influxdata.com/influxdb/releases/v2.9.1/influxdb2-2.9.1_darwin_amd64.tar.gz) ```sh # Download using cURL curl --location -O \ "https://download.influxdata.com/influxdb/releases/v2.9.1/influxdb2-2.9.1_darwin_amd64.tar.gz" ``` 2. Recommended:: Verify the integrity of the download–for example, enter the following command in your terminal: ```sh # Use 2 spaces to separate the checksum from the filename echo "224926fd77736a364cf28128f18927dda00385f0b6872a108477246a1252ae1b influxdb2-2.9.1_darwin_amd64.tar.gz" \ | shasum --algorithm 256 --quiet --check - ``` Replace the following: - `224926fd77736a364cf28128f18927dda00385f0b6872a108477246a1252ae1b`: the SHA checksum from the [downloads page](https://www.influxdata.com/downloads/#telegraf) 3. Unpackage the InfluxDB binary. Do one of the following: - In **Finder**, double-click the downloaded package file. - In your terminal (for example, **Terminal** or **[iTerm2](https://www.iterm2.com/)**), use `tar` to unpackage the file–for example, enter the following command to extract it into the current directory: ```sh # Unpackage contents to the current working directory tar zxvf ./influxdb2-2.9.1_darwin_amd64.tar.gz ``` 4. Optional: Place the `influxd` binary in your `$PATH`–for example, copy the binary to `/usr/local/bin`: ```sh # (Optional) Copy the influxd binary to your $PATH sudo cp influxdb2-2.9.1/influxd /usr/local/bin/ ``` With the `influxd` binary in your `$PATH` (`/usr/local/bin`), you can enter `influxd` in your terminal to start the server. If you choose not to move the `influxd` binary into your `$PATH`, enter the path to the binary to start the server–for example: ```sh ./influxdb2-2.9.1/influxd ``` [](#recommended--set-appropriate-directory-permissions) Recommended – Set appropriate directory permissions To prevent unwanted access to data, set the permissions on the influxdb `data-dir` to not be world readable. If installing on a server, set a umask of `0027` to properly permission all newly created files–for example, enter the following command in your terminal: ```bash chmod 0750 ~/.influxdbv2 ``` Both InfluxDB 1.x and 2.x have associated `influxd` and `influx` binaries. If InfluxDB 1.x binaries are already in your `$PATH`, run the v2 binaries in place or rename them before putting them in your `$PATH`. If you rename the binaries, all references to `influxd` and `influx` in this documentation refer to your renamed binaries. **Linux:** To install InfluxDB on Linux, do one of the following: - [Install InfluxDB as a service with systemd](#install-influxdb-as-a-service-with-systemd) - [Manually download and install the influxd binary](#manually-download-and-install-the-influxd-binary) #### InfluxDB and the influx CLI are separate packages The InfluxDB server ([`influxd`](/influxdb/v2/reference/cli/influxd/)) and the [`influx` CLI](/influxdb/v2/reference/cli/influx/) are packaged and versioned separately. *You’ll install the `influx CLI` in a [later step](#download-install-and-configure-the-influx-cli).* ### Install InfluxDB as a service with systemd 1. [Choose the InfluxData key-pair for your OS version](#choose-the-influxdata-key-pair-for-your-os-version). 2. Run the command for your OS version to install the InfluxData key, add the InfluxData repository, and install `influxdb`. *Before running the command, replace the fingerprint and key filename with the key-pair from the preceding step.* ```bash # Ubuntu and Debian # Add the InfluxData key to verify downloads and add the repository curl --silent --location -O https://repos.influxdata.com/influxdata-archive.key gpg --show-keys --with-fingerprint --with-colons ./influxdata-archive.key 2>&1 \ | grep -q '^fpr:\+24C975CBA61A024EE1B631787C3D57159FC2F927:$' \ && cat influxdata-archive.key \ | gpg --dearmor \ | sudo tee /etc/apt/keyrings/influxdata-archive.gpg > /dev/null \ && echo 'deb [signed-by=/etc/apt/keyrings/influxdata-archive.gpg] https://repos.influxdata.com/debian stable main' \ | sudo tee /etc/apt/sources.list.d/influxdata.list # Install influxdb sudo apt-get update && sudo apt-get install influxdb2 ``` ```bash # RedHat and CentOS # Add the InfluxData key to verify downloads curl --silent --location -O https://repos.influxdata.com/influxdata-archive.key gpg --show-keys --with-fingerprint --with-colons ./influxdata-archive.key 2>&1 \ | grep -q '^fpr:\+24C975CBA61A024EE1B631787C3D57159FC2F927:$' \ && cat influxdata-archive.key \ | gpg --dearmor \ | tee /etc/pki/rpm-gpg/RPM-GPG-KEY-influxdata > /dev/null # Add the InfluxData repository to the repository list. cat < Active: active (running) ``` For information about where InfluxDB stores data on disk when running as a service, see [File system layout](/influxdb/v2/reference/internals/file-system-layout/?t=Linux#installed-as-a-package). #### Pass configuration options to the service You can use systemd to customize [InfluxDB configuration options](/influxdb/v2/reference/config-options/#configuration-options) and pass them to the InfluxDB service. 1. Edit the `/etc/default/influxdb2` service configuration file to assign configuration directives to `influxd` command line flags–for example, add one or more `=` lines like the following: ```sh ARG1="--http-bind-address :8087" ARG2="--storage-wal-fsync-delay=15m" ``` 2. Edit the `/lib/systemd/system/influxdb.service` file to pass the variables to the `ExecStart` value: ```sh ExecStart=/usr/bin/influxd $ARG1 $ARG2 ``` ### Manually download and install the influxd binary *If necessary, adjust the example file paths and utilities for your system.* 1. In your browser or your terminal, download the InfluxDB binary for your system architecture (AMD64 or ARM). [InfluxDB v2 (amd64)](https://download.influxdata.com/influxdb/releases/v2.9.1/influxdb2-2.9.1_linux_amd64.tar.gz) [InfluxDB v2 (arm)](https://download.influxdata.com/influxdb/releases/v2.9.1/influxdb2-2.9.1_linux_arm64.tar.gz) ```sh # Use curl to download the amd64 binary. curl --location -O \ https://download.influxdata.com/influxdb/releases/v2.9.1/influxdb2-2.9.1_linux_amd64.tar.gz ``` ```sh # Use curl to download the arm64 binary. curl --location -O \ https://download.influxdata.com/influxdb/releases/v2.9.1/influxdb2-2.9.1_linux_arm64.tar.gz ``` 2. [Choose the InfluxData key-pair for your OS version](#choose-the-influxdata-key-pair-for-your-os-version). 3. Recommended:: Verify the authenticity of the downloaded binary–for example, enter the following command in your terminal. *Before running the command for your system, replace `https://repos.influxdata.com/influxdata-archive.key` with the key URL from the preceding step.* ```bash # amd64 # Download and import the key curl --silent --location https://repos.influxdata.com/influxdata-archive.key \ | gpg --import - 2>&1 \ | grep 'InfluxData Package Signing Key ' \ && # Download and verify the binary's signature file curl --silent --location "https://download.influxdata.com/influxdb/releases/v2.9.1/influxdb2-2.9.1_linux_amd64.tar.gz.asc" \ | gpg --verify - influxdb2-2.9.1_linux_amd64.tar.gz \ 2>&1 | grep 'InfluxData Package Signing Key ' ``` ```bash # arm64 # Download and import the key curl --silent --location https://repos.influxdata.com/influxdata-archive.key \ | gpg --import - 2>&1 \ | grep 'InfluxData Package Signing Key ' \ && # Download and verify the binary's signature file curl --silent --location "https://download.influxdata.com/influxdb/releases/v2.9.1/influxdb2-2.9.1_linux_arm64.tar.gz.asc" \ | gpg --verify - influxdb2-2.9.1_linux_arm64.tar.gz \ 2>&1 | grep 'InfluxData Package Signing Key ' ``` If successful, the output is similar to the following: ``` gpg: Good signature from "InfluxData Package Signing Key " [unknown] ``` 4. Extract the downloaded binary–for example, enter the following command for your system: ```bash # amd64 tar xvzf ./influxdb2-2.9.1_linux_amd64.tar.gz ``` ```bash # arm64 tar xvzf ./influxdb2-2.9.1_linux_arm64.tar.gz ``` 5. Optional: Place the extracted `influxd` executable binary in your system `$PATH`. ```bash # amd64 sudo cp ./influxdb2-2.9.1/usr/bin/influxd /usr/local/bin/ ``` ```bash # arm64 sudo cp ./influxdb2-2.9.1/usr/bin/influxd /usr/local/bin/ ``` If you choose to not move the `influxd` binary into your `$PATH`, enter the path to the binary to start the server–for example: ```bash ./influxdb2-2.9.1/usr/bin/influxd ``` [](#recommended--set-appropriate-directory-permissions) Recommended – Set appropriate directory permissions To prevent unwanted access to data, set the permissions on the influxdb `data-dir` to not be world readable. If installing on a server, we recommend setting a umask of `0027` to properly permission all newly created files. To set umask, use a UMask directive in a systemd unit file or run Influxdb as a specific user that has the umask properly set–for example, enter the following command in your terminal: ```sh chmod 0750 ~/.influxdbv2 ``` **Windows:** ### System requirements - Windows 10 - 64-bit AMD architecture - [Powershell](https://docs.microsoft.com/powershell/) or [Windows Subsystem for Linux (WSL)](https://docs.microsoft.com/en-us/windows/wsl/) ### Command line examples Use **Powershell** or **WSL** to execute `influx` and `influxd` commands. The command line examples in this documentation use `influx` and `influxd` as if installed on the system `PATH`. If these binaries are not installed on your `PATH`, replace `influx` and `influxd` in the provided examples with `./influx` and `./influxd` respectively. #### InfluxDB and the influx CLI are separate packages The InfluxDB server ([`influxd`](/influxdb/v2/reference/cli/influxd/)) and the [`influx` CLI](/influxdb/v2/reference/cli/influx/) are packaged and versioned separately. *You’ll install the `influx CLI` in a [later step](#download-install-and-configure-the-influx-cli).* [InfluxDB v2 (Windows)](https://download.influxdata.com/influxdb/releases/v2.9.1/influxdb2-2.9.1-windows_amd64.zip) Expand the downloaded archive into `C:\Program Files\InfluxData\` and rename the files if desired. ```powershell Expand-Archive .\influxdb2-2.9.1-windows_amd64.zip -DestinationPath 'C:\Program Files\InfluxData\' mv 'C:\Program Files\InfluxData\influxdb2-2.9.1-windows-amd64' 'C:\Program Files\InfluxData\influxdb' ``` [](#recommended--set-appropriate-directory-permissions) Recommended – Set appropriate directory permissions To prevent unwanted access to data, we recommend setting the permissions on the influxdb `data-dir` to not be world readable–for example: enter the following commands in your terminal: ```powershell $acl = Get-Acl "C:\Users\\.influxdbv2" $accessRule = New-Object System.Security.AccessControl.FileSystemAccessRule("everyone","Read","Deny") $acl.SetAccessRule($accessRule) $acl | Set-Acl "C:\Users\\.influxdbv2" ``` **Docker:** ### Install and set up InfluxDB in a container The following steps show how to use the [Docker CLI](https://docs.docker.com/reference/cli/docker/) to set up and run InfluxDB. but you can also [use Docker Compose](/influxdb/v2/install/use-docker-compose). *The following guide uses Docker mounted [volumes](https://docs.docker.com/storage/volumes/) to persist InfluxDB configuration and data. Persisting your data to a file system outside the container ensures that your data isn’t deleted if you delete the container.* 1. Install [Docker Desktop](https://www.docker.com/get-started/) for your system. 2. Start a Docker container from the [`influxdb` Docker Hub image](https://hub.docker.com/_/influxdb)–for example, in your terminal, enter the `docker run influxdb:2` command with command line flags for initial setup options and file system mounts. *If you don’t specify InfluxDB initial setup options, you can [set up manually](/influxdb/v2/get-started/setup/) later using the UI or CLI in a running container.* ```bash docker run \ --name influxdb2 \ --publish 8086:8086 \ --mount type=volume,source=influxdb2-data,target=/var/lib/influxdb2 \ --mount type=volume,source=influxdb2-config,target=/etc/influxdb2 \ --env DOCKER_INFLUXDB_INIT_MODE=setup \ --env DOCKER_INFLUXDB_INIT_USERNAME=ADMIN_USERNAME \ --env DOCKER_INFLUXDB_INIT_PASSWORD=ADMIN_PASSWORD \ --env DOCKER_INFLUXDB_INIT_ORG=ORG_NAME \ --env DOCKER_INFLUXDB_INIT_BUCKET=BUCKET_NAME \ influxdb:2 ``` The command passes the following arguments: - `--publish 8086:8086`: Exposes the InfluxDB [UI](/influxdb/v2/get-started/#influxdb-user-interface-ui) and [HTTP API](/influxdb/v2/reference/api/) on the host’s `8086` port. - `--mount type=volume,source=influxdb2-data,target=/var/lib/influxdb2`: Creates a volume named `influxdb2-data` mapped to the [InfluxDB data directory](/influxdb/v2/reference/internals/file-system-layout/?t=docker#file-system-layout) to persist data outside the container. - `--mount type=volume,source=influxdb2-config,target=/etc/influxdb2`: Creates a volume named `influxdb2-config` mapped to the [InfluxDB configuration directory](/influxdb/v2/reference/internals/file-system-layout/?t=docker#file-system-layout) to make configurations available outside the container. - `--env DOCKER_INFLUXDB_INIT_MODE=setup`: Environment variable that invokes the automated setup of the initial organization, user, bucket, and token when creating the container. - `--env DOCKER_INFLUXDB_INIT_`: Environment variables for initial setup options–replace the following with your own values: - `ADMIN_USERNAME`: The username for the initial [user](/influxdb/v2/admin/users/)–an admin user with an API [Operator token](/influxdb/v2/admin/tokens/#operator-token). - `ADMIN_PASSWORD`: The password for the initial [user](/influxdb/v2/admin/users/). - `ORG_NAME`: The name for the initial [organization](/influxdb/v2/admin/organizations/). - `BUCKET_NAME`: The name for the initial [bucket](/influxdb/v2/admin/buckets/). If successful, the command starts InfluxDB initialized with the user, organization, bucket, and *[Operator token](/influxdb/v2/admin/tokens/#operator-token)*, and logs to stdout. You can view the Operator token in the `/etc/influxdb2/influx-configs` file and use it to authorize [creating an All Access token](#examples). For more information, see [API token types](/influxdb/v2/admin/tokens/#api-token-types). *To run the InfluxDB container in [detached mode](https://docs.docker.com/engine/reference/run/#detached-vs-foreground), include the `--detach` flag in the `docker run` command.* For more InfluxDB configuration options, see the [`influxdb` Docker Hub image](https://hub.docker.com/_/influxdb) documentation. ### Run InfluxDB CLI commands in a container When you start a container using the `influxdb` Docker Hub image, it also installs the [`influx` CLI](/influxdb/v2/tools/influx-cli/) in the container. With InfluxDB setup and running in the container, you can use the Docker CLI [`docker exec`](https://docs.docker.com/reference/cli/docker/container/exec/) command to interact with the `influx` and `influxd` CLIs inside the container. #### Syntax ```bash docker exec -it ` ``` #### Examples ```bash # Create an All Access token docker exec -it influxdb2 influx auth create \ --all-access \ --token OPERATOR_TOKEN ``` ```bash # List CLI configurations docker exec -it influxdb2 influx config ls ``` ```bash # View the server configuration docker exec -it influxdb2 influx server-config # Inspect server details docker exec -it influxdb2 influxd inspect -d ``` ### Manage files in mounted volumes To copy files, such as the InfluxDB server `config.yml` file, between your local file system and a volume, use the [`docker container cp` command](https://docs.docker.com/reference/cli/docker/container/cp/). **Kubernetes:** ### Install InfluxDB in a Kubernetes cluster The instructions below use **minikube** or **kind**, but the steps should be similar in any Kubernetes cluster. InfluxData also makes [Helm charts](https://github.com/influxdata/helm-charts) available. 1. Install [minikube](https://kubernetes.io/docs/tasks/tools/install-minikube/) or [kind](https://kind.sigs.k8s.io/docs/user/quick-start/#installation). 2. Start a local cluster: ```bash # with minikube minikube start ``` ```bash # with kind kind create cluster ``` 3. Apply the [sample InfluxDB configuration](https://github.com/influxdata/docs-v2/blob/master/static/downloads/influxdb-k8-minikube.yaml) by running: ```bash kubectl apply -f https://raw.githubusercontent.com/influxdata/docs-v2/master/static/downloads/influxdb-k8-minikube.yaml ``` This creates an `influxdb` Namespace, Service, and StatefulSet. A PersistentVolumeClaim is also created to store data written to InfluxDB. **Important**: always inspect YAML manifests before running `kubectl apply -f `! 4. Ensure the Pod is running: ```bash kubectl get pods -n influxdb ``` 5. Ensure the Service is available: ```bash kubectl describe service -n influxdb influxdb ``` You should see an IP address after `Endpoints` in the command’s output. 6. Forward port 8086 from inside the cluster to localhost: ```bash kubectl port-forward -n influxdb service/influxdb 8086:8086 ``` **Raspberry Pi:** ### Requirements To run InfluxDB on Raspberry Pi, you need: - a Raspberry Pi 4+ or 400 - a 64-bit operating system. Recommended:: a [64-bit version of Ubuntu](https://ubuntu.com/download/raspberry-pi) of Ubuntu Desktop or Ubuntu Server compatible with 64-bit Raspberry Pi. ### Install Linux binaries Follow the [Linux installation instructions](/influxdb/v2/install/?t=Linux#install-linux) to install InfluxDB on a Raspberry Pi. ### Monitor your Raspberry Pi Use the [InfluxDB Raspberry Pi template](/influxdb/cloud/monitor-alert/templates/infrastructure/raspberry-pi/) to easily configure collecting and visualizing system metrics for the Raspberry Pi. #### Monitor 32-bit Raspberry Pi systems If you have a 32-bit Raspberry Pi, [use Telegraf](/telegraf/v1/) to collect and send data to: - [InfluxDB OSS](/influxdb/v2/), running on a 64-bit system - InfluxDB Cloud with a [**Free Tier**](/influxdb/cloud/account-management/pricing-plans/#free-plan) account - InfluxDB Cloud with a paid [**Usage-Based**](/influxdb/cloud/account-management/pricing-plans/#usage-based-plan) account with relaxed resource restrictions. ## Start InfluxDB If it isn’t already running, follow the instructions to start InfluxDB on your system: **macOS:** To start InfluxDB, run the `influxd` daemon: ```bash influxd ``` #### (macOS Catalina and newer) Authorize the influxd binary macOS requires downloaded binaries to be signed by registered Apple developers. Currently, when you first attempt to run `influxd`, macOS will prevent it from running. To manually authorize the `influxd` binary, follow the instructions for your macOS version to allow downloaded applications. ##### Run InfluxDB on macOS Ventura 1. Follow the preceding instructions to attempt to start `influxd`. 2. Open **System Settings** and click **Privacy & Security**. 3. Under the **Security** heading, there is a message about “influxd” being blocked, click **Allow Anyway**. 4. When prompted, enter your password to allow the setting. 5. Close **System Settings**. 6. Attempt to start `influxd`. 7. A prompt appears with the message *“macOS cannot verify the developer of “influxd”…”"*. Click **Open**. ##### Run InfluxDB on macOS Catalina 1. Attempt to start `influxd`. 2. Open **System Preferences** and click **Security & Privacy**. 3. Under the **General** tab, there is a message about `influxd` being blocked. Click **Open Anyway**. We are in the process of updating the build process to ensure released binaries are signed by InfluxData. #### “too many open files” errors After running `influxd`, you might see an error in the log output like the following: ```text too many open files ``` To resolve this error, follow the [recommended steps](https://unix.stackexchange.com/a/221988/471569) to increase file and process limits for your operating system version then restart `influxd`. **Linux:** If InfluxDB was installed as a systemd service, systemd manages the `influxd` daemon and no further action is required. If the binary was manually downloaded and added to the system `$PATH`, start the `influxd` daemon with the following command: ```bash influxd ``` **Windows:** In **Powershell**, navigate into `C:\Program Files\InfluxData\influxdb` and start InfluxDB by running the `influxd` daemon: ```powershell cd -Path 'C:\Program Files\InfluxData\influxdb' ./influxd ``` #### Grant network access When starting InfluxDB for the first time, **Windows Defender** appears with the following message: > Windows Defender Firewall has blocked some features of this app. 1. Select **Private networks, such as my home or work network**. 2. Click **Allow access**. **Docker:** To use the Docker CLI to start an existing container, enter the following command: ```bash docker start influxdb2 ``` Replace `influxdb2` with the name of your container. To start a new container, follow instructions to [install and set up InfluxDB in a container](?t=docker#install-and-set-up-influxdb-in-a-container). **Kubernetes:** To start InfluxDB using Kubernetes, follow instructions to [install InfluxDB in a Kubernetes cluster](?t=kubernetes#download-and-install-influxdb-v2). If successful, you can view the InfluxDB UI at [http://localhost:8086](http://localhost:8086). InfluxDB starts with default settings, including the following: - `http-bind-address=:8086`: Uses port `8086` (TCP) for InfluxDB UI and HTTP API client-server communication. - `reporting-disabled=false`: Sends InfluxDB telemetry information back to InfluxData. To override default settings, specify [configuration options](/influxdb/v2/reference/config-options) when starting InfluxDB–for example: [](#configure-the-port-or-address) Configure the port or address By default, the InfluxDB UI and HTTP API use port `8086`. To specify a different port or address, override the [`http-bind-address` option](/influxdb/v2/reference/config-options/#http-bind-address) when starting `influxd`–for example: **Linux:** ```bash influxd --http-bind-address ``` **Windows Powershell:** ```powershell ./influxd --http-bind-address ``` [](#opt-out-of-telemetry-reporting) Opt-out of telemetry reporting By default, InfluxDB sends telemetry data back to InfluxData. The [InfluxData telemetry](https://www.influxdata.com/telemetry) page provides information about what data is collected and how it is used. To opt-out of sending telemetry data back to InfluxData, specify the [`reporting-disabled` option](/influxdb/v2/reference/config-options/#reporting-disabled) when starting `influxd`–for example: **Linux:** ```bash influxd --reporting-disabled ``` **Windows Powershell:** ```powershell ./influxd --reporting-disabled ``` For information about InfluxDB v2 default settings and how to override them, see [InfluxDB configuration options](/influxdb/v2/reference/config-options/). With InfluxDB installed and initialized, [get started](/influxdb/v2/get-started/) writing and querying data. ## Download, install, and configure the `influx` CLI Recommended:: Install the `influx` CLI, which provides a simple way to interact with InfluxDB from a command line. For detailed installation and setup instructions, see [Use the influx CLI](/influxdb/v2/tools/influx-cli/). #### InfluxDB and the influx CLI are separate packages The InfluxDB server ([`influxd`](/influxdb/v2/reference/cli/influxd/)) and the [`influx` CLI](/influxdb/v2/reference/cli/influx/) are packaged and versioned separately. Some install methods (for example, the InfluxDB Docker Hub image) include both. #### Related - [influx auth](/influxdb/v2/reference/cli/influx/auth/) - [influx config](/influxdb/v2/reference/cli/influx/config/) - [influx - InfluxDB command line interface](/influxdb/v2/reference/cli/influx/) - [Manage API tokens](/influxdb/v2/admin/tokens/) [install](/influxdb/v2/tags/install/)