CrazyMax

Hum indeed, seems to be an issue with the metadata

Arg can't get the node: https://github.com/docker/buildx/actions/runs/7611314658/job/20726595786#step:6:5366 ``` node is not ready: /usr/bin/kubectl --kubeconfig /tmp/kubeconfig3632220465.yml wait --for=condition=Ready node/integrationk3s The connection to the server 127.0.0.1:32841 was refused - did you specify the...

> > E0122 12:49:12.819095 5009 node_container_manager_linux.go:57] "Failed to create cgroup" err="cannot enter cgroupv2 \"/sys/fs/cgroup/kubepods\" with domain controllers -- it is in an invalid state" cgroupName=[kubepods] > > E0122 12:49:12.819123 5009...

Can't use k3s 1.32 or 1.33: https://github.com/docker/buildx/actions/runs/15923094846/job/44914165242#step:7:10293 ``` time="2025-06-27T09:36:23Z" level=error msg="containerd exited: exit status 1" > stopped 2025-06-27 09:36:23.524642112 +0000 UTC m=+5.963589849 exit status 1 1 ,"waitK3s: ":node is not...

Looks like you forgot to install emulators: https://docs.docker.com/build/building/multi-platform/ ``` $ docker run --privileged --rm tonistiigi/binfmt --install all ```

> but the issue I had also happened on github actions with docker setup buildx Probably also forgot to add https://github.com/docker/setup-qemu-action > I will give it a spin Let us...

> `unix:///Users/groebroeck/.colima/docker.sock` This looks related to https://github.com/abiosoft/colima/issues/720 as you're using colima.

> I did setup QEMU and buildx using the docker actions, and the failure happens during the JReleaser full release step. Hum I don't see any error in this run:...

Ah I see the error in https://github.com/gotson/komga/actions/runs/5746101884/job/15575224773#step:11:577  But doesn't look like this gradle action propagates errors properly to the workflow. Also I don't see what gradle invokes as build...

Logs look truncated. Would need full logs (before `Dockerfile:8` like https://github.com/docker/buildx/issues/1986#issuecomment-1665158062).