I have a very simple container that I use for building Arch packages, just added it to the Docker Hub so others can use it: https://registry.hub.docker.com/u/tazjin/arch-pkgbuild/ It's basically an Arch container that gets updated at image create time and has base-devel installed. When running the container it automatically executes makepkg from /build. To try enter a folder with a PKGBUILD and just run docker run --rm -v $(pwd):/build tazjin/arch-pkgbuild and it'll install the dependencies in the container and build the package. Note that because of the minimal system the build dependencies need to be correct. The mirrorlist in the container is using servers in Sweden, you could replace it though if you wanted. 2014-09-03 9:04 GMT+02:00 Magnus Therning <magnus@therning.org>:
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.
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 there any aspects to it that makes it a bad choice for building packages?
/M
-- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
Heuristic is an algorithm in a clown suit. It’s less predictable, it’s more fun, and it comes without a 30-day, money-back guarantee. -- Steve McConnell, Code Complete