-
Story
-
Resolution: Unresolved
-
Minor
-
None
-
podman-5.1.0-1.el10
-
1
-
rhel-sst-container-tools
-
5
-
False
-
-
None
-
RUN 252
-
None
This is a follow up of https://issues.redhat.com/browse/RHEL-19138.
When a container is updated to change memory, cpu, etc, the changes are reverted when the container or host is rebooted.
Reproducer steps below,
# podman run -itd --name memory-test ubi8 81506ac128048e0c8323020e34d61a166f31320f3b918e81eb76f7a12fb8e3ca # podman stats memory-test ID NAME CPU % MEM USAGE / LIMIT MEM % NET IO BLOCK IO PIDS CPU TIME AVG CPU % 81506ac12804 memory-test 2.65% 462.8kB / 3.915GB 0.01% 1.056kB / 472B 0B / 0B 1 80.494ms 2.65% # podman update --memory 1G memory-test 81506ac128048e0c8323020e34d61a166f31320f3b918e81eb76f7a12fb8e3ca # podman stats memory-test ID NAME CPU % MEM USAGE / LIMIT MEM % NET IO BLOCK IO PIDS CPU TIME AVG CPU % 81506ac12804 memory-test 0.52% 462.8kB / 1.074GB 0.04% 1.196kB / 612B 0B / 0B 1 80.494ms 0.52% # podman restart memory-test memory-test # podman ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 81506ac12804 registry.access.redhat.com/ubi8:latest /bin/bash 28 seconds ago Up 2 seconds memory-test # podman stats memory-test ID NAME CPU % MEM USAGE / LIMIT MEM % NET IO BLOCK IO PIDS CPU TIME AVG CPU % 81506ac12804 memory-test 1.41% 503.8kB / 3.915GB 0.01% 1.126kB / 542B 0B / 0B 1 76.127ms 1.41%
Is there a way to make these changes persistent ?
- links to
-
RHBA-2024:131606
podman bug fix and enhancement update
