Skip to content
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

Issues Downloading Docker Images During Playbook Execution #2357

Open
Richie1710 opened this issue Aug 13, 2024 · 2 comments
Open

Issues Downloading Docker Images During Playbook Execution #2357

Richie1710 opened this issue Aug 13, 2024 · 2 comments

Comments

@Richie1710
Copy link
Contributor

Hello,
I've encountered an issue while running the playbook where certain Docker images could not be downloaded from the Nexus repository. The playbook attempts to pull the images, but it results in a 500 Internal Server Error. Here are the details:

Image: nexus.testbed.osism.xyz:8193/kolla/keystone-fernet:2023.2
    Error Message: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.45/images/create?tag=2023.2&fromImage=nexus.testbed.osism.xyz%3A8193%2Fkolla%2Fkeystone-fernet: Internal Server Error ("unknown: Remote Auto Blocked until 2024-08-13T07:45:05.681Z")

Image: nexus.testbed.osism.xyz:8193/kolla/haproxy:2023.2
    Error Message: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.45/images/create?tag=2023.2&fromImage=nexus.testbed.osism.xyz%3A8193%2Fkolla%2Fhaproxy: Internal Server Error ("unknown: Remote Auto Blocked until 2024-08-13T07:45:05.681Z")

It seems like the access to the remote repository might be temporarily blocked or there could be an issue with the Nexus server.

Could you please take a look at this? Any assistance would be greatly appreciated.

Thank you!

@berendt
Copy link
Member

berendt commented Aug 15, 2024

Looks like the external repository server cannot be reached. nexus.testbed.osism.xyz:8193 points to our osism.harbor.regio.digital server. It's probably better to use quay.io instead.

https://support.sonatype.com/hc/en-us/articles/213464888-A-proxy-repository-is-not-working-status-says-Remote-Automatically-Blocked-and-Unavailable

If a remote is responding very slowly, this can cause incoming requests to pile up waiting for this one particular remote to respond.  In extreme cases so many requests can pile up that the inbound request thread pool becomes exhausted, rendering the server unusable.

To solve this problem, we added the auto-block feature.  If a remote does not respond within the read timeout setting (default is 20 seconds, with 3 retries) it is auto-blocked. 

berendt added a commit that referenced this issue Aug 22, 2024
berendt added a commit that referenced this issue Aug 22, 2024
berendt added a commit that referenced this issue Aug 22, 2024
@Richie1710
Copy link
Contributor Author

Seems to be working with images from quay.io

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants