Unexpected end of file in Yarn install

Question

I'm facing a problem related to npm/yarn. We have an npm registry hosted in one of our VMs using Verdaccio to publish our private packages. When we install packages other than our own for the first time, they all are routed to registry.npmjs.org through http://localhost:4873 and cached on our VM for further quick access.

The problem is, if I install @amcharts/amcharts4-geodata package (which is around 71 MB of a tar file), I'm getting an error unexpected end of file. If I use verbose flag in npm install, I find that this is because of NodeJS not able to extract the zip file. The error stack is:

Error: http://localhost:4873/@amcharts%2famcharts4-geodata/-/amcharts4-geodata-4.1.16.tgz: unexpected end of file
    at Zlib.zlibOnError [as onerror] (zlib.js:183:17)

Observed and things I have tried:

1. It happens with both yarn and npm.
2. I disabled cache on Verdaccio. However disabling cache will still store the meta data of all third party packages.
3. Changing nodejs version doesn't have any impact.
4. If I create a simple test folder and install the same package there without giving a custom registry, it works.
5. I added a reverse proxy of nginx behind Verdaccio but it didn't fix the problem.

Answer 1

replace yarn install with yarn install || yarn install || yarn install

if you require even more stability, try

RUN for i in 1 2 3 4 5 6; do yarn install && break || sleep 1; done

source: https://github.com/yarnpkg/yarn/issues/7521#issuecomment-564122782

Answer 2

Update to Yarn version 2.x, as this bug was fixed there with no plan to back-port to v1.

Migration guide: https://yarnpkg.com/getting-started/migration

Source: https://github.com/yarnpkg/yarn/issues/7521#issuecomment-753484630