Skip to content

Did you know?

Podman 6, new in AlmaLinux 10.3, drops CNI networking, BoltDB, slirp4netns and cgroups v1.

Before updating, check your network backend. If it says "cni", recreate those networks with Netavark first.

  • DevOps & cloud
  • Applies to Podman 6 (AlmaLinux 10.3, RHEL 10.3 based distros)
  • Last checked

Explained

AlmaLinux 10.3 moves from Podman 5 to Podman 6.1, a major version that removes several legacy pieces at once. CNI networking is gone, so Netavark is the only network backend. The BoltDB database is gone, and Podman uses SQLite. Rootless networking uses pasta instead of slirp4netns, cgroups v1 is no longer supported, and firewall rules are written with nftables instead of iptables.

Most systems that started on RHEL 10 or AlmaLinux 10 already use Netavark and SQLite, so they won’t notice. Hosts that were migrated from older setups, or that carry custom CNI configs, can lose container networking after the update.

Check the backend before you run dnf upgrade:

podman info --format '{{.Host.NetworkBackend}}'

If it prints netavark, you’re fine. If it prints cni, list your networks with podman network ls, note their subnets, and plan to recreate them after switching to Netavark. Also check scripts that pass --network slirp4netns and replace it with --network pasta.

One more change: vendor defaults move from /etc/containers to /usr/share/containers. Your own files in /etc/containers still win, so keep custom settings there.

Learn more

← All tech tips · Suggest a fix

Back to top