mirrors/archlinux-docker
1
0
Fork 0
mirror of https://gitlab.archlinux.org/archlinux/archlinux-docker.git synced 2026-03-28 10:21:01 +01:00
Code Issues Projects Releases Wiki Activity

Document the 'repro' tag in README

Browse Source
This commit is contained in:
Robin Candau 2026-03-23 13:15:16 +01:00
parent 0d7c4c0017
commit ec82ba398e
No known key found for this signature in database
GPG Key ID: FDC3040B92ACA748
1 changed files with 12 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
README.md
View File

@ -12,11 +12,16 @@ Arch Linux provides OCI-Compliant container images in multiple repositories:
* [Daily in our ghcr.io repository][ghcr-containers]:
`podman pull ghcr.io/archlinux/archlinux:latest` or `docker pull ghcr.io/archlinux/archlinux:latest`
Three versions of the image are provided: `base` (approx. 150 MiB), `base-devel`
Four versions of the image are provided: `base` (approx. 150 MiB), `base-devel`
(approx. 260 MiB) and `multilib-devel` (approx. 300MiB) containing the
respective meta package. All of them are available as
tags with `latest` pointing to `base`. Additionally, images are tagged with their
date and build job number, f.e. `base-devel-20201118.0.9436`.
respective meta package; and `repro` which is a bit for bit reproducible image
based on the `base` version (note that, to ensure reproducibility, the pacman keys
are stripped from this image so you're expected to run
`pacman-key --init && pacman-key --populate archlinux` before being able to update
the system and install packages via `pacman`).
All of them are available as tags with `latest` pointing to `base`.
Additionally, images are tagged with their date and build job number,
f.e. `base-devel-20201118.0.9436`.
While the images are regularly kept up to date it is strongly recommended
running `pacman -Syu` right after starting a container due to the rolling
@ -35,7 +40,7 @@ $ cosign verify ghcr.io/archlinux/archlinux:latest --certificate-identity-regexp
* Provide the Arch experience in a Docker image
* Provide the simplest but complete image to `base`, `base-devel` and
`multilib-devel` on a regular basis
* `pacman` needs to work out of the box
* `pacman` needs to work out of the box (with the expection of the `repro` image for now, due to technical constraints)
* All installed packages have to be kept unmodified
>>>
@ -67,7 +72,7 @@ Make sure your user can directly interact with Podman (i.e. `podman info` works)
### Usage
There are multiple `make image-XXX` targets, where each creates the
respective `archlinux:XXX` image based on the corresponding meta package.
Currently those include `base`, `base-devel` and `multilib-devel`.
Currently those include `base`, `base-devel`, `multilib-devel` and `repro`.
## Pipeline
@ -118,4 +123,4 @@ Every year in June the content of the protected `GITLAB_PROJECT_TOKEN` variable
[self-container-registry]: https://gitlab.archlinux.org/archlinux/archlinux-docker/container_registry
[access-tokens]: https://gitlab.archlinux.org/archlinux/archlinux-docker/-/settings/access_tokens
[access-tokens]: https://gitlab.archlinux.org/archlinux/archlinux-docker/-/settings/access_tokens