# failed to solve: frontend dockerfile.v0: failed to resolve dockerfile frontend image: docker/dockerfile:1: not found

- **ID:** `docker/buildkit-frontend-image-not-found`
- **Domain:** docker
- **Category:** build_error
- **Verification:** ai_generated
- **Fix Rate:** 80%

## Root Cause

The BuildKit frontend image specified in the Dockerfile's syntax directive is not available or the registry is unreachable.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| Docker 23.0.5 | active | — | — |
| BuildKit 0.11.6 | active | — | — |
| Dockerfile 1.5.0 | active | — | — |

## Workarounds

1. **Explicitly set the syntax directive at the top of the Dockerfile: `# syntax=docker/dockerfile:1.5.0` and ensure the BuildKit version supports it. Then build with `DOCKER_BUILDKIT=1 docker build .`** (85% success)
   ```
   Explicitly set the syntax directive at the top of the Dockerfile: `# syntax=docker/dockerfile:1.5.0` and ensure the BuildKit version supports it. Then build with `DOCKER_BUILDKIT=1 docker build .`
   ```
2. **If behind a proxy, configure Docker daemon proxy settings in `/etc/systemd/system/docker.service.d/http-proxy.conf` to allow BuildKit to reach the registry.** (75% success)
   ```
   If behind a proxy, configure Docker daemon proxy settings in `/etc/systemd/system/docker.service.d/http-proxy.conf` to allow BuildKit to reach the registry.
   ```

## Dead Ends

- **** — Disabling BuildKit may work but loses build optimizations and can cause other errors if the Dockerfile uses syntax features only supported by BuildKit. (60% fail)
- **** — The error is not about a missing local image; BuildKit tries to fetch the image from the registry during build, and pulling it manually may not resolve the issue if the registry is blocked. (70% fail)