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

storage.conf contains invalid storage.options.overlay.pull_options* keys that podman cannot decode

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Undefined Undefined
    • None
    • CentOS Stream 10
    • containers-common
    • None
    • Yes
    • None
    • rhel-sst-container-tools
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • All
    • None

      What were you trying to do that didn't work?

      Any podman operation

      What is the impact of this issue to you?

      podman still works but the output has spurious warnings

      Please provide the package NVR for which the bug is seen:

      $ rpm -q podman containers-common
      podman-5.3.1-3.el10.x86_64
      containers-common-0.60.2-13.el10.noarch

      How reproducible is this bug?:

      Always

      Steps to reproduce

      1. sudo dnf install podman
      2. podman image ls
      3.  

      Expected results

      No warnings

      Actual results

      WARN[0000] Failed to decode the keys ["storage.options.overlay.pull_options" "storage.options.overlay.pull_options" "storage.options.overlay.pull_options" "storage.options.overlay.pull_options.enable_partial_images" "storage.options.overlay.pull_options.use_hard_links" "storage.options.overlay.pull_options.ostree_repos" "storage.options.overlay.pull_options.convert_images"] from "/usr/share/containers/storage.conf"

      If I copy storage.conf from /usr/share/containers/storage.conf to /etc/containers and comment out the last line (the "pull_options" key in the `storage.options.overlay` table) then the warning goes away

              rhn-support-jnovy Jindrich Novy
              michel.lind Michel Lind
              Container Runtime Eng Bot Container Runtime Eng Bot
              Container Runtime Bugs Bot Container Runtime Bugs Bot
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: