Quoting Vitaly Lavrov ([email protected]): > On 25.02.2014 22:54, Serge Hallyn wrote: > >Quoting Vitaly Lavrov ([email protected]): > >>On 23.02.2014 03:36, Stéphane Graber wrote: > >>>Hi, > >>> > >>>Thanks for your patch. > >>> > >>>Can I just ask you to sign it off? (Signed-off-by: Name <email>) > >>Hi! > >> > >>I found the source of the problem with a reboot of the container, but do > >>not know how best to fix it. > >>We have a race condition between the end of the old container and the > >>creation of the network interfaces > >>in the new container. Insert usleep (100000) before lxc_delete_network() > >>solves the problem with a reboot, > >>but it's a bad way. > >> > >>How to wait until the completion of the container? > > > >How exactly are you doing the test? just script > > > > lxc-start; > > lxc-stop; > > lxc-start; > lxc-stop -rn container
A-ha! Thanks. Yes, this is a bug in our reboot handling in lxcapi_start(). I can reproduce it trivially with lxc-stop -r on any container with lxc.network.type = phys. _______________________________________________ lxc-devel mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-devel
