Browse code

Updated CLI documentation for docker pull with notes on specifying URL

Docker-DCO-1.1-Signed-off-by: Matthew Heon <mheon@redhat.com> (github: mheon)

Matthew Heon authored on 2014/06/10 00:27:08
Showing 1 changed files
... ...
@@ -735,7 +735,7 @@ Running `docker ps` showing 2 linked containers.
735 735
 
736 736
 ## pull
737 737
 
738
-    Usage: docker pull NAME[:TAG]
738
+    Usage: docker pull [REGISTRY_PATH/]NAME[:TAG]
739 739
 
740 740
     Pull an image or a repository from the registry
741 741
 
... ...
@@ -745,6 +745,11 @@ Most of your images will be created on top of a base image from the
745 745
 [Docker Hub](https://hub.docker.com) contains many pre-built images that you
746 746
 can `pull` and try without needing to define and configure your own.
747 747
 
748
+It is also possible to manually specify the path of a registry to pull from.
749
+For example, if you have set up a local registry, you can specify its path to
750
+pull from it. A repository path is similar to a URL, but does not contain
751
+a protocol specifier (https://, for example).
752
+
748 753
 To download a particular image, or set of images (i.e., a repository),
749 754
 use `docker pull`:
750 755
 
... ...
@@ -752,8 +757,11 @@ use `docker pull`:
752 752
     # will pull all the images in the debian repository
753 753
     $ docker pull debian:testing
754 754
     # will pull only the image named debian:testing and any intermediate layers
755
-    # it is based on. (typically the empty `scratch` image, a MAINTAINERs layer,
756
-    # and the un-tared base.
755
+    # it is based on. (Typically the empty `scratch` image, a MAINTAINERs layer,
756
+    # and the un-tarred base).
757
+    $ docker pull registry.hub.docker.com/debian
758
+    # manually specifies the path to the default Docker registry. This could
759
+    # be replaced with the path to a local registry to pull from another source.
757 760
 
758 761
 ## push
759 762