https://cal.com logo
Join Slack
Powered by
# docker
  • d
    Hello, my meetings seem to have a hard-coded localhost:3000 URL in the meeting details which create a problem when clicking the preview. My .env variables BASE_URL and NEXT_PUBLIC_APP_URL are not set to localhost:3000 so I'm wondering where that's coming from. Also, how in the world do I get the Accept our license thing on the bottom. I've set NEXT_PUBLIC_LICENSE_CONSENT="agree" yet it makes no difference
    p
    c
    e
    • 4
    • 18
  • 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
    z
    c
    • 4
    • 37
  • c
    side note, small appearance of calcom in here https://blog.krum.io/replacing-docker-desktop-with-rancher-desktop/
    ❤️ 1
    p
    • 2
    • 2
  • v
    Hello, do you know when can we except the helm branch to be merged ? https://github.com/calcom/docker/pull/59
    p
    c
    • 3
    • 3
  • m
    Hello I have self hosted cal in my ubuntu. How do I check which version we have so I can plan for update. Anyone can help me with this thanks
    v
    • 2
    • 6
  • s
    Hello everyone, I used calendso on Docker on the Raspberry pi. It was fine and could worked, but rather slow. I have updated the repo with docker-compose pull and again run the docker, now getting the following error. Investigated that, at it seems it's because of CPU architechture.
    p
    • 2
    • 1
  • p
    hey @Colin - Krumware can you help @zomars and move docker into the mono repo? we want to offer official support to it
    ❤️ 1
    👀 1
    👍 2
    j
    • 2
    • 1
  • c
    hey Peer, sorry, been out sick today
  • c
    @zomars do you want to find a time to chat about that?
  • c
    @Philip Niedertscheider I'm getting error messages when running the latest. just wondering if you're getting the same
  • c
    Copy code
    [next-auth][error][NO_SECRET] 
docker-calcom-1  | @calcom/web:start: <https://next-auth.js.org/errors#no_secret> Please define a `secret` in production. MissingSecret [MissingSecretError]: Please define a `secret` in production.
docker-calcom-1  | @calcom/web:start:     at assertConfig (/calcom/node_modules/next-auth/core/lib/assert.js:26:14)
docker-calcom-1  | @calcom/web:start:     at NextAuthHandler (/calcom/node_modules/next-auth/core/index.js:34:52)
docker-calcom-1  | @calcom/web:start:     at NextAuthNextHandler (/calcom/node_modules/next-auth/next/index.js:21:51)
docker-calcom-1  | @calcom/web:start:     at /calcom/node_modules/next-auth/next/index.js:57:38
docker-calcom-1  | @calcom/web:start:     at Object.apiResolver (/calcom/node_modules/next/dist/server/api-utils/node.js:184:15)
docker-calcom-1  | @calcom/web:start:     at runMicrotasks (<anonymous>)
docker-calcom-1  | @calcom/web:start:     at processTicksAndRejections (internal/process/task_queues.js:95:5)
docker-calcom-1  | @calcom/web:start:     at async NextNodeServer.runApi (/calcom/node_modules/next/dist/server/next-server.js:395:9)
docker-calcom-1  | @calcom/web:start:     at async Object.fn (/calcom/node_modules/next/dist/server/base-server.js:477:37)
docker-calcom-1  | @calcom/web:start:     at async Router.execute (/calcom/node_modules/next/dist/server/router.js:243:32) {
docker-calcom-1  | @calcom/web:start:   code: 'NO_SECRET'
docker-calcom-1  | @calcom/web:start: }
  • c
    nvm, obvious missing env variable is obvious
    🙏 2
  • j
    hi guys, just checking out cal and tried the deploy on heroku button as quick test. It built but application crashes when I try using it. Is the heroku button still supported?
  • c
    @Jimmy Chan I'm not sure that's related to docker, but maybe your issue is like this one? https://github.com/calcom/cal.com/issues/2389
  • c
    it also could be crashing due to missing env variables. if heroku gives you any log output, that would be great to see
  • j
    Copy code
    @calcom/prisma:db-deploy: error Command failed with exit code 1.
2022-05-03T20:35:27.655376+00:00 app[web.1]: @calcom/prisma:db-deploy: Error: command finished with error: command (packages/prisma) yarn run db-deploy exited
  • j
    this seems the most relevant. I checked config vars: BASE_URL CALENDSO_ENCRYPTION_KEY DATABASE_URL NEXTAUTH_SECRET these were all set. is there any more needed?
  • d
    If prisma deploy is failing, it could be the DATABASE_URL format. for running the app, I'm not sure if relevant but I have found that the V1.5 release also requires NEXT_PUBLIC_WEBAPP_URL. Also maybe JWT_SECRET.
  • d
    If your postgres password/cred contain special characters, make sure they are URL-encoded as well.
  • z
    BASE_URL is deprecated BTW
  • j
    i removed 
    BASE_URL
    and added 
    NEXT_PUBLIC_WEBAPP_URL
    still has the same issue. I couldnt change the postgres db url since its set by heroku for their attached postgres
  • j
    where in the docs do they mention 
    JWT_SECRET
    👍 1
  • d
    It's not really in the "docs" per-se, but in the latest V1.5 release, in the .env.example file: https://github.com/calcom/cal.com/blob/V1.5/.env.example#L53
  • d
    That is most likely not your issue though if it's failing on the prisma/db step.
  • n
    Hi, I’m trying to deploy cal using docker but without using docker compose… does anyone success doing this?
  • j
    for me I removed any prisma build, deploy, or migrate stuff from turbo dependencies and package scripts as I do that manually first.
  • c
    I'm working on instructions for bypassing that in the meantime
  • c
    now I need to fix the tailwind portion as well
  • c
    Is anyone around to test the latest calendso/calendso:latest docker image? We're back to stable, but welcome additional eyes!
    ❤️ 1
    a
    • 2
    • 1
  • c
    @zomars this is an interesting issue that might be able to use some eyes. https://github.com/calcom/docker/issues/126 I'm not sure as far as which apps should be available in the self-hosted version. Also not sure if the google token is required at build time now instead of runtime, with the database configuration changes.
    a
    • 2
    • 9
12345...10Latest