Introduction to Consul Installation

This is Phase 1 of our comprehensive HashiCorp Consul training series. In this initial tutorial, we will take you from zero to a running local Consul node. You will learn how to verify your installation, write a clean configuration file, launch Consul securely in agent mode, and access its dynamic web dashboard.

Step 1: Downloading & Installing the Consul Binary

We will install Consul on a standard Debian/Ubuntu Linux VM. HashiCorp provides official package repositories to make installation and updates seamless.

1. Add the HashiCorp GPG Key

Open your terminal and import the official security signing key:

wget -O- https://apt.releases.hashicorp.com/gpg | gpg --dearmor | sudo tee /usr/share/keyrings/hashicorp-archive-keyring.gpg > /dev/null

2. Add the Package Repository

Inject the repository configuration into your apt sources list:

echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/hashicorp.list

3. Install the Binary

Update your local indices and install Consul:

sudo apt update && sudo apt install consul -y

4. Verify the Installation

Check that the Consul CLI is active and ready:

consul --version

You should see output detailing the Consul version, package type, and Git commit hash.

Step 2: Writing the Configuration

While you can launch Consul with raw CLI flags, using a structured JSON configuration file is best practice in enterprise environments.

Create a dedicated configuration directory and write your settings:

sudo mkdir -p /etc/consul.d
sudo nano /etc/consul.d/consul.hcl

Inject the following base single-node configuration block:

# /etc/consul.d/consul.hcl
datacenter = "dc-devops-01"
data_dir   = "/opt/consul"

# Enable UI and bind it to allow remote connections
ui_config {
  enabled = true
}

# Bind system interfaces
bind_addr   = "0.0.0.0" # Bind to all interfaces
client_addr = "0.0.0.0" # Expose client ports (UI/API)

# Single node setup parameters
server           = true
bootstrap_expect = 1

Step 3: Launching the Consul Agent

We will configure Consul to run as a reliable background service managed by systemd.

1. Set Proper Permissions

Ensure the system data folder belongs to the dedicated consul user created by the package manager:

sudo mkdir -p /opt/consul
sudo chown -R consul:consul /opt/consul /etc/consul.d

2. Start and Enable the Service

Use systemd to launch Consul and register it for auto-start on system boot:

sudo systemctl enable consul
sudo systemctl start consul

3. Check Status

Verify that the service is running correctly:

sudo systemctl status consul

You should see an active, green status showing that the Consul agent is listening on port 8500.

Step 4: Exploring the Web UI

Once Consul starts up:

1. Open your browser and navigate to http://<your-node-ip>:8500.
2. You will be greeted by the official Consul Web dashboard!
3. Explore the Services tab—you should see consul registered as the primary operational service node.
4. Explore the Nodes tab to verify your server is active and healthy.

Congratulations! You have completed Phase 1. You now have a solid foundation to construct highly available server clusters in Phase 2: Building a Highly Available Server Cluster.