Update the documentation

[ci skip]
This commit is contained in:
Olaf Meeuwissen 2017-08-26 22:53:08 +09:00
parent 6bff8d5c38
commit 7c5dee0139
1 changed files with 13 additions and 13 deletions

View File

@ -3,27 +3,27 @@
Devuan Docker Base Images
=========================
Not quite happy with the state of [Devuan][1] [Docker][2] images on
the [Docker Hub][3], I decided to roll my own.
For reasons outlined in my [Sandwiching Docker Between Devuan][1] blog
post (in the bottom part), I decided to roll my own Devuan base images.
You can pull this image with
You can pull the latest Devuan ``stable`` image with
``` sh
docker pull registry.gitlab.com/paddy-hack/devuan
```
Versioned images are available from the [container registry][4] as
Versioned images are available from [the container registry][2] as
well.
How does this work?
-------------------
How did I get there?
--------------------
I had to start somewhere, so the first step takes a Debian base image
and converts that following the Devuan [migration instructions][5].
and converts that following the Devuan [migration instructions][3].
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][4].
again to the [container registry][2].
BTW, you can pull the migrated image with
@ -31,8 +31,8 @@ BTW, you can pull the migrated image with
docker pull registry.gitlab.com/paddy-hack/devuan/migrated
```
[1]: https://devuan.org/
[2]: https://docker.com/
[3]: https://hub.docker.com/
[4]: https://gitlab.com/paddy-hack/devuan/container_registry
[5]: https://devuan.org/os/documentation/dev1fanboy/Upgrade-to-Devuan
if so inclined.
[1]: https://paddy-hack.gitlab.io/posts/sandwiching-docker-with-devuan/
[2]: https://gitlab.com/paddy-hack/devuan/container_registry
[3]: https://devuan.org/os/documentation/dev1fanboy/Upgrade-to-Devuan