scripts and Dockerfiles to build jmtd/debian* docker images
What I use to build jmtd/debian:* docker images on the Docker registry.
-
build: This is a sid/unstable base image, variant buildd: this includes
apt,build-essentialand their dependencies. It's suitable as a base image for building a Debian package, or the basis of a buildd. -
jessie: a base debian installation of jessie (current stable). Approx. 218M in size.
-
wheezy: a base debian installation of wheezy (oldstable). Approx 163M in size.
-
wheezy-i386: a base debian installation of the i386-architecture version of wheezy. This could be used for anything requiring a 32-bit toolchain. Approx 166M in size.
To build your own images, clone this repo, cd to the local path and run
sudo make release=jessie prefix=jmtd arch=amd64 mirror=http://httpredir.debian.org/debian/
All the arguments above are optional. The values in the example above are
the defaults. The resulting image would be tagged jmtd/debian:jessie-amd64.
I don't want to maintain a zillion different images, but there are a few other variants that might be of use for people:
- Now jessie is released, I'll probably add jessie-i386 and phase out wheezy-i386.
- Perhaps introduce floating release tags, e.g.
:stable. - A
winebase image, derived from (probably)jessie-i386. - Possibly a base X image, with x11vnc, uxterm and a lightweight window
manager. Last I checked
openboxwas a bit smaller thanicewm. - minimised images. As per Joey H's blog, The Debian images here are
base Debian images, to avoid being misleading, but that makes them much
larger than Docker's "semi-official" Debian images (twice as large). We
could/should offer minimized images, starting with
--variant=minbasebut also incorporating other things, such as some of the techniques used by emdebian. Just so long as we clearly label them as being modified from stock Debian.
what does docker.io run -it debian sh
run? by Joey Hess, which
recommends only trust docker images you build yourself
.
— Jonathan Dowland jmtd@debian.org