[lxc-users] Containers start without networking
Hello, After the first boot of my hosts, the containers are auto-starting without networking. I have to lxc-stop and lxc-start (without the -d) to "service networking restart" and all goes right. LXC version : 0.8.0~rc1-8+deb7 Regards, -- *Joris MICHAUX* Ingénieur systèmes et réseaux *Skype:* h4mm3r.toxyc 425, rue Jean Rostand 31670 Labège, France *Tel:* +33 (0)5 82 08 07 31 www.france-pari.fr - www.sportnco.com *Social:* [facebook] https://www.facebook.com/pages/France-Pari/ [twitter] https://twitter.com/FrancePari [linkedin] http://www.linkedin.com/company/france-pari [scoop.it] http://www.scoop.it/t/paris-sportifs-1 Rencontrez-nous au salon EIG à berlin, stand #525* du 20 au 23 octobre Meet us at *EIG in Berlin, stand #525*: 20-23 October ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Containers start without networking
Hello, I never encounter this problem with my containers. However, you should upgrade LXC to a more recent version to see if the problem persists. According to the version you mention, i assume that you run LXC in a Debian Wheezy (oldstable). If you do not plan to upgrade to Debian Jessie (stable), you should use the LXC package in the Wheezy backports. This version is 1:1.0.6-6+deb8u1~bpo70+1 and is more up-to-date. Friendly, Xavier Le 23/09/2015 08:59, Joris Michaux a écrit : Hello, After the first boot of my hosts, the containers are auto-starting without networking. I have to lxc-stop and lxc-start (without the -d) to "service networking restart" and all goes right. LXC version : 0.8.0~rc1-8+deb7 Regards, ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
[lxc-users] Parity containers
I had to stop using LXC when running my application, Asterisk, resulted in crashes. Something has changed lately.I used the latest Centos 7 kernel, from elrepo. Can somebody help me by providing a config file where a container has 100% rights, in parity with the main session of the computer? For me LXC is just a way to partition my box into lighter virtual machines, so I need full parity, where the container has full access to all resources of the machine. I think too much security ends up getting in the way of the business. ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Eth0 not present on boot
Dear Peter, I also rename the veth to the name of the container and without this, as the default a random name will be used. You'll see why with the later you don't notice an issue: If a container goes down, the veth did not vanish as long as there is a tcp connection using it. And in case of a shutdown scenario, there's a good chance to interrupt communication processes in the middle of conversation, e.g. during delivery of content. Then, an outerside client will wait for output until an application level timeout or because of TCP handshake timeouts. This typically will take about 5min. In my experience, sometimes you even cant "delete the link" as described by Fayar, but i was able to rename the interface "away" (ip link set dev $DEV name $DEV._away). It will vanish later but the restarting container may use the name again for a new veth. greetings Guido On 23.09.2015 03:24, Peter Steele wrote: > On 09/22/2015 08:08 AM, Guido Jäkel wrote: >> * Do you use lxc.network.veth.pair to name the hosts side of the veth? > Yes. I rename the veth interfaces to match the names of the containers. >> * Was the Container up and running "just before" and you (re)start it within >> less than 5min? >> > Yes. When the problem occurs, a reboot has just been issued on the container > (using the "reboot" command). When the container restarts, its eth0 is > missing. Another reboot and the eth0 interface reappears. Curiously, it > appears to happen much more frequently on some hardware than it does on > others. > > ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] Eth0 not present on boot
Up to know, we've only seen it happen on specific servers, running one of our test suites. The same test suite on my personal cluster does not exhibit this issue, whereas the test engineer that encountered this problem sees it regularly. My servers have SAS drives whereas his have SATA drives. Other than that the servers are not especially different (1U four drive systems). I'm going to have to get some quality time on the misbehaving servers and try to get a better understanding of what's going on using a simpler test to reproduce the problem. Peter On 09/23/2015 01:38 PM, Guido Jäkel wrote: Dear Peter, I also rename the veth to the name of the container and without this, as the default a random name will be used. You'll see why with the later you don't notice an issue: If a container goes down, the veth did not vanish as long as there is a tcp connection using it. And in case of a shutdown scenario, there's a good chance to interrupt communication processes in the middle of conversation, e.g. during delivery of content. Then, an outerside client will wait for output until an application level timeout or because of TCP handshake timeouts. This typically will take about 5min. In my experience, sometimes you even cant "delete the link" as described by Fayar, but i was able to rename the interface "away" (ip link set dev $DEV name $DEV._away). It will vanish later but the restarting container may use the name again for a new veth. greetings Guido On 23.09.2015 03:24, Peter Steele wrote: On 09/22/2015 08:08 AM, Guido Jäkel wrote: * Do you use lxc.network.veth.pair to name the hosts side of the veth? Yes. I rename the veth interfaces to match the names of the containers. * Was the Container up and running "just before" and you (re)start it within less than 5min? Yes. When the problem occurs, a reboot has just been issued on the container (using the "reboot" command). When the container restarts, its eth0 is missing. Another reboot and the eth0 interface reappears. Curiously, it appears to happen much more frequently on some hardware than it does on others. ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
