The getaddrinfo EAI_AGAIN error again

[AgentCoop]

• v6.11.4, within the node:6.11.4-onbuild image:
• Linux 0123f9db6b51 4.12.8-2-ARCH deps: update openssl to 1.0.1j #1 SMP PREEMPT Fri Aug 18 14:08:02 UTC 2017 x86_64 GNU/Linux:
• dns.lookup():

There are lots of similar issues but not one stated clearly how this problem can be fixed.

In run bower install --allow-root when building a Docker image and every time I get errors like this one: bower morris.js#^0.5.1 EAI_AGAIN Request to https://registry.bower.io/packages/morrisjs failed: getaddrinfo EAI_AGAIN registry.bower.io:443

The bower package raising error can be any. Some people say that the problem relates the number of libuv threads but tweaking UA_THREADPOOL_SIZE environment variable did not help.

With few packages to install there are no issues, in my case I have about 20 packages to install and the error appears somewhere in the middle of the process.

As for now I have to use this "solution":

RUN bower install --allow-root; exit 0 # Workaround for the bower install getaddrinfo EAI_AGAIN error
RUN bower install --allow-root

[bnoordhuis]

EAI_AGAIN means the DNS server replied that it cannot currently fulfill the request. (If you want the hairy details, the RCODE field in the response is set to 2, SERVFAIL.)

There is no single solution because it entirely depends on why the DNS server sends that back. Maybe it's overloaded, maybe the network is down, maybe it got the same reply from its upstream server.

In general, the best you can do is wait a while and try again. Hope that helps.

[corvello]

I found this same situation today. Its really a DNS issue. I workaround setting up the github.com ip address temporary on the hosts file .

[hackhat]

Im getting this on docker, not sure why.

[AnirbanKundu]

I am getting this error while trying to dockerizing my Node JS app

[oskapt]

Im getting this on docker, not sure why.

If you're using an image derived from alpine linux, there are known issues with the musl dns resolver.

If working in Kubernetes, the alpine dns issues create additional problems with options ndots:5. A workaround is to use options ndots:2 to force normal 3-part domain names to be tried as fully-qualified.

(Edited: Added K8S detail)