nerdctl build is failed with Error (dial tcp: lookup distrib on 135.xx.xx.xx:53: no such host)
Open
Nobody has claimed this yet.
area/containerd
- Dominant language
- Go
- Stars
- 10.3k
- Forks
- 1.5k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 48
Description
Hi Team,
Image build is failing using nerdctl. I raised the bug on nerdctl github (https://github.com/containerd/nerdctl/issues/1871) and they suggested that it seems to be an issue with buildkit so raising the issue here.
# ./nerdctl build --no-cache --progress=plain --build-arg fromImageRepository='distrib:5000/img-3ppextent-22.12.0' --build-arg fromImageTag='8' --build-arg ReleaseVerse='user-admin-22.12.0:425 | 2023-01-17 17:52:43 IST' --tag 'distrib:5000/user-admin-22.12.0:425' --file '/repo/img-sw-22.12.0-623220927/user-admin/user-admin-22.12.0-425/Dockerfile' '/repo/img-sw-22.12.0-623220927/user-admin/user-admin-22.12.0-425/' #1 [internal] load .dockerignore
#1 transferring context: 2B done
#1 DONE 0.0s
#2 [internal] load build definition from Dockerfile
#2 transferring dockerfile: 5.27kB done
#2 DONE 0.0s
#3 [internal] load metadata for distrib:5000/img-3ppextent-22.12.0:8
#3 ERROR: failed to do request: Head "https://distrib:5000/v2/img-3ppextent-22.12.0/manifests/8": dial tcp: lookup distrib on 135.xx.xx.xx:53: no such host
------
> [internal] load metadata for distrib:5000/img-3ppextent-22.12.0:8:
------
Dockerfile:4
--------------------
2 | ARG fromImageRepository
3 | ARG fromImageTag
4 | >>> FROM ${fromImageRepository}:${fromImageTag}
5 |
--------------------
error: failed to solve: distrib:5000/img-3ppextent-22.12.0:8: failed to do request: Head "https://distrib:5000/v2/img-3ppextent-22.12.0/manifests/8": dial tcp: lookup distrib on 135.xx.xx.xx:53: no such host
FATA[0000] no image was built
Contributor guide
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.
Research direction
Start with the linked nerdctl issue and the failing command, then inspect the Dockerfile at line 4 where the parameterized FROM image is resolved. Trace how BuildKit handles the registry hostname distrib and its DNS lookup. Done means identifying whether the failure belongs to BuildKit or the registry/network configuration and documenting a reproducible resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, dockerfile, go
- Domain
- build-system, infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100