注意:这是https://hub.docker.com/_/docker%E7%9A%84%60arm32v6%60%E6%9E%84%E5%BB%BA%E7%9A%84%22%E6%AF%8F%E6%9E%B6%E6%9E%84%22%E4%BB%93%E5%BA%93%E2%80%94%E2%80%94%E6%9B%B4%E5%A4%9A%E4%BF%A1%E6%81%AF%EF%BC%8C%E8%AF%B7%E5%8F%82%E8%A7%81%E5%AE%98%E6%96%B9%E9%95%9C%E5%83%8F%E6%96%87%E6%A1%A3%E4%B8%AD%E7%9A%84%22%E9%99%A4amd64%E5%A4%96%E7%9A%84%E6%9E%B6%E6%9E%84%EF%BC%9F%22https://github.com/docker-library/official-images#architectures-other-than-amd64%E4%BB%A5%E5%8F%8A%E5%AE%98%E6%96%B9%E9%95%9C%E5%83%8FFAQ%E4%B8%AD%E7%9A%84%22Git%E4%B8%AD%E9%95%9C%E5%83%8F%E7%9A%84%E6%BA%90%E4%BB%A3%E7%A0%81%E5%B7%B2%E6%9B%B4%E6%94%B9%EF%BC%8C%E7%8E%B0%E5%9C%A8%E8%AF%A5%E6%80%8E%E4%B9%88%E5%8A%9E%EF%BC%9F%22https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what%E3%80%82
维护者:
https://github.com/docker-library/docker
获取帮助:
Docker社区Slack、Server Fault、Unix & Linux或Stack Overflow
Dockerfile链接(参见FAQ中的"‘Shared’和‘Simple’标签的区别?"https://github.com/docker-library/faq#whats-the-difference-between-shared-and-simple-tags%E3%80%82%EF%BC%89
https://github.com/docker-library/docker/blob/3cb6ed40f1274ee9041835533bb625cf55f63e91/29-rc/cli/Dockerfile
https://github.com/docker-library/docker/blob/3cb6ed40f1274ee9041835533bb625cf55f63e91/29-rc/dind/Dockerfile
https://github.com/docker-library/docker/blob/b510c2bbe64b878dee6480992ab5d8cd9c02027d/28/cli/Dockerfile
https://github.com/docker-library/docker/blob/b510c2bbe64b878dee6480992ab5d8cd9c02027d/28/dind/Dockerfile
问题提交地址:
https://github.com/docker-library/docker/issues?q=
支持的架构:(https://github.com/docker-library/official-images#architectures-other-than-amd64)
https://hub.docker.com/r/amd64/docker/%E3%80%81https://hub.docker.com/r/arm32v6/docker/%E3%80%81https://hub.docker.com/r/arm32v7/docker/%E3%80%81https://hub.docker.com/r/arm64v8/docker/%E3%80%81https://hub.docker.com/r/winamd64/docker/
已发布镜像 artifact 详情:
https://github.com/docker-library/repo-info/blob/master/repos/docker%EF%BC%88https://github.com/docker-library/repo-info/commits/master/repos/docker%EF%BC%89
(镜像元数据、传输大小等)
镜像更新:
https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fdocker
https://github.com/docker-library/official-images/blob/master/library/docker%EF%BC%88https://github.com/docker-library/official-images/commits/master/library/docker%EF%BC%89
本描述的来源:
https://github.com/docker-library/docs/tree/master/docker%EF%BC%88https://github.com/docker-library/docs/commits/master/docker%EF%BC%89
虽然通常不推荐在Docker中运行Docker,但存在一些合法用例,例如Docker自身的开发。
Docker是一个开源项目,通过在Linux、Mac OS和Windows上提供操作系统级虚拟化的额外抽象层和自动化,实现应用程序在软件容器中的自动化部署。
***.org/wiki/Docker_(software)
!https://raw.githubusercontent.com/docker-library/docs/c350af05d3fac7b5c3f6327ac82fe4d990d8729c/docker/logo.png
在运行Docker-in-Docker之前,请务必阅读Jérôme Petazzoni关于该主题的优秀博客文章https://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/%EF%BC%8C%E5%85%B6%E4%B8%AD%E4%BB%96%E6%A6%82%E8%BF%B0%E4%BA%86%E8%BF%99%E6%A0%B7%E5%81%9A%E7%9A%84%E4%B8%80%E4%BA%9B%E4%BC%98%E7%BC%BA%E7%82%B9%EF%BC%88%E4%BB%A5%E5%8F%8A%E5%8F%AF%E8%83%BD%E9%81%87%E5%88%B0%E7%9A%84%E4%B8%80%E4%BA%9B%E6%A3%98%E6%89%8B%E9%97%AE%E9%A2%98%EF%BC%89%E3%80%82
如果您仍然确定需要Docker-in-Docker,而不仅仅是访问容器主机的Docker服务器,请继续阅读。
。如果您使用--network=host、共享网络命名空间(如Kubernetes Pod中),或通过其他方式使容器可被网络访问(包括通过其网关接口在dind实例中启动的容器),这可能存在安全问题(例如可能导致对主机系统的访问)。建议通过将变量设置为适当的值(如-e DOCKER_TLS_CERTDIR=/certs)来启用TLS。在19.03+版本中,此行为默认启用。
启用时,Docker守护进程将以--host=tcp://0.0.0.0:2376 --tlsverify ...启动(禁用时,Docker守护进程将以--host=tcp://0.0.0.0:2375启动)。
在DOCKER_TLS_CERTDIR指定的目录中,入口点脚本将创建/使用三个目录:
ca:证书颁发机构文件(cert.pem、key.pem)server:dockerd(守护进程)证书文件(cert.pem、ca.pem、key.pem)client:docker(客户端)证书文件(cert.pem、ca.pem、key.pem;适用于DOCKER_CERT_PATH)为了从"客户端"容器使用此功能,至少需要共享$DOCKER_TLS_CERTDIR目录的client子目录(如下例所示)。
要禁用此镜像行为,只需覆盖容器命令或入口点以直接运行dockerd(... arm32v6/docker:dind dockerd ...或... --entrypoint dockerd arm32v6/docker:dind ...)。
console$ docker run --privileged --name some-docker -d \ --network some-network --network-alias docker \ -e DOCKER_TLS_CERTDIR=/certs \ -v some-docker-certs-ca:/certs/ca \ -v some-docker-certs-client:/certs/client \ arm32v6/docker:dind
注意:--privileged是Docker-in-Docker正常运行所必需的,但应谨慎使用,因为它提供了对主机环境的完全访问权限,如Docker文档的相关部分中所述。
console$ docker run --rm --network some-network \ -e DOCKER_TLS_CERTDIR=/certs \ -v some-docker-certs-client:/certs/client:ro \ arm32v6/docker:latest version Client: Docker Engine - Community Version: 18.09.8 API version: 1.39 Go version: go1.10.8 Git commit: 0dd43dd87f Built: Wed Jul 17 17:38:58 2019 OS/Arch: linux/amd64 Experimental: false Server: Docker Engine - Community Engine: Version: 18.09.8 API version: 1.39 (minimum version 1.12) Go version: go1.10.8 Git commit: 0dd43dd87f Built: Wed Jul 17 17:48:49 2019 OS/Arch: linux/amd64 Experimental: false
console$ docker run -it --rm --network some-network \ -e DOCKER_TLS_CERTDIR=/certs \ -v some-docker-certs-client:/certs/client:ro \ arm32v6/docker:latest sh / # docker version Client: Docker Engine - Community Version: 18.09.8 API version: 1.39 Go version: go1.10.8 Git commit: 0dd43dd87f Built: Wed Jul 17 17:38:58 2019 OS/Arch: linux/amd64 Experimental: false Server: Docker Engine - Community Engine: Version: 18.09.8 API version: 1.39 (minimum version 1.12) Go version: go1.10.8 Git commit: 0dd43dd87f Built: Wed Jul 17 17:48:49 2019 OS/Arch: linux/amd64 Experimental: false
console$ docker run --rm --network some-network \ -e DOCKER_TLS_CERTDIR=/certs \ -v some-docker-certs-client:/certs/client:ro \ arm32v6/docker:latest info Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: 18.09.8 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: 894b81a4b802e4eb2a91d1ce216b8817763c29fb runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f init version: fec3683 Security Options: apparmor seccomp Profile: default Kernel Version: 4.19.0-5-amd64 Operating System: Alpine Linux v3.10 (containerized) OSType: linux Architecture: x86_64 CPUs: 12 Total Memory: 62.79GiB Name: e174d61a4a12 ID: HJXG:3OT7:MGDL:Y2BL:WCYP:CKSP:CGAM:4BLH:NEI4:IURF:4COF:AH6N Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false Product License: Community Engine WARNING: bridge-nf-call-iptables is disabled WARNING: bridge-nf-call-ip6tables is disabled
console$ docker run --rm -v /var/run/docker.sock:/var/run/docker.sock arm32v6/docker:latest version Client: Docker Engine - Community Version: 18.09.8 API version: 1.39 Go version: go1.10.8 Git commit: 0dd43dd87f Built: Wed Jul 17 17:38:58 2019 OS/Arch: linux/amd64 Experimental: false Server: Docker Engine - Community Engine: Version: 18.09.7 API version: 1.39 (minimum version 1.12) Go version: go1.10.8 Git commit: 2d0083d Built: Thu Jun 27 17:23:02 2019 OS/Arch: linux/amd64 Experimental: false
console$ docker run --privileged --name some-docker -d \ --network some-network --network-alias docker \ -e DOCKER_TLS_CERTDIR=/certs \ -v some-docker-certs-ca:/certs/ca \ -v some-docker-certs-client:/certs/client \ arm32v6/docker:dind --storage-driver overlay2
受https://github.com/docker/docker-ce-packaging/blob/57ae892b13de399171fc33f878b70e72855747e6/systemd/docker.service#L30-L45%E5%90%AF%E5%8F%91%EF%BC%8C%E6%82%A8%E5%8F%AF%E8%83%BD%E9%9C%80%E8%A6%81%E8%80%83%E8%99%91%E4%B8%BA%E4%BB%A5%E4%B8%8B%E8%BF%90%E8%A1%8C%E6%97%B6%E9%85%8D%E7%BD%AE%E9%80%89%E9%A1%B9%E8%AE%BE%E7%BD%AE%E4%B8%8D%E5%90%8C%E7%9A%84%E5%80%BC%EF%BC%8C%E7%89%B9%E5%88%AB%E6%98%AF%E7%94%9F%E4%BA%A7%E7%8E%AF%E5%A2%83%E4%B8%AD%E7%9A%84Docker%E5%AE%9E%E4%BE%8B%EF%BC%9A
console$ docker run --privileged --name some-docker -d \ ... \ --ulimit nofile=-1 \ --ulimit nproc=-1 \ --ulimit core=-1 \ --pids-limit -1 \ --oom-score-adj -500 \ arm32v6/docker:dind
其中一些可能不受主机dockerd的设置支持,例如--ulimit nofile=-1,会出现类似error setting rlimit type 7: operation not permitted的错误,有些可能从主机dockerd实例继承合理的值,或者可能不适用于您的Docker-in-Docker使用场景(例如,您可能希望将--oom-score-adj设置为高于主机dockerd的值,以便Docker-in-Docker实例在主机Docker实例之前被终止)。
重要提示:运行在Docker容器中的应用程序有多种存储数据的方式。我们鼓励docker镜像的用户熟悉可用的选项,包括:
查看此镜像中包含的软件的[许可信息]([***]
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。


探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
无需登录使用专属域名
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
Harbor Proxy Repository 对接专属域名
Portainer Registries 加速拉取
Nexus3 Docker Proxy 内网缓存
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
docker search 限制
站内搜不到镜像
离线 save/load
插件要用 plugin install
WSL 拉取慢
安全与 digest
新手拉取配置
镜像合规机制
manifest unknown
no matching manifest(架构)
invalid tar header(解压)
TLS 证书失败
DNS 超时
域名连通性排查
410 Gone 排查
402 与流量用尽
401 认证失败
429 限流
D-Bus 凭证提示
413 与超大单层
来自真实用户的反馈,见证轩辕镜像的优质服务