On Tuesday, 10.11.2015 at 13:55, Anil Madhavapeddy wrote: > On 28 Oct 2015, at 14:43, Martin Lucina <[email protected]> wrote: > > > > Hi all, > > > > following up on Justin's work on Docker builds, I've made Docker images > > with pre-built rumprun toolchains available. > > > > This should help people on Linux or Mac who don't want to build their own > > toolchain from source, and in theory could be used to develop on Windows as > > well. > > > > Quick start: > > > > 1. Install Docker. > > 2. $ docker run -ti mato/rumprun-toolchain-hw-x86_64 > > > > The images are automatically rebuilt when rumpkernel/rumprun changes. > > > > For details, please see the Wiki page at > > http://wiki.rumpkernel.org/Howto:-Using-prebuilt-Rumprun-toolchains-with-Docker > > This is very useful, thanks! I've got Nginx working with an additional > container that adds in genisoimage/curl to the mix. > > I notice that the automated build of rumprun-packages includes these > packages, but then disables its use interactively via a "CMD" entry: > > CMD ["echo", "This is a CI container, nothing to run here!"] > > It would be quite useful to have a container that includes everything > needed to build rumprun-packages, and then the CI build on top of that. > (or else everyone building rumprun-packages using your toolchain > container will just need to repeat the installation of the build > prerequisites).
Good idea. TODO.PUSH(this) :-) In the long run, I think there should be a separate docker image for each package, rather than one giant image that builds everything. However, I don't yet know how to implement that in an automated fashion. -mato
