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

why run my local gpg is fails ? #529

Closed
ZRothschild opened this issue Dec 30, 2018 · 1 comment
Closed

why run my local gpg is fails ? #529

ZRothschild opened this issue Dec 30, 2018 · 1 comment
Labels
question Usability question, not directly related to an error with the image

Comments

@ZRothschild
Copy link

Gpg: keyserver receive failed: No keyserver available or Gpg: keyserver receive failed: connot assign rquested address but the dockerfile can run the labs.play-with-docker.com

@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

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

2 participants