Deployed 1f92693 with MkDocs version: 1.1.2

This commit is contained in:
github-actions
2022-09-25 13:54:31 +00:00
parent a90a6a5cf0
commit 5f558dc3f7
4 changed files with 6 additions and 8 deletions

View File

@@ -2227,13 +2227,13 @@ Docker images are present as layers on top of the base layer. These layers are t
<p><a href="https://github.com/docker/labs/blob/master/beginner/chapters/webapps.md">Creating and containerizing a basic Flask app</a></p>
</li>
</ol>
<p>Here is another <a href="https://www.katacoda.com/courses/docker/2">beginner level lab</a> from Katacoda for dockerizing a node js application. You dont even need a local setup for this and its easy to follow along.</p>
<p>Here is another <a href="https://github.com/docker/awesome-compose/tree/master/react-express-mongodb">beginner level lab</a> for dockerizing a MERN (Mongo + React + Express) application and its easy to follow along.</p>
<h2 id="advanced-features-of-docker">Advanced features of Docker</h2>
<p>While we have covered the basics of containerization and how a standalone application can be dockerized, processes in the real world need to communicate with each other. This need is particularly prevalent in applications which follow a microservice architecture. </p>
<p><strong>Docker networks</strong></p>
<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>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://dockerlabs.collabnix.com/beginners/volume/creating-volume-mount-from-dockercli.html">Docker lab</a> is a great place to start playing with volumes.</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>