never mind - found it

still it's all but a smooth ride

Anyone know how to enable the api (and swagger) via docker compose?

@Peer @zomars I'm hitting a little snag, hopefully it's simple to clear up for me. Is there a server-side fetch happening for auth? I'm setting my webapp_url to http://docker.localhost:3000 My browser can access that URL, but the service itself will not be able to resolve that network address. If I just use http://localhost:3000, it works fine, as my machine's localhost:3000 and the container's localhost:3000 both resolve to the same socket/server. I'm getting this error: calcom-docker-calcom-1 | @calcom/webstart stack: 'FetchError: request to http://docker.localhost:3000/api/auth/session failed, reason: getaddrinfo ENOTFOUND docker.localhost\n' which looks like a server-side request I could likely change NEXTAUTH_URL, but it looks like it's forced to match WEBAPP_URL here: (and I'm not yet certain which other issues having those be different might cause) https://github.com/calcom/cal.com/blob/ce41397517f04674f83fde43739be91a61b5df40/apps/web/next.config.js#L29-L31

Dears I need some support. When our DevOps engineer tried to deploy Cal to the AWS environment using docker-compose, he got an error “* Status: network stack not found, Code: 1" - do you know if someone encountered this error before?

Hello all, what will be the endpoint of api if I am using docker?

Hello All, I'm trying to deploy calcom behind an nginx reverse proxy. I get the following error when trying to add the Google Calendar integration:

Error 400: redirect_uri_mismatch

redirect_uri=http://<redacted>/api/integrations/googlecalendar/callback

Note the http instead of https in the URI What I see from sniffing the traffic is that as soon the broswer calls

GET /api/auth/session

it receives a

Set-Cookie

response header with the correct value of

next-auth.callback-url=https://<redacted>

. But when I go to add the calendar integration and the browser calls

POST /api/auth/callback/credentials?

the app answers with an incorrect value

Set-Cookie: next-auth.callback-url=http://<redacted>

. Any ideas or suggestions on how to get it working? Thanks

For those joining, this was resolved, here's the discussin: https://github.com/calcom/docker/discussions/168

I have successfully installed using docker and local postgres database, there are couple of issues which i am unable to resolve. 1. The url i provides was without https (http://domain.com:3000), when i access Outlook 365 calendar it says it requires https or should be http://localhost. Tried both localhost and adding https (which broke the site) 2. How do i change these values without going through the entire rebuild? Just changing the env file and composer up command would work? Most cases its not rebuilding it properly.

do we wanna add scarf.sh?

whats the benefit of adding https://scarf.sh @Avi Press

Anyone knows how to deal with this problem? Looks like the build process cannot access the database, even though it’s running. I know the DB is running, because I’ve got it in a different terminal and when I port-map it, I can connect to it from host. But for some reason

DOCKER_BUILDKIT=0 docker compose build calcom

still tells me it can’t connect 🤔

Hi, What's the use of

NEXT_PUBLIC_LICENSE_CONSENT

environment key? We are using the self hosted version of cal.com

@channel Hi, I am having trouble when executing the command

DOCKER_BUILDKIT=0 docker-compose build calcom

It starts building with the dockerfile but when it is on step 15/28 then this error ṕops up

network stack not found

ERROR: Service 'calcom' failed to build : Build failed

Hey @Colin - Krumware My docker container running cal.com is getting killed my the host machine. Any help?

I'm not certain. Do you have a scanning or security tool in place that could be killing processes in the container?

I decided to wonder back in here. Perhaps we can discuss ways to make this go?

Are doing something similar for our repo? cc @Colin - Krumware https://turbo.build/repo/docs/handbook/deploying-with-docker

we are, it looks like the --docker flag is new though

I'll go through and compare, thanks for the note!

something breaks that version at the yarn install step

not a helpful error ugh

Getting this error.

DOCKER_BUILDKIT=0 docker compose build calcom Any help?

Need to update your submodule, there was a fix in the core project to address that in the past couple of days

there was a package resolution issue in the embed-* projects which was causing a version mismatch. it could still surface I suppose, but I know that was breaking in the build

(sorry, forgot to hit send, meant to provide that as more context)

I'm not sure why there is a public open invite to work on this docker sub project.