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 up
fails to build docker container
#877
Comments
Thanks for reporting this! What happened is that in the new node-alpine Docker image, which we started using with Beta release since we upgraded the version of node we use, they by default ship openssl 3, instead of the openssl 1.1 that was shipped with it before. This by itself shouldn't be an issue, but, Prisma doesn't support openssl 3 when running it on alpine, for now! So while waiting for that, we need to use openssl 1.1 Quick fix for you is to add We will make sure to fix this soon and release a Wasp version that has it fixed! |
Related Prisma issue here: prisma/prisma#16553 . |
New release is out, that fixes this! https://github.com/wasp-lang/wasp/releases/tag/v0.7.2 . |
Describe the bug
When following the deployment instructions for railway, the docker container cannot be built because libssl is not found.
To Reproduce
Steps to reproduce the behavior:
railway up
Expected behavior
I expect that the docker container for the service should be able to be built.
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: