anyone with a bit more experience with Docker, here @Sascha Foerster is experiencing a database reset when it comes to enabled apps when upgrading to a new release following these steps to upgrade, any clues?

cd /home/calcom-docker
git pull
git submodule update --remote --init
docker compose pull
DOCKER_BUILDKIT=0 docker compose build calcom
docker compose up -d

Oh, it’s only happening with the activation and deactivation of apps in the admin backend. All other settings are fine. Just for clarification. :)

So, app status get reseted after upgrading. I’m pretty sure that comes from the app seeder, maybe it runs and reestablishes its status to some kind of default status

That sounds like what is happening.

That's interesting, is there something that can be checked in the migration scripting? This sounds like it probably isn't limited to the docker deployments

Version 2.6 tagged and pushed 🎉

Version 2.6.1 is tagged and published 🎉

Hi, hope you guys are fine ! Tried Cal today with self hosted with docker and I have some questions 🙂 I can't use workflows and API keys both give me that

But I don't find in the documentation if it's a self hosted restriction or just a bug

same for Stripe I got error but saw on github discution that is on progress since last week

all this keys are completed for information and I redeployed 30min ago on the latest

Hey Val. When you see that enterprise feature notice is because is a feature you can enable having a license key. As an admin you can go to that suggested URL and follow the steps

Do you have an exhaustive list of feature that I can't use without license? Because I found anything apart https://github.com/calcom/cal.com/tree/main/packages/features/ee But I don't understand SSO, SAML, OIDC, SCIM, SIEM it's not really understanble for me ahah

🎉 v2.6.2 tagged and pushed

Hey @Colin - Krumware @Peer - Can we have v2.6.3 and the updated version tag as well please? I've just tried pulling and still shows v2.6.0 which is concerning. I have no clue what version I'm running, and a bunch of users are having some serious issues with date availability including dates being bookable when they shouldn't, overrides not actually working and "Could not book the meeting. No available users found."...

v2.6.5 tagged and pushed

v2.6.6 tagged and building

How can we help you automating this? @Colin - Krumware

Hey. Is there any fix for

network mode "stack" not supported by buildkit - you can define a custom network for your builder using the network driver-opt in buildx create

when doing

docker compose build calcom

? I've tried the

DOCKER_BUILDKIT=0 docker compose build calcom

workaround but it only resulted in the build failing at:

Step 13/33 : RUN yarn global add turbo &&     yarn config set network-timeout 1000000000 -g &&     turbo prune --scope=@calcom/web --docker &&     yarn install
 ---> Running in 4488a2de3d12
1 error occurred:
        * Status: network stack not found, Code: 1

🎉 v2.6.8 on its way

@Colin - Krumware Not sure how this affects things: https://blog.alexellis.io/docker-is-deleting-open-source-images/

We've already also been pushing to ghcr as a backup, but I'm monitoring for this and other projects regarding the base images. I don't expect that the NodeJS foundation will drop their account, but we can move the images elsewhere or switch to different base images if need be

@Peer you might also be interested in this story if you haven't caught wind of it yet

damn.. why docker doing this?! D

to be honest, docker hub has been nothing but pain in my opinion

didnt get an email, I think because we are already on a verified publisher plan

@zomars re: 2.7.0

Step 13/33 : RUN yarn global add turbo &&     yarn config set network-timeout 1000000000 -g &&     turbo prune --scope=@calcom/web --docker &&     yarn install
 ---> Running in 6c55dd5001d0
yarn global v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Installed "turbo@1.8.3" with binaries:
      - turbo
Done in 8.16s.
yarn config v1.22.19
success Set "network-timeout" to "1000000000".
Done in 0.03s.
 ERROR  could not determine if yarn is using `nodeLinker: node-modules`: .yarnrc.yml: open /calcom/.yarnrc.yml: no such file or directory
Turbo error: could not determine if yarn is using `nodeLinker: node-modules`: .yarnrc.yml: open /calcom/.yarnrc.yml: no such file or directory
1 error occurred:
        * Status: The command '/bin/sh -c yarn global add turbo &&     yarn config set network-timeout 1000000000 -g &&     turbo prune --scope=@calcom/web --docker &&     yarn install' returned a non-zero code: 1, Code: 1

I think I saw some guidance in a comment about a potential need for an updated yarn version?

yea looks like I need to include .yarnrc.yml and update yarn version