Is this a docs issue?
Type of issue
Other
Description
As discussed in this Slack thread, a customer attempted to create a second isolated Docker Build Cloud builder using:
docker buildx create --driver cloud /
After checking internally, I was informed that docker buildx create command does not provision a new Docker Build Cloud builder. Instead, it connects Buildx to an existing Docker Build Cloud builder. The command only creates a second builder when local buildkit containers are used.
Location
https://docs.docker.com/reference/cli/docker/buildx/create/#description
Suggestion
Suggested wording that I would put under description -
“Note: When using docker buildx create, it connects Buildx to an existing Docker Build Cloud builder. It does not create or provision a new Docker Build Cloud builder. To create a new builder, please use local buildkit containers instead."
Is this a docs issue?
Type of issue
Other
Description
As discussed in this Slack thread, a customer attempted to create a second isolated Docker Build Cloud builder using:
docker buildx create --driver cloud /
After checking internally, I was informed that docker buildx create command does not provision a new Docker Build Cloud builder. Instead, it connects Buildx to an existing Docker Build Cloud builder. The command only creates a second builder when local buildkit containers are used.
Location
https://docs.docker.com/reference/cli/docker/buildx/create/#description
Suggestion
Suggested wording that I would put under description -
“Note: When using docker buildx create, it connects Buildx to an existing Docker Build Cloud builder. It does not create or provision a new Docker Build Cloud builder. To create a new builder, please use local buildkit containers instead."