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

[RHEL EPIC] Persist runtime resource changes in Podman - RHEL 9.5

XMLWordPrintable

    • [RHEL EPIC] Persist runtime resource changes in Podman - RHEL 9.5
    • Hide

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

      • See test suggestions in description.
      Show
      The following needs to be verified in order for this epic to be considered complete: See test suggestions in description.
    • Red Hat Enterprise Linux
    • rhel-sst-container-tools
    • 13
    • False
    • Hide

      None

      Show
      None
    • Yes
    • QE ack, Dev ack, Docs ack, PXE ack
    • Enhancement
    • Hide
      .Runtime resource changes in Podman are persistent

      The updates of container configuration by using the `podman update` command are persistent. Note that this enhancement is for both SQLite and BoltDB database backends.
      Show
      .Runtime resource changes in Podman are persistent The updates of container configuration by using the `podman update` command are persistent. Note that this enhancement is for both SQLite and BoltDB database backends.
    • Done

      Description

      SME: Matt Heon

      Changes made via `podman update` (for example, to change resource quotas) are not currently persistent. This was a design choice in keeping with typical immutable-style deployments. It was later reinforced by database decisions. With the change to SQLite, there was an opportunity to revisit design.

      Possible QE Test:

      podman run dt  -name tester alpine

      podman exec tester cat /sys/fs/cgroup/pids.max   # note number s/b 2048

      podman update --pids-limit=1024 tester

      podman exec tester cat /sys/fs/cgroup/pids.max   # validate 1024

      podman stop tester

      podman start tester

      podman exec tester cat /sys/fs/cgroup/pids.max   # validate 1024

      1. Prior versions of Podman would have the original pids.max value after the stop/start, and NOT 1024

      Goal

      Persist resource modifications made with `podman update` when using SQLite database.

      Non-Goal

      Changing existing BoltDB based deployments.

       

       

              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:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: