
Status: Downloaded newer image for mysql:latest Our docker pull command will get the layers of the images from the blob store and automatically create the image using the manifest file: …ĭigest: sha256:1c75ba7716c6f73fc106dacedfdcf13f934ea8c161c8b3b3e4618bcd5fbcf195 Usually, the images are distinct layers tightly coupled in an ordered form as described in the manifest file. Let's pull the official MySQL image from Docker Hub using the docker pull command: $ docker pull mysql:latestĬ2920c795b25: Downloading 105.6MB/107.8MB Latest Tag – Unless we have any reservations on the MySQL version, we can go with the latest version available in the repository.Official Image Stamping – These are more secure and curated images from the MySQL developer team.

There are two points we should consider when choosing which version of an image to pull from the Docker Hub: We can simply build a container based on the MySQL image pulled from the Docker Hub. Now, let’s bring the MySQL server instance into Docker.
