Go to file
Olaf Meeuwissen 651ed7d1d5 Work around a documented bug in Devuan jessie's debootstrap
See http://bugs.devuan.org//cgi/bugreport.cgi?bug=115
2017-08-26 22:29:11 +09:00
scripts Use here documents in a consistent manner 2017-08-19 15:09:08 +09:00
.dockerignore Keep git repository out of the Docker context 2017-08-18 11:50:27 +09:00
.gitignore Add a build phase to roll a "pristine" Devuan base image 2017-08-09 21:25:43 +09:00
.gitlab-ci.yml Build based on symbolic suite name 2017-08-26 21:18:09 +09:00
COPYING Add a verbatim copy of the full license text 2017-08-17 12:34:58 +09:00
README.md Sync documentation with current state of affairs 2017-08-09 21:52:26 +09:00
bootstrap.sh Work around a documented bug in Devuan jessie's debootstrap 2017-08-26 22:29:11 +09:00
build.sh Build based on symbolic suite name 2017-08-26 21:18:09 +09:00
builder.df Refactored CI setup and image naming 2017-08-19 14:27:34 +09:00
derive.sh Build based on symbolic suite name 2017-08-26 21:18:09 +09:00
migrate.df Parameterize build on Devuan suite name 2017-08-19 17:53:59 +09:00
migrate.sh Fix oversight in 11e0bd83 2017-08-26 21:40:59 +09:00
repository@devuan.org.asc Fix SKS keyserver network connectivity errors 2017-08-08 06:08:05 +09:00

README.md

build status

Devuan Docker Base Images

Not quite happy with the state of Devuan Docker images on the Docker Hub, I decided to roll my own.

You can pull this image with

docker pull registry.gitlab.com/paddy-hack/devuan

Versioned images are available from the container registry as well.

How does this work?

I had to start somewhere, so the first step takes a Debian base image and converts that following the Devuan migration instructions. The image is pushed to the registry, mainly for reference purposes, and used to run Devuan's debootstrap. This produces a rootfs that is imported to the Docker cache, pushed, re-tagged and pushed again to the container registry.

BTW, you can pull the migrated image with

docker pull registry.gitlab.com/paddy-hack/devuan/migrated