using an external dockerfile frontend on windows slows down the build

Open
#4,205 15 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, dockerfile
Domain
build-system

Research direction

Start by reproducing the Windows build with # syntax=docker/dockerfile:1 and inspect the external Dockerfile frontend image-config resolution that reports a 68.7-second delay. Done means the frontend can be used without the repeated roughly 60-second build penalty; the issue does not name a source file or test to start from.

Written by the indexing model from the issue text.

Description

area/windows area/windows-lcow

when I add: # syntax=docker/dockerfile:1 at the start of my dockerfile one of the first things the build does is tries

 => resolve image config for docker.io/docker/dockerfile:       68.7s

which takes 68 seconds. It looks like it's trying to pull the latest version and maybe it just takes that long, but I'd like a way to improve this as it adds a 60 second penalty every build I try to run.

Windows version: 10.0.22621.2134
Docker Desktop: 4.22.1
Docker Engine: 24.0.5
Buildkit v0.11.6+0a15675913b7
Buildx: v0.10.4 c513d34049e499c53468deac6c4267ee72948f02

Dominant language
Go
Stars
10.3k
Forks
1.5k
Avg merge
1d 23h
Merged PRs (30d)
48

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from moby/buildkit

All issues in moby/buildkit

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.