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
{{ message }}
This repository has been archived by the owner on Apr 17, 2021. It is now read-only.
Build failed: The command '/bin/sh -c apt-key adv --keyserver pgp.mit.edu --recv-key 8325FECB83821E31D3582A69CE050D236DB6FA3F' returned a non-zero code: 2
I suspect problem is that docker build environment has unreliable networking or the keyserver gets hit too hard by the docker build environment (these images build when debian/centos images get updated so it might be a time of peak keyserver activity).
I believe a safer approach would be one of the following:
Download the ASCII key, place it in repo, COPY into image and run apt-key.
Find a binary key, place it in repo and copy it into /etc/apt/trusted.gpg.d. Might copy/match the file from the "repo package" if one exists.
Either approach should be done by generating as few layers as possible.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We see build errors when retrieving apt keys every so often. e.g.
I suspect problem is that docker build environment has unreliable networking or the keyserver gets hit too hard by the docker build environment (these images build when debian/centos images get updated so it might be a time of peak keyserver activity).
I believe a safer approach would be one of the following:
COPY
into image and runapt-key
./etc/apt/trusted.gpg.d
. Might copy/match the file from the "repo package" if one exists.Either approach should be done by generating as few layers as possible.
The text was updated successfully, but these errors were encountered: