Closed ttys3 closed 2 years ago
@ttys3 will this trigger oom error?
I think I have the same problem with postgres
and mysql
containers. podman stats
shows very high memory usage, but top
, sar -r
on host shows that memory usage is just normal. After a while the container gets kiiled by systemd-oomd
.
@sify21 I do not think OOM related to this issue.
https://github.com/containers/common/pull/870 has been merge.
when new version > 3.4.4 released, this can be closed.
It is in the release candidates for 4.0 now.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
related PR:
https://github.com/containers/podman/pull/12703
https://github.com/containers/common/pull/870
Description
podman stats
shows incorrect memory usageSteps to reproduce the issue:
prepare data dir:
sudo podman play kube kafka.pod.yaml
kafka.pod.yaml content:
go run producer.go
podman stats
, you will see the kafka broker container memoryUSAGE
increasing very fast, you'll see it goes to GBsbut if you
exec
into the contianer, and usetop
show the real memory usage, it only used344M
maybeJust wait small minutes in order to generate some network traffic for the container.
Describe the results you received:
The memory increase very fast, and incorrect.
Describe the results you expected:
the memory usage should match the one
RSS
intop
command in the container.Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
cgroup v2
kernel
5.15.11-arch2-1 #1 SMP PREEMPT Wed, 22 Dec 2021 09:23:54 +0000 x86_64 GNU/Linux