refine docker section
This commit is contained in:
parent
a7da48e7ec
commit
4a2ec0efd3
1 changed files with 3 additions and 3 deletions
|
@ -18,18 +18,18 @@ tweaking to before becoming fully functional.
|
|||
### Docker
|
||||
|
||||
this project uses [Dockerfiles][df] to allow for *mostly-reproducible* builds.
|
||||
[podman][podman] is used instead of docker, because the official docker software
|
||||
[podman][podman is used] instead of docker, because the official docker software
|
||||
is commercial and obnoxious.
|
||||
|
||||
**neither docker nor podman is required for executing the binaries.**
|
||||
binaries are to be isolated and extracted from the resulting containers.
|
||||
those binaries can then be transferred across platforms, like any other APE.
|
||||
|
||||
[podman]: https://docs.podman.io/en/latest/markdown/podman-build.1.html
|
||||
[df]: https://docs.docker.com/engine/reference/builder/
|
||||
[podman]: https://docs.podman.io/en/latest/markdown/podman-build.1.html
|
||||
|
||||
in the future, it would be nice to use something
|
||||
like what [Void Linux][void] does for its packages,
|
||||
like [what Void Linux does for its packages,][void]
|
||||
which would entirely sidestep the clunkiness
|
||||
of Dockerfiles and working with containers.
|
||||
|
||||
|
|
Loading…
Reference in a new issue