`EROFS: read-only file system, chmod '/var/task/generated/prisma-client/runtime/query-engine-rhel-openssl-1.0.x'`

I followed the setup in https://github.com/prisma/prisma2-e2e-tests/tree/master/platforms/netlify (clone, remove .netlify/state.json, yarn install, yarn prisma2 generate, execute commands from build.sh manually (zip does not exist and has to be done manually), get deployed site and function!).

When then calling the function, I get:

{"errorType":"Error","errorMessage":"\nInvalid `prisma.()` invocation in\n/var/task/generated/prisma-client/index.js:323:37\n\n\n\nEROFS: read-only file system, chmod '/var/task/generated/prisma-client/runtime/query-engine-rhel-openssl-1.0.x'","trace":["Error: ","Invalid `prisma.()` invocation in","/var/task/generated/prisma-client/index.js:323:37","","","","EROFS: read-only file system, chmod '/var/task/generated/prisma-client/runtime/query-engine-rhel-openssl-1.0.x'","    at PrismaClientFetcher.request (/var/task/generated/prisma-client/index.js:60:27)"]}

https://goofy-tereshkova-4bf91a.netlify.com/.netlify/functions/index

Theory: Because the the generated client was created on Windows, it is missing the necessary file permission flags.

(index.zip that was uploaded: index.zip)

[divyenduz]

In my understanding, this issue happens when the build machine is an OS without binary flags (like windows) and the deployment machine is a machine with binary flags.

If you specify a binary provider in your Prisma schema file to download the binary for target platform OS, like in the case of netlify:

binaryTargets = ["native", "rhel-openssl-1.0.x"]

The binary download happens with prisma2 generate on the build OS (windows). But the downloaded binary doesn’t have any executable flag as it is on windows.

When this binary is deployed a Prisma client attempts to run it, it fails. Most likely on this line. This would usually just work but on lambda it doesn’t work because this part of the filesystem is not writeable.

---

Next steps: We need to validate the above hypothesis and solve this in some way (already have +x flag on binaries in S3 or downloading the files in /tmp (writeable for lambda) adding the +x flag and copying the binary or something else)

[abelchee]

Copy to tmp folder works for me.

const binaryPath = '/tmp/query-engine-rhel-openssl-1.0.x';
if (!fs.existsSync(binaryPath)) {
  const { spawnSync } = require('child_process');

  spawnSync('cp', [
    `${process.env.LAMBDA_TASK_ROOT}/node_modules/.prisma/client/query-engine-rhel-openssl-1.0.x`,
    '/tmp/',
  ]);

  spawnSync('chmod', [`555`, '/tmp/query-engine-rhel-openssl-1.0.x']);
}

And need an env:

  PRISMA_QUERY_ENGINE_BINARY: /tmp/query-engine-rhel-openssl-1.0.x