
library/archlinuxMaintained 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
Dockerfile linkslatest, base, base-20260104.0.477168
base-devel, base-devel-20260104.0.477168
multilib-devel, multilib-devel-20260104.0.477168
Where to file issues:
[***]
Supported architectures: (more info)
amd64
Published image artifact details:
repo-info repo's repos/archlinux/ directory (history)
(image metadata, transfer size, etc)
Image updates:
official-images repo's library/archlinux label
official-images repo's library/archlinux file (history)
Source of this description:
docs repo's archlinux/ 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.
!logo
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:
base, base-devel and multilib-devel on a regular basispacman needs to work out of the box⚠️⚠️⚠️ 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 run
pacman-key --initon 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.
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务