I’m using the package 2.0.7-2~bpo8+1 on Debian Jessie. (from backports)
According to the topic here - I should use man pages to get the current documentation.
If I follow
man lxc.info - I should use the network key with the index [i]:
lxc-info -n foo -c lxc.network.0.veth.pair
it I try it with the following cmd, it works like documented:
lxc-info -n test -c lxc.network.0.ipv4
if I use the config key which is documented for lcx.container.conf, it’s not working:
specify the ipv4 address to assign to the virtualized interface. Several lines specify several ipv4 addresses. The address is in format x.y.z.t/m, eg. 192.168.1.123/24. The broadcast address should be specified on the same line, right after the ipv4 address.
lxc-info -n test -c lxc.network.ipv4
It looks like, some parts already using the API / config for LXC 2.1 and some not.
I’m working on a Puppet LXC container management module, using the ruby-lxc 1.2.2 bindings and it has no constant behavior, which makes it very complicated to implement the provider.