Docker "buildx create" - "failed to find driver" / "no valid driver" in CI

docker buildx create could not set up a builder because the --driver you named is unknown or unavailable. Buildx supports a fixed set of drivers (docker, docker-container, kubernetes, remote), and anything else - or a driver whose backend is missing - fails here.

What this error means

A docker buildx create --driver <x> fails immediately with failed to find driver "<x>" or no valid drivers found. No builder is created, so every later buildx build has nothing to run on.

docker buildx output

ERROR: failed to find driver "docker-cointainer"
# or, when the backend is unavailable:
ERROR: no valid drivers found

Common causes

The driver name is misspelled or unsupported

Only docker, docker-container, kubernetes, and remote are valid. A typo (docker-cointainer) or an invented driver name is rejected outright.

The driver's backend is not reachable

The docker-container driver needs a working Docker daemon to launch the BuildKit container; the kubernetes driver needs a reachable cluster/context. If the backend is absent, no valid driver can be initialized.

buildx is too old to know the driver

An outdated buildx plugin may not recognize a newer driver name, so it reports the driver as not found.

How to fix it

Name a valid driver and confirm its backend

Use a supported driver and make sure its backend (daemon or cluster) is available first.

Terminal

docker buildx create --name ci --driver docker-container --use
docker buildx inspect --bootstrap   # starts the BuildKit container

Let setup-buildx-action provision the builder

In GitHub Actions the action creates a working docker-container builder for you.

.github/workflows/build.yml

- uses: docker/setup-buildx-action@v3
  with:
    driver: docker-container

How to prevent it

Reference only the four supported buildx drivers.
Keep the buildx plugin current so newer drivers are recognized.
Ensure the driver backend (daemon/cluster) is up before buildx create.