Deployed 4b1c22e with MkDocs version: 1.1.2

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
 <p>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 <code>host</code> option allows sharing of network stack with the host, <code>bridge</code> allows communication between containers running on the same host but not external to the host, <code>overlay</code> facilitates interaction between containers across hosts attached to the same network and <code>macvlan</code> 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 <a href="https://docs.docker.com/network/">docker networks</a> itself is a good place to start.</p>
 <p><strong>Volumes</strong></p>
 <p>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 <a href="https://www.katacoda.com/courses/docker/persisting-data-using-volumes">KataKoda lab</a> is a great place to start playing with volumes.</p>
-<p><a href="https://linkedin.github.io/school-of-sre/orchestration_with_kubernetes/">In the next section</a> we see how container deployments are orchestrated with Kubernetes.</p>
+<p><a href="https://linkedin.github.io/school-of-sre/level102/containerization_and_orchestration/orchestration_with_kubernetes/">In the next section</a> we see how container deployments are orchestrated with Kubernetes.</p>