Running Podman?

Podman rootless or Quadlet not cooperating? We sort it out.

Podman is Docker-compatible on the surface and meaningfully different underneath: no daemon, rootless by default, a UID remap you have to understand, and a different story for long-running services through Quadlet and systemd. We work through the subuid map, the socket activation, the SELinux labels and the compose compatibility edges until containers come up the same way they did on the Docker host they came from.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

podman.log

still broken

What it is

Podman at a glance

Podman is a container engine from Red Hat, launched to run OCI containers without a long-running daemon and with rootless execution as a first-class option. Its CLI is deliberately close to Docker's, so most docker commands translate line for line, but under the hood it uses user namespaces, crun or runc, and a direct exec model rather than a client-server socket.

The newer story around Quadlet, which lets you describe a container as a systemd unit, is what makes it a serious choice for production servers rather than only a developer substitute for Docker. On Red Hat Enterprise Linux, Fedora, CentOS Stream and Rocky, it is the default container tool. On Debian, Ubuntu and macOS it works but needs more operator attention, especially around the rootless UID map and networking.

Type
Daemonless OCI container engine with rootless support
First released
2018 initial release
License
Apache 2.0, free and permissive
Maintained by
Red Hat and the containers project community
Typically used for
Container execution on Linux servers, developer workstations, rootless CI, systemd-managed services

The honest version

Podman pros and cons

No technology is all upside. This is where Podman earns its place and where it tends to cause trouble.

Where Podman is strong

  • No daemon to run or secureEach podman command runs in the invoking user's own process tree, which removes a whole class of privilege-escalation concerns that live with the Docker socket.
  • Rootless is genuinely workableA regular user can build, run and manage containers without sudo, with user namespaces handling the mapping inside the container cleanly once /etc/subuid is set.
  • systemd integration through QuadletDescribing a container as a .container file and letting systemd supervise it is a cleaner production story than long-running podman run invocations held open by shell scripts.
  • Drop-in CLI compatibilityMost docker scripts work verbatim after aliasing docker to podman, which keeps the muscle memory from a decade of Docker usage useful.
  • Pods as a first-class objectGrouping several containers into a shared network and PID namespace at the engine level makes small Kubernetes-adjacent patterns feasible without a cluster.

Where Podman bites

  • Rootless networking has real limitsBinding privileged ports like 80 and 443 requires extra configuration, slirp4netns is slower than the root network stack, and some iptables-based behaviour simply does not apply the same way.
  • Compose compatibility is partialpodman-compose covers most of Compose v2, but healthchecks, depends_on, secrets and some volume features behave differently or incompletely depending on version.
  • UID remap trips every new userA missing /etc/subuid entry or a filesystem that does not support the xattrs rootless needs is the single most common failure mode, and the error message does not point obviously at the fix.
  • macOS and Windows experience is a VMPodman Machine runs a Linux VM under the hood with its own performance and filesystem caveats, which is the same trade Docker Desktop makes but less polished out of the box.
  • Ecosystem tooling leans Docker-firstMany commercial tools, CI runners and build systems still assume a Docker socket, so a Podman-only shop ends up either exposing the Podman socket in Docker-compatible mode or writing small shims.
  • Quadlet is young documentationThe unit-file format and the generators are powerful, but the official examples cover only part of what a real production service needs, so a first Quadlet rollout usually needs a few iterations.

Sound familiar?

Common Podman problems we fix

The Podman problems that bring people to us, and what you have once each one is fixed.

cannot find mapping for UID 1000 in /etc/subuid

Rootless containers refuse to start

A user whose /etc/subuid and /etc/subgid entries were never populated, usually on a server that was not provisioned through a config management tool that knows about Podman.

UID mapping in place, containers running

short-name did not resolve to an alias

Images will not pull by short name

A Podman install with no unqualified-search registries configured, so docker pull nginx works but podman pull nginx fails until registries.conf is set.

Registries configured, pulls clean

Failed to start container-web.service Quadlet

A Quadlet unit will not start under systemd

