OpenVZ containers - how can you manage /dev/shm sharing?

Hello everyone,

Hope your week is going well! I'm very new to containers and most of my
past work has been in the virtualized environments, recently I'm working
more with containers and ran into a weird issue.

We have OpenVZ containers at work and some of these are running Jenkins in
slave mode. To speed things up, these were set up to use the Jenkins
workspace as a mount in */dev/shm* (tmpfs memory). So while working on
these systems, they reported that during a build, the slaves would report
out of memory errors.

The issue is that Jenkins copies over GB's of files to the workspace
mounted in memory and exceeds the physical memory allocation for the VE
(guest container). The problem is the HN (hardware host) has 144GB of
memory and it's correctly allocating the */dev/shm* as 71GB (please correct
me if I'm wrong here), which is showing up for the guest VE's as well, even
though they only have 20GB of allocated physical memory.

Being new to containers, what is the proper method to share resources like
*/dev/shm* with containers? Should you oversubscribe the containers
(risking the host go OOM) or keep hard limits?

Any recommended read is highly welcome!

Thanks,
Rob


-- 
Robert Freiberger
510-936-1210

_______________________________________________
svlug mailing list
[email protected]
http://lists.svlug.org/lists/listinfo/svlug