npm install error - getaddrinfo EAI_AGAIN registry.npmjs.org:443 #270

akelle17 · 2018-01-24T22:38:10Z

Everytime I try to npm install a file I get the following error:
getaddrinfo EAI_AGAIN registry.npmjs.org:443

I am using stefanscherer/node-windows:8.9.3 image but have had this issue with many other images as well.

Initial npm error:

npm logs:

The text was updated successfully, but these errors were encountered:

StefanScherer · 2018-01-31T15:18:15Z

Hi @akelle17
Sounds like a general network problem inside Windows containers.
What's your environment? Windows 10 with Docker for Windows? Or a Windows Server 2016? Which versions, both OS and Docker or D4W?

Maybe running the script mentioned in https://docs.microsoft.com/en-us/virtualization/windowscontainers/troubleshooting gives you more details.

StefanScherer · 2018-03-03T17:18:42Z

Still having problems?

binarymist · 2018-04-18T02:31:58Z

This known issue for Docker and is discussed in detail here: https://development.robinwinslow.uk/2016/06/23/fix-docker-networking-dns/

Simple fix is to create the file /etc/docker/daemon.json

and insert:

{
    "dns": ["10.0.0.2", "8.8.8.8"]
}

where 10.0.0.2 is the first DNS server your machine requests records from, and 8.8.8.8 is the fallback DNS server, google in this case.

suryaveera1995 · 2018-05-25T15:41:46Z

This issue again coming, can you guys please tell me how to solve this, especially if this is on the AWS

Rama001 · 2019-02-04T07:38:48Z

I can't install browser sync still this error appears.

alifgithub · 2019-02-21T09:26:58Z

pm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EAI_AGAIN: request to https://registry.npmjs.org/npm failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org registry.npmjs.org:443
npm WARN registry Using stale data from https://registry.npmjs.org/ due to a request error during revalidation.
/usr/local/bin/npm -> /usr/local/lib/node_modules/npm/bin/npm-cli.js
/usr/local/bin/npx -> /usr/local/lib/node_modules/npm/bin/npx-cli.js

[email protected]
updated 1 package in 46.932s

any have idea for solve it ? help me please

StefanScherer · 2019-02-21T10:10:05Z

In earlier Windows versions sometimes a sleep has helped before running commands that need internet connection. It seemed that the RUN instruction and setting up network runs in parallel.

See

dockerfiles-windows/getaddrinfo/Dockerfile

Line 5 in 967d4d8

    
           RUN powershell -Command Sleep 2 ; wget -Uri https://github.com/StefanScherer/win-getaddrinfo/releases/download/1.0.8/getaddrinfo.exe -OutFile C:\Windows\system32\getaddrinfo.exe -UseBasicParsing

as an example

luckyyang · 2019-08-01T05:37:22Z

/etc/docker/daemon.json do not work for me. I have to reboot my ubuntu server to resolve my problem.

raghureddycloud · 2019-08-30T09:55:18Z

Restarting system resolved my issue.

karanvij-ai · 2019-09-21T02:27:03Z

Hi All,

I am running Docker Toolbox on windows 10 home.

Following were the steps(In Docker console -> Docker Quick Start and using bash from git installation):

npm install -g create-react-app
create-react-app frontend
cd frontend
npm run test
npm run build
6.npm run start
code .

Created docker file(Dockerfile.dev):

FROM node:alpine

WORKDIR '/app'

COPY package.json .

RUN npm install

COPY . .

CMD ["npm", "run", "start"]

$ docker build -f Dockerfile.dev .

Output in console:

Sending build context to Docker daemon 146.5MB
Step 1/6 : FROM node:alpine
---> ef7d474eab14
Step 2/6 : WORKDIR '/app'
---> Using cache
---> c47b0eb2c3c1
Step 3/6 : COPY package.json .
---> Using cache
---> e5c66b740c8b
Step 4/6 : RUN npm install
---> Running in 962746bea142
npm ERR! code EAI_AGAIN
npm ERR! errno EAI_AGAIN
npm ERR! request to https://registry.npmjs.org/react failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-09-21T01_00_35_350Z-debug.log
The command '/bin/sh -c npm install' returned a non-zero code: 1

Also, I couldn't find the complete log, not sure where is location.

Please help, Thanks

