Docker运行-d <private image =“”>给出致命的。在其他主机上可以吗？

Question

让命令说明一切：

在名为 coreworker

的主机上

core@coreworker-1 ~ $ docker images
REPOSITORY                                                                           TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
hub-docker-repo:5000/485d5874-c786-4b90-93ac-8db5342a6059                            1                   bbd5d4d98156        31 minutes ago      139.3 MB
ec2-54-169-239-164.ap-southeast-1.compute.amazonaws.com:5000/hub-action-repository   latest              66ecb895d185        14 hours ago        856.4 MB
ec2-54-169-239-164.ap-southeast-1.compute.amazonaws.com:5000/hub-ext-node-base       0.12.7              f2f1afc202e4        8 days ago          136.6 MB
...

core@coreworker-1 ~ $

在名为 devhost

的主机上

core@devhost ~ $ docker images
REPOSITORY                   TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
<none>                       <none>              67e45ce93dee        48 minutes ago      725 MB
node                         0.12.7              a4b45afffe4a        5 days ago          642.2 MB
jwnintex/mesos-worker        latest              42f1b41b0089        5 weeks ago         504 MB
jwnintex/nginx-port-router   latest              11edcdf1a5fc        9 weeks ago         126.4 MB
jwnintex/consul              latest              e66fb6787628        10 weeks ago        69.4 MB
jwnintex/mesos-master        latest              187d84106a3e        3 months ago        561.8 MB
jwnintex/marathon            latest              b1d8dd91146a        3 months ago        699.3 MB
jwnintex/zookeeper           latest              9b72d56707c9        4 months ago        304.3 MB
jwnintex/registrator         latest              b1c29d1a74a9        6 months ago        11.79 MB

但是当我这样做时：

core@devhost ~ $ docker images -a hub-docker-repo:5000
REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE

现在在 hub-docker-repo

devhost 上运行图像

告知它了：

core@devhost ~ $ ping hub-docker-repo
PING hub-docker-repo.service.consul (172.17.8.150) 56(84) bytes of data.
64 bytes from coreworker-1.node.dc1.consul (172.17.8.150): icmp_seq=1 ttl=63 time=8.27 ms
64 bytes from coreworker-1.node.dc1.consul (172.17.8.150): icmp_seq=2 ttl=63 time=5.19 ms

现在试试吧

core@devhost ~ $ docker run -d hub-docker-repo:5000/485d5874-c786-4b90-93ac-8db5342a6059:1
Unable to find image 'hub-docker-repo:5000/485d5874-c786-4b90-93ac-8db5342a6059:1' locally
Pulling repository hub-docker-repo:5000/485d5874-c786-4b90-93ac-8db5342a6059
FATA[0000] Error: image 485d5874-c786-4b90-93ac-8db5342a6059:1 not found

现在尝试在 coreworker 上实际托管注册表（作为泊坞窗图片）

core@coreworker-1 ~ $ docker run -d hub-docker-repo:5000/485d5874-c786-4b90-93ac-8db5342a6059:1
98d642c1bafd30569d853e92167c7b4fe720bd67f65ec0d0719ec5a36bb6616f

为什么我无法运行该远程图像？或者更好，甚至发现它？

Answer 1

事实证明，图像从未被推动过，因此其他主机无法看到。