Quoting Fajar A. Nugraha (l...@fajar.net): > On Fri, Sep 13, 2013 at 10:16 PM, Fajar A. Nugraha <l...@fajar.net> wrote: > > > On Fri, Sep 13, 2013 at 7:43 PM, Serge Hallyn > > <serge.hal...@ubuntu.com>wrote: > > > >> I'm wondering > >> > > whether it could just be that there is a socket waiting for a tcp > >> timeout, holding the veth open. > >> > >> > > It may be the case. > > > > However, doing "ip link del" on the host side (after the container was > > down) always succeded in deleting the veth. > > > > > After trying with saucy and latest 3.10 kernel, still the same bug, I gave > up trying to fix this. Just something I have to live with, I guess. > > The strange thing is that dong "ip link del" from the host, even when the > container is up, succeeded. So there should be no problem related to socket > open. > > Is there some kind of hook where I can add the "ip link del" command > manually when the container shuts down?
lxc.network.script.down Sorry I've not had a chance to try to reproduce, but it's an interesting bug. ------------------------------------------------------------------------------ LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
