ENOENT: no such file or directory, copyfile

[pchaganti]

pnpm version:

7.29.0

Code to reproduce the issue:

pnpm i

Expected behavior:

Installs all packages

Actual behavior:

Error

Additional information:

There is an earlier commit that says this issue was fixed - #5930

This is still happening with the latest version of 7.29.0. I am running in a container and pnpm install always errors out at some point with the "ENOENT: no such file or directory, copyfile" error.

I have tried to remove the cache folder and node_modules and pnpm store prune and none of them help either.

node ➜ /workspaces/prabhakar/testapp (master) $ pnpm -v
7.29.0

node ➜ /workspaces/prabhakar/testapp (master) $ pnpm i
Scope: all 9 workspace projects
 WARN  GET https://registry.npmjs.org/ajv error (ECONNRESET). Will retry in 10 seconds. 2 retries left.
ui                                       |  WARN  deprecated @aws-amplify/xr@4.0.15
ui                                       |  WARN  deprecated uuid@3.4.0
Downloading registry.npmjs.org/mapbox-gl/1.13.1: 6.84 MB/6.84 MB, done
Downloading registry.npmjs.org/react-icons/4.8.0: 15.7 MB/15.7 MB, done
ui                                       |  WARN  deprecated querystring@0.2.0
Packages: +1094
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Packages are copied from the content-addressable store to the virtual store.
  Content-addressable store is at: /workspaces/prabhakar/.pnpm-store/v3
  Virtual store is at:             node_modules/.pnpm
 ENOENT  ENOENT: no such file or directory, copyfile '/workspaces/prabhakar/.pnpm-store/v3/files/7f/65c6403a23d93fb148e8259b012d6552ab3bff178f4a7d6a9d9cec0f60429fc1899e39b4bca8cc08afc75d9a7c7bfdb13fc372ca63c85eb22b0355eb4d6000' -> '/workspaces/prabhakar/testapp/node_modules/.pnpm/@aws-sdk+types@3.186.0/node_modules/@aws-sdk/_tmp_5505_c93a908b7e3177a2ec502d6603f68311/dist-cjs/logger.js'

pnpm: ENOENT: no such file or directory, copyfile '/workspaces/prabhakar/.pnpm-store/v3/files/7f/65c6403a23d93fb148e8259b012d6552ab3bff178f4a7d6a9d9cec0f60429fc1899e39b4bca8cc08afc75d9a7c7bfdb13fc372ca63c85eb22b0355eb4d6000' -> '/workspaces/prabhakar/testapp/node_modules/.pnpm/@aws-sdk+types@3.186.0/node_modules/@aws-sdk/_tmp_5505_c93a908b7e3177a2ec502d6603f68311/dist-cjs/logger.js'
Progress: resolved 1135, reused 709, downloaded 383, added 99

[ianldgs]

We're also experiencing this. Only it's in CI, which makes it harder to workaround by deleting the store.

What we do is roughly:

try {
  await $`pnpm install --frozen-lockfile`;

  await $`pnpm build`;
  await $`pnpm test`;
  await $`pnpm lint`;
} finally {
  await $`pnpm store prune`;
}

And there might be concurrent builds reading from the same store.

[masterkain]

I started getting this issue when I switched to a node-19 docker image instead of native macos

[SSylvain1989]

Change my docker config to osxfs (Legacy) , i was on VirtioFS solve my problem

[zkochan]

This looks like a duplicate of #5803