Feature request: Choose public or private visibility when pushing a new repository to Docker Hub
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 35/100
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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
-
Use a Docker Hub namespace whose default repository visibility is Public.
-
Tag a local image with a repository name that does not exist:
docker tag myapp:latest <username>/new-repository:latest -
Push the image:
docker push <username>/new-repository:latest -
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
- Docker Hub default privacy settings: https://docs.docker.com/docker-hub/settings/
- Docker Hub repository creation API, including
is_private: https://docs.docker.com/reference/api/hub/latest/operations/CreateRepository/ - Related feature request: https://github.com/docker/cli/issues/4977
This request overlaps with #4977; I am linking it to preserve the existing discussion and implementation constraints.
- Vorherrschende Sprache
- Go
- Sterne
- 6.1k
- Forks
- 2.2k
- Ø Merge
- 1 T. 8 Std.
- Gemergte PRs (30 T.)
- 62
Entwicklungsumgebung
- Enthält ein Dockerfile oder eine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus docker/cli
-
Mode option in tmpfs volume is ignored when deployed via docker stack deployEvtl. vergeben @locker95 hat das vor 15 Tagen übernommen. Offenkind/bug status/0-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
Maintainer antworten meist innerhalb von 1 Tag
-
docker stack: text after an unbraced `$VAR` is dropped when it starts with `-`, `:-`, `?` or `:?`Evtl. vergeben @sebxt hat das vor 28 Tagen übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 87/100
Maintainer antworten meist innerhalb von 1 Tag
-
filename completion on `docker load -i`Evtl. vergeben @cra hat das vor 31 Tagen übernommen. Offenkind/feature status/0-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
Maintainer antworten meist innerhalb von 1 Tag
-
docker build treats uppercase HTTP(S) URLs as local pathsEvtl. vergeben @TanvirTian hat das vor 38 Tagen übernommen. Offenkind/bug status/0-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
Maintainer antworten meist innerhalb von 1 Tag
-
`docker context export` writes a truncated tar archiveEvtl. vergeben @2arian3 hat das vor 54 Tagen übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 92/100
Maintainer antworten meist innerhalb von 1 Tag
Ähnliche Issues
-
agent-review-finding chore
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
jordansmall/spindrift#7254 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
pg-sharding/spqr#3275 ·
Maintainer antworten meist innerhalb von 1 Tag
-
create_or_update_file rejects explicitly empty file contentEvtl. vergeben @Elon-Jiang hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
github/github-mcp-server#3883 ·
Maintainer antworten meist innerhalb von 4 Tagen
-
feature
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
databricks/terraform-provider-databricks#6210 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
IBM-Cloud/terraform-provider-ibm#7115 ·
Maintainer antworten meist innerhalb von 2 Tagen