Docker推送＆＃34; blob上传未知＆＃34;

Question

我正在使用TFS 2017版本将docker镜像推送到Azure容器注册表。

构建机器：Ubuntu 16.04 TFS 2017更新3

推送功能过去工作正常，突然而且无处不在，它在尝试上传图片时开始出错：

 /usr/bin/docker login -u ******** -p ******** sdpacr.azurecr.io
 Login Succeeded

 /usr/bin/docker push sdpacr.azurecr.io/calendarmanagement:7787
 The push refers to a repository [sdpacr.azurecr.io/calendarmanagement]

 dc11b75335b3: Preparing
 b61450f05433: Preparing
 a6f0db82af58: Preparing
 03a2d35de712: Preparing
 3abbdf53e460: Preparing
 7f091d9051a0: Preparing
 e27a10675c56: Preparing
 7f091d9051a0: Waiting
 e27a10675c56: Waiting
 a6f0db82af58: Layer already exists
 3abbdf53e460: Layer already exists
 03a2d35de712: Layer already exists
 b61450f05433: Layer already exists
 e27a10675c56: Layer already exists
 7f091d9051a0: Layer already exists
 dc11b75335b3: Pushed
 blob upload unknown
 blob upload unknown
 /usr/bin/docker logout sdpacr.azurecr.io
 Remove login credentials for sdpacr.azurecr.io

我在Windows上设置了另一个构建代理并为Windows安装了Docker，它似乎工作正常。

我错过了什么？以及如何实际检索有关此错误的更多信息？

启用调试后编辑

DEBU[0226] Calling POST /v1.24/auth
DEBU[0226] form data: {"password":"*****","serveraddress":"sdpacr.azurecr.io","username":"58e8ba75-9161-4656-96aa-00217a9c929d"}
DEBU[0227] hostDir: /etc/docker/certs.d/sdpacr.azurecr.io
DEBU[0232] hostDir: /etc/docker/certs.d/sdpacr.azurecr.io
DEBU[0232] attempting v2 login to registry endpoint https://sdpacr.azurecr.io/v2/
DEBU[0238] Increasing token expiration to: 60 seconds
DEBU[0244] Calling POST /v1.24/images/sdpacr.azurecr.io/calendarmanagement/push?tag=7789
DEBU[0249] hostDir: /etc/docker/certs.d/sdpacr.azurecr.io
DEBU[0249] hostDir: /etc/docker/certs.d/sdpacr.azurecr.io
DEBU[0249] Trying to push sdpacr.azurecr.io/calendarmanagement to https://sdpacr.azurecr.io v2
DEBU[0250] Pushing repository: sdpacr.azurecr.io/calendarmanagement:7789
DEBU[0250] Pushing layer: sha256:865df7790a65d2bc0ca600f8dc65e324c2931953b915cddf8969d41b1d7dad95
DEBU[0250] Increasing token expiration to: 60 seconds
DEBU[0251] Assembling tar data for 9b3ba858ef55bdfe518861fcd5ffdd1e7bf18ed3880fc8878bae2acf466bff0f
ERRO[0276] Upload failed, retrying: dial tcp: lookup neumanaged118.blob.core.windows.net on 8.8.4.4:53: read udp 192.168.50.112:49447->8.8.4.4:53: i/o timeout
ERRO[0276] Upload failed, retrying: dial tcp: lookup neumanaged118.blob.core.windows.net on 8.8.4.4:53: read udp 192.168.50.112:49447->8.8.4.4:53: i/o timeout
ERRO[0276] Upload failed, retrying: dial tcp: lookup neumanaged118.blob.core.windows.net on 8.8.4.4:53: read udp 192.168.50.112:49447->8.8.4.4:53: i/o timeout
ERRO[0276] Upload failed, retrying: dial tcp: lookup neumanaged118.blob.core.windows.net on 8.8.4.4:53: read udp 192.168.50.112:49447->8.8.4.4:53: i/o timeout
ERRO[0276] Upload failed, retrying: dial tcp: lookup neumanaged118.blob.core.windows.net on 8.8.4.4:53: read udp 192.168.50.112:49447->8.8.4.4:53: i/o timeout
DEBU[0281] Pushing layer: sha256:865df7790a65d2bc0ca600f8dc65e324c2931953b915cddf8969d41b1d7dad95
DEBU[0303] Assembling tar data for 9b3ba858ef55bdfe518861fcd5ffdd1e7bf18ed3880fc8878bae2acf466bff0f
ERRO[0312] Upload failed, retrying: net/http: TLS handshake timeout
ERRO[0318] Upload failed, retrying: blob upload unknown
DEBU[0323] Increasing token expiration to: 60 seconds
ERRO[0327] Upload failed, retrying: net/http: TLS handshake timeout
DEBU[0328] Pushing layer: sha256:865df7790a65d2bc0ca600f8dc65e324c2931953b915cddf8969d41b1d7dad95
DEBU[0343] Assembling tar data for 9b3ba858ef55bdfe518861fcd5ffdd1e7bf18ed3880fc8878bae2acf466bff0f
ERRO[0365] Upload failed, retrying: net/http: TLS handshake timeout
ERRO[0372] Upload failed, retrying: blob upload unknown
DEBU[0387] Pushing layer: sha256:865df7790a65d2bc0ca600f8dc65e324c2931953b915cddf8969d41b1d7dad95
DEBU[0388] Increasing token expiration to: 60 seconds
DEBU[0388] Assembling tar data for 9b3ba858ef55bdfe518861fcd5ffdd1e7bf18ed3880fc8878bae2acf466bff0f
ERRO[0390] Upload failed, retrying: received unexpected HTTP status: 502 Bad Gateway
DEBU[0410] Pushing layer: sha256:865df7790a65d2bc0ca600f8dc65e324c2931953b915cddf8969d41b1d7dad95
DEBU[0410] Assembling tar data for 9b3ba858ef55bdfe518861fcd5ffdd1e7bf18ed3880fc8878bae2acf466bff0f
ERRO[0413] Upload failed: blob upload unknown
ERRO[0413] Attempting next endpoint for push after error: blob upload unknown
DEBU[0413] Skipping v1 endpoint https://sdpacr.azurecr.io because v2 registry was detected

Answer 1

也许 https://github.com/docker/distribution/issues/2225 会帮助您

proxy_set_header X-Forwarded-Proto https

需要添加到sdpacr.azurecr.io nginx / apache