scrumpyjack wrote, On 01/21/2015 01:09 PM:
On Wed, 21 Jan 2015, Fajar A. Nugraha wrote:
It is, to be frank. lxc already supports macvlan, so there's no need to
create it manually and use phys.
I have been reading more in macvlan support and it is now clearer.
If it's I want to to have /32
Quoting Smart Goldman (ytlec2...@gmail.com):
2015-01-17 5:31 GMT+09:00 Serge Hallyn serge.hal...@ubuntu.com:
Operation not permitted? That's unexpected. Are you running a custom
kernel or custom selinux policy?
Yes, mine is ubuntu system provided by a VPS service of
On Wed, 21 Jan 2015, Fajar A. Nugraha wrote:
On Wed, Jan 21, 2015 at 7:09 PM, scrumpyjack scrumpyj...@me.com wrote:
Yes, i want to give a /32 to a container.
This is on ubuntu server. The host has 100.0.0.10/24, router is on
100.0.0.1, the container is on 100.0.0.11 (fake IPs, of course).
lxc version:1.0.7
I tried to create a lxc on lvm with command:
lxc-create -n mylxc2 -t centos -B lvm
and i got the errors:
Copy /usr/local/var/cache/lxc/centos/x86_64/6/rootfs to /dev/lxc/mylxc2 ...
Copying rootfs to /dev/lxc/mylxc2 ...mkdir: cannot create directory
‘/dev/lxc/mylxc2’: File
Quoting 黄奕 (ruffian...@126.com):
lxc version:1.0.7
I tried to create a lxc on lvm with command:
lxc-create -n mylxc2 -t centos -B lvm
and i got the errors:
Copy /usr/local/var/cache/lxc/centos/x86_64/6/rootfs to /dev/lxc/mylxc2 ...
Copying rootfs to /dev/lxc/mylxc2 ...mkdir: cannot create
On Wed, Jan 21, 2015 at 3:31 PM, ScrumpyJack scrumpyj...@me.com wrote:
On Mon, 19 Jan 2015, ScrumpyJack wrote:
I'd like to connect a physical interface from a host to a LXC container
guest like so:
lxc.network.type=phys
And then assign a routable IP/32 address to the LXC container
On Mon, 19 Jan 2015, ScrumpyJack wrote:
I'd like to connect a physical interface from a host to a LXC container
guest like so:
lxc.network.type=phys
And then assign a routable IP/32 address to the LXC container for it to
just work.
The problem is that I don't have a spare real
On Wed, 21 Jan 2015, Fajar A. Nugraha wrote:
It is, to be frank. lxc already supports macvlan, so there's no need to
create it manually and use phys.
I have been reading more in macvlan support and it is now clearer.
If it's I want to to have /32 in the container, then there are other ways
On Wed, Jan 21, 2015 at 7:09 PM, scrumpyjack scrumpyj...@me.com wrote:
Yes, i want to give a /32 to a container.
If i stick to
lxc.network.type = macvlan
lxc.network.flags = up
lxc.network.link = eth0
lxc.network.name = eth1
lxc.network.ipv4 = 21.45.463.23/32 (fake IP, obvs)
