Closed sayzlim closed 1 month ago
It might be related to this, https://github.com/prisma/prisma/issues/25020
Can you try rolling back your Prisma version to 5.17?
It looks like you also need to pin the Prisma version to 5.17 in the docker file
RUN set -x \
&& apk add --no-cache curl \
&& yarn add npm-run-all dotenv semver prisma@5.17.0
When I check the Prisma version in the yarn.lock file, it shows that the version is already 5.14. Do I need to upgrade the version or keep 5.14?
prisma@5.14.0:
version "5.14.0"
resolved "https://registry.yarnpkg.com/prisma/-/prisma-5.14.0.tgz#ffc4696a43b044b636c3303b7aa98c13c2ade4dd"
integrity sha512-gCNZco7y5XtjrnQYeDJTiVZmT/ncqCr5RY1/Cf8X2wgLRmyh9ayPAGBNziI4qEE4S6SxCH5omQLVo9lmURaJ/Q==
dependencies:
"@prisma/engines" "5.14.0"
Thank you, @mikecao! I followed your instructions and updated the Dockerfile, and I’m pleased to report that the deployment is now successful.
Describe the Bug
I recently rebased my local commits onto the latest changes from the master repository, but the migration is incomplete due to the following errors in the logs. I'm still struggling to resolve the permission issues with Prisma. Do you have any suggestions on how to address this error?
Database
PostgreSQL
Relevant log output
No response
Which Umami version are you using? (if relevant)
No response
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
Railway