【问题标题】:error pulling image configuration when apply ./get-docker-images.sh应用 ./get-docker-images.sh 时提取图像配置时出错
【发布时间】:2019-01-18 16:42:30
【问题描述】:
Pulling hyperledger/fabric-couchdb:amd64-0.4.13
Error response from daemon: Get https://registry-1.docker.io/v2/hyperledger/fabric-couchdb/manifests/amd64-0.4.13: read tcp 10.0.2.15:47240->54.175.43.85:443: read: connection reset by peer

申请时: vagrant@vagrant:/vagrant/bin$ ./get-docker-images.sh

我在 Windows 8 上使用带有 Ubuntu 16.04 的 VM 虚拟工具箱

有人知道如何解决这个问题吗?

get-docker-images.sh 的内容:

# set the default Docker namespace and tag
DOCKER_NS=hyperledger
ARCH=amd64
VERSION=1.3.0
BASE_DOCKER_TAG=amd64-0.4.13

# set of Hyperledger Fabric images
FABRIC_IMAGES=(fabric-peer fabric-orderer fabric-ccenv fabric-tools)

for image in ${FABRIC_IMAGES[@]}; do
  echo "Pulling ${DOCKER_NS}/$image:${ARCH}-${VERSION}"
  docker pull ${DOCKER_NS}/$image:${ARCH}-${VERSION}
done

THIRDPARTY_IMAGES=(fabric-kafka fabric-zookeeper fabric-couchdb fabric-baseos)

for image in ${THIRDPARTY_IMAGES[@]}; do
  echo "Pulling ${DOCKER_NS}/$image:${BASE_DOCKER_TAG}"
  docker pull ${DOCKER_NS}/$image:${BASE_DOCKER_TAG}
done

执行的命令:

vagrant@vagrant:/vagrant/bin$ ./get-docker-images.sh
Pulling hyperledger/fabric-peer:amd64-1.3.0
amd64-1.3.0: Pulling from hyperledger/fabric-peer
Digest: sha256:c521647ccedf6e02a737e20ee66d6957293c8d85c2f272bf7b62fae1e2be81a5
Status: Image is up to date for hyperledger/fabric-peer:amd64-1.3.0
Pulling hyperledger/fabric-orderer:amd64-1.3.0
amd64-1.3.0: Pulling from hyperledger/fabric-orderer
Digest: sha256:510e0baa4d5df084f7e1de8072f2be6f0db766d668a8932b3eef19c3e9d65399
Status: Image is up to date for hyperledger/fabric-orderer:amd64-1.3.0
Pulling hyperledger/fabric-ccenv:amd64-1.3.0
amd64-1.3.0: Pulling from hyperledger/fabric-ccenv
Digest: sha256:ea988663d2af2e392d686524f2d7a7ab70ee4ee783c50792b5bc9745450d776d
Status: Image is up to date for hyperledger/fabric-ccenv:amd64-1.3.0
Pulling hyperledger/fabric-tools:amd64-1.3.0
amd64-1.3.0: Pulling from hyperledger/fabric-tools
Digest: sha256:638a53bba0582adf71c08ba3658b5d05d79f49c44f38344cca7ede10dbab3290
Status: Image is up to date for hyperledger/fabric-tools:amd64-1.3.0
Pulling hyperledger/fabric-kafka:amd64-0.4.13
amd64-0.4.13: Pulling from hyperledger/fabric-kafka
Digest: sha256:892f3ce913ea826d842bbe7e1babecf9194e873168d563c23668866d2fd29600
Status: Image is up to date for hyperledger/fabric-kafka:amd64-0.4.13
Pulling hyperledger/fabric-zookeeper:amd64-0.4.13
amd64-0.4.13: Pulling from hyperledger/fabric-zookeeper
Digest: sha256:f2c0d4a4d73614e34e0161929d7571a72bc379034c704eb170c80b7acde97d92
Status: Image is up to date for hyperledger/fabric-zookeeper:amd64-0.4.13
Pulling hyperledger/fabric-couchdb:amd64-0.4.13
Error response from daemon: Get https://registry-1.docker.io/v2/hyperledger/fabric-couchdb/manifests/amd64-0.4.13: read tcp 10.0.2.15:47024->54.175.43.85:443: read: connection reset by peer

【问题讨论】:

  • 这听起来像是网络连接问题,或者可能是本地代理设置问题。就其本身而言,这并不是真正指向任何特定问题或可重现的解决方法的错误消息。
  • 但我的机器上有任何代理,我可以从 VM Tool Box ping 站点(ping production.cloudflare.docker.com 回复成功)
  • +1 用于提出与编程和开发有关的 Docker 问题。你展示了一个带有流控制的脚本。
  • 我只是在执行这个命令:vagrant@vagrant:/vagrant/bin$ ./get-docker-images.sh
  • 我找到了解决方案:更改指向 Google DNS dns-nameservers 8.8.8.8 8.8.4.4 的 VM 的 DNS 设置然后 vagrant halt vagrant up 但我们需要在不同的时间以良好的互联网速度

标签: linux windows docker blockchain


【解决方案1】:

我找到了解决方案: 更改 VM 的 DNS 设置 指向 Google DNS

dns-nameservers 8.8.8.8       8.8.4.4

然后

vagrant halt

vagrant up

但我们需要在不同的时间尝试 网速不错

通过以下命令打开您的 /etc/network/interfaces 文件:sudo vi /etc/network/interfaces
和 ... 指向 Google DNS

接口文件应如下所示:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

    # The loopback network interface
    auto lo
    iface lo inet loopback

    # The primary network interface
    auto eth0
    iface eth0 inet dhcp
    pre-up sleep 2

    dns-nameservers 8.8.8.8   8.8.4.4

另请参阅此链接: https://github.com/docker/for-win/issues/611

【讨论】:

    猜你喜欢
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2018-08-09
    • 1970-01-01
    • 1970-01-01
    • 2018-01-01
    • 1970-01-01
    • 2019-01-23
    相关资源
    最近更新 更多