# dev_container: Detect actual buildx availability instead of assuming Docker has it \(\#53910\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/75fa566511e3ae7d03cfd76008512080291bd81d)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 75fa566511e3ae7d03cfd76008512080291bd81d

Requested commit: 75fa566511e3ae7d03cfd76008512080291bd81d

Commit: 75fa566511e3ae7d03cfd76008512080291bd81d

Tree: 5ca8e549125380578ebbd370a9845d7280f068e6

Author: krisswee

Committer: GitHub

## Message

```
dev_container: Detect actual buildx availability instead of assuming Docker has it (#53910)

`supports_compose_buildkit()` returned `!self.is_podman()`, assuming
every Docker install has buildx. On setups like Colima where the buildx
CLI plugin isn't installed, this causes builds to fail with "classic
builder doesn't support additional contexts" since `DOCKER_BUILDKIT=1`
alone isn't enough without the plugin.

Now probes for `docker buildx version` at construction time and caches
the result. When buildx isn't found, the existing scratch-image fallback
path (same one Podman uses) kicks in instead.

Closes #53890

Release Notes:

- Fixed dev container builds failing on Docker installations without the
buildx plugin.

---------

Co-authored-by: krisswee <krisswee@users.noreply.github.com>
Co-authored-by: KyleBarton <kjb@initialcapacity.io>
```

## Parents

- [5af494d455f6f01e2d8a5d946d81ce2604daf322](https://git.cafe/gitcafe/zed/commit/5af494d455f6f01e2d8a5d946d81ce2604daf322?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/75fa566511e3ae7d03cfd76008512080291bd81d?format=markdown)