nirajkvinit · 2019-12-14T14:16:31Z

This known issue for Docker and is discussed in detail here: https://development.robinwinslow.uk/2016/06/23/fix-docker-networking-dns/

Simple fix is to create the file /etc/docker/daemon.json

and insert:
{
    "dns": ["10.0.0.2", "8.8.8.8"]
}
where 10.0.0.2 is the first DNS server your machine requests records from, and 8.8.8.8 is the fallback DNS server, google in this case.

Yes! It worked! Thank you!

sid42 · 2019-12-26T03:27:05Z

@karanvij-ai Seeing the same issue, were you able to find a fix?

Tokenyet · 2020-01-09T16:48:46Z

I got a server network issue, and a client restart to let me ssh, and the problem happened. I'll show my steps to slove this issue, hope it help someone 😄

Follow the dns modification step above.
sudo service docker restart or sudo systemctl restart docker to restart docker.
sloved (maybe).

gitaumoses4 · 2020-01-20T19:27:08Z

@Tokenyet it did solve my issue. Thanks alot.

edvegas · 2020-02-26T10:18:14Z

I couldn't resolve issue with adding DNS setting to docker daemon, but I found another solution (maybe this will be useful for someone) - just use host network to resolve dns names by adding --network host setting, ex.:
docker build . --network host -t mytag ...

cyansprite · 2020-03-06T15:36:54Z

Not sure if this will help or even why this is a thing but..
To fix this issue I created the /etc/docker/daemon.json file, sudo systemctl restart docker, then delete the file, sudo systemctl restart docker again.. THEN it works, just restarting docker didn't work, nor did it work when the file was present. Weird but.. this is here if it helps anyone.

hmoralesp · 2020-03-30T00:31:22Z

I couldn't resolve issue with adding DNS setting to docker daemon, but I found another solution (maybe this will be useful for someone) - just use host network to resolve dns names by adding --network host setting, ex.:
docker build . --network host -t mytag ...

it's works

anuragarwalkar · 2020-04-02T17:53:51Z

I couldn't resolve issue with adding DNS setting to docker daemon, but I found another solution (maybe this will be useful for someone) - just use host network to resolve dns names by adding --network host setting, ex.:
docker build . --network host -t mytag ...

worked for me 😊

Xuezenghuigithub · 2020-06-18T09:17:54Z

I couldn't resolve issue with adding DNS setting to docker daemon, but I found another solution (maybe this will be useful for someone) - just use host network to resolve dns names by adding --network host setting, ex.:
docker build . --network host -t mytag ...

it's works. thank u so much~👏

mojtaba-eshghie · 2020-08-03T11:17:08Z

This known issue for Docker and is discussed in detail here: https://development.robinwinslow.uk/2016/06/23/fix-docker-networking-dns/

Simple fix is to create the file /etc/docker/daemon.json

and insert:
{
    "dns": ["10.0.0.2", "8.8.8.8"]
}
where 10.0.0.2 is the first DNS server your machine requests records from, and 8.8.8.8 is the fallback DNS server, google in this case.

Worked for me.

DaniVS · 2020-10-11T22:04:14Z

I couldn't resolve issue with adding DNS setting to docker daemon, but I found another solution (maybe this will be useful for someone) - just use host network to resolve dns names by adding --network host setting, ex.:
docker build . --network host -t mytag ...

This solved my issue on Fedora 32.

Kif11 · 2020-11-27T21:10:52Z

I had the same issue on WSL2 Ubuntu, @binarymist solution worked.

mojtabaRKS · 2020-12-09T16:15:20Z

@binarymist @Tokenyet thank you guys ! your solution was really helpful !

CimeM · 2021-02-04T16:08:00Z

Problem
I am using Docker for Desktop (20.10.2) on Windows 10 (20H2 OSS build 19042). I could not install NPM packages due to:
npm ERR! request to https://registry.npmjs.org/canvas failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org
Pinging the registry.npmjs.org returned that the address could not be resolved so I turned to DNS.

Solution
Being inside a windows container I checked what interface number the container was using with:
Get-DnsClient
Then I changed to a known DNS address with: (The interface number was 4 with my container)
Set-DnsClientServerAddress -InterfaceIndex 4 -ServerAddresses ("8.8.8.8")

I hope this is helpful to those using windows containers on Windows clients.

