In order to persist application data, containerized applications need to mount data volumes. In this video, learn how to design Dockerfiles with data volumes.
- Any files stored inside a container cease to exist when the container itself ceases to exist. You can't easily move the data across systems. As the files are written into the host machine where the container is running. What's more writing to the containers are writable layer requires you to use storage drivers, which we can see our performance. That's fair volumes come in. Volumes are the best practice for writing and accessing data at runtime. Volumes are accessed outside of the lifecycle of the container, meaning that volumes can be shared between containers. Volumes can be used as an external state from the application point of view, usually to use volumes for any persistent data needs. A volume can be local to the Docker hosting environment, such as data discs in the devil of a computer. Volumes could also be remote connections such as to file shares or two cloud providers. Some volume types provide even encryption out of the box. Volumes can be shared across containers, and they exist even when all containers using them are deleted. container applications can connect to existing volumes or create new volumes when needed. The volumes can be mounted as writable or read-only depending on the application needs. New volumes can even be automatically filled with prepopulated data.
Learn more about the AZ-400 exam at https://docs.microsoft.com/en-us/learn/certifications/exams/az-400.
- Building and running Dockerfiles
- Mounting data volumes
- Creating an Azure Container Registry
- Running apps from ACR
- Deploying ACR apps in ACI
- Creating AKS clusters
- Deploying apps to AKS