-
Epic
-
Resolution: Done
-
Normal
-
rhel-9.5
-
[RHEL EPIC] Persist runtime resource changes in Podman - RHEL 9.5
-
-
Red Hat Enterprise Linux
-
sst_container_tools
-
13
-
False
-
-
Yes
-
QE ack, Dev ack, Docs ack, PXE ack
-
Enhancement
-
-
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
- 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.
- clones
-
RHEL-33566 [RHEL EPIC] Persist runtime resource changes in Podman - RHEL 10.0 Beta
- Closed