Prerequisites

Before diving into the installation, ensure that the following prerequisites are met:

1. Sudo Privileges: Administrative privileges are required to perform installation and configuration tasks.
2. Internet Access: The server must have internet access to download Prometheus binaries.
3. Firewall Configuration: Ensure that port 9090 is open to access Prometheus’s web interface.

Step 1: Installing Prometheus Binary Files

Update Package Repositories

Before downloading Prometheus, update the package repositories to ensure all packages are up to date:

sudo yum update -y

Download Prometheus Binary

Use the following command to download the latest Prometheus binary:

curl -LO https://github.com/prometheus/prometheus/releases/download/v2.22.0/prometheus-2.22.0.linux-amd64.tar.gz

Extract and Rename Files

Extract the downloaded archive and rename the folder for convenience:

tar -xvf prometheus-2.22.0.linux-amd64.tar.gz
mv prometheus-2.22.0.linux-amd64 prometheus-files

Step 2: Setting Up Prometheus User and Directories

Create Prometheus User

Create a dedicated system user for running Prometheus:

sudo useradd --no-create-home --shell /bin/false prometheus

Create Necessary Directories

Set up the required directories for Prometheus configuration and data storage:

sudo mkdir /etc/prometheus
sudo mkdir /var/lib/prometheus

Set the appropriate ownership for these directories:

sudo chown prometheus:prometheus /etc/prometheus
sudo chown prometheus:prometheus /var/lib/prometheus

Step 3: Moving Prometheus Binary Files

Move Prometheus Binaries

Move the prometheus and promtool binaries to a system-wide location:

sudo cp prometheus-files/prometheus /usr/local/bin/
sudo cp prometheus-files/promtool /usr/local/bin/
sudo chown prometheus:prometheus /usr/local/bin/prometheus
sudo chown prometheus:prometheus /usr/local/bin/promtool

Move Console Files

Copy Prometheus console files to the appropriate directories:

sudo cp -r prometheus-files/consoles /etc/prometheus
sudo cp -r prometheus-files/console_libraries /etc/prometheus
sudo chown -R prometheus:prometheus /etc/prometheus/consoles
sudo chown -R prometheus:prometheus /etc/prometheus/console_libraries

Step 4: Configuring Prometheus

The Prometheus configuration file defines how the application behaves, which metrics to scrape, and how often.

Create prometheus.yml

Create the main configuration file at /etc/prometheus/prometheus.yml:

sudo vi /etc/prometheus/prometheus.yml

Add the following content:

global:
  scrape_interval: 10s

scrape_configs:
  - job_name: 'prometheus'
    scrape_interval: 5s
    static_configs:
      - targets: ['localhost:9090']

Set ownership of the configuration file:

sudo chown prometheus:prometheus /etc/prometheus/prometheus.yml

Step 5: Creating a Systemd Service for Prometheus

To ensure Prometheus runs as a service, create a systemd unit file.

Create the Service File

Open a new service file for Prometheus:

sudo vi /etc/systemd/system/prometheus.service

Add the following content:

[Unit]
Description=Prometheus
Wants=network-online.target
After=network-online.target

[Service]
User=prometheus
Group=prometheus
Type=simple
ExecStart=/usr/local/bin/prometheus \
    --config.file /etc/prometheus/prometheus.yml \
    --storage.tsdb.path /var/lib/prometheus/ \
    --web.console.templates=/etc/prometheus/consoles \
    --web.console.libraries=/etc/prometheus/console_libraries

[Install]
WantedBy=multi-user.target

Reload Systemd and Start Prometheus

Reload the systemd manager configuration and start Prometheus:

sudo systemctl daemon-reload
sudo systemctl start prometheus

Verify that the service is running:

sudo systemctl status prometheus

Enable the service to start on boot:

sudo systemctl enable prometheus

Step 6: Accessing the Prometheus Web Interface

Prometheus’s web interface can be accessed via port 9090. Open a web browser and navigate to:

http://<your-server-ip>:9090/graph

Here, you can query existing metrics and visualize data. The default configuration scrapes Prometheus’s own metrics.

Step 7: Adding Additional Monitoring Targets

Prometheus can monitor multiple targets. To add more targets, edit the prometheus.yml file:

scrape_configs:
  - job_name: 'my-app'
    static_configs:
      - targets: ['my-app-server:8080']

Restart Prometheus to apply changes:

sudo systemctl restart prometheus

Conclusion

In this guide, we have covered the complete process of installing and configuring Prometheus on a Linux server. Prometheus is a powerful tool for monitoring system health, gathering metrics, and triggering alerts. Its flexibility allows you to monitor various services and applications by simply adjusting the configuration file.

By following these steps, you’ve set up a robust monitoring solution for your systems. Remember to keep Prometheus updated and secure access to its web interface for optimal performance and security.

Benefits of Podman

No Daemon Required

Unlike Docker, Podman does not need a continuously running service in the background. This feature makes it more resource-efficient, as it only runs processes when necessary, without the overhead of an always-on daemon. This design choice improves system performance and makes Podman a great option for both development and production environments.

Rootless Operation

Podman can operate without root privileges, providing a significant security advantage. Containers traditionally require root access to manage and control, which opens up potential vulnerabilities. By running containers in a rootless mode, Podman reduces the attack surface, enhancing security by limiting the access level of processes.

Docker Compatibility

Podman is largely compatible with Docker’s command-line interface (CLI). This means that Docker users can easily transition to Podman with minimal changes to their workflows. Podman allows users to leverage their existing Docker expertise without the need for extensive retraining or modification of existing Docker-based processes.

