Latest tag unexpectedly changed architecture to ARM64 instead of AMD64

[zvanelslande]

Issue Summary

Pulling the latest container image from dockerhub gave issues due to missing amd64 architecture. I noticed that the current architecture for the latest tag is arm64.

Steps to Reproduce

1. on an amd64 system, pull the latest container tag for cal.com

Actual Results

• There is no image found for the amd64 architecture

Evidence

Trying to pull docker.io/calcom/cal.com:latest...
Error: unable to copy from source docker://calcom/cal.com:latest: choosing an image from manifest list docker://calcom/cal.com:latest: no image found in image index for architecture "amd64", variant "", OS "linux"

[linear[bot]]

CAL-6758

[ljrobins]

Same issue here, noticed it a few days ago.

[tigerblue77]

Yes of course it's an URGENT issue... WTF is this application with 950 issues and 348 PR and then breaking latest tag... @zvanelslande thanks for opening !

[mo1297mo]

same issue here. today

[draylegend]

Is there a service that doesn't brake, even when I pay?

[jkoopmann]

Guys this is urgent due to https://github.com/calcom/cal.com/discussions/25598

[asm0dey]

What I did for now - built an image on my machine myself from the master and pushed it to the server via docker pussh. Which is indeed stupid and dangerous, but better than having an open CVE

[tigerblue77]

@asm0dey LMAO but why...

1. Your comment is not linked to current issue
2. You can use the v9.5.11 tag to get the image for amd64 architecture

But of course the current issue is still valid and need to be fixed as the latest tag should be amd64

[asm0dey]

Ah, it's good to know that at least there are versioned images!

[keithwillcode]

Apologies for the confusion. We recently brought the calcom/docker repository into the main mono repo and as part of that, ARM support was added. When new releases are shipped, a version of each is sent out. Will make sure we get a fix to this soon.

[tigerblue77]

THANK YOU @keithwillcode ! 🚀

I really don't mean to be rude but... Any plan to drastically reduce the +900 issues ?

[keithwillcode]

Absolutely. We've been knocking this down quite a bit as of late. Many times there are lots of duplicates. But indeed we want to have fewer issues altogether.

As a reference, Next.js itself has over 2000+ issues. While the number can be scary, it doesn't tell the full story. If you have specific, high priority issues you'd like to see fixed ASAP, send them my way and we'll get them lined up soon.

[jkoopmann]

If you have specific, high priority issues you'd like to see fixed ASAP, send them my way and we'll get them lined up soon.

Issue 20358 comes to mind. :-) Now that you ask. It is incredibly annoying and should be easy to fix. I was going for it today with Claude support but during reproduction discovered that my cal.com instance was hacked because the auto-update with :latest failed due to this bug.....

[keithwillcode]

If you have specific, high priority issues you'd like to see fixed ASAP, send them my way and we'll get them lined up soon.

Issue 20358 comes to mind. :-) Now that you ask. It is incredibly annoying and should be easy to fix. I was going for it today with Claude support but during reproduction discovered that my cal.com instance was hacked because the auto-update with :latest failed due to this bug.....

Sure thing. We’ll look into it

[keithwillcode]

I just bumped #20358 to high priority and @volnei is looking

[jkoopmann]

... I would have expected this to be a very small issue and it would help tremendously with automatic updating which given all CVEs seems necessary! @volnei any chance?

[volnei]

hey @jkoopmann our latest docker image is completelly free of known CVEs and we have ARM and ARM64. Can you check it please?

docker pull calcom/cal.com:latest
latest: Pulling from calcom/cal.com
7f2b9668af76: Already exists 
a0da1fc24a51: Already exists 
62a266a3916e: Already exists 
79bcc4522f03: Already exists 
d33cbb514836: Already exists 
74e20ab7c205: Already exists 
3e117f67a017: Already exists 
aa9de81871f8: Already exists 
42740c475aae: Pull complete 
62572a0069fd: Pull complete 
d23711264aa9: Pull complete 
Digest: sha256:9085ab60f2f51831a5ee2c36b33d3c7a8d90b7e5067adeb6d44d1ef4768859f5
Status: Downloaded newer image for calcom/cal.com:latest
docker.io/calcom/cal.com:latest


docker image ls
REPOSITORY         TAG         IMAGE ID       CREATED        SIZE
calcom/cal.com     latest      c6accc8cdfc1   5 hours ago    6.01GB

[asm0dey]

@volnei there is still no latest for amd64

[dasrecht]

I went the way and disregarded latest and started using the last tagged version. Not the best way but at least something that works.

[volnei]

@dasrecht @asm0dey @jkoopmann I'm on it... would be quick.. I'll ping you all here

[tigerblue77]

@asm0dey it might be because of https://github.com/calcom/cal.com/issues/25880 Issues there getting out of control 😂 not sure if we should laugh or cry

[volnei]

@asm0dey it might be because of #25880 Issues there getting out of control 😂 not sure if we should laugh or cry

Yep, it’s related to that one 🙂 no need to cry, I’m here. ❤️

[asm0dey]

@tigerblue77 of course it is, this is why I created that one :)

[tigerblue77]

@asm0dey haha sorry didn't see you were the requester

[volnei]

hey everyone... docker image published to amd64 as default latest tag.

docker pull calcom/cal.com:latest

arm still available using

docker pull calcom/cal.com:v6.0.2-arm

@dasrecht @asm0dey @jkoopmann @tigerblue77 let me know if you have any issues

[tigerblue77]

Good morning gentlemen, I just upgraded from v5.9.14 to latest, which is v6.0.2 I guess but not sure since they don't have the same digest :

which is strange and shouldn't be the case (new issue I guess, there should be only 2 build : arm64 being tagged once & amd64 being tagged twice).

Aside from that :

• upgrade went well, I'm up and running in amd64 architecture, all good from my side
• v5.9.15 is still absent from Docker Hub.

[asm0dey]

Seems to be working for me, thank you!

[jkoopmann]

Latest seems to have pushed it to 6.0.2. Thanks.