00b8817331
The existing page is focused on listing a set of requirements for proposing a new repository. This information has become outdated and is duplicated in the `docker-library/official-images` and `docker-library/docs` GitHub repositories. This PR rewrites the Official Repositories page to describe what they actually are, and defers to GitHub/IRC for the subset of users that are interested in contributing. I also removed the requirement to contact partners@docker.com and made it optional to reduce the barrier to entry. Signed-off-by: Peter Salvatore <peter@psftw.com> Upstream-commit: 8f52eb7b827d658d6974056460afd722a5cb040f Component: engine
1.3 KiB
page_title: Repository page_description: Definition of an Repository page_keywords: containers, concepts, explanation, image, repository, container
Repository
Introduction
A repository is a set of images either on your local Docker server, or shared, by pushing it to a Registry server.
Images can be associated with a repository (or multiple) by giving them an image name using one of three different commands:
- At build time (e.g.,
docker build -t IMAGENAME), - When committing a container (e.g.,
docker commit CONTAINERID IMAGENAME) or - When tagging an image id with an image name (e.g.,
docker tag IMAGEID IMAGENAME).
A Fully Qualified Image Name (FQIN) can be made up of 3 parts:
[registry_hostname[:port]/][user_name/](repository_name:version_tag)
username and registry_hostname default to an empty string. When
registry_hostname is an empty string, then docker push will push to
index.docker.io:80.
If you create a new repository which you want to share, you will need to
set at least the user_name, as the default blank user_name prefix is
reserved for Official Repositories.
For more information see Working with Repositories