Docker Engine parts
The Docker Engine consists of two parts: a daemon, a server process that manages all the containers, and a client, which acts as a remote control for the daemon.Assignment
Check which version of Docker is running. This will verify that the daemon is running and that you can connect to it. If you can see the version number you know you are all set.Tips
docker
to see the full list of accepted arguments. This emulator provides only a limited set of shell and Docker commands, so some commands may not work as expected.
In this 10-minute tutorial, see how Docker works first-hand:
You'll search for and find an image another user built and shared in the Docker Hub Registry, a cloud-based collection of applications.
You'll download and run it - running images are containers - and have it output 'hello world'.
Then you'll install the 'ping' utility into the container, commit all your changes, and run a test of your updated image.
Finally, you'll push your image to the Docker Hub Registry so that other developers can find and use it...
...on a laptop, a VM in a data center, or a public cloud instance, without having to change anything at all about the image!