Unable to deploy buildx nodes from MacOS

[gboer]

When I run the following command, it doesn't deploy anything in kubernetes:

docker buildx create --name buildx-test --driver kubernetes --use

Running docker buildx ls shows it as inactive:

docker buildx ls
NAME/NODE       DRIVER/ENDPOINT                                   STATUS   PLATFORMS
buildx-test *   kubernetes
  buildx-test0  kubernetes:///buildx-test?deployment=&kubeconfig= inactive
desktop-linux   docker
  desktop-linux desktop-linux                                     running  linux/amd64, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/arm/v7, linux/arm/v6
default         docker
  default       default                                           running  linux/amd64, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/arm/v7, linux/arm/v6

I'm on the latest Docker Desktop 4.5.0, Intel MacOS 12.1. I've tried restarting my docker daemon, restarting my machine, double checked my terminal access to kubernetes, but nothing seems to resolve it.

Does anyone have any ideas of other things I can do to resolve it?

[AkihiroSuda]

Please provide pod logs

[gboer]

Well, I wish I could, but no pods are created. There's no deployment created. Nothing basically is done in kubernetes as far as I can see.

[crazy-max]

Maybe bootstrap the builder?: docker buildx inspect --builder buildx-test --bootstrap

[gboer]

Ah, that triggered the deployment process indeed @crazy-max , thanks! It's kind of odd that it doesn't do that by default, when you create it though. In Linux it doesn't need the bootstrapping.

[crazy-max]

To boot builder after creation you can add the --bootstrap flag:

$ docker buildx create --name buildx-test --driver kubernetes --use --bootstrap

More info: https://github.com/docker/buildx/blob/master/docs/reference/buildx_create.md#options

[crazy-max]

In Linux it doesn't need the bootstrapping.

For docker-container builder, it starts the builder if it's not running. Maybe we could do that for kubernetes too?

[gboer]

Nice that I don't need to call inspect separately. Still, if I don't actually bootstrap it in macOS, builds don't work while for Linux it does.

But yeah, I'd say it makes sense to start the build if you're creating it. I get from the point of Buildx that the builder has been created, but I would expect it to see in Kubernetes as well, while that's not the case. Was a bit confusing for me (nor did I understand how to actually make it work).