我的码头推送最新版本似乎几乎所有的时间都失败。码头推送失败
这是gcloud搬运工会发生什么 - 推
The push refers to a repository [us.gcr.io/rndb-140315/dream_closet]
80a8fcd2cfa1: Layer already exists
3bca4b8aadf9: Layer already exists
1f3202a15537: Layer already exists
5549f40f950c: Layer already exists
5f70bf18a086: Layer already exists
34d126c63186: Layer already exists
52b4a81ec16b: Layer already exists
6db3819d35cd: Layer already exists
46ecc6c4543a: Layer already exists
dial tcp 108.177.9.82:443: i/o timeout
这里是泊坞窗日志:
"Calling POST /v1.24/images/us.gcr.io/rndb-140315/dream_closet/push?tag=" 16-11-15T00:44:46.219497295Z" level=debug msg="hostDir: /etc/docker/certs.d/us.gcr.io"
16-11-15T00:44:46.250418329Z" level=debug msg="hostDir: /etc/docker/certs.d/us.gcr.io"
16-11-15T00:44:46.250519209Z" level=debug msg="Trying to push us.gcr.io/rndb-140315/dream_closet to https://us.gcr.io v2" 16-11-15T00:44:46.446481694Z" level=debug msg="Pushing repository: us.gcr.io/rndb-140315/dream_closet:latest"
16-11-15T00:45:16.709508684Z" level=error msg="Upload failed, retrying: dial tcp 108.177.10.82:443: i/o timeout"
16-11-15T00:45:16.709791097Z" level=error msg="Upload failed, retrying: dial tcp 108.177.10.82:443: i/o timeout"
16-11-15T00:45:16.710004220Z" level=error msg="Upload failed, retrying: dial tcp 108.177.10.82:443: i/o timeout"
16-11-15T00:45:51.711554093Z" level=error msg="Upload failed, retrying: dial tcp 108.177.10.82:443: i/o timeout"
16-11-15T00:46:31.712779966Z" level=error msg="Upload failed, retrying: dial tcp 108.177.10.82:443: i/o timeout"
16-11-15T00:47:17.355180162Z" level=error msg="Attempting next endpoint for push after error: Post https://us.gcr.io/v2/rndb-140315/dream_clos 16-11-15T00:47:17.355302561Z" level=debug msg="Skipping v1 endpoint https://us.gcr.io because v2 registry was detected"
任何想法如何解决?这工作在以前的版本。
_almost all the time_?所以这意味着有时上传工作正常。如果是这种情况,我会想到网络/流量问题。我还有时难以上传到码头中心。 – Marcs
一旦我相信我已经有了它的工作。它在不同的随机点给我一个I/O超时。我遇到的问题是我的互联网连接趋于可靠,所以我不相信这是我的网络。 – BeatingToADifferentRobot
您是否检查过Docker的日志? [Docker守护进程日志在哪里?](http://stackoverflow.com/questions/30969435/where-is-the-docker-daemon-log#30970134) – Marcs