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
Pull image via API: connection canceled #793
Comments
Hi @nlaplante We're actually seeing the same thing pulling from Docker repos right now - can you try again later and let me know if you're able to pull images? |
It's been doing this since starting working on an app which pulls images from AWS ECR repositories. I've been working on this for the past 3 weeks and I could never ever pull an image via the API. CLI works everytime. I'm not pulling from the Docker repositories. |
I tried this on latest daemon that I built myself and it is pulling fine. My POST request was to "http://localhost:2375/v1.27/images/create?fromImage=microsoft/nanoserver:latest" Below docker version info from docker -H 127.0.0.1:2375 version Client: Server: |
I've done more tests with this and most of the time it fails. Out of around 25 tries, I could pull the image 3 times.
Tried with latest Edge version too, still same error. |
BTW, image pulling via the API using the exact same code works fine on Fedora Linux. |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Expected behavior
Images pulled from remote repositories via API can be pulled successfully
Actual behavior
Pull process starts and then ends unexpectedly with a "Connection canceled..." entry in the logs.
Information
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: