Console Installation

Supported Distributions (x64 only)

The list below is limited to the widely adopted Linux distribution families that Docker documents for installing Docker Engine: Debian, Ubuntu, RHEL, CentOS, and Fedora. Raspberry Pi OS and SLES (s390x) are not included, as they are niche or specialized and have not been tested.

• Debian Bullseye 11 (oldoldstable)
• Debian Bookworm 12 (oldstable)
• Debian Trixie 13 (stable)
• Ubuntu Jammy 22.04 (LTS)
• Ubuntu Noble 24.04 (LTS)
• Ubuntu Questing 25.10
• RHEL 8
• RHEL 9
• RHEL 10
• CentOS Stream 9
• CentOS Stream 10
• Fedora 41
• Fedora 42
• Fedora 43

This list is maintained and updated by Docker. For the most up-to-date version information for each distribution, see the official Docker documentation: Install Docker Engine.

Deployment Models

You can deploy AIR in one of two models:

• Single Tier Deployment
  All platform components, such as App, Web, NATS, DB, and Redis, are installed and run on the same machine.
• 2-Tier Deployment
  All components except the Database Layer are installed and run on a single instance, while the Database has its own dedicated instance.

Note

Which deployment model to use?

The Single-Tier Model is the fastest way to deploy AIR and is recommended for, proof of concept (PoC), and testing purposes.

The Two-Tier Model is designed for all production environments and will support tens of thousands of assets/endpoints. This model includes the Console Server along with a separate dedicated Database Server, which enhances the overall performance of AIR at scale.

Our team is always available to collaborate with you to define the optimal setup.

Installation

Before you start

• Make sure you have updated package repositories of the Operating System you are using. Please find below the commands for CentOS and Ubuntu:

For CentOS:

yum update

For Ubuntu:

apt-get update

• Start and enable Docker service by executing the following command:

systemctl start docker && systemctl enable docker

Single-Tier Deployment

Note

Suitable for PoCs, Demos, and non-mission-critical deployments.

This deployment model installs all components into a single machine.

Method 1: Quick Deployment (preferred method)

1. Run the one-liner below and wait for it to complete.

   curl -fsSL https://cdn.binalyze.com/air-deploy/console.sh | sudo -E bash

2. Proceed with the Finalizing Setup section.

Method 2: Manual Deployment (use only when required)

1. Create a folder for the AIR under /opt directory and cd into it

   mkdir /opt/binalyze-air && cd /opt/binalyze-air

2. Download the docker-compose.yml file and save it.

   curl -fsSL "https://cdn.binalyze.com/air-deploy/docker-compose.yml" -o docker-compose.yml

3. Create the directory for the database volume with defined access:

   install -d -o 1001 -g 1001 ./volumes/data-master/binalyze-air/{data,log}
   install -d -o 1001 -g 1001 ./volumes/tornado/{data,config}

4. Create environment variables:

   AIR_POSTGRESQL_PASSWORD=$(head /dev/urandom | tr -dc 'a-zA-Z0-9' | head -c 32)
   
   echo "AIR_POSTGRESQL_PASSWORD=$AIR_POSTGRESQL_PASSWORD" >> .env
   echo "AIR_POSTGRESQL_URI=postgresql://air-data:$AIR_POSTGRESQL_PASSWORD@air.data-master.server:5432/airdb" >> .env
   echo "AIR_NATS_PASSWORD=$(head /dev/urandom | tr -dc 'a-zA-Z0-9' | head -c 32)" >> .env

5. Run the following command to start the AIR installation in Docker:

   docker compose -p binalyze-air up -d

6. Wait for the installation to complete. It may take several minutes.

7. Proceed with the Finalizing Setup section.

2-Tier Deployment

Note

Suitable for Enterprise Deployments.

This deployment model requires you to first deploy the Database Component (Step 1). Once the database is successfully installed and running, you can proceed with the deployment of the Console Server (Step 2). During this step, you will need to provide the IP address of the previously installed Database Server. This sequence is critical, as the Console Server relies on an active and accessible database instance to function correctly.

Method 1: Quick Deployment (preferred method)

1. Step 1 - On the Database Server: Run the one-liner command below and wait for it to complete (this script will deploy the database component).

   curl -fsSL https://cdn.binalyze.com/air-deploy/db.sh | sudo -E bash

2. Step 2 - On the Console Server: Once the database is deployed, the above script will output the commands that need to be executed on the Console Server machine.

   • SSH into the Console Server machine.
   • Run the commands provided by the above script and wait for it to complete.
   • Proceed with the Finalizing Setup section.

Method 2: Manual Deployment (use only when required)

Caution

You should execute the commands below on the Database Server!

1. SSH into the Database Server.

2. Create a folder for the AIR DB under /opt directory and cd into it

   mkdir /opt/binalyze-air-db && cd /opt/binalyze-air-db

3. Download the docker compose.yml file and save it.

   curl -fsSL "https://cdn.binalyze.com/air-deploy/docker-compose-db.yml" -o docker-compose.yml

4. Create the directory for the database volume with defined access:

   install -d -o 1001 -g 1001 ./volumes/data-master/binalyze-air/{data,log}

5. Create environment variables.

   AIR_POSTGRESQL_PASSWORD=$(head /dev/urandom | tr -dc 'a-zA-Z0-9' | head -c 32)
   echo "AIR_POSTGRESQL_PASSWORD=$AIR_POSTGRESQL_PASSWORD" >> .env

6. Run the following command to start the AIR Database component in Docker:

   docker compose -p binalyze-air-db up -d

7. Wait for the installation to complete. It may take several minutes.

8. Proceed to the installation of the Console Server

Caution

You should execute the commands below on the Console Server!

1. SSH into the Console Server

2. Create a folder for the AIR under /opt directory and cd into it

   mkdir /opt/binalyze-air && cd /opt/binalyze-air

3. Download the docker-compose.yml file and save it

   curl -fsSL "https://cdn.binalyze.com/air-deploy/docker-compose-without-db.yml" -o docker-compose.yml

4. Create the directory for the volume of the services with defined access:

   install -d -o 1001 -g 1001 ./volumes/tornado/{data,config}

5. Set the database URI for connecting the Console Server to the DB
   IMPORTANT:
   &#xNAN;You must fill in the values ​​of the following three variables. We need the passwords created on the DB server and the DB server IP address.
   &#xNAN;You can find the passwords in the /opt/binalyze-air-db/.env file on the DB Server.

   AIR_POSTGRESQL_PASSWORD=
   DB_SERVER_IP=
   
   echo "AIR_POSTGRESQL_URI=postgresql://air-data:$AIR_POSTGRESQL_PASSWORD@$DB_SERVER_IP:5432/airdb" >> .env
   echo "AIR_NATS_PASSWORD=$(head /dev/urandom | tr -dc 'a-zA-Z0-9' | head -c 32)" >> .env

6. Run the following command to start the AIR installation in Docker

   docker compose -p binalyze-air up -d

7. Wait for the installation to complete. It may take several minutes

8. Proceed with the Finalizing Setup section

Finalizing Setup

Regardless of the deployment model you choose, you will be asked to provide several configurations at the end of the deployment, such as an organization name and the credentials of the first user account.

Once you have completed the above steps successfully, you should:

1. Visit http://IP-ADDRESS for accessing the Console (IP address here is the public IP address of the machine you have deployed AIR)
2. Accept the EULA and provide the configuration you are asked for in each step
3. Complete the setup and log in using the credentials you have provided
4. Enjoy AIR!

Note

Checking the Health of Docker Containers

To ensure your AIR deployment is functioning correctly, regularly checking the status of your Docker containers is crucial. Here’s how you can monitor and manage the health of your containers:

1. Check Container Status:
   • Run the command sudo docker ps to list all active Docker containers. This command displays the current state of each container, allowing you to identify any that aren’t running as expected.
2. Recommended Method for Restarting Containers in AIR
   • When restarting your AIR containers, we recommend using the docker compose restart command instead of the docker compose down/up method.
   • The docker compose restart command allows you to restart all the containers without removing them, ensuring that essential logs and state information are retained. This is crucial for effective troubleshooting, as it helps preserve valuable data that could provide insights into potential issues.
   • Additionally, the docker compose restart command is a faster and less disruptive option compared to using docker compose down/up. The down/up approach can result in data loss from container recreation, whereas docker compose restart avoids this by maintaining the containers’ state.
   • By using the docker compose restart command, you help ensure logs remain intact, which can assist in resolving issues more efficiently.

Importance of Regular Checks

Regular monitoring and proactive management of your Docker containers help maintain the stability and reliability of your AIR deployment. By monitoring container statuses and knowing how to restart services quickly, you can ensure continuous operational performance.