gpg: keyserver receive failed: Address not available #380

Activity

1. chorrell commented on Apr 20, 2017

   

   chorrell

   on Apr 20, 2017

   Contributor

   More actions

   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
2. F30 commented on Jun 6, 2017

   

   F30

   on Jun 6, 2017

   More actions

   (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.

   👍React with 👍39Reacted by Daniel Quinn, Andrew Phillips, Ron Arts, Stephen Lacy, Stefan Nordhausen, Bryan Stitt, Dimitrios Karagiannis, Nikolay Kushin, Zlatko Čalušić, Andrew Kravchuk and 29 more
3. nicolas-albert commented on Dec 1, 2017

   

   nicolas-albert

   on Dec 1, 2017

   Last edited by nicolas-albert

   More actions

   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" )
   

   👍React with 👍12Reacted by Artem Melnyk, Nikos Paschos, Lenin Jose Meza Zarco, Domantas, Kevin Robatel, Adam Hanna, deniska-info, dekey, Thomas Gamauf, Irzhy Ranaivoarivony and 2 more

   🎉React with 🎉3Reacted by Adam Hanna, Wojciech Bartosiak and Kote Mushegiani

   ❤️React with ❤️3Reacted by Serghei Iakovlev, Adam Hanna and Kote Mushegiani
4. lkysow

   added a commit that references this issue on Mar 11, 2018

   Use ipv4 keyservers to fix failing builds.

   ...

   18ef0df
5. chorrell commented on May 25, 2018

   

   chorrell

   on May 25, 2018

   Contributor

   More actions

   Also see:

   • GPG failures #591
   • Drop keyserver.pgp.com and reorder pgp key servers #632
6. chorrell

   closed this as completedon May 25, 2018
7. redshiftzero

   added 2 commits that reference this issue on May 31, 2018

   CLI integration tests: Set reliable default keyserver.

   ...

   4d83d51

   CLI integration tests: Set reliable default keyserver.

   ...

   2677327
8. redshiftzero

   added 3 commits that reference this issue on Jun 14, 2018

   CLI integration tests: Set reliable default keyserver.

   ...

   0ad6f7b

   CLI integration tests: Set reliable default keyserver.

   ...

   a3fbbb2

   CLI integration tests: Set reliable default keyserver.

   ...

   caebc2d
9. israelshirk

   added a commit that references this issue on Jun 19, 2018

   Force ipv4 keyserver as per nodejs/docker-node#380

   8335bb4
10. redshiftzero

    added a commit that references this issue on Jun 21, 2018

    CLI integration tests: Set reliable default keyserver.

    ...

    e8df576
11. henrist

    added a commit that references this issue on Jun 27, 2018

    Try multiple keyservers

    ...

    3c45304
12. austinpray

    added a commit that references this issue on Sep 14, 2018

    Adds keyserver fallbacks

    ...

    d483ba9
13. avrabe

    added a commit that references this issue on Mar 17, 2019

    Added several gpg keyserver.

    ...

    d0bbea1
14. samsondav

    added a commit that references this issue on Feb 19, 2020

    Make the keyserver lookup more robust

    ...

    7b02551