always fail with slow internet, while npm does work

11 thoughts on “always fail with slow internet, while npm does work”

1. +1

2. @Jas99 Please don’t post +1 comment. 👍 in the main post is enough.

3. I also experience the same issue, this is a screenshot of a recent occurrance:

   

   It seems to be somewhat intermittent (almost 60%% probability of happening).

   This is my docker file:

   WORKDIR /opt/app
   
   RUN mkdir -p /opt
   ADD yarn-v0.18.1.tar.gz /opt/
   RUN mv /opt/dist /opt/yarn
   ENV PATH "$PATH:/opt/yarn/bin"
   
   ADD package.json yarn.lock /tmp/
   RUN cd /tmp && yarn
   RUN mkdir -p /opt/app && cd /opt/app && ln -s /tmp/node_modules
   ADD . /opt/app
   RUN cd /opt/app && yarn run gulp
   RUN cd /opt/app && yarn run start

4. I experienced it too, but setting the network-concurrency parameter to 1 solved it in my case:

   yarn install --network-concurrency 1
   

5. I had this same issue running yarn in a docker container on Ubuntu 17.04, and found that, in my case, running dnsmasq as a service (for an unrelated project) was causing the containerized yarn install to throw this error. Stopping dnsmasq solved the issue.

6. I had this issue when doing a yarn install into the Docker base image alexsuch/angular-cli (1.2.1). I figured out that deleting local Docker image and restarting Docker solved the problem.

   I suspect yarn keep failing because of the DNS record not found from the Docker image, for some reason (long Docker exec on my dev laptop can lead to little unwanted behaviours like these).

7. A quick & dirty fix is to add following line to your /etc/hosts file (*nix) or C:\Windows\System32\drivers\etc\ file (Windows):

   AAA.BB.CC.DDD registry.yarnpkg.com
   

   where AAA.BB.CC.DDD is the IP address currently mapped to the registry.yarnpkg.com domain. At the moment it’s 104.16.63.173 but may change. You can get it from here for example: https://www.ultratools.com/tools/pingResult?hostName=registry.yarnpkg.com

8. docker-machine restart solved it in my instance.

9. This problem happen when you change your network, maybe from a wifi network to another one.
   All you need to do is restart the docker service:
   sudo systemctl restart docker

10. Same issue for me in docker. but outside the docker it works.

11. --network-concurrency 1 didn’t work for me, here’s the workaround inspired by @avsd:

    apt-get install -y bind9-host
    registryYarnpkgComIpAddress=$(host registry.yarnpkg.com | awk '/has address/ { print $4 }' | head -n1)
    echo "${registryYarnpkgComIpAddress} registry.yarnpkg.com" >> /etc/hosts
    

Comments are closed.