concourse / concourse/docker-image-resource
Very Slow Resource Check Using DNS Name for Repository
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 162
- Forks
- 250
- PR merge metrics
- No merged PRs in 30d
Description
We use an Artifactory-based private docker repo and when I configure this resource to use the DNS name of the Artifactory server, it often takes a very long time to do the resource check. It just sits at "waiting for a suitable set of input versions" and spins and spins before finally completing. When we use the IP of the Artifactory server, the check happens nearly instantly every time.
I don't believe it is a DNS issue because we use DNS names for other resources and they complete immediately. I'm just looking for suggestions on how to troubleshoot this. I want to use the DNS name in case the IP changes.
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
The issue names no files, tests, or code entry points. Start by reproducing the resource check with the Artifactory DNS name and IP separately, then trace the check behavior to identify where the delay occurs. Done means explaining the DNS-versus-IP difference and confirming a practical fix or clear troubleshooting guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100