docker
/
docker-devuan_paddy-hack
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Sync documentation with current state of affairs 

[ci skip]
This commit is contained in:
Olaf Meeuwissen 2017-08-09 21:52:26 +09:00
parent 6c44a604b1
commit 95525806d2
1 changed files with 22 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
README.md
View File

@ -4,16 +4,35 @@ Devuan Docker Base Images
========================= =========================
Not quite happy with the state of [Devuan][1] [Docker][2] images on Not quite happy with the state of [Devuan][1] [Docker][2] images on
the [Docker Hub][3], I decided to roll my own. First cut is just a the [Docker Hub][3], I decided to roll my own.
migration from the Debian images following the [instructions][4].
You can pull this image with You can pull this image with
``` sh ``` sh
docker pull registry.gitlab.com/paddy-hack/devuan docker pull registry.gitlab.com/paddy-hack/devuan
```
Versioned images are available from the [container registry][4] 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][5].
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].
BTW, you can pull the migrated image with
``` sh
docker pull registry.gitlab.com/paddy-hack/devuan/migrated
``` ```
[1]: https://devuan.org/ [1]: https://devuan.org/
[2]: https://docker.com/ [2]: https://docker.com/
[3]: https://hub.docker.com/ [3]: https://hub.docker.com/
[4]: https://devuan.org/os/documentation/dev1fanboy/Upgrade-to-Devuan [4]: https://gitlab.com/paddy-hack/devuan/container_registry
[5]: https://devuan.org/os/documentation/dev1fanboy/Upgrade-to-Devuan