CODEWITHSUNDEEP
dockerboot2dockergcloud
BeatingToADifferentRobot
BeatingToADifferentRobot

Reputation: 404

Docker Push Fails

My docker pushes with the latest version appear to be failing almost all the time.

This is what happens with gcloud docker -- push

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

Here is the docker log:

"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"

Any ideas on how to resolve? This worked on a previous version.

Upvotes: 2

Views: 800

Answers (3)

Rachel
Rachel

Reputation: 2894

I've just had this same problem, which was caused by a network problem.

I had been using a VPN, it seemed that the specific VPN node through which I was connected couldn't cope with the bandwidth I was pushing at it.

When I disconnected from the VPN, it worked fine.

Upvotes: 2

BeatingToADifferentRobot
BeatingToADifferentRobot

Reputation: 404

A workaround that resolved the need for this was to do a gcloud app deploy instead of a docker push with a gcloud app deploy --image-url="xxxxxxxxx". In the past gcloud app deploy used to timeout because of the size of the image and the work around was to do a docker push. Now it seems to work fine.

Oddly, as part of the gcloud app deploy it does do a docker push to a different path in the gcloud container registry which seems to work.

Upvotes: 0

Senthil
Senthil

Reputation: 2246

If you have two images with same tag (which i was pushing to cloud).

Solution is:

Inspect your images and find two or more with the same tag: docker images Delete them: docker rmi --force 'image id'

Ref: Docker - What is proper way to rebuild and push updated image to docker cloud?

Upvotes: -1

Related Questions