Skip to content

gpg: keyserver receive failed: Address not available #380

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.

Sign up for GitHub

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

Jump to bottom
Closed
marciomsm opened this issue Apr 12, 2017 · 4 comments
Closed

gpg: keyserver receive failed: Address not available #380

marciomsm opened this issue Apr 12, 2017 · 4 comments

Comments

@marciomsm
Copy link

I am trying to generate a docker image to node 6.10 with alpine, but I get this error:

gpg: keyserver receive failed: Address not available

Does anyone knows how to solve it?
@chorrell
Copy link
Contributor

That looks like a possible network issue in your docker setup. We also recently updated the docker files to try more than one key server:

https://github.com/nodejs/docker-node/blob/master/6.10/Dockerfile#L18

We would get periodic failures with ha.pool.sks-keyservers.net

@F30
Copy link

F30 commented Jun 6, 2017

(Came here through Google after having the same error in a different container.)

In my case, the error with [ha.]pool.sks-keyservers.net was related to IPv4 vs. IPv6: GPG's dirmngr might select a v6 server from the pool and try to connect to it, even though it doesn't have v6 connectivity inside the container.
I'm not sure whether this is a bug in Docker or dirmngr, but there is at least this bug related to dirmngr and IPv6.

If one wants stay with sks-keyservers, ipv4.pool.sks-keyservers.net can be used.

@nluetic nluetic mentioned this issue Aug 22, 2017
Closed
@nicolas-albert
Copy link

nicolas-albert commented Dec 1, 2017 •
edited
Loading

Thank @chorrell , I fixed my Dockerfiles with your workaround 👍

( gpg --keyserver ha.pool.sks-keyservers.net --recv-keys "$GPG_KEYS" \
  || gpg --keyserver pgp.mit.edu --recv-keys "$GPG_KEYS" \
  || gpg --keyserver keyserver.pgp.com --recv-keys "$GPG_KEYS" )

@paolomainardi paolomainardi mentioned this issue Feb 5, 2018
Closed
@chorrell chorrell mentioned this issue Feb 20, 2018
Merged
lkysow added a commit to runatlantis/atlantis that referenced this issue Mar 11, 2018
@lkysow
Use ipv4 keyservers to fix failing builds.
18ef0df 
See nodejs/docker-node#380
@lkysow lkysow mentioned this issue Mar 11, 2018
Merged
@clingle clingle mentioned this issue Mar 14, 2018
Closed
@nijel nijel mentioned this issue Apr 18, 2018
Merged
@chorrell
Copy link
Contributor

Also see:

redshiftzero added a commit to freedomofpress/securedrop that referenced this issue May 31, 2018
@redshiftzero
CLI integration tests: Set reliable default keyserver.
4d83d51 
In Tails, the default keyserver is sometimes flaky [0], so
we implemented a retry in securedrop-admin update [1].

In the integration tests, using the same default pool as in
Tails, there appears to still be some flakiness. Digging a bit
my hypothesis is that this is occuring when we are assigned a keyserver
that is IPv6 from the pool [2]. For test purposes, I'm setting a
reliable default keyserver in gpg.conf.

[0] https://labs.riseup.net/code/issues/12689
[1] #3257
[2] nodejs/docker-node#380 (comment)
redshiftzero added a commit to freedomofpress/securedrop that referenced this issue Jun 4, 2018
@redshiftzero
CLI integration tests: Set reliable default keyserver.
2677327 
In Tails, the default keyserver is sometimes flaky [0], so
we implemented a retry in securedrop-admin update [1].

In the integration tests, using the same default pool as in
Tails, there appears to still be some flakiness. Digging a bit
my hypothesis is that this is occuring when we are assigned a keyserver
that is IPv6 from the pool [2]. For test purposes, I'm setting a
reliable default keyserver in gpg.conf.

[0] https://labs.riseup.net/code/issues/12689
[1] #3257
[2] nodejs/docker-node#380 (comment)
@rbreslow rbreslow mentioned this issue Jun 6, 2018
Merged
redshiftzero added a commit to freedomofpress/securedrop that referenced this issue Jun 14, 2018
@redshiftzero
CLI integration tests: Set reliable default keyserver.
0ad6f7b 
In Tails, the default keyserver is sometimes flaky [0], so
we implemented a retry in securedrop-admin update [1].

In the integration tests, using the same default pool as in
Tails, there appears to still be some flakiness. Digging a bit
my hypothesis is that this is occuring when we are assigned a keyserver
that is IPv6 from the pool [2]. For test purposes, I'm setting a
reliable default keyserver in gpg.conf.

