You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: