-
Bug
-
Resolution: Done-Errata
-
Major
-
rhel-8.8.0
-
None
-
None
-
ZStream
-
1
-
rhel-sst-container-tools
-
3
-
False
-
-
None
-
RUN 252
-
Approved Blocker
-
None
Description of problem:
podman update --memory option not updating the memory of the running container
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux release 8.8 (Ootpa)
Client: Podman Engine
Version: 4.4.1
API Version: 4.4.1
Go Version: go1.19.12
Built: Tue Sep 19 16:01:11 2023
OS/Arch: linux/amd64
How reproducible:
Steps to reproduce
- on any running container execute "podman stats" It will show you the memory it consuming currently and memory it can avail. That is the default memory of the machine
ID NAME CPU % MEM USAGE / LIMIT MEM % NET IO BLOCK IO PIDS CPU TIME AVG CPU %
8ae9b2b73438 test-purpose 0.00% 46.56MB / 1.865GB 2.50% 35.64kB / 8.835kB 235.4MB / 2.482MB 3 4.065274047s 0.04%
- now update the memory given to the container as below.
[root@rhel8 system]# podman update --memory 1G test-purpose
8ae9b2b73438db38b3744726f008af865bb500aeb95372759dd9d0e68930f301
- the new allocated memory is not seen with "podman stats"
ID NAME CPU % MEM USAGE / LIMIT MEM % NET IO BLOCK IO PIDS CPU TIME AVG CPU %
8ae9b2b73438 test-purpose 0.03% 37.86MB / 1.865GB 2.03% 35.64kB / 8.835kB 235.4MB / 2.482MB 3 4.066264632s 0.03%
Expected results : once we update memory of a running container using "podman update --memory" command podman stats should provide us the updated limit of the memory
Actual results: No changes are seen after executing "podman run --memory etc.." in podman stats.
Regards
Sachin
- links to
-
RHSA-2023:122557 container-tools:rhel8 security, bug fix, and enhancement update
-
RHSA-2023:123943 podman security, bug fix and enhancement update