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 a random name of > 'veth6HIE0A' instead of eth0. Am I mistaken as to how this is > supposed > to work. Ideally I would like to see something like > 'veth0-<container-name>' but 'vethN' when N either is assigned > automatically when containers are started or alternatively where I > set N > myself in the container's config. What's possible and what's not? 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 a kernel limit and not configurable or negotiable, but that was a couple of years ago and may have changed. YMMV > Thanks. Regards, Mike -- Michael H. Warfield (AI4NB) | (770) 978-7061 | [email protected] /\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0x674627FF | possible worlds. A pessimist is sure of it!
signature.asc
Description: This is a digitally signed message part
_______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
