Prisma error
I am using opensaas and i want to deploy on fly.io
wasp deploy fly deploy
running the command gets me this error:
Error: failed to fetch an image or build from source: error building: failed to solve: failed to compute cache key: failed to calculate checksum of ref 6c61ec4f-9a90-4c04-bc2d-ef8244bc25ed::umw7sund1x3nfq8q0smrcxylb: "/prisma": not found
What should i do?
2 Replies
Hi @george. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
The error you're encountering seems to be related to the Prisma setup in your Wasp project. It's possible that the Prisma client isn't being correctly initialized or there's an issue with the Prisma version.
Here are a few steps you can try:
1. Ensure you're using the correct Prisma version. There was an issue with Wasp not using the correct Prisma version when using node 16.15.1, but it was fixed by changing how Prisma is installed (source (https://github.com/wasp-lang/wasp/issues/631)).
2. Try running
wasp clean and then wasp start again. This can help resolve issues related to the Prisma client initialization (source (https://discord.com/channels/686873244791210014/1204021576979324949)).
3. Check your schema.prisma file. There was a case where a user resolved a similar issue by modifying the generator client section in schema.prisma (source (https://discord.com/channels/686873244791210014/1204021576979324949)).
4. If you're seeing an error about the DATABASE_URL environment variable not being found, it might be a Prisma error that doesn't actually prevent deployment. Make sure you've set the environment variables correctly on Fly (source (https://github.com/wasp-lang/wasp/issues/1321), source (https://discord.com/channels/686873244791210014/1196865084304150639)).
If none of these steps resolve your issue, it would be helpful to have more information about your setup and the exact steps you're taking before encountering the error.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @george, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?Hm! Other stuff works? ANy other context you can give on that error, the rest of the logs?