Tarball data seems corrupted

Running docker-compose up as stated on this guide shows a warning. I’m not sure if it is because of the slow internet connection.

Building server
Step 1/17 : FROM node:10 as frontend-builder
 ---> e05cbde47b8f
Step 2/17 : WORKDIR /frontend
 ---> Using cache
 ---> 75f414b9c9f1
Step 3/17 : COPY package.json package-lock.json /frontend/
 ---> Using cache
 ---> 7f67374c1f5d
Step 4/17 : RUN npm install
 ---> Running in a2b5e533a70e
npm WARN tarball tarball data for webpack-dev-server@3.2.1 (sha512-sjuE4mnmx6JOh9kvSbPYw3u/6uxCLHNWfhWaIPwcXWsvWOPN+nc5baq4i9jui3oOBRXGonK9+OI0jVkaz6/rCw==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for qs@6.7.0 (sha512-VCdBRNFTX1fyE7Nb6FYoURo/SPe62QCaAyzJvUjwRaIsc+NePBEniHlvxFmmX56+HZphIGtV0XeCirBtpDrTyQ==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for jquery-ui@1.12.1 (sha1-vLQEXI3QU5wTS8FIjN0+dop6nlE=) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for less@3.9.0 (sha512-31CmtPEZraNUtuUREYjSqRkeETFdyEHSEPAGq4erDlUXtda7pzNmctdljdIagSb589d/qXGWiiP31R5JVf+v0w==) seems to be corrupted. Trying one more time.
...
...

Oh. The problem there seems to be something going wrong when it’s downloading the tarballs from NPM.

Hopefully that was just a temporary thing (!).

Haven’t you gotten this working, since then? :smile: