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

gpg: keyserver receive failed: Cannot assign requested address #530

Closed
katomel4 opened this issue Dec 31, 2018 · 2 comments
Closed

gpg: keyserver receive failed: Cannot assign requested address #530

katomel4 opened this issue Dec 31, 2018 · 2 comments
Labels
question Usability question, not directly related to an error with the image

Comments

@katomel4
Copy link

gpg: keyserver receive failed: Cannot assign requested address
Only on Azure Devops build

@wglambert wglambert added the question Usability question, not directly related to an error with the image label Dec 31, 2018
@wglambert
Copy link

docker-library/official-images#4252 (comment)

TLDR; GPG servers are extremely flaky and we have yet to solve it reliably.

For automated testing, we usually just set our travis builds to repeat multiple times (like php) since it is usually just gpg failures.

For builds on my local machine (which is were most build tests for official image PRs are done) I run an nginx reverse proxy server to man-in-the-middle apt, apk, and gpg requests and cache them.

For the servers that build and push the official images we take an eventually consistent approach and mark builds as "unstable" if one or more tags fail to build and just allow the build to run later. They also have multiple retries for each tag.

Related issues: docker-library/cassandra#131 (comment), docker-library/tomcat#87, docker-library/tomcat#108, #263 (comment), docker-library/httpd#66 (comment), docker-library/php#586, docker-library/wordpress#291

@erinbit
Copy link

erinbit commented May 25, 2020

We faced this issue in our own docker builds and found another solution.

Use the keyserver to add the key once, then use apt-key export to export the key to a file. Add that file to your code repo, copy it into docker, and then use apt-key add to add it. No need to download keys anymore!

This way the builds will work well until the key is changed for some reason, which usually doesn't happen too often I hope.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Usability question, not directly related to an error with the image
Projects
None yet
Development

No branches or pull requests

3 participants