What happens when you put your app in a Docker container
Docker registry: how your image gets to the server
You build a Docker image on your laptop. It has to run on a server that you may never touch. How does the image get there? And where did the Python inside it come from?
-
1
In fact, one image already made that trip. During the build, the base image with Python came down to your laptop from a shared store of images on the internet, called a registry.
-
2
Yours can take the same road, the other way. You give it a name and a version label called a tag, here 1.0. Then
docker pushsends a copy up to the registry, and your laptop keeps its own. -
3
Over on the server,
docker pullasks the registry for the same name and tag. A copy comes down, and now the server has your image too. -
4
Rono is glad to see it there, with everything your app needs inside. Yet nothing runs, because nobody has started the image.
-
Quick check
Before the show, you see a spelling mistake on the request page.
Show the answer
No. The new image is only on your laptop. You push it to the registry, and then the server pulls it.
-
Go further
The registry you used, and a few words that go with it.