Docker pull: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 15: Line 15:
The command pulls each layer separately, and it will only pull the layers that do not exist in the local repository.
The command pulls each layer separately, and it will only pull the layers that do not exist in the local repository.


=Example=
==Example==


  docker pull registry.access.redhat.com/openshift3/jenkins-2-rhel7
  docker pull registry.access.redhat.com/openshift3/jenkins-2-rhel7
Line 26: Line 26:
  Digest: sha256:c2e5ffc909fc598628caebe56571849cbcbeea6c99f885a9870cb8c5967d5111
  Digest: sha256:c2e5ffc909fc598628caebe56571849cbcbeea6c99f885a9870cb8c5967d5111
  Status: Image is up to date for registry.access.redhat.com/openshift3/jenkins-2-rhel7:latest
  Status: Image is up to date for registry.access.redhat.com/openshift3/jenkins-2-rhel7:latest
=Pull from a Different Registry=

Revision as of 16:57, 5 December 2017

External

Internal

Overview

Pull an image or a repository from a registry and place it into the local registry. By default the command pulls from Docker Hub.

docker pull <name>[:<tag>]

The command pulls each layer separately, and it will only pull the layers that do not exist in the local repository.

Example

docker pull registry.access.redhat.com/openshift3/jenkins-2-rhel7
Using default tag: latest
Trying to pull repository registry.access.redhat.com/openshift3/jenkins-2-rhel7 ...
sha256:c2e5ffc909fc598628caebe56571849cbcbeea6c99f885a9870cb8c5967d5111: Pulling from registry.access.redhat.com/openshift3/jenkins-2-rhel7
26e5ed6899db: Already exists
66dbe984a319: Already exists
634b7b97a070: Already exists
Digest: sha256:c2e5ffc909fc598628caebe56571849cbcbeea6c99f885a9870cb8c5967d5111
Status: Image is up to date for registry.access.redhat.com/openshift3/jenkins-2-rhel7:latest

Pull from a Different Registry