https://cal.com logo
Join Slack
Powered by
Hi Team, I've spent all day trying to get a <Cal.c...
# docker
e
Hi Team, I've spent all day trying to get a Cal.com docker instance up and running without success. The documentation is woeful, and there are at least 3 different guides with different instructions. https://developer.cal.com/self-hosting/docker https://github.com/calcom/docker https://hub.docker.com/r/calcom/cal.com Does any one have either a more detailed guide on how to set this up on a VPS, or can point me in the direction of some documentation that is at least accurate? 😊
p
@Ali can you check why the docs are different and help here?
docker pull calcom/cal.com
is the correct pull btw
just yesterday we switched the namespace from calendso to cal.com
a
Hey @Elliott Apologies for the inconvenience. What issues are you running into?
e
Hey Ali, Peer. Thanks for the updates. I'm relatively new to Docker, but probably doing something wrong. However, I think I understand the underlying concepts... What I find confusing about the various documentation is: 1. There are multiple Git pull locations mentioned 2. git submodule update --remote --init errors out 3. Here mentions Yarn https://hub.docker.com/r/calcom/cal.com, where as here, there's no mention of Yarn https://developer.cal.com/self-hosting/docker - which is correct? 4. What's the sequence of events: a. Do I need to Clone the Docker from Github, or do docker pull calcom/cal.com b. Should I install the dependencies (Yarn, Postgres, NodeJS etc) or does the Docker container handle all of that for me? From what I understood, there wasn't much else needed to get an instance up and running with Docker, because it should: 1. Set up all the dependencies (except Docker & Docker Compose)? 2. Create a local database for me 3. Make a couple of test users But I can't even get as far as running it, which is where having 3 sets of documentation is confusing. Appreciate any and all help 😁🙏🏽
Step 5 - Build the Cal.com docker image: b) If a local or temporary database is required, start a local database via docker compose. "unknown shorthand flag: 'd' in -d" 🤷🏽‍♂️
When you say docker compose, you mean docker-compose... Again, documentation isn't clear enough
Next - Step 6 error: DOCKER_BUILDKIT=0 docker-compose build calcom [+] Building 0.0s (0/0) network mode "stack" not supported by buildkit
Links to this issue: https://github.com/calcom/docker/issues/121 Which isn't mentioned anywhere in the documentation.
So. after reading a bunch of Git issues, I saw that the error sometimes isn't fatal, and the build actually happens. I then moved to step 7 - Starting Cal.com with docker-compose up -d I've defined my NEXT_PUBLIC_WEBAPP_URL in the .env file, but can't access it... It's something like: http://VPSIPADDRESS:3000 Any ideas why it wouldn't be accessible?
message has been deleted
message has been deleted
c
@Elliott what docker runtime are you using?
a lot of the questions you are asking appear to be related to being new to docker, like you mention
I'm happy to help walk you through, I'm sorry I didn't see the thread sooner
e
Thanks so much for the reply, Colin. I'd definitely agree on the level of my questions, so I appreciate your patience and help.
I'll check my docker runtime now
Is this what you need? 😊
c
you can try starting without the -d, and that will attach to the cantainers and "tail" the logs
and hopefully show you if any errors are occurring
you can also look up how to print docker logs and that will help you too. might be good practice, all standard docker stuff here
The connection reset by peer is interesting, that shouldn't be happening
I wonder if postgres 15 is expecting some different config parameters
You could try specifying an older postgres version in the docker compose, like postgres:12
e
Thanks for your help, Colin. I think I've reached my limit in how much time and resource I'm willing to put into getting this up and running. I can see refactored Docker images are being worked on, and will just wait for an improved process to be shared before using more time and resources. Appreciate your help again 🙏🏽
Btw, I'm not trying to do anything special here. I just want to set up a self hosted instance of Cal.com for my team. Am I making things hard for myself here? Is there an easier way to spin it up via Docker?
I'd assumed I needed to build my own image to ensure I could use my own Base URL?
OK, I gave it "one last try" and have the Cal.com instance up using the "minimal to no modifications" path. However, I'd like to understand what the disadvantages are of doing this? What should I be aware of when it comes to making sure the data is secure, since I've read this isn't suitable for "production"? 😁
c
will shoot you a pm
25 Views
Open in Slack
PreviousNext
Powered by