CrazyMax
CrazyMax
GitHub hosted runner doesn't have enough space to build our image: https://github.com/docker/buildx/actions/runs/19330419315/job/55292703625#step:8:521 ``` #28 [linux/amd64->darwin/amd64 buildx-build 1/1] RUN --mount=type=bind,target=. --mount=type=cache,target=/root/.cache --mount=type=cache,target=/go/pkg/mod --mount=type=bind,from=buildx-version,source=/buildx-version,target=/buildx-version
Switch reusable workflow ref to `bake-distrib` https://github.com/docker/github-builder-experimental/pull/22 so builds are distributed across runners.
Pushed extra commit to also build our binaries with our reusable workflow.
Yes it needs https://github.com/moby/buildkit/pull/5586 first
Got it again with openbsd in https://github.com/docker/buildx/actions/runs/19291895364/job/55164364388?pr=3462#step:7:1209 ``` === RUN TestLaunch adapter_test.go:176: [client] send: {"seq":1,"type":"request","command":"initialize","arguments":{"adapterID":"","linesStartAt1":false,"columnsStartAt1":false}} adapter_test.go:193: [server] recv: {"seq":1,"type":"request","command":"initialize","arguments":{"adapterID":"","linesStartAt1":false,"columnsStartAt1":false,"pathFormat":"path"}} adapter_test.go:176: [server] send: {"seq":1,"type":"response","request_seq":1,"success":true,"command":"initialize","body":{"supportsConfigurationDoneRequest":true}} adapter_test.go:193: [client] recv: {"seq":1,"type":"response","request_seq":1,"success":true,"command":"initialize","body":{"supportsConfigurationDoneRequest":true}} adapter_test.go:176: [client] send:...
Thanks for reporting! This is a known issue. Atm Docker Desktop runs backend services on the host machine, and for Windows users it means that Docker config on WSL is...
As a workaround what you can do is creating the builder on WSL2: ``` $ docker buildx create --name mybuilder ``` And create another one with Powershell/CMD on Windows host...
Looking at the docs https://docs.docker.com/reference/compose-file/profiles/ I think it makes sense. > In my case, I have WG in a profile, along with diun: Can you show your full compose file...
I think that would be fine but as this could be a breaking change in some cases, would be applied to next major release.
> I don't think there is anything bake-specific in here, though. It just seems to be how named contexts are handled in BuildKit/Dockerfile. Yes indeed looks handled in https://github.com/moby/buildkit/blob/070d993324ee4f90c0517ca70229dcffa37c270a/frontend/dockerui/namedcontext.go#L149-L150 >...