microsoft / microsoft/aspire

aspire doctor should check for Docker buildx

Open
#16,118 1 comment 0 reactions 0 assignees View on GitHub
area-cli
Dominant language
C#
Stars
6.3k
Forks
991
Avg merge
2d 15h
Merged PRs (30d)
196

Description

## Description

`aspire doctor` checks for Docker/Podman presence and version, but does not check for the `docker buildx` plugin. When deploying with any target that requires building container images (Docker Compose, Kubernetes/Helm, etc.), the image build step fails with a confusing error:

```
Container runtime 'Docker' is not running or is unhealthy. Cannot build container image.
```

The actual issue is that `docker buildx version` returns exit code 1 because the buildx plugin is not installed, but the error message suggests Docker itself is unhealthy.

## Expected behavior

1. `aspire doctor` should check for `docker buildx` and report if it's missing
2. The image build step error message should distinguish between "Docker not running" and "buildx plugin not installed" — e.g. `Docker buildx plugin is not installed. Install it with 'apt-get install docker-buildx' or see https://docs.docker.com/buildx/install/`

## Reproduction

On Ubuntu 24.04 with `docker.io` installed (no buildx):

```bash
apt-get install -y docker.io # does NOT include buildx
aspire deploy # fails at image build step with misleading error
apt-get install -y docker-buildx # fixes the issue
```

This affects any deployment target that builds container images — Docker Compose, Kubernetes/Helm, etc.

## Additional context

Discovered while testing PR #16097 (`aspire destroy`) on a fresh Ubuntu 24.04 DigitalOcean VM.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.