http://bugzilla.opensuse.org/show_bug.cgi?id=1130161
http://bugzilla.opensuse.org/show_bug.cgi?id=1130161#c6
--- Comment #6 from Lutchy Horace
Must be a side effect of running inside your container. I cannot see a memory usage like that for a zypper search run on my machine directly.
I suspect that could be attributed to we're running entirely different LXC versions.
Can you provide the steps to reproduce your test env? Or is it just a plain OpenSUSE Tumbleweed container running in a default LXC container?
This bug report is against openSUSE Leap 15.0 though I am also experiencing similar behaviour with latest openSUSE Tumbleweed. Sure, you can see some context here https://forum.proxmox.com/threads/opensuse-containers-problem.52520/#post-24.... 1. Install latest Proxmox 5.3-11. 2. Pull latest image of openSUSE Leap 15.0 with lxc-download. 3. Create CT as unprivileged, see https://bugzilla.opensuse.org/show_bug.cgi?id=1130137. 4. Launch CT 5. At least for me, console doesn't get shown, lxc-attach will do. 6. Run 'zypper search openssh' 7. Observer memory usage from WebUI, lxc-info, or inside the container.
Also once zypper exits there is no way it can still use up any memory since the kernel will clean up all ressources that are allocated by the process.
I suspect this due to those lstat calls, something inside the kernel is holding that memory.
So if the mem consumption of your container stays high even after zypper exits there is something else wrong here.
I reported to LXC here https://github.com/lxc/lxc/issues/2918. I'll include another report to Proxmox later on. -- You are receiving this mail because: You are on the CC list for the bug.