[lxc-users] LXC, criu and cgroups...

[Tycho Andersen]

On Tue, Apr 07, 2015 at 10:11:18PM +0200, Dirk Geschke wrote:
> Hi Tycho,
> 
> I'm one step further again. rsync seems to use nc -U, but this
> option is not part of netcat.traditional, but netcat.openbsd 
> knows it. So with this packages I'm one step ahead.

Ah, actually it is LXD's rsync wrapper that is doing the nc -U, sounds
like we should stick a depends on netcat-openbsd in the packaging.
Thanks for pointing that out.

> I guess, one should react on errors if rsync fails...
> 
> Now it stops at:
> 
>    2015/04/07 21:51:45 client cert != key for 192.168.1.233
>    2015/04/07 21:51:45 allowing untrusted GET to /1.0/operations/70d96f6d-5dd0-49dc-b86c-c5e33702a01d/websocket?secret=LhfAenvHyoM2p4ycwkvYdc5pU6cX9XuLIh%2FLr8b6luTEkBqn4gjf81KEnbbEKXLdLMxGWKTbBQaPTaP8hwMPAx89rLI0FQLDK%2FfvX45RlcvbUHRuMGfW3PH9ijRmdLOEzHhm8g%3D%3D
>    2015/04/07 21:51:47 got error getting next reader websocket: close 1005, &{{%!s(*net.netFD=&{{10 0 0} 15 1 1 false unix 0xc2080e1b60 0xc2080e1b80 {139714654178008}})}}
> 
> The first two messages are irritating, but it seems to work. On
> the target host, I can find the img-files in /var/tmp/lxd_migration_...
> 
> But then, nothting else. After a reboot of the source host, nothing
> changes. On the source host I see again:
> 
>    2015/04/07 22:06:51 got error getting next reader websocket: close 1005 , &{{%!s(*net.netFD=&{{10 0 0} 14 1 1 false unix 0xc20811d780 0xc20811d7a0 {140705565387480}})}}
> 
> and on the target system:
> 
>    2015/04/07 22:06:51 got error getting next reader read tcp 192.168.1.233:8443: use of closed network connection, &{%!s(*os.File=&{0xc2080d6ae0}) {{%!s(int32=0) %!s(uint32=0)} %!s(uint32=0)} <nil>}
> 
> strange...

Can you show the output of `ps auxf`? Is it still hung rsyncing
something?

Tycho

> > > PS: I was not aware, that simply installing lxcfs will start it,
> > >     I did not even see it running. But probably it installs some 
> > >     lxc hooks for the bind mounts...
> > 
> > Yep, that's exactly right. Unfortunately, there are a couple of
> > problems with lxcfs: criu doesn't understand overmounting, and criu
> > doesn't understand how to dump fuse filesystems. So for now, we can't
> > c/r containers with lxcfs.
> 
> Ah, okay, systemd in a container seems to be no good idea at all.
> It takes multiple times more to start then plain old SysVInit...
> 
> Best regards
> 
> Dirk
> 
> -- 
> +----------------------------------------------------------------------+
> | Dr. Dirk Geschke       / Plankensteinweg 61    / 85435 Erding        |
> | Telefon: 08122-559448  / Mobil: 0176-96906350 / Fax: 08122-9818106   |
> | dirk at geschke-online.de / dirk at lug-erding.de  / kontakt at lug-erding.de |
> +----------------------------------------------------------------------+
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users