The Docker image can be seen as a read-only template for containers, specifying what's supposed to be installed, copied, configured, and exposed when a container is started.
We learned more about how we can interact with the Docker daemon and with individual Docker containers to read logs, copy files, and export the complete filesystem.
The Docker hub was introduced and we looked at what the official WordPress Docker image consisted of and how they configured the OS in the Dockerfile as well as in an ENTRYPOINT
file to some extent.
We downloaded and ran the WordPress image that failed as expected, and we fixed it by linking the required MySQL container to it.
In the next chapter, we will create a Dockerfile and publish a Docker image to the Docker registry hub so that we have a way to get our customized Docker images to wherever we decide to place our PaaS.