If it takes along time to boot then it likely isn't getting an ip address from dnmasq. Now last I checked br-int does have a dnsmasq running, but double-check that. You can lxc-attach to the container and manually do sudo dhclient eth0
This is assuming that you are on a new enough lxc so that the other veth endpoint is in fact being attached to br-int. Which version are you using? Quoting Anjali Kulkarni ([email protected]): > Hi, > > I notice that If I add my beth link to any other bridge except lxcbr0, my > ubuntu container takes a really long time to boot up, and seems to hang/wait > for a long time after this statement: > * Starting Bridge socket events into upstart ...done. > > My config file is: > > ……. > # Network configuration > lxc.network.type = veth > lxc.network.link = br-int > lxc.network.ipv4 = 172.16.0.2 > lxc.network.name = eth0 > lxc.network.flags = up > lxc.network.hwaddr = 00:16:3e:d9:c0:ce > > I found out, that if I keep > lxc.network.link = lxcbr0 > Instead of > lxc.network.link = br-int > > It boots up really fast. > Is there any way to get around this? I don't want to add the veth interface > to lxcbr0, but to br-int.. > > Anjali > > _______________________________________________ > lxc-users mailing list > [email protected] > http://lists.linuxcontainers.org/listinfo/lxc-users _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
