AlmaLinux 10.3 Moves to Podman 6: Check What Your Containers Still Use
Start with the service account that owns the containers. Run podman info as the user that owns the workload and make a note of the network backend and storage settings. If root runs containers on that machine too, check those separately. It matters on AlmaLinux 10.3 because the Podman 6 update keeps your configuration files but removes some of the machinery those files used to select.
What stays in /etc
The AlmaLinux release announcement puts the new vendor defaults under /usr/share/containers. Your files in /etc/containers stay in place and still take precedence. On a machine you've tuned over several releases, the local files deserve a close read. An explicit setting that once kept a workload running can now be the reason it won't start.
Podman also separates storage settings for rootful and rootless containers into different drop-in directories. There is a separate place for rootless defaults under /etc/containers/containers.rootless.conf.d/. That gives you a way to test a change for service accounts without applying the same policy to services that run as root.
Give an existing workload the first test
AlmaLinux lists five changes to look for on the old host. Netavark is the sole network backend; CNI is gone. Podman uses SQLite instead of BoltDB. Rootless networking uses pasta in place of slirp4netns. There is no cgroups v1 support, and firewall rules use nftables rather than iptables.
A new container on a fresh machine can sail through all of that without ever touching the settings you need to migrate. On a disposable copy of the host, start something your team actually runs, under its usual user. Can the process reach its database? Can a client reach the port you publish? If you have firewall scripts, check the rules and the traffic they were supposed to allow. The service can show as running while a client still can't connect. Fedora's recent VPN migration brought up a similar problem: the replacement package is only useful if the saved configuration works with the other end of the connection.
The check that also applies to 9.9
The November 16 release announcement puts the Podman 6 move under 10.3, even though AlmaLinux 9.9 came out on the same day. Both releases do change authselect. Group merging is off by default, so an installation that combines local and SSSD group records should compare a representative user's memberships before and after the test update. If that account loses access to something it could read before, the change may be in its groups rather than its container setup.
Your Best Solution to all Linux Based Problems