You should see something like this: REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZEĪlpine latest 3e467a6273a3 3 weeks ago 4.797 MB We can verify this is the case by listing the local images: $ sudo docker images Once the command completes, you should have the nginx image in your local machine, being managed by your local Docker engine. On the Docker Hub, you can see the descriptions of Docker images and take a look at their Dockerfiles, which contain the instructions that tell Docker how to build the image from the source.
When you run this command, Docker will attempt to pull the nginx image from the Docker Hub, which is a bit like GitHub but for Docker images. Let's imagine we want to pull a Docker image from a registry, like so: $ sudo docker pull nginx Check out the official docs for how to install Docker on Linux, or our previous post showing how to install Docker on a non-Linux machine. You will need Docker installed locally on your machine if you want to try out some of the commands in this post. In this post, I'll take a broad look at a few of them, including: image storage, the copy-on-write mechanism, union file systems, storage drivers, and volumes. There are lots of places inside Docker (both at the engine level and container level) that use or work with storage. With their kind permission, we are sharing it here for Codeship readers. This article was originally published on Deis by Eddy Mavungu.
