Error pulling image configuration docker

Description

This has been reported multiple times already (#357, #2151, #4539, #5255, etc.) and has never been completely solved, it has just disappeared by itself. Since yesterday, some pull requests to docker registry fail with errors like error pulling image configuration: Get https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/36/368db5c51bcd5821a9503b7d8349af948eaee516602969fe50915fd19f511cc0/data?Expires=1477399254&Signature=es6-HoHrzMRF1GtjFkiOq8E1aMlSMZzAwTWZuAI9DsRs-hJEdfRGoSYBBwSWxfzt2jZz0tySRfvpVSY8ef~wRwourd~QkA9G-sOf7ptk0B1FfWJLr7rlsmRSIpgF5sHMjkwxKTh~Tv-NzeDaEpMRMvm6fbMwjIJuZ~hKWZaH4z8_&Key-Pair-Id=APKAJECH5M7VWIS5YZ6Q: read tcp 10.0.2.15:35436->52.222.149.173:443: read: connection reset by peer

Steps to reproduce the issue:

1. Try to pull wordpress (latest). It will fail.

docker pull wordpress
Using default tag: latest
latest: Pulling from library/wordpress
43c265008fae: Pulling fs layer
6ee27d07994b: Pulling fs layer
d43536f442a0: Download complete
4d9469dadeb4: Waiting
4fc33aa1941b: Waiting
09b922600db1: Waiting
01805b6582a4: Waiting
ec43f09bb70c: Waiting
6568948eed6b: Waiting
2dc0094a10b5: Waiting
7142d56062ec: Waiting
7a44a9f63706: Waiting
9b7c9a7c3515: Waiting
59249fc11e6f: Waiting
31611c57ce32: Waiting
712c4eef2d95: Waiting
aaf3860b31ac: Waiting
b04c02901a3a: Waiting
eb9dd4eb321b: Waiting
error pulling image configuration: Get https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/36/368db5c51bcd5821a9503b7d8349af948eaee516602969fe50915fd19f511cc0/data?Expires=1477399254&Signature=es6-HoHrzMRF1GtjFkiOq8E1aMlSMZzAwTWZuAI9DsRs-hJEdfRGoSYBBwSWxfzt2jZz0tySRfvpVSY8ef~wRwourd~QkA9G-sOf7ptk0B1FfWJLr7rlsmRSIpgF5sHMjkwxKTh~Tv-NzeDaEpMRMvm6fbMwjIJuZ~hKWZaH4z8_&Key-Pair-Id=APKAJECH5M7VWIS5YZ6Q: read tcp 10.0.2.15:35436->52.222.149.173:443: read: connection reset by peer

1. Try to pull wordpress:4.3.1. It will take some time, but will eventually succeed (Some of the layers are going through one ore more retries).

 docker pull wordpress:4.3.1
4.3.1: Pulling from library/wordpress
d4bce7fd68df: Pull complete
a3ed95caeb02: Pull complete
77a07a807b0b: Pull complete
8e9dd06f34b8: Pull complete
bdeb40d51bd7: Pull complete
c1c9be13bf3c: Pull complete
b39c61dc46ac: Pull complete
7dd602b91016: Pull complete
523061e2010c: Pull complete
da8bdfcda793: Pull complete
0be8c57f353c: Pull complete
52c1189d4439: Pull complete
23ebc7f488dc: Pull complete
c2fadfc5c14d: Pull complete
08141e2af0f3: Pull complete
6f6c7167fd08: Pull complete
09fa28e1f215: Pull complete
fa2282b6ef71: Pull complete
8c2f663cf070: Pull complete

Describe the results you received:
I have failed to pull a latest image from docker hub, however, I have successfully pulled not the latest tag for the same image. This also happens for other images and other tags.

Describe the results you expected:
Obviously, I have expected to pull of the requested images.

Additional information you deem important (e.g. issue happens only occasionally):
I have first discovered the issue yesterday, a few hours after I got Virtualbox updated to VirtualBox-5.0.28-111378-Win. The issue stayed after upgrading to VirtualBox-5.1.8-111374-Win and also stayed after upgrading docker toolbox to latest (v1.12.2). Also, I am testing this in an office with other coworkers that are not hitting the issue, but use similar setup (differences in OS and software version is possible).

Output of docker version:

Client:
 Version:      1.12.2
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   bb80604
 Built:        Tue Oct 11 17:00:50 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.2
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   bb80604
 Built:        Tue Oct 11 17:00:50 2016
 OS/Arch:      linux/amd64

Output of docker info:

Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.12.2
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 32
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge overlay null host
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.24-boot2docker
Operating System: Boot2Docker 1.12.2 (TCL 7.2); HEAD : 9d8e41b - Tue Oct 11 23:40:08 UTC 2016
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 995.9 MiB
Name: test-host-2
ID: QFKW:A5SR:LMSM:YO7X:GXTI:463S:4D2Q:OPRH:3TRX:KWK3:KNZA:6BVF
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 13
 Goroutines: 23
 System Time: 2016-10-25T12:39:27.186690998Z
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox
Insecure Registries:
 127.0.0.0/8

Additional environment details (AWS, VirtualBox, physical, etc.):
Virtualbox on Windows. See used versions in the text above.

AWS support for Internet Explorer ends on 07/31/2022. Supported browsers are Chrome, Firefox, Edge, and Safari.
Learn more »

error pulling image configuration #27911

I have a fresh new win2K16 with containers enabled as well as hyper-v is turned on. Whenever I tru to issue the tes cmmand as indicated to test (firewal disabled, no proxy. )
docker pull microsoft/windowsservercore:10.0.14393.321
I get
error pulling image configuration: Get https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/
93/93a9c37b36d03323f7b8fdd7f0302f7e487a0e8b31ccd8e689c40a404d2f1ea9/data?Expires=1477932342&Signature=N2NdygkaXM6YfVCvXm
TpzD1vDn6k-P50sruyKW21-iVgVdMNwwLUGS0vN2E2ocHrBXowghRgtWX214AcQ5TWo7AqfufXTfsMU9s3TLQV8ed9-dFAXjC5QMImgTmC8Ef0NsQ26s6E
tgiWxvm6XJqV8txihfUO46BOuN-n3Lyfs_&Key-Pair-Id=APKAJECH5M7VWIS5YZ6Q: dial tcp 52.85.221.56:443: i/o timeout
Thanks

error pulling image configuration

Steps to reproduce the issue:

1. docker pull microsoft/windowsservercore:10.0.14393.321

error pulling image configuration: Get https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/
93/93a9c37b36d03323f7b8fdd7f0302f7e487a0e8b31ccd8e689c40a404d2f1ea9/data?Expires=1477932342&Signature=N2NdygkaXM6YfVCvXm
TpzD1vDn6k-P50sruyKW21-iVgVdMNwwLUGS0vN2E2ocHrBXowghRgtWX214AcQ5TWo7AqfufXTfsMU9s3TLQV8ed9-dFAXjC5QMImgTmC8Ef0NsQ26s6E
tgiWxvm6XJqV8txihfUO46BOuN-n3Lyfs_&Key-Pair-Id=APKAJECH5M7VWIS5YZ6Q: dial tcp 52.85.221.56:443: i/o timeout

I expexted a container to ve created

Additional information you deem important (e.g. issue happens only occasionally):

Output of docker version :

Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 1.12.2-cs2-ws-beta
Storage Driver: windowsfilter
Windows:
Logging Driver: json-file
Plugins:
Volume: local
Network: nat null overlay
Swarm: inactive
Default Isolation: process
Kernel Version: 10.0 14393 (14393.351.amd64fre.rs1_release_inmarket.161014-1755)
Operating System: Windows Server 2016 Standard
OSType: windows
Architecture: x86_64
CPUs: 1
Total Memory: 2 GiB
Name: ProdWebServer
ID: EAFQ:W3YV:HIXM:GWRN:WFJK:6TCQ:HEKP:AX6O:CESU:BQ2G:QLEP:OL3O
Docker Root Dir: C:ProgramDatadocker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false«`

Additional environment details (AWS, VirtualBox, physical, etc.):

The text was updated successfully, but these errors were encountered:

Источник

How do I resolve the “error pulling image configuration: error parsing HTTP 403 response body” error in Amazon ECS when pulling a Docker image from Amazon ECR?

Last updated: 2022-04-05

When I pull a Docker image from Amazon Elastic Container Registry (Amazon ECR) in Amazon Elastic Container Service (Amazon ECS), I get the following error message: “error pulling image configuration: error parsing HTTP 403 response body.”

Short description

Amazon ECR uses Amazon Simple Storage Service (Amazon S3) to store your image layers. When your containers download images from Amazon ECR, they must access Amazon ECR to get the image manifest and then Amazon S3 to download the image layers. The following is the Amazon Resource Name (ARN) of the Amazon S3 bucket that contains the layers for each Docker image.

If you use an S3 gateway endpoint in a route table with a policy that restricts access to starport-layer-bucket, then you receive the following error message:

By default, you get full access to all resources when you create a gateway endpoint in Amazon S3.

If you have a custom policy that allows access to specific resources, then you must add the starport-layer-bucket ARN to your Amazon S3 policy to resolve the error.

Resolution

2. From the navigation menu, choose Endpoints.

3. Select the S3 endpoint from the list.

4. Choose the Policy tab, and then choose Edit policy.

5. In the Resource section of the policy, add the following ARN:

Note: Be sure that the ARN includes your AWS Region.

For reference, consider the following example policy:

Источник

Docker error pulling image configuration #2167

Expected behavior

The image should be successfully pulled.

Actual behavior

mac_mini4:abcd mac-mini-4$ docker pull node
Using default tag: latest
latest: Pulling from library/node
85b1f47fba49: Pulling fs layer
5409e9a7fa9e: Pulling fs layer
661393707836: Pulling fs layer
1bb98c08d57e: Waiting
f957ac1b6e47: Waiting
166b7c18b759: Waiting
02cb65a8d0f6: Waiting
9052b6207e12: Waiting
error pulling image configuration: Get https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/ba/badd967af535567f92c04665ccbf4ccf63f58960e38a43f611b1b19ca3a713e7/data?Expires=1508747774&Signature=itXcTt8IGLoxsACN4OJMgmRgUfrEOE3i9J6g8ooOV9AANUAQgXnJb6Rme48DxjzCLTWnKKLQqASNNa2fNuxCCy9X6qVSBZGazxNktOwWe70fjIqR5ojTQG5GtaZUsoL0k6we

gPQXKMIBdZfGu33YeMPD7CymCow4Ww4dwwvPgo_&Key-Pair-Id=APKAJECH5M7VWIS5YZ6Q: dial tcp 192.168.65.1:443: getsockopt: connection refused
mac_mini4:abcd mac-mini-4$

Occurs with other images too..

Information

• OS : MacOS Seirra 10.12.6
• Docker Version 17.09.0-ce-mac35 (19611) Channel: stable a98b7c1b7c
• When I try to pull any images I get the above Behaviour
• What I have tried?
  a) Added dns under daemon tab of docker . «dns» : [ «8.8.8.8», «8.8.4.4» ]
  b) Added DNS Servers «8.8.8.8» and «8.8.4.4» under Network Preferences -> Advanced -> DNS tab
• Images: https://ibb.co/n2zCVm and https://ibb.co/g6HcwR

I checked some other posts and saw some users facing this similar issue. But they could resolve it just by setting up the DNS servers to 8.8.8.8, which unfortunately not working for me.
Can anyone please help?

What could be possibly wrong here in my steps? PS*: new to Docker here.
If you think I have not provided enough information, please let me know. I will update accordingly.

The text was updated successfully, but these errors were encountered:

Источник

How do I resolve the “error pulling image configuration: toomanyrequests” error when I use Docker images in AWS CodeBuild?

Last updated: 2022-05-19

I want to resolve the “error pulling image configuration: toomanyrequests” error that I get when I use Docker images in AWS CodeBuild.

Short description

If you use Docker images in CodeBuild, you can experience throttling when you pull layers from the public DockerHub repository.

To resolve the error that you receive when throttling happens, you must configure CodeBuild to authenticate the layer pulls using your DockerHub account credentials.

Important: To complete the following steps, you must have a DockerHub account and the user name and password for your account.

Resolution

Store your DockerHub credentials with AWS Secrets Manager

2. Choose Store a new secret.

3. In the Select secret type section, choose Other type of secrets.

4. In the Specify the key/value pairs to be stored in this secret section, choose the Secret key/value tab.

5. In the first text box, enter username. In the second text box, enter your DockerHub user name. Then, choose Add row.

6. In the first text box of the new row, enter password. In the second text box, enter your DockerHub password. Then, choose Add row.

8. For Secret name, enter a name for your secret. For example: dockerhub

10. Confirm that the default setting for Disable automatic rotation is selected.

12. Choose Store.

13. From the Secret name column, choose your secret.

14. In the Secret details section, note the Amazon Resource Name (ARN) for Secret ARN.

Resolve throttling that happens in the PROVISIONING phase

2. In the navigation pane, choose Build, and then choose Build projects.

3. Choose your build project.

4. Choose Edit, and then choose Environment.

5. Choose Override image.

6. For New environment image, choose Custom image.

7. For Environment type, select your custom image.

8. For Image registry, choose Other registry.

9. For External registry URL, enter the name of your Docker image.

10. For Registry credential, enter the secret ARN that you noted earlier.

11. Choose Update environment.

Resolve throttling that happens in other phases

Important: You must grant AWS Identity and Access Management (IAM) permissions to the CodeBuild service role to access the secret.

2. In the navigation pane, choose Build, and then choose Build projects.

3. Choose your build project.

4. Choose the Build details tab.

5. In the Environment section, for Service role, choose the service role ARN. This opens the IAM console.

6. On the Permissions tab, choose Add inline policy.

7. Choose the JSON tab.

8. Replace the code the text editor with the following IAM policy:

Important: Replace YOUR_SECRET_ARN with the secret ARN that you noted earlier.

9. Choose Review policy.

10. For Name, enter a name for the policy. For example: dockerhub_secret_access Note: You can choose any name for the policy. The name is for your own future reference only.

11. Choose Create policy.

Configure CodeBuild to retrieve the secret

2. In the navigation pane, choose Build, and then choose Build projects.

3. Choose your build project.

4. Choose Edit, and then choose Environment.

5. Expand the Additional configuration section.

6. To add environment variables, in the Environment variables section, for Name, enter DOCKERHUB_USERNAME.

7. For Value, enter the name of your secret, followed by :username. For example: dockerhub:username

8. For Type, choose Secrets Manager.

9. To add the next environment variable, choose Add environment variable.

10. For Name, enter DOCKERHUB_PASSWORD.

11. For Value, enter the name of your secret, followed by :password. For example: dockerhub:password

12. For Type, choose Secrets Manager.

13. Choose Update environment.

14. Modify your buildspec and add the following command before performing any other Docker actions:

Warning: This command can record details of your docker login username and password in build logs. After resolving the throttle error, reset your docker password.

Источник

error pulling image configuration (i/o timeout) #3

Docker can’t pull image.

Expected behavior

$sudo docker run hello-world
.
Hello from Docker!
This message shows that your installation appears to be working correctly.

..smth success output.

Actual behavior

dhXarDW31xnE_&Key-Pair-Id=APKAJECH5M7VWIS5YZ6Q: dial tcp: lookup dseasb33srnrn.cloudfront.net on 127.0.1.1:53: read udp 127.0.0.1:40048->127.0.1.1:53: i/o timeout.
See ‘docker run —help’.

Information

Distributor ID: LinuxMint
Description: Linux Mint 17.3 Rosa
Release: 17.3
Codename: rosa

Linux afi-elite 3.16.0-38-generic #52

14.04.1-Ubuntu SMP Fri May 8 09:43:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

docker version
Client:
Version: 17.05.0-ce
API version: 1.29
Go version: go1.7.5
Git commit: 89658be
Built: Thu May 4 22:17:31 2017
OS/Arch: linux/amd64

Server:
Version: 17.05.0-ce
API version: 1.29 (minimum version 1.12)
Go version: go1.7.5
Git commit: 89658be
Built: Thu May 4 22:17:31 2017
OS/Arch: linux/amd64
Experimental: false

Steps to reproduce the behavior

1. Install docker
2. run sudo docker run hello-world

The text was updated successfully, but these errors were encountered:

Источник

AWS ECR error pulling image configuration made easy with Bobcares by your side.

At Bobcares, we guarantee solutions for any query as a part of our AWS Support Service.

Let’s dive in and take a look at how our skilled Support Engineers recommend running a Docker image via the docker pull command.

Dealing with pulling image configuration AWS ECR error 

Did you know that it is possible to run a Docker image available in ECR by pulling it to the local environment via the docker pull command?

Well, our Support Engineers are here to show you how to get this done through a registry associated with another AWS account or through the default registry

Although, remember to keep in mind that users need to have permission to make calls to ecr:GetAuthorizationToken API via an IAM policy before authenticating to a registry and pull or push any image from any ECR repository.

Furthermore, ECR offers multiple IAM policies to control user access at different levels.

How to resolve pulling image configuration AWS ECR error

1. First, we will authenticate the Docker client to the ECR repository from where we plan to pull the image from.

   According to our Support Techs, it is essential to note that the authentications tokens are valid for 12 hours and have to be obtained for each registry used.

2. Although this step is optional, you can still go ahead and identify the image to be pulled:
   • First, list the repositories in the registry as seen below:

     aws ecr describe-repositories

   • Then, describe the images within the repository with the following command:

     aws ecr describe-images --repository-name amazonlinux

3. After that, we will pull the image via the docker pull command. Remember to keep the image name format as registry/repository[@digest] to pull by digest or registry/repository[:tag] to pull by tag.

   docker pull aws_account_id.dkr.ecr.us-west-2.amazonaws.com/amazonlinux:latest

In case you wind up with the “repository-url not found: does not exist or no pull access” error, worry not. We just have to authenticate the Docker client with Amazon ECR.

[Need an extra hand with Server Management? We are just a click away.]

Conclusion

At the end of the day, the Support Techs at Bobcares demonstrated how to go about AWS ECR error pulling image configuration without getting errors.

Spend time on your business, not on your servers.

Managing a server is time consuming. Whether you are an expert or a newbie, that is time you could use to focus on your product or service. Leave your server management to us, and use that time to focus on the growth and success of your business.

TALK TO US
Or click here to learn more.