Container Orchestration

Podman supports Kubernetes-compatible YAML files, which is essential for container orchestration. This allows Podman to seamlessly integrate into larger Kubernetes-based infrastructures, making it a solid choice for container management at scale. Whether managing a single container or orchestrating complex multi-container applications, Podman provides the flexibility needed to work in various environments.

Installing Podman

The installation of Podman depends on the operating system being used. Below is a detailed guide on how to install Podman on the most common platforms.

Installing Podman on Ubuntu

To install Podman on Ubuntu, follow these steps:

1. Add the Repository:

   sudo sh -c "echo 'deb https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/x${VERSION_ID}/ /' > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list"
   wget -nv https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable/x${VERSION_ID}/Release.key -O Release.key
   sudo apt-key add - < Release.key
   sudo apt-get update

2. Install Podman:

   sudo apt-get -y install podman

Installing Podman on CentOS/RHEL

For CentOS or RHEL, the steps are as follows:

1. Add the Repository:

   sudo yum -y install epel-release
   sudo yum -y install https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/CentOS_8/devel:kubic:libcontainers:stable.repo

2. Install Podman:

   sudo yum -y install podman

Installing Podman on Fedora

Fedora generally includes Podman in its default package repositories. To install the latest version:

sudo dnf -y install podman

Installing Podman on macOS

On macOS, you can use the Homebrew package manager to install Podman.

1. Ensure Homebrew is Installed:

   /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

2. Install Podman:

   brew install podman

3. Start Podman:

   podman machine init
   podman machine start

Installing Podman on Windows

To use Podman on Windows, the Windows Subsystem for Linux (WSL) is required.

1. Install WSL: Open PowerShell as an administrator and run the following command:

   wsl --install

Restart your computer after the installation.

2. Install a Linux Distribution: From the Microsoft Store, download and install a Linux distribution, such as Ubuntu.
3. Install Podman in the Linux Distribution: Follow the Ubuntu installation steps listed above to install Podman in the WSL environment.
4. Start Podman: Check the version of Podman by running:

   podman --version

Basic Podman Commands

Podman operates similarly to Docker in terms of its command structure. Below are some basic Podman commands to get you started.

Running a Container

To run a container with Podman:

podman run -it --name mycontainer ubuntu bash

This command starts a new container using the ubuntu image and opens an interactive terminal session (bash) inside the container.

Listing Running Containers

To list all running containers:

podman ps

Listing All Containers

To list all containers (including stopped ones):

podman ps -a

Stopping a Container

To stop a running container:

podman stop mycontainer

Removing a Container

To remove a stopped container:

podman rm mycontainer

Listing Images

To list all available container images:

podman images

Pulling an Image

To download a container image (e.g., Ubuntu):

podman pull ubuntu

Removing an Image

To remove an image:

podman rmi ubuntu

Running Your First Container with Podman

Running your first container with Podman is straightforward. Here’s a step-by-step guide using the ubuntu image.

Step 1: Pull the Ubuntu Image

podman pull ubuntu

Step 2: Run the Container

podman run -it --name first_container ubuntu bash

This will launch an interactive terminal session inside the container, using the bash shell.

Step 3: Perform Operations Inside the Container

You can now run various commands inside the container, such as installing software:

apt update
apt install -y nginx

Step 4: Exit the Container

Once you’re done, exit the container:

exit

Step 5: List Containers

To check the status of your containers, use:

podman ps -a

Image Management with Podman

Podman provides powerful tools for managing container images. Here are some common tasks:

Listing Existing Images

To view all the available container images on your system:

podman images

Pulling a New Image

To pull a new image, such as the alpine image:

podman pull alpine

Tagging an Image

To tag an image for easier reference:

podman tag alpine myrepo/alpine:latest

Pushing an Image

To push an image to a remote registry:

podman push myrepo/alpine:latest

Removing an Image

To remove an image from your local system:

podman rmi alpine

Networking and Storage with Podman

Podman provides options for managing networking and persistent storage for containers.

Network Management

By default, Podman creates a network for container communication. You can create your own custom network for specific use cases.

Create a Custom Network:

podman network create my_network

Connect a Container to the Custom Network:

podman run -d --name web --network my_network nginx

Volume Management

Podman also offers persistent storage through volumes, which are critical for data integrity when containers are stopped or removed.

Create a Persistent Volume:

podman volume create my_data_volume

Run a Container with Volume:

podman run -d --name db -v my_data_volume:/var/lib/mysql mysql

Security with Podman

Podman is designed with security in mind and offers several features to help ensure secure container operation.

Rootless Operation

One of the key features of Podman is its ability to run containers without requiring root privileges. This significantly reduces security risks, as containers do not have access to the system’s root-level resources.

SELinux Support

Podman is compatible with SELinux (Security-Enhanced Linux), which provides an additional layer of security for containers by enforcing mandatory access control policies.

Signed Container Images

Podman supports signed container images, ensuring that the images you are using are verified and trusted. This feature helps ensure that only authorized container images are used in your environment.

Conclusion

Podman is a powerful alternative to Docker, offering flexible and secure solutions for container management. Its ability to run without a daemon, operate rootless, and maintain compatibility with Docker makes it an attractive choice for developers and system administrators alike. Whether you’re working on a small project or orchestrating complex containerized applications, Podman provides the tools and capabilities to manage containers effectively. For more advanced use cases, be sure to explore the official Podman documentation.