The containers.conf file is read-only for Podman commands. The system connections and farm information must be stored in the podman.connections.json file, managed only by Podman.

Podman continues to support the old configuration options such as [engine.service_destinations] and the [farms] section. You can still add connections or farms manually if needed, however, it's not possible to delete a connection from the containers.conf file with the podman system connection rm command.

The slirp4netns network mode is deprecated. The pasta network mode is the default network mode for rootless containers.

Using cgroupsv1 for rootless containers is deprecated.

Note that cgroupsv1 is deprecated on Oracle Linux 9. See cgroupsv1.

The runc container runtime is deprecated. The default container runtime is crun.

Using pasta as a network name value is deprecated.

The BoltDB database backend is deprecated in favor of the SQLite database backend.

Creating Oracle Linux 9 containers on an Oracle Linux 7 host is unsupported. Attempts to deploy this configuration might succeed, but is not guaranteed.

Support for using the SHA-11 algorithm to generate the filename of the rootless network namespace is removed in Podman. You should restart rootless containers that were configured by using Podman earlier than version 4.1.1. Restarting these containers rather than just using slirp4netns ensures that these containers and join the network and connect with containers that were created with upgraded Podman versions.

The Container Network Interface (CNI) network stack is deprecated. You can use the Netavark network stack with Podman and other Open Container Initiative (OCI) container management applications. The Netavark network stack for Podman is also compatible with advanced Docker functionalities.