A .container file placed in the wrong directory for the user scope, a missing generator reload, or a unit that references an image not yet pulled on the host.

Quadlet units wired to systemd

port 80 is not allowed in rootless mode

Rootless cannot bind privileged ports

A service trying to expose port 80 or 443 directly under rootless, without configuring net.ipv4.ip_unprivileged_port_start or putting a reverse proxy in front.

Ports bound correctly

SELinux: avc: denied

SELinux denies a volume mount

A bind-mounted directory on a RHEL-family host without the right container_file_t labels, so the container sees the volume but cannot read or write it.

Labels applied, access clean

lsetxattr operation not supported

Storage driver cannot write metadata

A graphroot on a filesystem like plain FAT or an NFS mount that does not support the xattrs Podman's overlay driver expects.

Storage on a supported filesystem

no space left on device

The container store fills up

Images and layers accumulating under ~/.local/share/containers or /var/lib/containers until a build or pull runs out of room, often because old images are never pruned.

Store sized and pruned

podman-compose partial support

A compose file behaves differently to Docker

A production compose file that depends on service_healthy depends_on, named external networks or secrets in a way podman-compose does not fully implement.

Compose translated or replaced with Quadlet

What we do

Podman help, from migration to day-two

Call us for one failing rootless container, or hand us the whole Podman rollout.

Rescue
A rootless container that will not start, a Quadlet unit that systemd refuses, or a compose file misbehaving after a Docker migration. We work it back to a known-good state.
Docker to Podman migration
Reviewing existing Dockerfiles, compose files and CI pipelines against Podman's semantics, and converting what makes sense to Quadlet units rather than long-running CLI calls.
Rootless hardening
subuid and subgid provisioning, user namespaces, SELinux context, slirp4netns tuning, and the port and capability trade-offs documented.
Quadlet and systemd services
Container, Volume, Network and Pod unit files that boot cleanly, log through journald, and recover automatically after a host restart.
CI and build pipelines
Using Podman inside GitLab, GitHub Actions and Jenkins runners without exposing a daemon socket, including rootless builds and kaniko-style alternatives where it fits.
Managed Tech
Store pruning, image updates, Quadlet unit reviews, SELinux policy tracking, and an engineer on call when a Podman host throws something unexpected.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Podman alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Podman questions

Something else? Call+1 737 727 7327

Is Podman a drop-in replacement for Docker?

For most interactive docker commands, yes. For production use involving compose files, long-running services or privileged ports it is close but not identical. The right expectation is that everyday work translates line for line, and that a handful of pieces around networking, compose and systemd integration need deliberate attention during migration.

Why do our rootless containers fail on a fresh Linux host?

The common culprit is /etc/subuid and /etc/subgid never being populated for the service user, or the storage directory sitting on a filesystem that does not support the xattrs Podman expects. Fixing those two and reloading the user namespace usually resolves 80 percent of first-day Podman problems.

Should we use Quadlet or podman-compose for production?

For long-running services on a Linux host, Quadlet is the better choice. systemd supervises the container, journald collects the logs, and restart policy becomes a standard systemd concern. podman-compose is reasonable for development and for lift-and-shift of existing compose files, but it is not the long-term home for a production workload.

Does Podman work on macOS or Windows for development?

It works through Podman Machine, which runs a Linux VM under the hood. The experience is comparable to Docker Desktop in most day-to-day cases, with the same caveats: file-system bind-mount performance, networking that is one hop removed, and occasional friction when the VM state gets stale. For a production target of Linux hosts it is a reasonable local dev setup.

Can we move from Docker Compose to Podman without rewriting everything?

Usually, yes, with a phased plan. Start by running the compose file under podman-compose and catch the behaviour differences. Convert the most important services to Quadlet units so systemd owns them. Keep development on compose until the Quadlet pieces are solid, then retire the compose dependency. The migration rarely has to be a single cutover.

How much does Podman help cost?

Estimates are complimentary. Describe the host, the workload and the specific errors you are seeing, and you get a quote before any container is restarted.

Free estimate

Podman giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.