-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Umami fails to start due to Prisma being unable to locate OpenSSL after Docker image build #3107
Comments
If I make the following changes, it works: # Dockerfile
- && apk add --no-cache curl \
+ && apk add --no-cache curl openssl \ # db/postgresql/schema.prisma
generator client {
provider = "prisma-client-js"
+ binaryTargets = ["native", "linux-musl-openssl-3.0.x"]
}
|
2.15 images from GHCR are failing for me as well on Rocky Linux 9. |
Same here with Ubuntu 24.04. |
ubuntu22.04 same problem |
I rebuilt the image and pushed it out. Can you try downloading it again? |
Works. Great job, thanks. |
Successfully started! Thank you! |
Hello, I've updated to the latest version and get this error that seems to be related to the initial issue. |
- context: https://github.com/umami-software/umami.git#v2.14.0
+ context: https://github.com/umami-software/umami.git
building from master works for me. is there a forthcoming patch release? |
I'm receiving this same error message with the latest image from the mysql-latest tag. |
d43293d only updated
|
Please fix for mysql |
Should be fixed in v2.15.1. |
Describe the Bug
umami fails to start after building from v2.14.0 with docker.
check-db
fails because prisma cannot find openssl. see logs below for more.# .env UMAMI_DB_USER=umami UMAMI_DB_PASSWORD=password UMAMI_DB_NAME=umami UMAMI_APP_SECRET=vwVXk1Y52GLLJWSC
Related issues:
Database
PostgreSQL
Relevant log output
Which Umami version are you using? (if relevant)
v2.14.0
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
Docker
The text was updated successfully, but these errors were encountered: