Getting Started guide > Image Building Best Practices produces error
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker
- Domain
- documentation
Research direction
Open the Getting Started guide at /tutorial/image-building-best-practices/#layer-caching and inspect step 3. Reproduce the documented docker build -t getting-started . command with current Docker Desktop on Windows, then determine what the guide needs so the step works without disabling BuildKit. Done means the instructions work as written or clearly document any required setup.
Written by the indexing model from the issue text.
Description
Following the the Getting Started guide. I'm using the latest version of Docker Desktop for Windows (4.17.0 99724) on Windows 11 latest / all updates applied as of this writing.
On page:
http://localhost/tutorial/image-building-best-practices/#layer-caching
... Layer Caching section, in step 3, you'll get an error:
C:\source\app>docker build -t getting-started .
[+] Building 0.0s (1/2)
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 2B 0.0s
failed to solve with frontend dockerfile.v0: failed to read dockerfile: open /var/lib/docker/tmp/buildkit-mount1883853740/Dockerfile: no such file or directory
To remedy, followed instructions in the Stack Overflow article below to resolve. Go to Settings > Docker Engine and modify the "buildkit:" entry from "true" to "false".
https://stackoverflow.com/questions/64221861/an-error-failed-to-solve-with-frontend-dockerfile-v0
However, I have no idea what I'm doing here ... there's probably a better way to do this? And the way I fixed it may have long term ramifications I don't know about because, after all, I'm just "getting started" here.
- Dominant language
- JavaScript
- Stars
- 3.1k
- Forks
- 6.4k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker/getting-started
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
docker/getting-started#481 · 2 comments · 5 reactions ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 65/100
docker/getting-started#394 · 1 comment · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
docker/getting-started#494 ·
-
Chat Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
docker/getting-started#482 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 1/100
docker/getting-started#477 ·
All issues in docker/getting-started
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#3692 ·
-
agent/guide documentation hive/hosted-available-lke648397-260827-5n31
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Add: BuyPass TV Openchannels:add check:passed
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
S: triage
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100