concourse / concourse/docker-image-resource
http over https port on private registry
Open
Nobody has claimed this yet.
needs-more-information
- Dominant language
- Go
- Stars
- 162
- Forks
- 250
- PR merge metrics
- No merged PRs in 30d
Description
when check if running on a private registry it is failing to fetch the digest due to sending a plain http request on a https port even with 443 specified as the port
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 by reproducing the digest fetch against a private registry using HTTPS on port 443, then trace the docker image resource's registry request path. Done means the digest request uses HTTPS for that registry and succeeds without sending plain HTTP to the HTTPS port.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100