> For the complete documentation index, see [llms.txt](https://asus-isg-aidc.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://asus-isg-aidc.gitbook.io/guide/v1.3.0/guide/overview/service-catalog/podman.md).

# Podman Engine

| Developer | Last modified |
| --------- | ------------- |
| AIDC Team | 2026/01/30    |

## Service Introduction

**Podman Engine** is a daemonless container engine that is compatible with Docker CLI but doesn't require a continuously running daemon. It's suitable for environments with higher security requirements.

![](https://pub-f334ff01208c4e6195b80133ac6e6030.r2.dev/portal/marketplace/service-catalog-podman.png)

### Quick Summary

| Item                          | Details                 |
| ----------------------------- | ----------------------- |
| ⏱️ **Estimated Time**         | 5-15 minutes            |
| 💻 **Supported Platforms**    | Ubuntu22.04, RHEL 8.9   |
| 🔧 **Minimum Nodes Required** | 1 node                  |
| 📦 **Included Components**    | Podman, container-tools |

***

## Prerequisites

Before starting the deployment, ensure the following requirements are met:

### Hardware Requirements

| Role            | Minimum Spec                 | Recommended Spec              |
| --------------- | ---------------------------- | ----------------------------- |
| **Podman Host** | 2 vCPU / 4GB RAM / 20GB Disk | 4 vCPU / 8GB RAM / 100GB Disk |

### Network Requirements

* ✅ Outbound internet access for pulling images
* ✅ No daemon port required (Podman is daemonless)

### Other Requirements

* ✅ Nodes have been provisioned and are in **Ready** state

***

## Deployment Dialog Introduction

Podman Engine deployment is divided into **3 steps**:

{% @mermaid/diagram content="flowchart LR
Step1\["Step 1: Installation Target"]
Step2\["Step 2: Container Configuration"]
Review\["Step 3: Review and Deploy"]

```
Step1 --> Step2
Step2 --> Review" %}
```

[Step 1: Installation Target](#step-1-installation-target-selection) | [Step 2: Container Configuration](#step-2-container-configuration) | [Step 3: Review and Deploy](#step-3-review-and-deploy)

***

### Step 1: Installation Target Selection

![](https://pub-f334ff01208c4e6195b80133ac6e6030.r2.dev/portal/marketplace/service-catalog-podman-step1.png)

| Parameter Name                | Type   | Description                          |    Required   | Validation Rules                  | Example        |
| ----------------------------- | ------ | ------------------------------------ | :-----------: | --------------------------------- | -------------- |
| **Podman Installation Group** | string | Target Group for Podman installation | ⚪ Conditional | **Either Group or Node required** | `podman-hosts` |
| **Podman Installation Node**  | string | Target Node for Podman installation  | ⚪ Conditional | **Either Group or Node required** | `node-01`      |

{% hint style="warning" %}
**⚠️ Selection Rule**

At least one of **Group** or **Node** must be selected.\
When selecting Group, Podman will be installed on **all Nodes** in that Group.
{% endhint %}

***

### Step 2: Container Configuration

![](https://pub-f334ff01208c4e6195b80133ac6e6030.r2.dev/portal/marketplace/service-catalog-podman-step2.png)

| Parameter Name      | Type   | Description                    |  Required  | Validation Rules                                  | Example        |
| ------------------- | ------ | ------------------------------ | :--------: | ------------------------------------------------- | -------------- |
| **Image**           | string | Container image name           | ⚪ Optional | **Required if containerCount is filled**          | `nginx:latest` |
| **Container Count** | number | Number of Containers to create | ⚪ Optional | **Required if image is filled; positive integer** | `3`            |

{% hint style="info" %}
**💡 Tip**

Image and Container Count must be filled together or left empty together. If left empty, only Podman Engine will be installed without creating containers.
{% endhint %}

***

### Step 3: Review and Deploy

![](https://pub-f334ff01208c4e6195b80133ac6e6030.r2.dev/portal/marketplace/service-catalog-podman-step3.png)

***

## Post-Deployment Status

After successful deployment, you can view in **Status Monitor**:

* Task status progress
* Execution status of each node
* Error logs (if any)

### Deployment Verification

After the deployment status shows **Completed**, perform the following checks:

**1. Check Podman Version**

```bash
podman --version
```

✅ **Expected Result:** show Podman version

**2. Check Running Containers**

```bash
podman ps
```

✅ **Expected Result:** Shows running containers (if Image was specified)

**3. Test Container Execution**

```bash
podman run --rm hello-world
```

✅ **Expected Result:** Hello message displayed

***

## Frequently Asked Questions

### Q: Can Podman completely replace Docker?

A: In most cases, yes. Podman provides a Docker-compatible CLI, but some Docker-specific features (like Docker Swarm) may not be supported.

### Q: How to use Docker Compose files?

A: You can use the `podman-compose` tool, or convert compose files to Pod definitions using `podman generate kube`.

### Q: Is Podman suitable for production environments?

A: Yes. Podman is widely used in enterprise Linux distributions like RHEL and is the default container engine in RHEL 8+.

### Q: How to migrate from Docker to Podman?

A: In most cases, simply replace the `docker` command with `podman`. Images and configurations are compatible.

### Q: What are the advantages of Podman over Docker?

A: Daemonless architecture, rootless containers by default, no single point of failure, and better security isolation.

***

## Related References

* [Service Catalog](/guide/v1.3.0/guide/overview/service-catalog.md)
* [Status Monitor User Guide](/guide/v1.3.0/guide/overview/status-monitor.md#podman-status-card)
* [Podman Official Documentation](https://podman.io/docs)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://asus-isg-aidc.gitbook.io/guide/v1.3.0/guide/overview/service-catalog/podman.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.