Following most basic steps for default scenario yielded a migration issue

[rrufus]

Hello. I am completely new to calcom and decided to try self hosting a version on my mac just to check it out.

I followed the steps on https://github.com/calcom/docker?tab=readme-ov-file#most-users-running-calcom-with-docker-compose and did not change any environment variables after copying .env.example to .env as I could see that each required variable had a default value set.

After running docker compose up -d and waiting for it to finish, I opened calcom on localhost:3000 which redirected me to http://localhost:3000/auth/login, which did not load. When I looked at the console I saw Object { name: "Internal Server Error.", message: "500 - Internal Server Error.", statusCode: 500 }.

I ran docker ps and saw I had three containers running – "database", "docker-calcom-1", and "docker-studio-1". Running docker logs yielded

The table public.users does not exist in the current database. on docker-calcom-1

and ongoing rolling errors on database, eg 2024-10-29 03:42:55.693 UTC [71] ERROR: relation "public.users" does not exist at character 57 2024-10-29 03:42:55.693 UTC [71] STATEMENT: SELECT COUNT(*) FROM (SELECT "public"."users"."id" FROM "public"."users" WHERE 1=1 OFFSET $1) AS "sub"

I noticed that a new version of this repo was released just 6 hours ago, see https://github.com/calcom/docker/releases/tag/v4.6.13 and https://hub.docker.com/r/calcom/cal.com/tags – and when I run docker images I can see that the one I have in my local registry is tagged as latest, and was created 6 hours ago.

I wonder if some migration bug was introduced in this version or whether I have made a mistake?

I can also see that currently the "main" tag is not the same as the "latest" tag – would it make any difference to use the "main" tag for the image in the docker-compose.yml by default?