Docker image yet on v5.0.19

[ivancarlosti]

Our latest version on Docker repository is v5.0.19 , please update

[xcellentavi]

Tagging @PeerRich and @zomars, is there a reason why images are not being pushed to docker hub (https://hub.docker.com/r/calcom/cal.com/tags)? The last one occurred about 2 weeks ago.

Thank you!

[ivancarlosti]

Looks like the Docker push action is broken https://github.com/calcom/docker/actions/runs/14121755816

[ivancarlosti]

Still failing... https://github.com/calcom/docker/actions/runs/14152445262

[ivancarlosti]

Still failing... https://github.com/calcom/docker/actions/runs/14186960112

[ivancarlosti]

Failing... https://github.com/calcom/docker/actions/runs/14211291809

[xcellentavi]

@ivancarlosti, I know it's frustrating but at this point I think we just wait for someone to submit a PR otherwise this is not going to help them resolve the issues with the image compiling. I believe it was mentioned in #426 that the dockerfile needs to be edited and hopefully that will be done soon enough.

[PeerRich]

we are insanely bottlenecked on product improvements and have always been clear that the docker image is community maintained.

everyone here is free to open a PR

[xcellentavi]

Thank you @PeerRich and of course we understand priority goes to product improvements and glad to see v5.2 was released recently.

I cannot contribute or open a PR request as I lack programming knowledge or proficiency in TypeScript. According to an AI request, the following "may" explain the issue with the docker builds (but as I cannot verify it, it could be completely wrong):

In v5.0.19, the Dockerfile utilized a single-stage build process. All dependencies, including node_modules, were installed and retained within the same image. This approach ensured that all necessary files were present during both the build and runtime phases.​

In subsequent versions, starting from v5.0.20, a multistage build was adopted. While this method is efficient for reducing image size by separating build and runtime environments, it introduced a critical oversight:​

• Dependencies installed during the build stage were not transferred to the final stage.​

As a result, the final runtime image lacked essential dependencies like node_modules, leading to failures during the build and deployment processes.​

AI suggests either copying node_modules from the builder stage or reinstalling production dependencies in the final stage by editing the dockerfile. Once again, without proper expertise, this may not be the correct approach, but hopefully it could lead someone in the proper direction to troubleshoot the errors occurring with the build and push to Docker Hub.

Tagging @TauqeerAhmad5201 as he expressed an interest in contributing to help with the docker releases in discussion #100 recently.

Once again, thank you to all who can support this project. I appreciate seeing it continue to develop whenever possible.

[nnethery]

@xcellentavi @ivancarlosti Submitted a PR #429. Up to the maintainers now to merge.

[ivancarlosti]

You guys are opening commits to fix it but nobody is approving it, how can we proceed?

[ivancarlosti]

Looks updated! o/

[andrelung]

Can confirm, my site just updated to v5.3.1