Feature request: Choose public or private visibility when pushing a new repository to Docker Hub
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Go
- Estrellas
- 6.1k
- Forks
- 2.2k
- Merge medio
- 1 d 8 h
- PR fusionados (30 d)
- 62
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de docker/cli
-
Mode option in tmpfs volume is ignored when deployed via docker stack deployPosiblemente ocupada @locker95 la tomó hace 15 días. Abiertokind/bug status/0-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Los mantenedores suelen responder en 1 día
-
docker stack: text after an unbraced `$VAR` is dropped when it starts with `-`, `:-`, `?` or `:?`Posiblemente ocupada @sebxt la tomó hace 28 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 87/100
Los mantenedores suelen responder en 1 día
-
filename completion on `docker load -i`Posiblemente ocupada @cra la tomó hace 31 días. Abiertokind/feature status/0-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
docker build treats uppercase HTTP(S) URLs as local pathsPosiblemente ocupada @TanvirTian la tomó hace 38 días. Abiertokind/bug status/0-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Los mantenedores suelen responder en 1 día
-
`docker context export` writes a truncated tar archivePosiblemente ocupada @2arian3 la tomó hace 54 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 92/100
Los mantenedores suelen responder en 1 día
Todos los issues de docker/cli
Issues similares
-
agent-review-finding chore
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
jordansmall/spindrift#7254 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
pg-sharding/spqr#3275 ·
Los mantenedores suelen responder en 1 día
-
create_or_update_file rejects explicitly empty file contentPosiblemente ocupada @Elon-Jiang la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
github/github-mcp-server#3883 ·
Los mantenedores suelen responder en 4 días
-
feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
databricks/terraform-provider-databricks#6210 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
IBM-Cloud/terraform-provider-ibm#7115 ·
Los mantenedores suelen responder en 2 días