kasmtech
[Bug] - Docker memory limit not seen in Workspaces
Describe the bug When checking the amount of memory available (free) it shows the host memory and not the container limits. Same issues described here: https://www.reddit.com/r/docker/comments/huoc3j/any_possible_way_to_show_limited_memory_in/. Could this make workspaces prone to OOMs (running out of memory) and apps unable to manage memory effectively?
To Reproduce Steps to reproduce the behavior:
- Start a new workspace, in my case Firefox with default 2.7G memory limit.
- Load any memory intensive (web)app; I started a speedtest.net on 10G link.
- See error:
Expected behavior Workspace applications to be aware of available memory and not OOM/crash. Running something similar in a VM would degrade performance and have lower speedtest results, but not crash.
Screenshots
After increasing memory limit to 10G, I could see Firefox taking over 5G RAM, peak was 9G during a speedtest:
Workspace memory (from linuxserver.io image) is showing the correct values in the cgroup, but not by tools like free:
Workspaces Version Version 1.16.1.be60db
Workspaces Installation Method Single Server, LXC in Proxmox
Additional context This could be partially mitigated by not using a memory limit, ie. #706.
