Introduction
Setting up install podman on a RHEL 10 server is a common task for system administrators, DevOps engineers, and site reliability engineers. This guide explains how to Install Podman on RHEL 10, with all the commands you need, the SELinux and firewalld considerations to keep in mind, and how to validate the result on the live system.
Prerequisites
The procedure assumes you are working on a fully patched RHEL 10 machine. Run sudo dnf upgrade -y before continuing so you start from a known good baseline. SELinux should be in enforcing mode (the default), and firewalld should be running. You will also need a user account with sudo privileges configured in /etc/sudoers.d/.
Step 1: Update RHEL 10 and Enable Repositories
Ensure your RHEL 10 system is fully patched before installing new software. The AppStream repository is enabled by default on registered systems and provides the modular packages needed for most modern workloads. Pay attention to file ownership and permissions here — a service that is misconfigured at the file-system level will fail in subtle, hard-to-diagnose ways even though dnf reports a clean install.
sudo dnf upgrade -y
sudo dnf repolist enabledStep 2: Install Required Packages
Install the podman package along with any supporting dependencies from the standard RHEL 10 repositories. dnf will automatically resolve and pull in libraries, language runtimes, and configuration files. Logging at this stage is critical — anything you do here that is not logged will be very difficult to audit six months from now, so prefer commands that leave a trail in /var/log or the systemd journal.
sudo dnf install -y podmanStep 3: Apply the Initial Configuration
Now configure the component for your environment. Always keep a backup copy of the original configuration file so you can roll back quickly if something goes wrong, and prefer editing files in /etc/ over modifying the package defaults inside /usr/share/. Pay attention to file ownership and permissions here — a service that is misconfigured at the file-system level will fail in subtle, hard-to-diagnose ways even though dnf reports a clean install.
sudo nano /etc/sysconfig/myapp.confTroubleshooting Common Issues
If the service refuses to start, the first place to look is the systemd journal — every service on RHEL 10 logs there by default. Filter to the last boot to avoid wading through historical entries. The second most common class of problem on a fresh install is SELinux denials, especially when a service tries to read from or write to a directory that is not labelled with its expected type. Use ausearch -m AVC -ts recent to look for denials, and either set the correct file context with semanage fcontext + restorecon or flip the relevant boolean. Finally, if the service starts but is unreachable, double-check firewalld with firewall-cmd --list-all and confirm the runtime configuration matches the permanent one.
sudo journalctl -b --priority=err
sudo ausearch -m AVC -ts recent
sudo firewall-cmd --list-allBest Practices and Hardening
For any production deployment on RHEL 10 you should track configuration in a version control system, apply security errata regularly with dnf-automatic, and centralise log collection so that a compromised host cannot quietly erase its own audit trail. Run periodic OpenSCAP compliance scans against the CIS or DISA STIG profile to catch drift. If the service exposes a network port, place it behind a reverse proxy or VPN where possible and rotate any credentials it uses on a schedule. Snapshot the system (using Stratis, LVM, or your hypervisor) before every major change so you have a fast rollback path.
sudo dnf install -y dnf-automatic
sudo systemctl enable --now dnf-automatic.timer
sudo oscap xccdf eval --profile xccdf_org.ssgproject.content_profile_cis /usr/share/xml/scap/ssg/content/ssg-rhel10-ds.xmlVerification
After completing every step, run a quick set of checks to confirm the deployment is healthy on RHEL 10. Examine the systemd unit state to make sure no units have failed, look for any SELinux denials in the audit log, inspect the listening sockets to confirm the service is bound to the expected interface and port, and finally make a real client request to validate end-to-end functionality. If any of those four checks fail, return to the troubleshooting section before treating the deployment as complete.
sudo systemctl --failed
sudo ausearch -m AVC -ts recent || true
sudo ss -tulpn
sudo journalctl --since "10 minutes ago" --priority=warningConclusion
By following this guide you have a working install podman setup on RHEL 10 that follows Red Hat’s recommended practices. The system is ready for production use: services are enabled at boot, log output flows to the systemd journal, and the firewall is locked down to only the ports you opened. Schedule regular dnf-automatic security updates to keep it that way.
Looking forward, consider encoding the steps above as an Ansible role so the procedure becomes reproducible across your entire fleet, and add a Prometheus scrape config (or a Zabbix template) so the service is monitored from the moment it starts. Pair the deployment with a backup strategy — restic, borgbackup, or rsnapshot all work well on RHEL 10 — so that recovery from data loss is a matter of minutes rather than hours.
