Re: [lxc-users] lxc insttability

Both. To be accurate, the script tries to delete the host part, but since the pair is managed as one (in terms of add/delete) it causes the pair to be gone as well. -- Fajar On Fri, Feb 19, 2016 at 11:08 PM, Bostjan Skufca wrote: > Does it delete both interfaces, the one in

Re: [lxc-users] lxc insttability

We have noticed this problem too. We are on Ubuntu (trusty) and the veth interfaces do get left behind on the host bridge device (seemingly at random) after stopping ephemeral containers. We have tried to see if it was related to containers being started/shut down in parallel, or due to other

Re: [lxc-users] lxc insttability

Tnx for insight Guido. But this "bug" only happens on RH-based hosts, or not? It might be that it is happening on others too and I am not noticing it as devices detach from bridges and do not interfere with active networking. If this is common case, then maybe LXC itself should rename stale

Re: [lxc-users] lxc insttability

Dear Bostjan The veth will not disappear after shutdown of the container until all pending TCP connections through this veth-pair are timed out (CLOSE/FIN-WAIT). Sometimes, i even can't delete it on the host. And because, i name the host-side of each veth to the name of the container, i have

Re: [lxc-users] lxc insttability

Does it delete both interfaces, the one in host's namespace which is added to bridge (vethX) and the one in container's namespace (appears as ethX in there) too? b. On 19 February 2016 at 11:58, Fajar A. Nugraha wrote: > On Fri, Feb 19, 2016 at 5:41 PM, Bostjan Skufca

Re: [lxc-users] lxc insttability

I had similar experience using CentOS 7 as host. I did not investigate it yet, but for some reason veth network interfaces were not being destroyed when containers stopped, and this could only be seen with "brctl show" as more interfaces were attached to a bridge than there were containers