https://cal.com logo
Join Slack
Powered by
morning all! im trying to build the docker contain...
# docker
k
morning all! im trying to build the docker container but its failing at the 
COPY calendso/prisma
beause it cant find prisma. anyone else run into this w the docker container? i am using git recursively from https://hub.docker.com/r/calendso/calendso
p
@zomars i bet the docker needs to be changed to support the new turbo repo change that went live today
z
Definetly
Oh man, so many different cases to support
p
ah no worries 🙏
but this was kinda expected hehe
k
thanks all - @zomars can you let me know when the update is pushed?
@zomars also 
/bin/sh: 1: next: not found
for after the prisma fix
z
You mean my PR? is a work in progress. I not a Docker expert so I need some testing to do first.
k
yes your pr, me neither trying things as well, if i find something that works ill let you know
❤️ 1
p
@Colin - Krumware do you have experience with docker + turbo repo?
c
oh whoa, big changes here
❤️ 1
let me peek
p
yessssir
c
not a big deal, just a change to a subdirectory
❤️ 1
@zomars's stuff is pretty close
p
can you open a PR?
also @zomars and @Colin - Krumware we should merge the docker repo into turbo repo and close the docker repo, thoughts?
k
@Colin - Krumware, @zomars is close (fixes the prisma issue) but now docker cant find next
Copy code
@calcom/web:build: cache miss, executing b2e1e4a3479ffe28
@calcom/web:build: $ next build
@calcom/web:build: /bin/sh: 1: next: not found
c
it's probably bc of package.json, working on it
🙏 1
z
@Peer wouldn't that imply that we officially support Docker now?
k
thank you!
i tried all the SO/github answers, but none were working for me
c
yea i'm not sure we need to rush to do that. Many folks keep deployment definitions outside of the code repos
but honestly, supporting a container build is no big deal
i think it's actually a simpler change to the dockerfile
just a few mins
k
awesome thank you 🙂
(to the package json file i added next, react, react-dom) and that stops throwing the cant find next error, but now its throwing 
Failed to load next.config.js
c
this thing got crazy
haha yea that's what i'm working on right now
there is a new 
packages/
folder at the root directory
k
ok i see your branch, also trying things w the packages
c
going to have to refactor this dockerfile for the new repo but should be able to get a workaround rolling
@Kathryn Remivasan try my latest update. There are a number of scary looking build errors, but the build completes and appears to run just fine
k
Thanks I'll give this a try!
Open in Slack
PreviousNext
Powered by