Feature request: Choose public or private visibility when pushing a new repository to Docker Hub

未關閉
#7,400 2 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
35/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
docker, go
領域
cli

研究方向

Start with the related discussion in issue #4977 and review Docker Hub’s repository creation API, especially its is_private field. The payload names no CLI files or tests, so first locate the docker push command and its registry handling. Done means new Docker Hub repositories use the requested visibility before upload, mismatches and failures stop the push, and other registries are clearly handled.

由索引模型根據 Issue 內容生成。

描述

Description

When running docker push for a Docker Hub repository that does not yet exist, Docker Hub creates it using the namespace's default repository visibility.

If that default is public, a user intending to upload a private image can accidentally publish it. The CLI does not offer a public/private selection before uploading.

I would like an option to explicitly select the intended visibility when pushing to a new Docker Hub repository.

Steps illustrating the current behavior
  1. Use a Docker Hub namespace whose default repository visibility is Public.

  2. Tag a local image with a repository name that does not exist:

    docker tag myapp:latest <username>/new-repository:latest
    
  3. Push the image:

    docker push <username>/new-repository:latest
    
  4. Check the newly created repository's visibility in Docker Hub.

The repository is created as public according to the namespace default, without a visibility selection in the CLI.

Proposed behavior

Allow users to explicitly select visibility before the first upload. For example, the following is proposed syntax, not an existing option:

docker push --visibility private <username>/new-repository:latest
docker push --visibility public <username>/new-repository:latest

An optional interactive mode could offer:

Choose visibility for the new Docker Hub repository:
> Private
  Public

Automation should be able to use the explicit flag without any interactive prompt. Existing command behavior should remain unchanged when the feature is not requested.

Expected safeguards
  • Create a missing repository with the requested visibility before uploading any image content.
  • Verify the repository's visibility before pushing, and stop if verification or creation fails, including permission or private-repository quota errors.
  • For an existing repository, report a visibility mismatch rather than silently changing its visibility.
  • Clearly report unsupported registries if this functionality is specific to Docker Hub.
Implementation consideration

Repository visibility is managed by Docker Hub rather than the standard image-push protocol. This may require Docker Hub API integration or a dedicated CLI plugin. A check before uploading also cannot prevent another authorized actor from changing repository visibility concurrently or afterward.

References and related discussion

This request overlaps with #4977; I am linking it to preserve the existing discussion and implementation constraints.

主要語言
Go
星號
6.1k
分支
2.2k
平均合併
1 天 8 小時
30 天內合併 PR
62

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

docker/cli 的其他 Issue

查看 docker/cli 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。