Error Pulling Image Configuration Download Failed After Attempts 6 Dialing

152 views

Skip to first unread message

Sylvia Heidemann

unread,

Jan 10, 2024, 1:34:44 AM1/10/24

to dhonchimderi

We are having the same issue when pushing to docker hub. It seems to be irradic and erred out initially mid-push of one of the images. Subsequent push attempts error out immediately. Over the weekend I was able to get one of them to upload after many attempts (lucky timing somehow?)

Problem:
Whenever I attempt to pull an image using docker pull, I consistently get this error: error pulling image configuration: download failed after attempts=6: unexpected EOF.
Observation:
Interestingly, when I switch to a different network, the pull command works perfectly. This leads me to believe that there might be something specific with my primary network causing the issue.

error pulling image configuration download failed after attempts 6 dialing

Download https://tuvitrindzu.blogspot.com/?ce=2x6OkZ

Hi, we are getting an error pulling images from ECR private repositories from a server that get access to Internet through a web proxy. We ask proxy admin to allow access to .dkr.ecr.us-east-2.amazonaws.com. We are using aws cli to authenticate with amazon and docker, docker login is successful with aws token, however when we pull the image we get an error like this, after some timeouts reported by docker trying to get image layers:

As this error is often the result of simple mistakes, you might want to consider using automation to prevent recurrences in the future. [Datree.io]( ) is a tool that can validate your YAML files against custom schemas and highlight any misconfigurations. You could use it to check that `image` fields only reference images with specific registries and tags, lowering the chance of accidentally starting a pod with an invalid image.

I appear to have solved my problem, i.e., I was able to configure a web map and use this within Collector to call Survey123 and prepopulate a new feature service (created by 123) with the data coming from the web map feature service. My sources of error were varied and included: (1) spaces in the URL. Because I had many fields to pre-populate, I was typing the URL in Notepad with word wrap, then copying this into the URL link properties. Doing so, however, introduced spaces into the string that caused issues with fields prepopulating. (2) Setting the readonly property to yes for text fields to prepopulate in 123 seemed to be an issue. As a result, I removed the yes, i.e., did not make them readonly. (3) I also failed to download 123 surveys after making changes to them. As a result, I was trying to prepopulate an old survey which didn't work. Hopefully this experience helps others.