tkn-cli-serve is deployed from docker.io registry
Open
Nobody has claimed this yet.
help wanted
kind/bug
lifecycle/frozen
- Dominant language
- Go
- Stars
- 608
- Forks
- 263
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 125
Description
Expected Behavior
tkn-cli-serve works.
Actual Behavior
Failed to pull image "docker.io/rupali/serve-tkn:v2": rpc error: code = Unknown desc = Error initializing source docker://rupali/serve-tkn:v2: Error reading manifest v2 in docker.io/rupali/serve-tkn: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
- Tekton Pipeline version:
Pipeline version: v0.35.0
Triggers version: v0.19.1
Operator version: 0.57.0
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 tkn-cli-serve deployment with Pipeline v0.35.0, Triggers v0.19.1, and Operator 0.57.0, then trace where the docker.io/rupali/serve-tkn:v2 image is configured. Done means the deployment pulls its image successfully without the Docker Hub rate-limit error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100