Difference between revisions of "LibCT"
(add status of implementation according to mail from jejb https://lists.linux-foundation.org/pipermail/containers/2014-June/034669.html) |
m |
||
| Line 1: | Line 1: | ||
| + | == Description == | ||
| + | |||
| + | Libct is a containers management library which provides convenient API for frontend programs to rule a container during its whole lifetime. | ||
| + | |||
| + | == Source code == | ||
| + | |||
| + | [https://github.com/xemul/libct https://github.com/xemul/libct] | ||
| + | |||
== Requirements == | == Requirements == | ||
* '''DONE''' C/C++ bindings (for Parallels SDK) | * '''DONE''' C/C++ bindings (for Parallels SDK) | ||
Revision as of 15:31, 30 April 2015
Description
Libct is a containers management library which provides convenient API for frontend programs to rule a container during its whole lifetime.
Source code
https://github.com/xemul/libct
Requirements
- DONE C/C++ bindings (for Parallels SDK)
- DONE Python bindings (for OpenStack)
- Might make sence to write Python code that just goes via RPC
- DONE Fine grained support for namespaces and cgroups
- +/- Extendable support for different private FS
- +/- Extendable support for different NICs
- DONE Support for external bind mounts
- DONE Ability to enter a CT
- +/- Ability to configure running CT
- - Integration with CRIU for checkpointing
- - Integration with CRIU for migration
- - Ability to operate on remote host
- - Ability to be used by non-root App
- - Ability to resurrect after sudden App crash
- - Ability to work on OpenVZ kernel (backend)
- - Ability to run libct supporting tools on older (OpenVZ) kernels (depends on above)
- +/- Integration with Docker libcontainer to give any container system implementing the ability to deploy docker packages
- - Backend for Solaris Zones and probably Virtuozzo Windows Containers
