OpenAPITools / OpenAPITools/openapi-generator

[BUG][Docker] Docker Hub Image Access Management blocks access to OpenAPITools container images

Open
#11,504 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue: Bug
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

User openapitools on Docker Hub is not a Verified Publisher, which means images in that account, e.g. openapitools/openapi-generator-cli, cannot be downloaded by users in organisations with Image Access Management enabled.

openapi-generator version

v4.3.1

OpenAPI declaration file content or url

N/A

Generation Details

N/A

Steps to reproduce
  • Be signed in to Docker Desktop for Windows with an organisation with Image Access Management enabled.
  • docker pull openapitools/openapi-generator-cli:v4.3.1

Failure result:

Error response from daemon: pull access denied for openapitools/openapi-generator-cli, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
Related issues/PRs

Nothing I saw.

Suggest a fix

I assume the fix is to join the Docker Verified Publisher program if that's possible for free, open-source projects.

Alongside that, I'm recommending that my employer disable Image Access Management, as I'm sure we'll hit this problem again with other open-source projects, and the whole thing is pretty awful from a UX perspective anyway.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file or test is named. Start by reproducing the documented docker pull with Docker Hub Image Access Management enabled, then review the openapitools Docker Hub account and the Docker Verified Publisher requirement. The issue is done when users in affected organisations can download the listed container image.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
devops
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.