a8871b93b9
This adds back in the references to private repositories and provides some refactoring to the Working with repositories documentation including updating references to the "Central" registry to Docker.io. It also: * Fixes some links and references to Central Index * Fixes anchors in other files to updated titles in Working with Repositories. * Renamed Central Index in the remaining places. * Updated terms documentation to reflect Docker.io * Updated some Docker Index naming to be consistent. * Updates menu labels and hyperlinks. Docker-DCO-1.1-Signed-off-by: James Turnbull <james@lovedthanlost.net> (github: jamtur01) Docker-DCO-1.1-Signed-off-by: O.S. Tezer <ostezer@gmail.com> (github: ostezer)
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.
sudo docker build -t IMAGENAME), - When committing a container (e.g.
sudo docker commit CONTAINERID IMAGENAME) or - When tagging an image id with an image name (e.g.
sudo 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 Docker images.
For more information see Working with Repositories