-
Epic
-
Resolution: Done
-
Normal
-
rhel-10.0.beta
-
[RHEL EPIC] containers.conf read only - RHEL 9.5
-
-
Red Hat Enterprise Linux
-
rhel-sst-container-tools
-
20
-
False
-
-
Yes
-
QE ack, Dev ack, Docs ack, PXE ack
-
Enhancement
-
-
Done
Description
Starting in Podman v5.0, the containers.conf file will be read-only. In addition, the system connections and farm information formerly stored in the `containers.conf` file will now be stored in the `podman.connections.json` file.
Per mheon@redhat.com on June 20, 2024:
"Basically: Before, several Podman commands (`podman system connection` suite, plus `podman farm`, plus possibly a few more I'm forgetting) would rewrite the containers.conf file to add bits (basically treating it as a database for connections). This would not lose user-added configuration, but did remove all user-added comments, formatting, etc. We're not doing that anymore. The /usr/share/containers/containers.conf and /etc/containers/containers.conf files will never be modified by Podman even when adding, removing, etc system connections and farms. Instead, we moved those to a separate file.
System connections still in the file that were added by Podman 4.x will remain after the upgrade to 5.0."
What SSTs and Layered Product teams should review this?
- clones
-
RHEL-40637 [RHEL EPIC] containers.conf read only - RHEL 9.5
- Closed