[Lxc-users] veth interface not deleted?

[Serge Hallyn]

Quoting Fajar A. Nugraha (list at fajar.net):
> On Tue, Oct 1, 2013 at 4:46 AM, Serge Hallyn <serge.hallyn at ubuntu.com>wrote:
> 
> > Quoting Fajar A. Nugraha (list at fajar.net):
> >
> >
> > Would injecting tcp rst really be necessary? In my test, doing "ip link
> > > del" on the host side of the interface ALWAYS succeed, no matter what the
> > > state the guest container's interface is.
> > >
> > > Serge, do you have the particular commit ids for
> > "lxc.network.script.down"
> > > support? Backporting that would probably be the best step for me to try.
> >
> > commit 74a2b5864f2ece87bf522d1c1cbd590dc24c0c53
> > Author: Jan Kiszka <jan.kiszka at siemens.com>
> > Date:   Mon Jul 9 19:15:48 2012 +0200
> >
> >     Add network-down script
> >
> >
> 
> A follow up to this issue, I found out that the lxc package from
> ubuntu-lxc/stable (1.0.0~alpha2+) can't be use as-is on current LTS
> (precise) due to various issues (e.g. apparmor problem, containers detected
> as not started if started automatically on boot but behaves correctly when
> started manually, etc) which I haven't had time to track further.

ubuntu-lxc/daily fixes the autostart containers detected as not started
issue.  Might also fix your apparmor issue - I woudl assume it does
since it is what I run very heavily on my precise box.

I also never have stray veths.

-serge