title: Express js npm install fails reason: getaddrinfo EAI_AGAIN
body: <p>I have a Node.JS / Express.JS server-side program, which I run inside a Node.JS docker container. It was working for the last ~2 years, now it produces a strange error upon installing.
  I use docker-compose to install / run the program.</p>
  <p>The Dockerfile:</p>
  <pre><code>FROM node:10
  ARG PORT
  ENV PORT ${PORT}
  
  # Create app directory
  ADD backend /app
  WORKDIR /app
  
  RUN npm ci --only=production
  
  EXPOSE $PORT
  
  CMD [&quot;npm&quot;, &quot;run&quot;, &quot;start-prod&quot;]
  </code></pre>
  <p>When I try to install it (with <code>docker-compose</code>, it fails every time, with this message:</p>
  <pre><code>Building backend
  Step 1/10 : FROM node:10
   ---&gt; a8441ebf4e4d
  Step 2/10 : ARG PORT
   ---&gt; Using cache
   ---&gt; d985b4141806
  Step 3/10 : ENV PORT ${PORT}
   ---&gt; Using cache
   ---&gt; e053f5bb49fa
  Step 4/10 : ADD backend /app
   ---&gt; Using cache
   ---&gt; 409d0ab160ea
  Step 5/10 : WORKDIR /app
   ---&gt; Using cache
   ---&gt; b7aad109486b
  Step 6/10 : RUN cp environment-prod-docker.js environment.js
   ---&gt; Using cache
   ---&gt; 218df5ff1cff
  Step 7/10 : RUN cat environment.js
   ---&gt; Using cache
   ---&gt; 87965e20e57e
  Step 8/10 : RUN npm ci --only=production
   ---&gt; Running in 9352da8c367e
  npm WARN prepare removing existing node_modules/ before installation
  npm ERR! code EAI_AGAIN                                                                                                                                                                                                                                                        
  npm ERR! errno EAI_AGAIN                                                                                                                                                                                                                                                       
  npm ERR! request to https://registry.npmjs.org/bcryptjs/-/bcryptjs-2.4.3.tgz failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org registry.npmjs.org:443                                           
  </code></pre>
  <p>I have read that it might be possible that this is a proxy error. I have tried to change to my home wifi, my home cable, and mobile data: still produced the same error. If I copy the link, I can download the said .tgz file from the browser.</p>