Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-40637

[RHEL EPIC] containers.conf read only - RHEL 9.5

XMLWordPrintable

    • [RHEL EPIC] containers.conf read only - RHEL 9.5
    • Hide

      The following needs to be verified in order for this epic to be considered complete:

      • Verify the `contatiners.conf` file is Read Only
      • Verify system connections and farm info are stored in `podman.connections.json`
      • Basic Podman commands run without issue.
      Show
      The following needs to be verified in order for this epic to be considered complete: Verify the `contatiners.conf` file is Read Only Verify system connections and farm info are stored in `podman.connections.json` Basic Podman commands run without issue.
    • Red Hat Enterprise Linux
    • rhel-sst-container-tools
    • 20
    • False
    • Hide

      None

      Show
      None
    • Yes
    • QE ack, Dev ack, Docs ack, PXE ack
    • Enhancement
    • Hide
      .The `containers.conf` file is now read-only

      The system connections and farm information stored in the `containers.conf` file is now read-only. The system connections and farm information will now 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 is not possible to delete a connection from the `containers.conf` file with the `podman system connection rm` command.

      You can still manually edit the `containers.conf` file if needed.
      System connections that were added by Podman v4.0 remain unchanged after the upgrade to Podman v5.0.
      Show
      .The `containers.conf` file is now read-only The system connections and farm information stored in the `containers.conf` file is now read-only. The system connections and farm information will now 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 is not possible to delete a connection from the `containers.conf` file with the `podman system connection rm` command. You can still manually edit the `containers.conf` file if needed. System connections that were added by Podman v4.0 remain unchanged after the upgrade to Podman v5.0.
    • 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?

              tsweeney@redhat.com Tom Sweeney
              tsweeney@redhat.com Tom Sweeney
              Container Runtime Eng Bot Container Runtime Eng Bot
              Container Runtime Bugs Bot Container Runtime Bugs Bot
              Gabriela Necasova Gabriela Necasova
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: