morning all im trying to build the docker container but its

Question

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>

Peer · Answer

< zomars> i bet the docker needs to be changed to support the new turbo repo change that went live today

zomars · Answer

Definetly

zomars · Answer

Oh man so many different cases to support

Peer · Answer

ah no worries pray

Peer · Answer

but this was kinda expected hehe

Kathryn Remivasan · Answer

thanks all < zomars> can you let me know when the update is pushed

Kathryn Remivasan · Answer

< zomars> also ` bin sh 1 next not found` for after the prisma fix

zomars · Answer

You mean my PR is a work in progress I not a Docker expert so I need some testing to do first

Kathryn Remivasan · Answer

yes your pr me neither trying things as well if i find something that works ill let you know

Peer · Answer

< Colin Krumware> do you have experience with docker + turbo repo

Colin - Krumware · Answer

oh whoa big changes here

Colin - Krumware · Answer

let me peek

Peer · Answer

yessssir

Colin - Krumware · Answer

not a big deal just a change to a subdirectory

Colin - Krumware · Answer

< zomars> s stuff is pretty close

Peer · Answer

can you open a PR

Peer · Answer

also < zomars> and < Colin Krumware> we should merge the docker repo into turbo repo and close the docker repo thoughts

Kathryn Remivasan · Answer

< Colin Krumware> < zomars> is close fixes the prisma issue but now docker cant find next

Kathryn Remivasan · Answer

``` calcom web build cache miss executing b2e1e4a3479ffe28 calcom web build $ next build calcom web build bin sh 1 next not found```

Colin - Krumware · Answer

it s probably bc of package json working on it

zomars · Answer

< Peer> wouldn t that imply that we officially support Docker now

Kathryn Remivasan · Answer

thank you

Kathryn Remivasan · Answer

i tried all the SO github answers but none were working for me

Colin - Krumware · Answer

yea i m not sure we need to rush to do that Many folks keep deployment definitions outside of the code repos

Colin - Krumware · Answer

but honestly supporting a container build is no big deal

Colin - Krumware · Answer

i think it s actually a simpler change to the dockerfile

Colin - Krumware · Answer

just a few mins

Kathryn Remivasan · Answer

awesome thank you slightly smiling face

Kathryn Remivasan · Answer

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`

Colin - Krumware · Answer

this thing got crazy

Colin - Krumware · Answer

haha yea that s what i m working on right now

Colin - Krumware · Answer

there is a new `packages ` folder at the root directory

Kathryn Remivasan · Answer

ok i see your branch also trying things w the packages

Colin - Krumware · Answer

going to have to refactor this dockerfile for the new repo but should be able to get a workaround rolling

Colin - Krumware · Answer

< 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

Colin - Krumware · Answer

Kathryn Remivasan · Answer

Thanks I ll give this a try