---
title: "Configuring Podman in RHEL 8"
slug: "configuring-podman-in-rhel-8"
updated: 2024-09-17T12:38:58Z
published: 2024-09-17T12:38:58Z
canonical: "help.hyperscience.ai/configuring-podman-in-rhel-8"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.hyperscience.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring Podman in RHEL 8

In v33.1.0 and later, Hyperscience gives you the possibility to deploy the application on RHEL 8.4 or later. RHEL 8.4 and later uses Podman instead of Docker. The sections below describe how you can configure Podman.

## Prerequisites

Before you start configuring RHEL 8, you need to meet the following requirements, depending on whether you are installing or upgrading the Hyperscience application.

### Installing the Hyperscience application on a new RHEL 8.4+ instance

If you are already running RHEL 8.4 or later, and you are installing Hyperscience for the first time, you may proceed directly to the steps outlined in [Configuring Podman](/deployment/docs/configuring-podman-in-rhel-8#configuring-podman).

### Upgrading from RHEL 7 to RHEL 8.4+ when Hyperscience is already installed

Before you start configuring RHEL 8, you need to upgrade Hyperscience to a RHEL-8-compatible version (v33.1.0 or later) by following these steps:

1. To save space that is consumed by Docker images, clear the Docker containers.
2. Upgrade your Hyperscience application to v33.1.0 or later by following the steps outlined in our [Upgrading to v33](/deployment/docs/upgrading-to-v33) article.
3. Check the application’s health status.
4. Upgrade from RHEL 7.x to RHEL 8.4 or later by following the steps outlined in Red Hat’s [Upgrading From RHEL 7 to RHEL 8](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/upgrading_from_rhel_7_to_rhel_8/index) article.

## Configuring Podman

To configure Podman, follow the steps below:

1. Install the *container-tools* module using the following command:

```bash
yum module install -y container-tools
```

To learn more, see the “1.5. Getting container tools” section of Red Hat’s [Building, running, and managing containers](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/building_running_and_managing_containers/index#proc_getting-container-tools_assembly_starting-with-containers) article.
2. Install the *podman-docker* package using the following command:

```bash
yum install -y podman-docker
```

The *podman-docker* package replaces the Docker command-line interface and *docker-api* with the matching Podman commands. Every time you run a Docker command, the system will actually run a Podman command. To learn more, see the “1.3 Running containers without Docker” section of Red Hat’s [Building, running, and managing containers](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/building_running_and_managing_containers/assembly_starting-with-containers_building-running-and-managing-containers#con_running-containers-without-docker_assembly_starting-with-containers) article.
3. Enable Podman API using the following commands:

```bash
yum install podman-remote
systemctl enable --now podman.socket
```

To learn more, see the “15.1. Enabling the Podman API using systemd in root mode” section of Red Hat’s [Building, running, and managing containers](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/building_running_and_managing_containers/index#proc_getting-container-tools_assembly_starting-with-containers) article.
4. Enable the Podman restart service using the following command:

```bash
systemctl enable --now podman-restart.service
```

Enabling this option allows Podman to restart the Hyperscience application automatically upon OS restart.
5. Give *sudo* access, as it is a requirement for installations, upgrades, and running the *run.sh* command on RHEL 8. To learn how to give *sudo* access, see Red Hat’s [Managing sudo access](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_basic_system_settings/managing-sudo-access_configuring-basic-system-settings).
6. If you are upgrading the Hyperscience application, you also need to recreate the database container.