Standalone mode

[crazy-max]

In in the future we might want to use buildx in standalone mode.

Also display buildx version being used as suggested in docker/buildx#850 (comment)

Signed-off-by: CrazyMax crazy-max@users.noreply.github.com

[tonistiigi]

Can you add more docs? I'm not sure what standalone mode means and what cases I would want to use it.

[crazy-max]

@tonistiigi Added a section in the README about this use case and also a job in our ci workflow to check this behavior: https://github.com/docker/setup-buildx-action/runs/5997903516?check_suite_focus=true

Docker info
  Docker info skipped in standalone mode
Download and install buildx
  Downloading https://github.com/docker/buildx/releases/download/v0.8.2/buildx-v0.8.2.linux-amd64
  Standalone mode
  Fixing perms
  Added buildx to the path
Buildx version
  /tmp/docker-setup-buildx-sUFOIL/bin/buildx version
  github.com/docker/buildx v0.8.2 6224def4dd2c3d347eee19db595348c50d7cb491
Creating a new builder instance
  /tmp/docker-setup-buildx-sUFOIL/bin/buildx create --name builder-cc4b69f7-2699-433a-9998-687962319ba0 --driver kubernetes --buildkitd-flags --allow-insecure-entitlement security.insecure --allow-insecure-entitlement network.host --use
  builder-cc4b69f7-2699-433a-9998-687962319ba0
Booting builder
  /tmp/docker-setup-buildx-sUFOIL/bin/buildx inspect --bootstrap --builder builder-cc4b69f7-2699-433a-9998-687962319ba0
  #1 [internal] booting buildkit
  #1 waiting for 1 pods to be ready
  #1 waiting for 1 pods to be ready 10.4s done
  #1 DONE 10.5s
  Name:   builder-cc4b69f7-2699-433a-9998-687962319ba0
  Driver: kubernetes
  
  Nodes:
  Name:      builder-cc4b69f7-2699-433a-9998-687962319ba00-59f548fdf-msdbr
  Endpoint:  
  Status:    running
  Platforms: linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/386
Inspect builder
  {
    "name": "builder-cc4b69f7-2699-433a-9998-687962319ba0",
    "driver": "kubernetes",
    "node_name": "builder-cc4b69f7-2699-433a-9998-687962319ba00-59f548fdf-msdbr",
    "node_status": "running",
    "node_platforms": "linux/amd64,linux/amd64/v2,linux/amd64/v3,linux/386"
  }

[tonistiigi]

Is there a point in making it configurable or should it just be an automatic fallback if there is no docker or accessing docker buildx fails while buildx binary exists?

[tonistiigi]

You can add "mode. In this case buildx binary is invoked directly, instead of calling it as a docker plugin."

[crazy-max]

Is there a point in making it configurable or should it just be an automatic fallback if there is no docker or accessing docker buildx fails while buildx binary exists?

Good point, I guess we can do that.

[tonistiigi]

Does the build-push action support the same thing?

[crazy-max]

Does the build-push action support the same thing?

Not yet, will work on it.