-
Maintained by:
Arch Linux trusted users Santiago Torres-Arias, Christian Rebischke and Justin Kromlinger as well as Arch Linux developer Pierre Schmitz. -
Where to get help:
the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow
-
Where to file issues:
https://gitlab.archlinux.org/archlinux/archlinux-docker/issues -
Published image artifact details:
repo-info repo'srepos/archlinux/
directory (history)
(image metadata, transfer size, etc) -
Image updates:
official-images repo'slibrary/archlinux
label
official-images repo'slibrary/archlinux
file (history) -
Source of this description:
docs repo'sarchlinux/
directory (history)
Arch Linux, is a lightweight and flexible Linux® distribution that tries to Keep It Simple.
Currently, we have official packages optimized for the x86-64 architecture. We complement our official package sets with a community-operated package repository that grows in size and quality each and every day.
Our strong community is diverse and helpful, and we pride ourselves on the range of skill sets and uses for Arch that stem from it. Please check out our forums and mailing lists to get your feet wet. Also glance through our wiki if you want to learn more about Arch.
The root filesystem tarball for this image is auto-generated weekly at 00:00 UTC on Sunday in Arch Linux infrastructure. Given the rolling-release nature of Arch Linux, images are tagged with the included meta package and the timestamp of the date they were generated. For example, archlinux:base-20201101.0.7893
was generated the First of November 2020 in CI job #7893. The latest
tag will always match the latest base
tag.
Besides base
we also provide images for the base-devel
and multilib-devel
meta packages.
This image is intended to serve the following goals:
- Provide the Arch experience in a Docker Image
- Provide simplest but complete image to
base
,base-devel
andmultilib-devel
on a regular basis pacman
needs to work out of the box- All installed packages have to be kept unmodified
⚠️ ⚠️ ⚠️ NOTE: For Security Reasons, these images strip the pacman lsign key. This is because the same key would be spread to all containers of the same image, allowing for malicious actors to inject packages (via, for example, a man-in-the-middle). In order to create a lsign-key runpacman-key --init
on the first execution, but be careful to not redistribute that key.⚠️ ⚠️ ⚠️
Root filesystem tarballs are provided by our GitLab for at least two months.
Arch Linux is a rolling release distribution, so a full update is recommended when installing new packages. In other words, we suggest to either execute RUN pacman -Syu
immediately after your FROM
statement or as soon as you docker run
into a container.
You can build this image with the tools on the Arch Linux GitLab repository using the included makefile.
The Docker image creation scripts contained under the repository archlinux are licensed under GPLv3. All the licensing information for the packages contained in it can be found under /usr/share/licenses/
inside of the image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the repo-info
repository's archlinux/
directory.
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.