[0] https://labs.riseup.net/code/issues/12689
[1] #3257
[2] nodejs/docker-node#380 (comment)
redshiftzero added a commit to freedomofpress/securedrop that referenced this issue Jun 14, 2018
@redshiftzero
CLI integration tests: Set reliable default keyserver.
a3fbbb2 
In Tails, the default keyserver is sometimes flaky [0], so
we implemented a retry in securedrop-admin update [1].

In the integration tests, using the same default pool as in
Tails, there appears to still be some flakiness. Digging a bit
my hypothesis is that this is occuring when we are assigned a keyserver
that is IPv6 from the pool [2]. For test purposes, I'm setting a
reliable default keyserver in gpg.conf.

[0] https://labs.riseup.net/code/issues/12689
[1] #3257
[2] nodejs/docker-node#380 (comment)
redshiftzero added a commit to freedomofpress/securedrop that referenced this issue Jun 15, 2018
@redshiftzero
CLI integration tests: Set reliable default keyserver.
caebc2d 
In Tails, the default keyserver is sometimes flaky [0], so
we implemented a retry in securedrop-admin update [1].

In the integration tests, using the same default pool as in
Tails, there appears to still be some flakiness. Digging a bit
my hypothesis is that this is occuring when we are assigned a keyserver
that is IPv6 from the pool [2]. For test purposes, I'm setting a
reliable default keyserver in gpg.conf.

[0] https://labs.riseup.net/code/issues/12689
[1] #3257
[2] nodejs/docker-node#380 (comment)
israelshirk added a commit to nlp-secure/percona-docker that referenced this issue Jun 19, 2018
@israelshirk
Force ipv4 keyserver as per nodejs/docker-node#380
8335bb4
redshiftzero added a commit to freedomofpress/securedrop that referenced this issue Jun 21, 2018
@redshiftzero
CLI integration tests: Set reliable default keyserver.
e8df576 
In Tails, the default keyserver is sometimes flaky [0], so
we implemented a retry in securedrop-admin update [1].

In the integration tests, using the same default pool as in
Tails, there appears to still be some flakiness. Digging a bit
my hypothesis is that this is occuring when we are assigned a keyserver
that is IPv6 from the pool [2]. For test purposes, I'm setting a
reliable default keyserver in gpg.conf.

[0] https://labs.riseup.net/code/issues/12689
[1] #3257
[2] nodejs/docker-node#380 (comment)

(cherry picked from commit caebc2d)
henrist added a commit to capralifecycle/jenkins-slave that referenced this issue Jun 27, 2018
@henrist
Try multiple keyservers
3c45304 
Related:
- https://www.bountysource.com/issues/44071259-gpg-keyserver-receive-failed-address-not-available
- nodejs/docker-node#380 (comment)
This was referenced Jul 6, 2018
Closed
Merged
Closed
@austinpray austinpray mentioned this issue Sep 14, 2018
Closed
austinpray added a commit to austinpray/python that referenced this issue Sep 14, 2018
@austinpray
Adds keyserver fallbacks
d483ba9 
Closes docker-library#334
Ref nodejs/docker-node#380
Ref https://github.com/nodejs/docker-node/blob/526c6e618300bdda0da4b3159df682cae83e14aa/Dockerfile-alpine.template#L23-L25
Ref https://gitlab.com/meltano/meltano/issues/90
@austinpray austinpray mentioned this issue Sep 14, 2018
Closed
@tomverin tomverin mentioned this issue Sep 27, 2018
Merged
@dlangh dlangh mentioned this issue Oct 17, 2018
Closed
avrabe added a commit to avrabe/ros2_raspbian_tools that referenced this issue Mar 17, 2019
@avrabe
Added several gpg keyserver.
d0bbea1 
For building dockerfiles it seems others use this workaround too: nodejs/docker-node#380
@RajeshwariS RajeshwariS mentioned this issue Jul 9, 2019
Closed
samsondav pushed a commit to smartcontractkit/builder that referenced this issue Feb 19, 2020
Make the keyserver lookup more robust
7b02551 
See: nodejs/docker-node#380
@flongford flongford mentioned this issue Jul 15, 2020
Open
@ferrarimarco ferrarimarco mentioned this issue Oct 30, 2020
Closed
@albertvaka albertvaka mentioned this issue Nov 10, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@chorrell @nicolas-albert @F30 @marciomsm