3 ms·
Someone (probably me, eventually) needs to write a libcontainer and a libresource that can be used on BSD / Linux without the LXC mess
by nwmcsween 13y ago
Someone (probably me, eventually) needs to write a libcontainer and a libresource that can be used on BSD / Linux without the LXC mess
- contingencies 13y agoLike this? http://libvirt.org/ http://libvirt.org/ It seems the FreeBSD port originally failed due to deficiencies in kernel features[1] but is now available[2] at least partially, possibly only to manage workloads on remote systems (typically Linux). [1] http://forums.freebsd.org/showthread.php?p=100894 http://forums.freebsd.org/showthread.php?p=100894 [2] http://svnweb.freebsd.org/ports/head/devel/libvirt/ http://svnweb.freebsd.org/ports/head/devel/libvirt/
- nwmcsween 13y agoNo libvirt is a disgusting mess, look at the internals sometime.
- chubot 13y agoDo you have experience with BSD RACCT? https://wiki.freebsd.org/Hierarchical_Resource_Limits https://wiki.freebsd.org/Hierarchical_Resource_Limits If so I'm curious how they compare with cgroups. I agree a platform-independent API would be very useful, but I wonder how close the semantics are. I think a process-isolation model, possibly with capiscum, is more interesting than the LXC-like "VM model" (which does seem messy to me). I don't need an init process and fake hardware inside the container. Just Unix process tree isolation. For example, I think BSD jails have the option to use host networking, which in Linux is analogous to not using network namespaces.