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

オープン
#7,400 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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時間
マージ済み PR(30日)
62

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

docker/cli のほかの issue

docker/cli の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。