OpenAPITools / OpenAPITools/openapi-generator
Not able to pull docker image openapitools/openapi-generator-online:v6.5.0 or any other image from the same repository
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Bug Report Checklist
- Have you provided a full/minimal spec to reproduce the issue?
- Have you validated the input using an OpenAPI validator (example)?
- Have you tested with the latest master to confirm the issue still exists?
- Have you searched for related issues/PRs?
- What's the actual output vs expected output?
- [Optional] Sponsorship to speed up the bug fix or feature request (example)
Description
Not able to pull docker image openapitools/openapi-generator-online:v6.5.0 or any other image from the same repository
openapi-generator version
openapitools/openapi-generator-online:v6.5.0 or any other version
OpenAPI declaration file content or url
docker pull not working :
docker pull openapitools/openapi-generator-online:v6.5.0
Generation Details
Getting below error while trying to pull the image:
##[error]ERROR: (RegistryErrorResponse) An error response is received from the docker registry 'index.docker.io'. Please retry later.
Steps to reproduce
pull the image using below command :
docker pull openapitools/openapi-generator-online:v6.5.0
Getting the error :
##[error]ERROR: (RegistryErrorResponse) An error response is received from the docker registry 'index.docker.io'. Please retry later.
Suggest a fix
Looks like some issue related to permission at repository level or some throttling issue
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 docker pull openapitools/openapi-generator-online:v6.5.0 and compare the registry response for other tags from the same repository. Investigate whether the reported Docker registry error is caused by image availability, repository permissions, or throttling; done means the pull succeeds or the external cause and required fix are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100