-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
socket.timeout: timed out on compose push #6837
Comments
This also happened to me quite a few times but always assumed it was related with the connection, the push is made from a VM running in US on GCE to a ECR in Europe, in general after a retry it worked. I suspect this issue might also be related to a timeout threshold in docker-compose or the docker engine. |
I am seeing a similar issue pushing from a EKS container to Docker Hub. Also seeing this in some system logs: "Not continuing with push after error: context canceled" |
I had the same problem with
It helped me. |
@nkazakov Hello could you explain me better how to set the environment variables? my problem is with |
@brunosousadev Hello. You should create file .env (or add lines to existed file) with this parameters:
Time in seconds. Or you can set these parameters to global environment variables of your OS. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it had not recent activity during the stale period. |
HOW I GOT AROUND THIS. Ok, I had this issue on a Mac, current release, to a registry docker image running on a server at work.. Would keep getting stuck on a specific blob. |
If anyone has the same problem with the new update of MacOS Big Sur after update to a new release(cannot start docker or docker sad starting any time or run docker-compose up have the same issue mentioned above -> may be caused by disk corruption) you can try Clean/Purge data in docker desktop and then restart, it worked for me |
|
Description of the issue
python trace weh pushing to registry
Context information (for bug reports)
we use docker-compose to push build images via jenkins CI to aws ecr
time docker-compose -f .jenkins/docker-compose.images-base.1.yml push
Output of
docker-compose version
Client: Docker Engine - Community
Version: 19.03.1
API version: 1.40
Go version: go1.12.5
Git commit: 74b1e89
Built: Thu Jul 25 21:21:22 2019
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.1
API version: 1.40 (minimum version 1.12)
Go version: go1.12.5
Git commit: 74b1e89
Built: Thu Jul 25 21:19:53 2019
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.2.6
GitCommit: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
runc:
Version: 1.0.0-rc8
GitCommit: 425e105d5a03fabd737a126ad93d62a9eeede87f
docker-init:
Version: 0.18.0
GitCommit: fec3683```
python version
Python 3.7.3
Output of
docker-compose config
(Make sure to add the relevant
-f
and other flags)Steps to reproduce the issue
time docker-compose -f .jenkins/docker-compose.images-base.1.yml push
Observed result
python trace
Expected result
Stacktrace / full error message
Additional information
OS version / distribution,
docker-compose
install method, etc.No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 19.04
Release: 19.04
Codename: disco
pip3 install
wheel
docker-compose
awscli
The text was updated successfully, but these errors were encountered: