a month ago
I receive this often and it is extremely uncomfortable. I have to retry practically all deployments due to this error. This has been happening since I became a client of yours, but sometimes you reach your limit with this issue. I can't just deploy changes and that's it. I always have to be waiting for the build to work, and it's stressful.
LOG:
[stage-0 6/10] RUN --mount=type=cache,id=s/2aee70ac-27dc-491e-807d-c83dafa70b58-/usr/local/share/cache/yarn/v6,target=/usr/local/share/.cache/yarn/v6 yarn install --frozen-lockfile
"yarn install --frozen-lockfile" did not complete successfully: exit code: 1
View in context
yarn install v1.22.22
warning package.json: "dependencies" has dependency "postcss" with range "8.4.30" that collides with a dependency in "devDependencies" of the same name with version "^8"
warning package.json: "dependencies" has dependency "typescript" with range "5.2.2" that collides with a dependency in "devDependencies" of the same name with version "^5"
warning pedicita-frontend@0.1.0: "dependencies" has dependency "postcss" with range "8.4.30" that collides with a dependency in "devDependencies" of the same name with version "^8"
warning pedicita-frontend@0.1.0: "dependencies" has dependency "typescript" with range "5.2.2" that collides with a dependency in "devDependencies" of the same name with version "^5"
[1/4] Resolving packages...
[2/4] Fetching packages...
error https://registry.yarnpkg.com/@heroui/popover/-/popover-2.3.17.tgz: Extracting tar content of undefined failed, the file appears to be corrupt: "ENOENT: no such file or directory, chmod '/usr/local/share/.cache/yarn/v6/npm-@heroui-popover-2.3.17-195b6a7c92c38721ca2077ed679d562fc9fe670e-integrity/node_modules/@heroui/popover/dist/use-aria-popover.js'"
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error ENOENT: no such file or directory, open '/usr/local/share/.cache/yarn/v6/npm-is-extglob-2.1.1-a88c02535791f02ed37c76a1b9ea9773c833f8c2-integrity/node_modules/is-extglob/.yarn-metadata.json'
2 Replies
6 days ago
It is the cache having issues
Try remove any caching if it is there in your docker
6 days ago
For quick sol try in service in Railway dashboard clear build cache and redeploy OR clean cache before install RUN yarn cache clean in docker file
For long term fix add ENV YARN_CACHE_FOLDER=/tmp/yarn-cache to docker file