afonsoalbrecht · 2021-06-12T20:46:58Z

This known issue for Docker and is discussed in detail here: https://development.robinwinslow.uk/2016/06/23/fix-docker-networking-dns/

Simple fix is to create the file /etc/docker/daemon.json

and insert:
{
    "dns": ["10.0.0.2", "8.8.8.8"]
}
where 10.0.0.2 is the first DNS server your machine requests records from, and 8.8.8.8 is the fallback DNS server, google in this case.

that doesn't work for me and the other solutions don't work either. I'm on Ubuntu 20.04

NickKelly1 · 2021-06-21T12:17:18Z

restarting worked for me (sudo systemctl restart docker)

preetsindhal · 2021-08-17T09:54:46Z

This known issue for Docker and is discussed in detail here: https://development.robinwinslow.uk/2016/06/23/fix-docker-networking-dns/

Simple fix is to create the file /etc/docker/daemon.json

and insert:
{
    "dns": ["10.0.0.2", "8.8.8.8"]
}
where 10.0.0.2 is the first DNS server your machine requests records from, and 8.8.8.8 is the fallback DNS server, google in this case.

After creating the file I had to reboot the machine then it worked. 👍

Iman · 2021-10-04T03:11:36Z

This known issue for Docker and is discussed in detail here: https://development.robinwinslow.uk/2016/06/23/fix-docker-networking-dns/

Simple fix is to create the file /etc/docker/daemon.json

and insert:
{
    "dns": ["10.0.0.2", "8.8.8.8"]
}
where 10.0.0.2 is the first DNS server your machine requests records from, and 8.8.8.8 is the fallback DNS server, google in this case.

Works like a charm on a Digitalocean VPS

chibuikesebastine · 2021-11-15T05:57:45Z

I couldn't resolve issue with adding DNS setting to docker daemon, but I found another solution (maybe this will be useful for someone) - just use host network to resolve dns names by adding --network host setting, ex.: docker build . --network host -t mytag ...

You just saved me severally days of headache.

mr-zero-03 · 2021-12-20T19:51:22Z

I couldn't resolve issue with adding DNS setting to docker daemon, but I found another solution (maybe this will be useful for someone) - just use host network to resolve dns names by adding --network host setting, ex.: docker build . --network host -t mytag ...

This one worked for me! Thank you

ShinJustinHolly3317 · 2022-08-27T07:54:59Z

This known issue for Docker and is discussed in detail here: https://development.robinwinslow.uk/2016/06/23/fix-docker-networking-dns/

Simple fix is to create the file /etc/docker/daemon.json

and insert:
{
    "dns": ["10.0.0.2", "8.8.8.8"]
}
where 10.0.0.2 is the first DNS server your machine requests records from, and 8.8.8.8 is the fallback DNS server, google in this case.

This works for me. Thanks a lot dude.

ThangalakshmiKP · 2022-09-13T10:23:58Z

This issue again coming, can you guys please tell me how to solve this, especially if this is on the AWS

yes i am also getting same like:
{
"status": "failure",
"err_msg": "getaddrinfo EAI_AGAIN bucket_name.s3.amazonaws.com bucket_name.s3.amazonaws.com:443",
"status_code": 404
}
please help!

mustafaStakater · 2022-12-03T17:06:23Z

For the peeps using Buildah who came across this issue when using alpine image, I updated the buildah build command to override container dns with google dns server buildah bud --dns='8.8.8.8'

stasfainberg · 2023-12-13T22:11:11Z

hey guys,

i run Docker 24.0.7 on Ubuntu 22.04.3 LTS.
i tried installing express module on a Node.js container (docker run -v $PWD:/app -w /app node npm install express) but it failed with the same errors.

weird but... a restart solved my problem too!!!

could be related to any port mapping i run before that with Nginx container (docker run -p 8080:80 -v $PWD:/usr/share/nginx/html nginx) i saw it created a FW rule on my Ubuntu

baba216 · 2023-12-20T10:04:12Z

Hello Members,

Docker Version: 24.0.7
OS:Ubuntu 22.04.3 LTS

Short answer:
even after adding dns in daemon.json its not working, enable IPv4 forwarding [ref]

Long Answer :
Even after after adding dns in daemon.json the issue was not resolved. On further investigation and downgrading to docker version 20.10.17 , I noticed one additional error message [ie, IPv4 forwarding is disabled. Networking will not work.] which was not visible for docker version 24.0.7. Please find complete details

