docker compose build calcom fails with "network mode "stack" not supported by buildkit" #121
Comments
|
Those are typically warns and do not fail the build. Is there more log content available? |
|
"network mode "stack" not supported by buildkit. You can define a custom network for your builder using the network driver-opt in buildx create." is terminal and exits the build process But you're right that |
|
"network mode "stack" not supported by buildkit" is a separate issue I'm working around. Can you give the output of the |
|
@krumware here is the complete build output: Could it be due to these sub-modules 404'ing, why is that btw? |
|
I'm sorry y'all are having that error. This is a tough one to unpack remotely. This error has existed in the build for some time, and while it says fatal in the logs, that doesn't necessarily mean that the docker build was fatal. What docker runtime are you using for building the image? (it may just be docker desktop, but there are many available now). Any extra environmental info you can provide to help track this down would be awesome. Here is the same error message in the github actions build where the container build succeeds (the relevant section of the logs): Regarding the 404s, those are private repositories that are not yet available for public consumption. They are not required for the build. You shouldn't notice them unless you followed the old instructions and tried to update the calcom submodule recursively. |
|
With me, I was simply not waiting long enough. It presented the |
I do then end up stuck with #122 but that's a separate issue. |
|
with DOCKER_BUILDKIT=0 I was able to start the build but for me it crashes at Step 12 with this message: |
|
I'm running into the same issues noted by @drwb and @Frank-Wiebeler on a fresh and up to date install of Ubuntu 22.04 server using the latest docker install. |
I have read in #129 that you were able to solve the issue: how did you do that? I am stuck at the network stack not found error :( |
|
related to #134 |
- added numerous environment variable changes such as implied defaults that can be overriden. - skipped out on using git modules and just pull repo into build/launch step. Adherance to license requires no repackaging and this solves this. - cleaned up now unnecessary .env file. - recycled environment section using yaml features. - writing a few strings to config path to persist data between container starts that focus on cryptography and secrets. - writing installed commit to the config path in case the end user needs to change the upstream git commit ID to a newer version for detection and automagic upgrades. - added docker-compose.override.yml pattern to .gitignore to allow users to customize their local dev environment if they use docker-compose.yml - wrote a dockerfile/container image which allows for uploading the base container to a private or public docker container registry without breaking the license rules. - left .env ignore in case users wish to continue to use the old method. - updated README.md to include updated simplified instructions. - added start.sh script and wait-for-it.sh into the shell $PATH to allow for a potential future of allowing the main executable (node JS app) to run under a limited privilege user while still allowing the init scripts to be executed securely. - added some input sanitation for certain critical variables. - by default disabled/commented out the studio service as its not to typically be run to enforce better default deployment practices. I would like to figure out what specific query to execute via the CLI instead of running a whole container to establish the first user in the end. - wrote relatively unopinionated docker-compose.yml file to avoid causing problems for people trying to deploy this behind a reverse proxy for potential features such as TLS/HTTPS termination. - upgraded compose version to latest '3.9' to be sure to enable most modern feature set. Fixes calcom#87 by providing a working baseline with sober defaults. Fixes calcom#88 by ensuring consistency across all containers Environment vars. Fixes calcom#93 by allowing users to mount the application files within their IDE workspace, however, this will never solve for any times you will need to run yarn build steps. Fixes calcom#99 by no longer using git submodules and just pulling a single commit depth copy of the ORIGIN repository on app bootstrap/first boot. Fixes calcom#113 by no longer requiring build locally if the community maintainer of the Cal docker repository on GitHub will push this image to the hub. Fixes calcom#121 by removing dependency on BuildKit this is done by simply deploying the app if its detected to be the first execution of this container be it due to no container persistence or a commit version upgrade from ORIGIN. Fixes calcom#128 by removing dep on BuildKit Fixes calcom#123 not replicatable and confirmed to be working in repository shipped state. Fixes calcom#136 by building app on first launch from user define-able envvars which can be defined in numerous ways.
|
For folks landing in this issue, docker-compose is not the only method of building the image. In our GHA, we stand up the database service and its container, by running docker/.github/workflows/docker-build-push-dockerhub.yml Lines 69 to 94 in 9f27918 |
|
Cross-posted from Slack: OK, after spending a few hours on it, i think i figured out a fix:
|
|
You really shouldn't have to that extra work. Can you share what docker runtime/tools and their versions you're using? |
|
My setup was working until I recently tried to update it (due to hoping that a certain has been ironed out in a newer version). Now I am stuck at "not supported by buildkit". Has anybody succeeded in applying the solution above? I don't even know where to start... |
|
Same here, basically stuck at this: When doing Any hints? |
Can you please make a more in-depth explanation, for those who are not that advanced? Thank you |
|
The error reports that your network named |
|
For me I had to comment calcom:
image: calcom.docker.scarf.sh/calcom/cal.com
build:
context: .
dockerfile: Dockerfile
args:
NEXT_PUBLIC_WEBAPP_URL: ${NEXT_PUBLIC_WEBAPP_URL}
NEXT_PUBLIC_LICENSE_CONSENT: ${NEXT_PUBLIC_LICENSE_CONSENT}
CALCOM_TELEMETRY_DISABLED: ${CALCOM_TELEMETRY_DISABLED}
NEXTAUTH_SECRET: ${NEXTAUTH_SECRET}
CALENDSO_ENCRYPTION_KEY: ${CALENDSO_ENCRYPTION_KEY}
DATABASE_URL: ${DATABASE_URL}
# network: stack
restart: always
networks:
- stack
ports:
- 3000:3000
env_file: .env
environment:
- DATABASE_URL=postgresql://${POSTGRES_USER}:${POSTGRES_PASSWORD}@${DATABASE_HOST}/${POSTGRES_DB}
depends_on:
- database |
|
Supporting this would have saved a lot of time: docker/buildx#175 |
|
I solved this problem by editing the calcom-docker/docker-compose.yaml file with the following configuration. version: '3.8' volumes: networks: services: calcom: Optional use of Prisma Studio. In production, comment out or remove the section below to prevent unwanted access to your database.studio: END SECTION: Optional use of Prisma Studio. |
|
Decided to give it another try, but getting stuck at the same error again. Is there now an official solution to this? Thanks! |
|
@dravagnolli You can use several backticks on a separate before and after your posted YAML to disable Markdown rules. See https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#quoting-code for an example. |
Following the instructions to build the container.
docker compose build calcomfails with:WARN[0000] The "NEXT_PUBLIC_TELEMETRY_KEY" variable is not set. Defaulting to a blank string. [+] Building 0.0s (0/0) network mode "stack" not supported by buildkit. You can define a custom network for your builder using the network driver-opt in buildx create.DOCKER_BUILDKIT=0 docker compose build calcomthen fails with:$ husky install fatal: Not a git repository (or any of the parent directories): .gitWhich I assume is related to disabling buildkit.
Ubuntu 20.04.4 LTS
Client: Docker Engine - Community, Version: 20.10.16
docker-compose version 1.25.0, build unknown
Docker Compose version v2.5.0
Any pointers appreciated.
The text was updated successfully, but these errors were encountered: