Timeout error on yarn install with date-fns@next on Dockerhub

[Dvisacker]

I'm receiving the following error (see bottom of the log below) when doing a yarn install using the date-fns@next package. Everything is working fine with the non-alpha versions and I can also do the install from my computer and wget the package url without any problem.

Building in Docker Cloud's infrastructure...
Cloning into '.'...

KernelVersion: 4.4.0-1060-aws
Components: [{u'Version': u'18.03.1-ee-3', u'Name': u'Engine', u'Details': {u'KernelVersion': u'4.4.0-1060-aws', u'Os': u'linux', u'BuildTime': u'2018-08-30T18:42:30.000000000+00:00', u'ApiVersion': u'1.37', u'MinAPIVersion': u'1.12', u'GitCommit': u'b9a5c95', u'Arch': u'amd64', u'Experimental': u'false', u'GoVersion': u'go1.10.2'}}]
Arch: amd64
BuildTime: 2018-08-30T18:42:30.000000000+00:00
ApiVersion: 1.37
Platform: {u'Name': u''}
Version: 18.03.1-ee-3
MinAPIVersion: 1.12
GitCommit: b9a5c95
Os: linux
GoVersion: go1.10.2
Starting build of index.docker.io/proofsuite/amp-client:latest...
Step 1/19 : FROM node as builder


 ---> 37f455de4837

Step 2/19 : RUN mkdir /usr/src/app


 ---> Running in ee9fff5fc879

Removing intermediate container ee9fff5fc879

 ---> 6003512c2925

Step 3/19 : WORKDIR /usr/src/app


Removing intermediate container a333d4a70ded

 ---> aff5b84b868d

Step 4/19 : ENV PATH /usr/src/app/node_modules/.bin:$PATH


 ---> Running in 0dbaf1809ed3

Removing intermediate container 0dbaf1809ed3

 ---> fe832a7228ea

Step 5/19 : COPY package.json /usr/src/app/package.json


 ---> b232399ef432

Step 6/19 : COPY public/ /usr/src/app/public/


 ---> 7324dea98d53

Step 7/19 : COPY src/ /usr/src/app/src/


 ---> 3258d87a395a

Step 8/19 : RUN yarn install --silent


 ---> Running in b397ea5ebac6

�[91mwarning react-scripts > autoprefixer > browserslist@2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
�[0m
�[91mwarning react-scripts > babel-preset-react-app > babel-preset-env > browserslist@2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
�[0m
�[91mwarning react-scripts > css-loader > cssnano > autoprefixer > browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
�[0m
�[91mwarning react-scripts > css-loader > cssnano > postcss-merge-rules > browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
�[0m
�[91mwarning react-scripts > css-loader > cssnano > postcss-merge-rules > caniuse-api > browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
�[0m
�[91mwarning react-scripts > eslint > file-entry-cache > flat-cache > circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
�[0m
�[91mwarning @storybook/react > @storybook/core > autoprefixer > browserslist@2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
�[0m
�[91mwarning enzyme > rst-selector-parser > nearley > nomnom@1.6.2: Package no longer supported. Contact support@npmjs.com for more info.
�[0m
�[91merror An unexpected error occurred: "https://registry.yarnpkg.com/date-fns/-/date-fns-2.0.0-alpha.25.tgz: ESOCKETTIMEDOUT".
�[0m
Removing intermediate container b397ea5ebac6

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

Cheers

[kossnocorp]

That is either npm or your local network problem, and date-fns has nothing to with it, sorry.

[jamiehd]

@kossnocorp weirdly I have exactly the same problem with this package specifically on dockerhub. It installs fine locally. Do you know of any reason why this would specifically affect your package? Does it do anything specific that takes longer than other packages? Thanks

[yuki-takei]

@jamiehd
Maybe because CPUs of dockerhub are too weak. Try to increase network-timeout of yarn.

# 300sec
yarn config set network-timeout 300000

Though I faced the same problem (always occured ESOCKETTIMEDOUT for date-fns), this worked for me.

[jamiehd]

@jamiehd
Maybe because CPUs of dockerhub are too weak. Try to increase network-timeout of yarn.

# 300sec
yarn config set network-timeout 300000

Though I faced the same problem (always occured ESOCKETTIMEDOUT for date-fns), this worked for me.

Thanks for the tip @yuki-takei I'll give that a go.

[saobei]

@jamiehd
Maybe because CPUs of dockerhub are too weak. Try to increase network-timeout of yarn.

# 300sec
yarn config set network-timeout 300000

Though I faced the same problem (always occured ESOCKETTIMEDOUT for date-fns), this worked for me.

solve this problem

[durvalprintes]

Thx, problem solved!