madworx / docker-minix

QEMU-based Docker image for Minix 3, based on the official CD-ROM ISO image installation from the Minix website

docker-minix

QEMU-based Docker image for Minix 3, based on the official CD-ROM ISO image installation from the Minix website.

QEMU will use KVM acceleration, if your hardware supports it, and you're running the container in privileged mode.

Available at Docker hub as madworx/minix.

Usage

Run a specific command in MINIX

$ docker run --rm -it madworx/minix uname -a
Minix 192.168.76.9 3.3.0 Minix 3.3.0 (GENERIC) i386

Start in background, connect via ssh

$ docker run --rm -d --name minix madworx/minix
$ docker exec -it minix ssh localhost
For post-installation usage tips such as installing binary
packages, please see:
http://wiki.minix3.org/UsersGuide/PostInstallation

For more information on how to use MINIX 3, see the wiki:
http://wiki.minix3.org

We'd like your feedback: http://minix3.org/community/

#

Source

Source code is hosted on github.

Contributions

All and any contributions are welcome in form of pull requests.

Author

Martin Kjellstrand [email protected]

docker-minix's Issues

Stripped PXE-booted distribution

The current setup with a static qcow2 image is a bit clunky, does not utilize the underlying operating systems ability to expand etc.

To reach this goal, we'll need to ascertain the possibility to create a small net-boot or harddrive-based Minix distribution, which can boot enough to pivot the root file system to NFS.

The current Minix "ramdisk"-based solution packs the entire distribution (300Mbyte) into the ramdrive, occupying unnecessary RAM as well as docker image size.

Travis expects log output each 10 minutes

We'll need to rewrite the timeout handling in expect to output status messages (e.g. "still working...") each minute or so, to account for individual build stages potentially taking longer than 10 minutes.

Something is making the builds in Travis CI fail, sometimes

Add debugging to expect and qemu to figure out what's really happening under the hood.
I cannot reproduce this on local builds.