On Wed, Sep 03, 2014 at 12:36:23PM -0400, Leonid Isaev wrote:
On Wed, Sep 03, 2014 at 09:04:37AM +0200, Magnus Therning wrote:
For various reasons I'm looking into not using `makechrootpkg` when building the 200+ packages I put into a non-official repo. Obviously it's important to keep the building environment separate from my ordinary system environment. Going to full virtualisation is definitely overkill and the only containers I know of are chroots and docker.
If by chroot you mean also nspawn, then it is mostly equivalent to docker and lxc. The only thing bad about systemd-nspawn is its lack of easy config through files (it only supports cmdline switches which is ridiculously cumbersome). Also, docker is more complex than a plain lxc-tools approach.
So, I would go with lxc as the simplest and most flexible solution. In fact, that's how I build my packages.
Oki, I've never looked at lxc, I was under the impression that docker used to build on lxc in the past. Is that not true any longer?
Is there a template included for Arch? That would be quite nice because building the docker image for Arch is a bit ugly I'd say....
Finally, what about running a 32bit container on a 64bit host? I've not managed to find any indication that this is officially supported in docker, but it seems to work just fine.
Docker has some nice attributes, in particular no need for root access. However, I don't know a whole lot about it, so I wonder are
Where do you take this from? Rootless containers require a specific host kernel configuration (which -ARCH kernels don't have).
Well, I'm probably imprecise here. What I meant was that after the service has been started (which requires root) any user in the docker group can start images.