Note: this is the "per-architecture" repository for the i386 builds of https://hub.docker.com/_/cirros -- for more information, see https://github.com/docker-library/official-images#architectures-other-than-amd64 and https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what.
Maintained by:
https://github.com/tianon/docker-brew-cirros
Where to get help:
the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow
Dockerfile linksWARNING: THIS IMAGE IS NOT SUPPORTED ON THE i386 ARCHITECTURE
Where to file issues:
https://github.com/tianon/docker-brew-cirros/issues?q=
Supported architectures: (https://github.com/docker-library/official-images#architectures-other-than-amd64)
https://hub.docker.com/r/amd64/cirros/, https://hub.docker.com/r/arm32v7/cirros/, https://hub.docker.com/r/arm64v8/cirros/, https://hub.docker.com/r/ppc64le/cirros/
Published image artifact details:
https://github.com/docker-library/repo-info/blob/master/repos/cirros (https://github.com/docker-library/repo-info/commits/master/repos/cirros)
(image metadata, transfer size, etc)
Image updates:
https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fcirros
https://github.com/docker-library/official-images/blob/master/library/cirros (https://github.com/docker-library/official-images/commits/master/library/cirros)
Source of this description:
https://github.com/docker-library/docs/tree/master/cirros (https://github.com/docker-library/docs/commits/master/cirros)
The CirrOS project provides linux disk and kernel/initramfs images. The images are well suited for testing as they are small and boot quickly. Please note that:
CirrOS images have useful tools and function for debugging or developing cloud infrastructure.
https://github.com/cirros-dev/cirros#readme
!https://raw.githubusercontent.com/docker-library/docs/b449be7df57e9ed9086bb5821bfb5d6cdc5d67a4/cirros/logo.png
View license information for the software contained in this image:
The code for building CirrOS is available under GPLv2. The binary images that will be distributed contain many different licenses all of which are opensource.
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 https://github.com/docker-library/repo-info/tree/master/repos/cirros.
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 登录认证访问私有仓库
无需登录使用专属域名
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
Harbor Proxy Repository 对接专属域名
Portainer Registries 加速拉取
Nexus3 Docker Proxy 内网缓存
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
manifest unknown
no matching manifest(架构)
invalid tar header(解压)
TLS 证书失败
DNS 超时
410 Gone 排查
402 与流量用尽
401 认证失败
429 限流
D-Bus 凭证提示
413 与超大单层
来自真实用户的反馈,见证轩辕镜像的优质服务