Step 4/6 : RUN npm install
---> [Warning] IPv4 forwarding is disabled. Networking will not work.
---> Running in 410fdfb3445e
npm ERR! code EAI_AGAIN
npm ERR! errno EAI_AGAIN
npm ERR! request to https://registry.npmjs.org/axios failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org

npm ERR! A complete log of this run can be found in:

npm ERR! /root/.npm/_logs/2023-12-20T09_56_37_800Z-debug.log

The command '/bin/sh -c npm install' returned a non-zero code: 1

After I enabled ipv4 forward. It started working.

akelle17 closed this as completed Mar 20, 2018

exxonvaldez mentioned this issue Mar 2, 2020

Add title to dashboard, isochrone, and routesScreen pages trynmaps/metrics-mvp#467

Merged

geoph9 mentioned this issue Oct 15, 2020

on docker-compose build, storefront give build error saleor/saleor-platform#43

Closed

breakingflower mentioned this issue Oct 23, 2020

Running on ARMv7 - No MySQL, run with postgres db? mriedmann/humhub-docker#145

Closed

NikolayCharaev mentioned this issue Nov 3, 2024

> This known issue for Docker and is discussed in detail here: https://development.robinwinslow.uk/2016/06/23/fix-docker-networking-dns/ #471

Open

mperdikeas mentioned this issue Nov 7, 2024

ERROR: No matching distribution found for Flask==2.0.2 prakhar1989/docker-curriculum#373

Open

npm install error - getaddrinfo EAI_AGAIN registry.npmjs.org:443 #270

npm install error - getaddrinfo EAI_AGAIN registry.npmjs.org:443 #270

Comments

akelle17 commented Jan 24, 2018

StefanScherer commented Jan 31, 2018

StefanScherer commented Mar 3, 2018

binarymist commented Apr 18, 2018

suryaveera1995 commented May 25, 2018

Rama001 commented Feb 4, 2019 • edited Loading

alifgithub commented Feb 21, 2019

StefanScherer commented Feb 21, 2019

luckyyang commented Aug 1, 2019

raghureddycloud commented Aug 30, 2019

karanvij-ai commented Sep 21, 2019

Created docker file(Dockerfile.dev):

CMD ["npm", "run", "start"]

npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2019-09-21T01_00_35_350Z-debug.log The command '/bin/sh -c npm install' returned a non-zero code: 1

nirajkvinit commented Dec 14, 2019

sid42 commented Dec 26, 2019

Tokenyet commented Jan 9, 2020 • edited Loading

gitaumoses4 commented Jan 20, 2020

edvegas commented Feb 26, 2020

cyansprite commented Mar 6, 2020

hmoralesp commented Mar 30, 2020

anuragarwalkar commented Apr 2, 2020

Xuezenghuigithub commented Jun 18, 2020

mojtaba-eshghie commented Aug 3, 2020

DaniVS commented Oct 11, 2020

Kif11 commented Nov 27, 2020

mojtabaRKS commented Dec 9, 2020

CimeM commented Feb 4, 2021 • edited Loading

afonsoalbrecht commented Jun 12, 2021 • edited Loading

NickKelly1 commented Jun 21, 2021

preetsindhal commented Aug 17, 2021

Iman commented Oct 4, 2021

chibuikesebastine commented Nov 15, 2021

mr-zero-03 commented Dec 20, 2021

ShinJustinHolly3317 commented Aug 27, 2022

ThangalakshmiKP commented Sep 13, 2022 • edited Loading

mustafaStakater commented Dec 3, 2022

stasfainberg commented Dec 13, 2023 • edited Loading

baba216 commented Dec 20, 2023

Rama001 commented Feb 4, 2019 •

edited

Loading

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-09-21T01_00_35_350Z-debug.log
The command '/bin/sh -c npm install' returned a non-zero code: 1

Tokenyet commented Jan 9, 2020 •

edited

Loading

CimeM commented Feb 4, 2021 •

edited

Loading

afonsoalbrecht commented Jun 12, 2021 •

edited

Loading

ThangalakshmiKP commented Sep 13, 2022 •

edited

Loading

stasfainberg commented Dec 13, 2023 •

edited

Loading