On Mon, Aug 31, 2015 at 5:10 AM, Michael H. Warfield
wrote:
> On Sun, 2015-08-30 at 13:51 -0700, Peter Steele wrote:
> > I want to pick my own naming convention for the veth interfaces
> > created
> > by LXC rather than using the auto-generated names. I tried adding the
> > entry
>
> > lxc.networ
On 08/30/2015 03:10 PM, Michael H. Warfield wrote:
I played with this a while back and found that you are severely
limited for the name length. Using the container name for that is,
sooner or later, going to overflow that limit and possibly generated
an error on container startup. I think it's
On 08/30/2015 04:37 PM, Andrey Repin wrote:
Please start from the beginning.
What network topology you want for your containers, and what specific features
you need from VETH interface, that other networking modes do not offer?
I'm using host bridging with lxc.network.type = veth. Everything is
Hi,
I would like to know if there is an alternative option of lxc.network.script.up
with an unprivileged containter.
It looks like this configuration file is not used.
I would like to use script.up and script.down to manage the network and
Openflow configuration
Every time a containter star
Greetings, Peter Steele!
> I want to pick my own naming convention for the veth interfaces created
> by LXC rather than using the auto-generated names. I tried adding the entry
> lxc.network.veth.pair = veth0
> in one of my privileged containers but it still get a random name of
> 'veth6HIE0A'
On Sun, 2015-08-30 at 13:51 -0700, Peter Steele wrote:
> I want to pick my own naming convention for the veth interfaces
> created
> by LXC rather than using the auto-generated names. I tried adding the
> entry
> lxc.network.veth.pair = veth0
> in one of my privileged containers but it still get
Hi Peter,
lxc.network.type = veth
lxc.network.veth.pair = veth0
Should be enough in your container configuration file (config)
Also, you can make sure there is no related entries in lxc.conf and
default.conf .
lxc.network.veth.pair cannot be set when using Unprivileged container
But you
I want to pick my own naming convention for the veth interfaces created
by LXC rather than using the auto-generated names. I tried adding the entry
lxc.network.veth.pair = veth0
in one of my privileged containers but it still get a random name of
'veth6HIE0A' instead of eth0. Am I mistaken as
Is there a way to determine the auto-generated MAC address that
lxc-create assigns to a container, apart from starting it and inspecting
the live container?
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.or
On 08/30/2015 11:10 AM, Peter Steele wrote:
Clearly there is user error here on my part and I am not correctly
specifying how to configure LXC containers to use host bridging under
CentOS. I'll have to do some more digging.
I figured it out. I've been using commands similar to
lxc-create -t
Yonsy, yes, 1.0.7 was the version I was referring to with "lts-lxc".
For reference, I've created the kernel issue here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490267
Best,
Thomas
On Sun, Aug 30, 2015 at 7:15 PM, Yonsy Solis wrote:
>
>
> On dom, ago 30, 2015 at 8:19 AM, Serge Hal
On 08/29/2015 03:26 PM, Fajar A. Nugraha wrote:
It should be "tcpdump -n -i bond0 host 172.16.0.1" and "tcpdump -n -i
veth5BJDXU host 172.16.0.1"
Okay, I ran this test, plus a few others. This specific test generated
no icmp traffic on either bond0 or the veth interface. After starting
th
On dom, ago 30, 2015 at 8:19 AM, Serge Hallyn
wrote:
Quoting Thomas Müller (muellerthomas...@gmail.com):
Hi Serge,
thanks for your response.
If this is a kernel issue, what puzzles me a bit is that this error
goes
away when switching from the lts-lxc version to the lxc-stable ppa.
Wh
Quoting Thomas Müller (muellerthomas...@gmail.com):
> Hi Serge,
>
> thanks for your response.
>
> If this is a kernel issue, what puzzles me a bit is that this error goes
> away when switching from the lts-lxc version to the lxc-stable ppa. While
Hm, then maybe I'm wrong. Though I'm failing to
Hi Serge,
thanks for your response.
If this is a kernel issue, what puzzles me a bit is that this error goes
away when switching from the lts-lxc version to the lxc-stable ppa. While
the ppa version seems to fix this bug, it still has the issue that oleg
mentioned above (
https://bugs.launchpad.n
15 matches
Mail list logo
