Paul Colomiets

By the way, you can use the following in the apt-sources.list, to skip confirmation on each upgrade: ``` deb [arch=amd64 trusted=yes] http://ubuntu.zerogw.com vagga main ```

Yes, you're right. I'll try to move it to HTTPS in a week or so (should be a little bit easier than package signing).

Okay, `https://ubuntu.zerogw.com` is up and running. I'm not going to enable HSTS or redirects. I mean it will be accessible both by HTTP and HTTPS at least for some time....

BTW, I'm curious about your integration with integer32 playpen. I would be cool if you share some details in chat or just contact me privately.

@piranna you already can do this, if you have the kernel which supports unprivileged overlayfs (ubuntu has, as well as our arch linux kernel build). You can check it with...

@jirutka, can you share a link? I though docker had problems with first version of overlayfs driver, but they have fixed all issues in the second version (by "overlayfs driver"...

> How? Hardlinks can work only if you can ensure that files will not be modified in-place, but always recreated. Sure. We can hardlink equal files after image has been...

Hm.. can you try `tailhook/vagga` image? This one is tested. This allows us to find out if this is a problem with the docker image, or some kind of kernel...

> I'm not entirely sure whether that section applies to the host or the container where vagga is running To the host. But if it's in container is `1` then...

@mkpankov, vagga uses pivot root everywhere exactly for this reason. So the issue is somewhere else.