podman-rpms

Automate RPM packaging of rootless Podman Quadlet containers for RHEL.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/juburr/mad-skills --skill podman-rpms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: podman-rpms
Source: https://github.com/juburr/mad-skills/tree/main/podman-rpms
Command: npx skills add https://github.com/juburr/mad-skills --skill podman-rpms

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Deploying containerized applications on RHEL via rootless Podman and Quadlet requires careful, manual setup of per-user storage, UID/GID mappings, lingering, and offline image delivery. This skill provides a structured RPM-based approach to standardize and automate these tasks for reproducible deployments.

Core Features & Use Cases

  • RPM-packaged Quadlet templates that adapt to Podman 4.x and 5.x plus per-user, rootless execution.
  • Guidance for configuring subuid/subgid, user lingering, and air-gapped image delivery for reliable fleet deployments.
  • End-to-end deployment workflow from packaging to runtime, including validation steps and rollback considerations.

Quick Start

Build and deploy an RPM that packages Quadlet templates and per-user Podman configuration for your application.

Frequently Asked Questions about podman-rpms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate rootless Podman Quadlet deployments with RPM packages?

Rootless Podman Quadlet deployments are automated by packaging Quadlet templates into RPMs that configure per-user storage, subuid/subgid mappings, and user lingering for secure, repeatable deployments across RHEL 8/9/10.

What is the best way to deliver Podman container images in an air-gapped RHEL environment?

Air-gapped Podman image delivery in RHEL is handled through an RPM-based approach that packages the images alongside Quadlet templates, ensuring reliable fleet deployments without requiring network access to external registries during installation.

Does this RPM deployment approach work across different Podman and RHEL versions?

The RPM deployment approach supports RHEL 8, 9, and 10 with compatibility for both Podman 4.x and 5.x, automatically detecting Podman versions to apply the correct sysusers, subuid handling, and RPM policy guidance.

How do I configure subuid, subgid, and lingering for per-user rootless Podman containers?

Configuring subuid, subgid, and lingering for per-user rootless Podman containers is managed through the RPM deployment workflow, which standardizes UID/GID mappings and enables lingering to ensure containers persist after user sessions end.

Why does my rootless Podman deployment fail after user logout on RHEL?

Rootless Podman deployments fail after user logout when user lingering is not enabled, which is required to allow per-user systemd services and Quadlet units to continue running independently of active login sessions.

Can I include validation steps and rollback considerations in an RPM-packaged Podman deployment?

RPM-packaged Podman deployments can include end-to-end deployment workflows from packaging to runtime, incorporating validation steps and rollback considerations to ensure reliable container execution and recovery.