Pushing kaniko-chains to kind-registry
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 277
- Forks
- 164
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 61
Description
I was wondering if anyone else got the following error while running
tkn task start --param IMAGE=kind-registry:5000/kaniko-chains --use-param-defaults --workspace name=source,emptyDir="" --workspace name=dockerconfig,secret=docker-credentials kaniko-chains
"https://kind-registry:5000/v2/": http: server gave HTTP response to HTTPS client?
I've added that repo to insecure registries for my local docker engine:
Insecure Registries:
kind-registry:5000
127.0.0.0/8
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 reported tkn task start command with the kind-registry:5000/kaniko-chains image and compare the Docker engine's insecure-registry setting with the registry configuration used by the task. Done means identifying the source of the HTTP/HTTPS mismatch and documenting or implementing the required configuration; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100