Bummer! This is just a preview. You need to be signed in with a Basic account to view the entire video.
Start a free Basic trial
to watch this video
Docker packages apps into a single unit, called an __image__. When these images are run via Docker, they're called containers, where a single container is an instance of an image. It's possible to run many containers based on a single image.
-
0:00
Docker packages apps into a single unit called an image.
-
0:04
When these images are run via Docker they're called containers.
-
0:08
Where a single container is an instance of an image,
-
0:11
it's possible to run many containers based on a single image.
-
0:15
You can think of a container as a shipping container, just like you'd see on ships.
-
0:20
Within each shipping container could be many different kinds of contents.
-
0:24
But because they're all uniform in shape,
-
0:26
they can all be handled the same way even though their content is different.
-
0:31
Usually the contents of a container are related in some way and
-
0:34
will be delivered to the same location.
-
0:36
In Docker, the contents of a container come together to form a singular unit
-
0:41
that represents an app, service, website or any single piece of software.
-
0:46
Docker packages the programs, services, and libraries your app depends on in to
-
0:50
an image along with your instructions on how to run it.
-
0:54
And the environment it should run in.
-
0:56
This all gets taken by docker and run on the host machine as a container.
-
1:00
An image is a mutable file that essentially a snapshot of a container.
-
1:05
They're created with the build command.
-
1:07
And they produce a container when started with the run command.
-
1:11
Images can be stored in the Docker registry, which is like a GitHub for
-
1:15
Docker images.
-
1:16
Then they could be retrieved later on the system where you wanna deploy them.
-
1:20
Because images can become pretty large,
-
1:22
they're designed to be composed of layers of other images.
-
1:26
That means, we only have to send small amounts of data over the network
-
1:29
when transferring images.
-
1:31
To make all this magic happen, Docker uses three major components.
-
1:35
The Docker daemon, which is a process running on your host OS.
-
1:39
Docker registries,
-
1:41
which are servers daemons connect to in order to retrieve images they need.
-
1:45
And the Docker client, which issues commands to the Docker daemon.
-
1:50
The Docker daemon coordinates running containers, packaging images and
-
1:54
transferring images to and from registries.
-
1:56
The Docker command line interface or client is what you see.
-
2:00
The client is where you run commands on the host machine.
-
2:03
To spin up new Docker containers, build Docker files into images,
-
2:07
monitor running containers and many other tasks.
-
2:10
Docker registries store Docker images.
-
2:13
We talked about Docker hub earlier which is the public registry anyone can use.
-
2:18
The Docker tools are configured to talk to Docker hub by default.
-
2:22
But that's just one of the available registries.
-
2:24
Docker cloud is another one.
-
2:26
And you can run a private registry on your company's own servers if you want.
-
2:30
If you run a Docker pull command using the Docker client,
-
2:33
the Docker daemon will connect to a Docker registry, retrieve an image, and
-
2:38
store it on the Docker host machine.
-
2:40
When you use the Docker run command,
-
2:42
the Docker daemon launches a copy of a locally stored image as a new container.
-
2:47
You can even run your own private registry within your organization.
-
2:50
Which allows you to manage your company's images without pushing them to the public
-
2:54
Docker registry.
You need to sign up for Treehouse in order to download course files.
Sign up