Difference between revisions of "LibCT"
m |
(pull request to libcontainer) |
||
| Line 26: | Line 26: | ||
* +/- Integration with Docker libcontainer to give any container system implementing the ability to deploy docker packages | * +/- 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 | * - Backend for Solaris Zones and probably Virtuozzo Windows Containers | ||
| + | |||
| + | == See also == | ||
| + | * [https://github.com/docker/libcontainer/pull/434 Initial integration of libct into libcontainer] | ||
Revision as of 21:13, 19 June 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
