1 = Info for developers =
3 == Command Line Tool ==
7 # pct create 200 debian-7.0-standard_7.0-2_i386.tar.gz
13 You can get detailed help with:
19 We use integers values for container names (and do not allow to use
20 arbitrary names for containers).
22 == LXC Configuration ==
24 We store LXC container configurations on the cluster file system:
26 /etc/pve/nodes/lxc/<CTID>.conf
28 There is a symbolic link for the local node at
30 /etc/pve/lxc => /etc/pve/nodes/<localhost>/lxc
32 see man pct.conf for syntax details.
36 CRIU (1.5.2) does not work well with kernel 3.10.0, so checkpoint/restore
37 and live migration does not work.
43 - LXD uses a local database to store configuration files, which simply
44 does not work with our distributed configuration file system
47 - We want to use our existing libraries (i.e. Storage). Also see:
48 https://lists.linuxcontainers.org/pipermail/lxc-users/2015-June/009441.html
49 where they write: "Lxd will not be as flexible as lxc in many ways,
50 including with respect to backing stores."
52 We have a different goal, and want to support many new storage technologies
55 - It is a wrapper around LXC, and only provides a REST API and new CLI
56 tool. But Proxmox VE already provides a full featured API, and CLI tools
57 are automatically generated from that API.