Master everything you need to know about Docker containers to easily create, deploy, and run your applications with containers.

DevOps for Developers

By now, you've probably heard the buzz around Docker. It's fundamentally changed the development process and been adopted by software teams of all sizes, and for good reason: Docker makes it considerably easier to create, deploy, and run applications with the use of containers.

Docker is here to stay, and is becoming one of the most in-demand technologies on the market. Mastering it now will help you produce better software, level up your career, and stand out from the crowd. Get started today.

Docker for Developers

When a container writes files, it writes them *inside* of the container. Which means that when the container dies (the host machine restarts, the container is moved from one node to another in a cluster, it simply fails, etc.) all of that data is lost. It also means that if you run the same container several times in a load-balancing scenario, each container will have its own data, which may result in inconsistent user experience.

A rule of thumb for the sake of simplicity is to ensure that containers are stateless, for instance, storing their data in an external database (relational like an SQL Server or document-based like MongoDB) or distributed cache (like Redis). However, sometimes you want to store files in a place where they are persisted; this is done using volumes.

Using a volume, you map a directory inside the container to a persistent storage. Persistent storages are managed through drivers, and they depend on the actual Docker host. They may be an Azure File Storage on Azure or Amazon S3 on AWS. With Docker Desktop, you can map volumes to actual directories on the host system; this is done using the *-v* switch on the *docker run* command.





In this lesson, you will learn how to use volumes to prevent data loss.

Using Volumes