Building CT3 app with docker - libssl error
When building ct3 app I get an error saying that in
prisma generate
it can't load libssl package. I've done it before like a milion times in 2022 and it worked. I haven't changed anything in dockerFile since and it is just copied from the docs.
Error:
16 Replies
On localhost it builds and generates prisma model alright
there was an issue related to prisma/libssl in the new version of alpine
we updated the docs recently
should work again if you follow that
also make sure you're on the newest prisma version
Yeah, I see that and I updated dockerfile and I get
I though that it was cache issue but with
--no-cache
flag i get the same error
Do you know why that might be an issue?the issue was on prisma itself
changing their ssl dependency and breaking a lot of stuff
not only on docker
So what can I do about that?
The error I get is connected with the
openssl1.1-compat
package that docker just can't findinstall an older version of the openssl
compatible with prisma
GitHub
fix(doc): dockerFile builds fail as openssl1.1-compat doesn't exist...
Closes #
✅ Checklist
I have followed every step in the contributing guide (updated 2022-10-06).
The PR title follows the convention we established conventional-commit
I performed a functional t...
I changed the openssl package to the proper one and it works
There is no
openssl1.1-compat
but there is openssl1.1-compat-dev
😉seems like you're still on alpine 3.16?
see this discussion https://github.com/t3-oss/create-t3-app/issues/975
GitHub
bug: docs - Docker node:16-alpine requires setting `engineType = "b...
Provide environment information System: OS: Linux 6.0 Fedora Linux 37 (Workstation Edition) CPU: (16) x64 AMD Ryzen 7 PRO 6850U with Radeon Graphics Memory: 23.97 GB / 30.12 GB Container: Yes Shell...
different alpine versions come with different openssl stuff
its kind of a mess
Yeah, it's like that in docs
You're right for 3.17 it just works 🙂
oh then docs are wrong i think?
3.16 should use regular openssl if i understand the issue correctly
i dont use ct3a in docker tbh so my knowledge is just github discussion
Ok, then we need to update the version instead of package name
Changed it in the PR
And also I checked if it works
Still building but the part that was messing things up is alright
It works