From e4a4aafd04804bc149355264c58d700668036a9a Mon Sep 17 00:00:00 2001 From: github-actions Date: Wed, 4 Aug 2021 17:13:08 +0000 Subject: [PATCH] Deployed 4b1c22e with MkDocs version: 1.1.2 --- .../containerization_with_docker/index.html | 2 +- sitemap.xml.gz | Bin 225 -> 225 bytes 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/level102/containerization_and_orchestration/containerization_with_docker/index.html b/level102/containerization_and_orchestration/containerization_with_docker/index.html index 8bbf6e3..2e8a437 100644 --- a/level102/containerization_and_orchestration/containerization_with_docker/index.html +++ b/level102/containerization_and_orchestration/containerization_with_docker/index.html @@ -1625,7 +1625,7 @@ Docker images are present as layers on top of the base layer. These layers are t

Docker networks facilitate the interaction between containers running on the same hosts or even different hosts. There are several options provided through docker network command which specifies how the container interacts with the host and with other containers. The host option allows sharing of network stack with the host, bridge allows communication between containers running on the same host but not external to the host, overlay facilitates interaction between containers across hosts attached to the same network and macvlan which assigns a separate MAC address to a container for legacy containers are some important types of networks supported by Docker. This however is outside the scope of this module. The official documentation on docker networks itself is a good place to start.

Volumes

Apart from images, containers and networks, Docker also provides the option to create and mount volumes within containers. Generally, data within docker containers is non-persistent i.e once you kill the container the data is lost. Volumes are used for storing persistent data in containers. This KataKoda lab is a great place to start playing with volumes.

-

In the next section we see how container deployments are orchestrated with Kubernetes.

+

In the next section we see how container deployments are orchestrated with Kubernetes.

diff --git a/sitemap.xml.gz b/sitemap.xml.gz index c60c8bdeb3d678686aae7098ae1a432cdc3b4c93..b57890754e81e6cda8f4c042277cef93642a9392 100644 GIT binary patch delta 14 VcmaFJ_>hrJzMF$%@u`Vyw*e*u1!MpK delta 14 VcmaFJ_>hrJzMF$1==emo+W;hE1rPuL