In dockerhub, you can create public and private repo’s to push your docker images. Dockerhub provides lots of advantages, some of them are:<\/p>\n\n\n\n
- You can easily push and pull images anytime.<\/li>
- You have the flexibility to create a private repo to store your customized images.<\/li>
- You can pull high-quality images from the official vendors.<\/li>
- You can pull images from external vendors as well.<\/li>
- You can create an organization and add your teammates.<\/li><\/ul>\n\n\n\n
How to find the images in the docker hub<\/h3>\n\n\n\n
To find the available images in the docker hub, goto <\/a>Dockerhub<\/a><\/p>\n\n\n\n
![\"dockerhub\"](\"https:\/\/naiveskill.com\/wp-content\/uploads\/2021\/06\/image-16-1024x298.png\")
<\/figure>\n\n\n\nOn the search bar, search for any images. let’s search for the Nginx image<\/p>\n\n\n\n
![\"dockerhub\"](\"https:\/\/naiveskill.com\/wp-content\/uploads\/2021\/06\/image-17-1024x522.png\")
<\/figure>\n\n\n\nAs you can see, we have more than 8k images available for Nginx. It is always recommended to use official images.<\/p>\n\n\n\n
Now we have a pretty good idea about how to find images in Dockerhub. Now let’s proceed further to understand what docker pull does.<\/p>\n\n\n\n
What docker pull does?<\/h2>\n\n\n\n
Docker pulls basically pulls an image or a repository from a registry. Docker will pull an image from the docker hub if you do not specify any registry. While pulling images, you have the flexibility to select the version as well. If the version is not specified docker pull command will always pull the latest<\/strong> image.<\/p>\n\n\n\n
Now let’s proceed further and see the syntax of the docker pull<\/p>\n\n\n\n
syntax <\/p>\n\n\n\n
docker pull [OPTIONS] NAME[:TAG|@DIGEST]\n<\/pre>\n\n\n\n
There are many options available for image pull. To get a list of options, type.<\/p>\n\n\n\n
\u279c ~ docker pull --help\n\nUsage: docker pull [OPTIONS] NAME[:TAG|@DIGEST]\n\nPull an image or a repository from a registry\n\nOptions:\n -a, --all-tags Download all tagged images in the repository\n --disable-content-trust Skip image verification (default true)\n --platform string Set platform if server is multi-platform capable\n -q, --quiet Suppress verbose output\n\u279c ~\n<\/pre>\n\n\n\n
docker pull hello-world<\/h2>\n\n\n\n
In this session, we will be pulling a hello-world docker image from the dockerhub. Before proceeding further, make sure the docker is installed in your system and is running.<\/p>\n\n\n\n
Now let’s pull the hello-world image from the dockerhub<\/p>\n\n\n\n
docker pull hello-world\nUsing default tag: latest\nlatest: Pulling from library\/hello-world\nDigest: sha256:9f6ad537c5132bcce57f7a0a20e317228d382c3cd61edae14650eec68b2b345c\nStatus: Image is up to date for hello-world:latest\ndocker.io\/library\/hello-world:latest<\/pre>\n\n\n\n
The above command will download the hello-world image from dockerhub to your local system. Run the below command to verify if the image gets successfully pulled.<\/p>\n\n\n\n
docker image ls\nREPOSITORY TAG IMAGE ID CREATED SIZE\nhello-world latest d1165f221234 3 months ago 13.3kB<\/pre>\n\n\n\n
What to do after docker pull?<\/h2>\n\n\n\n
Once you have pulled an image from the dockerhub, the next step is to run the image using the docker run command.<\/strong> The run command creates an isolated container that runs on your host machine.<\/p>\n\n\n\n
Let’s run the hello-world image which we pulled earlier<\/p>\n\n\n\n
\u279c ~ docker run hello-world\n\nHello from Docker!\nThis message shows that your installation appears to be working correctly.\n\nTo generate this message, Docker took the following steps:\n 1. The Docker client contacted the Docker daemon.\n 2. The Docker daemon pulled the \"hello-world\" image from the Docker Hub.\n (amd64)\n 3. The Docker daemon created a new container from that image which runs the\n executable that produces the output you are currently reading.\n 4. The Docker daemon streamed that output to the Docker client, which sent it\n to your terminal.\n\nTo try something more ambitious, you can run an Ubuntu container with:\n $ docker run -it ubuntu bash\n\nShare images, automate workflows, and more with a free Docker ID:\n https:\/\/hub.docker.com\/\n\nFor more examples and ideas, visit:\n https:\/\/docs.docker.com\/get-started\/\n``\n<\/pre>\n\n\n\n
If you are getting output as Hello from Docker<\/strong>! It means your hello-world image is working as expected.<\/p>\n\n\n\n
The hello-world image was a basic image to verify the docker setup. Now let’s pull another image from the dockerhub and run it using the docker run command.<\/p>\n\n\n\n
Pull an nginx image<\/h2>\n\n\n\n
In this session, we will be pulling an Nginx image from the dockerhub. More information about the Nginx image can be found here<\/a>.<\/p>\n\n\n\n
Run the below command to pull an Nginx image<\/p>\n\n\n\n
docker pull nginx\nUsing default tag: latest\nlatest: Pulling from library\/nginx\n69692152171a: Already exists\n30afc0b18f67: Pull complete\n596b1d696923: Pull complete\nfebe5bd23e98: Pull complete\n8283eee92e2f: Pull complete\n351ad75a6cfa: Pull complete\nDigest: sha256:6d75c99af15565a301e48297fa2d121e15d80ad526f8369c526324f0f7ccb750\nStatus: Downloaded newer image for nginx:latest\ndocker.io\/library\/nginx:latest<\/pre>\n\n\n\n
Verify if the image is by running the below command:<\/p>\n\n\n\n
docker images\nREPOSITORY TAG IMAGE ID CREATED SIZE\nnginx latest d1a364dc548d 3 weeks ago 133MB<\/pre>\n\n\n\n
Let’s run the Nginx image and forward the request to port 8080<\/p>\n\n\n\n
docker run --name mynginx -d -p 8080:80 nginx:latest\necdefe6d6e2661e8fc44a13d4f036fefefd2959658fa79c24d74eafe075bcd3a<\/pre>\n\n\n\n
goto http:\/\/localhost:8080 to access the Nginx web UI<\/p>\n\n\n\n
![\"what](\"https:\/\/naiveskill.com\/wp-content\/uploads\/2021\/06\/image-18.png\")
<\/figure>\n\n\n\nIf you are getting the above page, it means your Nginx setup is working as expected.<\/p>\n\n\n\n
Let’s run the below command and check if there is any container that gets created for the Nginx image<\/p>\n\n\n\n
docker ps\nCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES\necdefe6d6e26 nginx:latest \"\/docker-entrypoint.\u2026\" 2 minutes ago Up 2 minutes 0.0.0.0:8080->80\/tcp mynginx<\/pre>\n\n\n\n
There is one container named mynginx<\/strong> that is running for Nginx installation.<\/p>\n\n\n\n
Now we understand how to pull an image from the public dockerhub repo, let’s proceed further and understand how to pull an image from a private repo.<\/p>\n\n\n\n
docker pull from a private repo?<\/h2>\n\n\n\n
To pull an image from the private repo, first, you need to login into your git repo with your credentials.<\/p>\n\n\n\n
docker login\nLogin with your Docker ID to push and pull images from Docker Hub. If you don't have a Docker ID, head over to https:\/\/hub.docker.com to create one.\nUsername: naiveskill\nPassword:<\/pre>\n\n\n\n
Once you are logged in, you can run the below command to pull the image from the private repo.<\/p>\n\n\n\n
docker pull myrepo\/myimage<\/pre>\n\n\n\n
You can also specify the tag while pulling the image<\/p>\n\n\n\n
docker pull myrepo.com\/myimage:tag<\/pre>\n\n\n\n
I hope now you are comfortable with pulling and running a docker image. In the next session, we will understand another important concept related to docker pull which is image digest<\/strong><\/p>\n\n\n\n
docker image digest<\/h2>\n\n\n\n
Docker containers are basically present in the form of [namespace\/] followed by a tag. Docker digest is provided as a hash of a Docker image supported by the Docker v2 registry format. The sha256 generates the hash and is deterministic based on the image build.<\/p>\n\n\n\n
So instead of passing the image name, docker images can be directly run using digest<\/p>\n\n\n\n
To list down the image digest, type the below command:<\/p>\n\n\n\n
docker images --digests\nREPOSITORY TAG DIGEST IMAGE ID CREATED SIZE\nnginx latest sha256:6d75c99af15565a301e48297fa2d121e15d80ad526f8369c526324f0f7ccb750 d1a364dc548d 3 weeks ago 133MB<\/pre>\n\n\n\n
Now let’s try to run this image using digest<\/p>\n\n\n\n
docker run --name mydigestnginx -d -p 8081:80 nginx:latest@sha256:6d75c99af15565a301e48297fa2d121e15d80ad526f8369c526324f0f7ccb750\na4f6e3db8597712b9e6c9a3f17cda55c87a1fe259af56183080859fe182d5fed<\/pre>\n\n\n\n
go to http:\/\/localhost:8081 to access the Nginx web UI.<\/p>\n\n\n\n
To get more information about the image digest, go to this link<\/a>.<\/p>\n\n\n\n
where does docker pull stores images?<\/h2>\n\n\n\n
When you pull an image from the dockerhub, the images will be downloaded into your system and reside in memory. The next question that might come to your mind is where the images get stored on a hard disk.<\/p>\n\n\n\n
So the images stored in your system are based on the OS on which the docker is running. Please find below the image path for different operating systems:<\/p>\n\n\n\n
Ubuntu: \/var\/lib\/docker\/
Fedora: \/var\/lib\/docker\/
Debian: \/var\/lib\/docker\/
Windows: C:\\ProgramData\\DockerDesktop
MacOS: ~\/Library\/Containers\/com.docker.docker\/Data\/vms\/0\/<\/p>\n\n\n\nConclusion<\/h2>\n\n\n\n
I hope you have found this article useful. We have started with the basics of dockerhub, and we deep dive into the docker pull command. We also pulled and ran hello-world and Nginx images from the dockerhub. And finally, we understood what image digest is and where the docker images save on disk. Please do let me know in the comment box if you need more clarification on any topic.<\/p>\n\n\n\n
More to read?<\/h2>\n\n\n\n
Docker layers<\/a><\/p>\n\n\n\n
Which docker base image to use<\/a><\/p>\n\n\n\n