Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error Deploying with prisma #125

Closed
s-kris opened this issue Mar 11, 2021 · 11 comments
Closed

Error Deploying with prisma #125

s-kris opened this issue Mar 11, 2021 · 11 comments
Labels
priority: medium rewrite candidate type: bug code to address defects in shipped code

Comments

@s-kris
Copy link

s-kris commented Mar 11, 2021

Describe the bug
Prisma query engine not found when deployed with target:serverless.

Build fails when using target: experimental-serverless-trace.

Tried both ui installation and manual installation.
Looking forward to deploy my next js + prisma app to netlify. Thank you.

More info:
prisma/prisma#6051

Versions

  • Next.js: 10.0.8
  • plugin (if installed at fixed version):

If you're using the CLI to build

  • OS: [e.g. macOS, Windows]
  • netlify/cli version:

If you're using file-based installation

  • netlify.toml:
@jlengstorf
Copy link

thanks for this, @s-kris! do you have a repo and/or build log we can look at? it will make chasing this down much faster

thank you!

@s-kris
Copy link
Author

s-kris commented Mar 12, 2021

Sorry. I forgot to include the error for target:serverless.

Query engine binary for current platform "rhel-openssl-1.0.x" could not be found. This probably happens, because you built Prisma Client on a different platform. (Prisma Client looked in "/query-engine-rhel-openssl-1.0.x") Searched Locations: /.prisma/client /opt/build/repo/node_modules/@prisma/client / /var/task/node_modules/.prisma/client /var/task /var/task/node_modules/.prisma/client You already added the platforms "native", "rhel-openssl-1.0.x", "darwin" to the "generator" block in the "schema.prisma" file as described in https://pris.ly/d/client-generator, but something went wrong. That's suboptimal. Please create an issue at https://github.com/prisma/prisma-client-js/issues/new

I opened this issue on prisma as well.

I will create minimal repo tomorrow and share it :)

@jlengstorf
Copy link

thank you!

@s-kris
Copy link
Author

s-kris commented Mar 13, 2021

Hi @jlengstorf
Please find the minimal repo here: https://github.com/s-kris/test-prisma-netlify
You need to visit /api/prisma-test to see the error response.
Thank you for your patience. :)

@s-kris
Copy link
Author

s-kris commented Mar 14, 2021

Looks like this has something to do with prisma

prisma/prisma#6032

@jlengstorf
Copy link

thanks for following up with this @s-kris! we'll keep an eye on that Prisma issue

@lindsaylevine lindsaylevine added priority: medium type: bug code to address defects in shipped code labels Mar 19, 2021
@s-kris
Copy link
Author

s-kris commented Mar 24, 2021

update:
The same repo works perfectly when deployed to vercel.

prisma/prisma#6051 (comment)

@jlengstorf
Copy link

this should be fixed as of Prisma 2.20.0! prisma/prisma#6051 (comment)

we confirmed it working, so I'll close this, but please let us know if you see it again!

@s-kris
Copy link
Author

s-kris commented Apr 1, 2021

Hey @jlengstorf the original error wasn't fixed. Here's the deployed url: https://60638a6d69433d000751b036--cocky-babbage-06fac3.netlify.app/api/prisma-test

Also, it says in he comment here: prisma/prisma#6051 (comment) that original error still remains. Can you please share a sample repo if you got this working? It'd be really helpful.

sample repo: https://github.com/s-kris/test-prisma-netlify
branch: p2.20

@jlengstorf jlengstorf reopened this Apr 14, 2021
@tlrjs
Copy link

tlrjs commented Apr 16, 2021

Nice to see this was reopened as I'm also running into this same issue. I can't tell if it's a Prisma issue or Netlify because I deployed the same repo to Vercel without any issues.

@ascorbic
Copy link
Contributor

Thanks for the report. I'm going to close this, because there is a new version of the plugin out which doesn't use experimental-serverless-trace. If you're still having trouble after upgrading, please could you open a new issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: medium rewrite candidate type: bug code to address defects in shipped code
Projects
None yet
Development

No branches or pull requests

5 participants