Documentation

Deploy the InfluxData Platform (TICK stack) in Docker containers

The quickest way to start using the InfluxDB 1.x platform (TICK stack) OSS is to download and deploy the InfluxData Sandbox. The InfluxData Sandbox uses Docker containers to deploy the InfluxData Platform components. The InfluxData Sandbox provides a containerized, ready-to-use TICK stack, built using Docker and Docker Compose, to capture data from your local machine and the Docker containers.

After deploying using the InfluxData Sandbox, you will have the latest versions of:

  • Telegraf
  • InfluxDB OSS
  • Chronograf
  • Kapacitor OSS

The InfluxData Sandbox is not recommended for production use.

Requirements

Download and run the Sandbox

The InfluxData Sandbox is open source and is available for download from Github. To download it, use git to clone the source repository:

# Clone the InfluxData Sandbox from Github
git clone https://github.com/influxdata/sandbox.git

The Sandbox repo includes a sandbox binary used to provision and manage the Sandbox’s containers and data. Run ./sandbox up from inside the sandbox directory to download the necessary images, then build and start all the required Docker containers.

# cd into the sandbox directory
cd sandbox

# Start the sandbox
./sandbox up

Make sure no other instances of TICK stack components are running on your local machine when starting the Sandbox. Otherwise you will run into port conflicts and the Sandbox won’t be able to start properly.

Once started, two tabs will open in your browser:

  1. Chronograf (localhost:8888)
  2. InfluxData Sandbox Documentation (localhost:3010)

Chronograf is the web-based user interface for the TICK stack and can be used to manage the stack. You can use Chronograf to:

Using nightly builds

The ./sandbox up command includes a -nightly option that will pull nightly builds for InfluxDB and Chronograf, giving you the most recent updates and experimental functionality.

Nightly builds are experimental and are not guaranteed to be functional.

./sandbox up -nightly

Interacting with the Sandbox TICK stack

With the Sandbox running, each component of the TICK stack is available to work with. The Sandbox documentation provides tutorials for interacting with each component. The documentation is available at localhost:3010/tutorials (with the Sandbox running) or on Github.

All configuration files, tools, and CLIs needed for managing each component of the TICK stack are included in their respective Docker containers. Tasks outlined throughout the InfluxData documentation can be accomplished using the InfluxData Sandbox.

The ./sandbox enter command opens a console inside the specified container where the project’s configuration files and CLIs are available.

# Pattern
./sandbox enter [ telegraf | influxdb | chronograf | kapacitor ]

# Example: console into the telegraf container
./sandbox enter telegraf

After updating a configuration file in a Sandbox container, use the ./sandbox restart command to restart the containers and apply the updated configuration.


Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: