Files
docker-cli/components/engine/docs/sources/terms/repository.md
T
Sven Dowideit c4684e29f0 now, with shiney markdown
Docker-DCO-1.1-Signed-off-by: Sven Dowideit <SvenDowideit@fosiki.com> (github: SvenDowideit)
Upstream-commit: ac999a9cb2b0976e021aeb8825bb051df6bd0976
Component: engine
2014-04-16 11:04:14 +10:00

1.3 KiB
Raw Blame History

page_title: Repository page_description: Definition of an Repository page_keywords: containers, lxc, 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:

  1. At build time (e.g. sudo docker build -t IMAGENAME ),
  2. When committing a container (e.g. sudo docker commit CONTAINERID IMAGENAME) or
  3. 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) .literal}

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