How Does Docker Get Around the Networking Domain? Part 1
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
Already have an account? Sign In »
6 hours 56 minutes
hi and welcome to the fifth Money.
This is the first lesson.
Let's see what we are going to learn here.
Sort of begin with. We are going to learn what talker networks are,
and then we are going to learn the principles and check behind doctor networks.
You're also going to discuss the doctor network architecture,
and then we are going to take a look at the options available to us when using doctor networks
That's big in
containers. Use Net network name spaces.
And if you remember, we talked about how continues function in our first listen. And there we heard the term name spaces.
So Doctor networks used a component off these
for networking. Namely, they're called network name spaces. It's like virtual instances off network hardware or, in other words, interfaces.
Andi. They have. They each have their own independent grouting and even have their own five or rules. It's both a feature off containers and also limits to keep the networks isolated
on this otherwise told to do so.
So say that we start the container followed by another.
These two containers are by itself isolated unless told otherwise to do so.
But now, Doctor network support communicating to each other wire there continue names. So why, Dennis?
This feature will surely be tremendously beneficial once we see the uses off this when with the lessons to come.
So how do these name spaces name Space vice? Separated networks do the networking between them
and, if needed, with the host and the outside world.
They use what are called virtual even it devices,
which operate in full duplex mode.
If that was confusing for you, let me explain. It broke transmission modes very briefly.
half duplex and full duplex simplex packets go in one direction and never the other. So think off a one way ticket.
Half duplex packets go both ways, but only one direction at a time. So after transmission is done one way they allowed packets to go the opposite way to way ticket. But a plane can only take off or land at a given time. Never boat.
Full duplex packets go boat back and forth simultaneously to a ticket. And like modern airports, planes are constantly going back and forth, taking off and landing.
Now that we have got an idea off how doctor manages to get all of these networks and continues working seamlessly. Let's look at the architecture off which Docker operates.
It is called the Container Networking Model
or C N. P.
On There are a few terms associated with it.
first of all, we have what is called the sandbox.
A sandbox is where a particular container keeps it's configuration off the network stack,
and then we have.
endpoint is what connects a sandbox to a network, meaning it provides abstraction off the connection to the network so that containers have no need to figure out how to connect to the network off different types providing better portability,
as you can see here.
So that then there is the network.
Now, for those of you who are familiar with
the TCP I, p stack or the always I networking model
when we say, uh, networking,
it doesn't mean the same thing here. Here, a network means a collection of endpoints that have interconnectivity
so like this.
And if you observe this image here, you can see that
I mean, sure, you
you can see that
there are two drivers called network driver and the I P A M driver. The network driver here is just like one that comes with the Ethernet card on your WiFi adapter, and a doctor and doctor has a support for
a range of drivers so that they used given the situation. But when utilizing the network, only one driver can be picked.
Next we have the I. P A. I am driver or, if it's expanded Internet Protocol address management or I p address management drivers. These are responsible for things like submitting and the actual I'd be addressing off the containers
on Docker has been built in. Hence, they're able to provide eyepiece to containers and manage submit for containers.
So if you take
a look at the picture here again, you can see the components we referred to being illustrated here. We have a brief idea of how it all comes together, starting from the lower level, the drivers
on the docker engine sitting on top of it and then utilizing them, uh, utilizing the services for submitting an I P management and compatibility making those services available for the networks running on it and those networks providing services to the sandbox is connected
to them. Why, in points
ultimately giving the current continues that connectivity.
So that's what's goes inside off what the user sees in the next video. Let's take a look at what actually is available for users to utilize.