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

Railway deploy fails #1704

Closed
d3ward opened this issue Dec 13, 2022 · 5 comments
Closed

Railway deploy fails #1704

d3ward opened this issue Dec 13, 2022 · 5 comments

Comments

@d3ward
Copy link

d3ward commented Dec 13, 2022

Hello , need help to understand how to fix that error that is blocking me to deploy umami on Railway
I used the recommended deploy button , but also tried with manual deploy and issue persist

#16 2.074 Database type detected: postgresql
#16 2.094 Copied /app/db/postgresql to /app/prisma
 
#16 2.420 $ prisma generate
 
#16 5.180 Prisma schema loaded from prisma/schema.prisma
 
#16 5.681 Error: Unable to establish a connection to query-engine-node-api library. It seems there is a problem with your OpenSSL installation!
#16 5.681 Details: Unable to require(`/app/node_modules/prisma/libquery_engine-linux-musl.so.node`)
#16 5.681  Error loading shared library libssl.so.1.1: No such file or directory (needed by /app/node_modules/prisma/libquery_engine-linux-musl.so.node)
#16 5.681 [Context: getConfig]
#16 5.681
#16 5.681 Prisma CLI Version : 4.5.0
#16 5.710 error Command failed with exit code 1.
#16 5.710 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
 
#16 5.723 ERROR: "build-db-client" exited with 1.
#16 5.744 error Command failed with exit code 1.
 
#16 5.744 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
#16 5.758 ERROR: "build-db" exited with 1.
#16 5.789 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
#16 5.791 error Command failed with exit code 1.
 
#16 ERROR: executor failed running [/bin/sh -c yarn build-docker]: exit code: 1
-----
> [builder 5/5] RUN yarn build-docker:
-----
executor failed running [/bin/sh -c yarn build-docker]: exit code: 1
@mikecao
Copy link
Collaborator

mikecao commented Dec 13, 2022

It says right there, It seems there is a problem with your OpenSSL installation!. You'll have to contact Railway about it.

@mikecao mikecao closed this as completed Dec 13, 2022
@sparky005
Copy link

sparky005 commented Dec 20, 2022

It says right there, It seems there is a problem with your OpenSSL installation!. You'll have to contact Railway about it.

Ok that's fair, but the docs should not recommend that we use Railway then. The docs prominently feature using Railway to deploy, but that method is currently broken. It's not a great first impression of the product for new users.

@sparky005
Copy link

sparky005 commented Dec 20, 2022

@d3ward @mikecao this is the actual issue and fix: prisma/prisma#16553 (comment)

I added that apk install line to both the builder and the runner in the Dockerfile, though I'm not sure it's actually needed in the runner.

EDIT: looks like someone has opened PR for it as well: #1708

@AidfulAI
Copy link

The RUN apk add --update --no-cache openssl1.1-compat line needs also to be added to the runner. Without, I received an error stating that the connection to the database was not possible:

yarn run v1.22.19
$ npm-run-all check-db update-tracker start-server
$ node scripts/check-db.js
✓ DATABASE_URL is defined.
✗ Unable to connect to the database.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "check-db" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

@d3ward @mikecao this is the actual issue and fix: prisma/prisma#16553 (comment)

I added that apk install line to both the builder and the runner in the Dockerfile, though I'm not sure it's actually needed in the runner.

EDIT: looks like someone has opened PR for it as well: #1708

@gregonarash
Copy link

If someone runs into this issue - Prisma + Alpine version is the problem. Likely just updating Prisma to 4.8.0 will fix it.

#1708

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants