Failed build, no way to redeploy?
scottagirs
HOBBYOP

2 years ago

1.320 [3/5] Fetching packages…

32.71 error Error: ENOENT: no such file or directory, scandir '/usr/local/share/.cache/yarn/v6/npm-mdast-util-find-and-replace-1.1.1-b7db1e873f96f66588c321f1363069abf607d1b5-integrity/node_modules/mdast-util-find-and-replace'

32.71 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Dockerfile:20

18 | ENV NIXPACKSPATH /app/nodemodules/.bin:$NIXPACKS_PATH

19 | COPY . /app/.

20 | >>> RUN --mount=type=cache,id=s/6d6d7ed7-e7a8-4764-aec1-55e4a24e3ad3-/usr/local/share/cache/yarn/v6,target=/usr/local/share/.cache/yarn/v6 yarn install --frozen-lockfile

21 |

22 | # build phase

ERROR: failed to solve: process "/bin/bash -ol pipefail -c yarn install --frozen-lockfile" did not complete successfully: exit code: 1

Error: Docker build failed

View Deploy details

ⓘ Deployment information is only viewable by Project members and Railway admins.

Solved

3 Replies

scottagirs
HOBBYOP

2 years ago

Looks like this happens when yarn.lock changes, maybe some caching?


brody
EMPLOYEE

2 years ago

You can disable the cache by setting a service variable NIXPACKS_NO_CACHE to 1

https://nixpacks.com/docs/configuration/environment


Status changed to Solved Railway almost 2 years ago


scottagirs
HOBBYOP

2 years ago

Thanks, Brody—SOLVED. It's weird because I tried this some time ago for a similar (if not the same) issue, and it didn't make a difference, but this time, worked just fine. Thanks again


Loading...