Docker desktop volume location drivers#
You can view all info about a container with docker inspect, which shows the filesystem drivers and data, as well as all the existing mounts and volumes.
Docker desktop volume location driver#
Docker’s storage is complicated, and actually varies wildly depending on what storage driver it’s using. However, touching this data is likely a bad idea.
Whenever you pull an image from the internet, it’s downloaded and stored, usually forever. Images store the entire contents of the image on your drive. Each container will have its own file system, optionally created with “volume mounts” that bind data from the host to the container. You might have multiple containers running in parallel off the same image. You can think of them like ISO files for a virtual machine operating system.Ĭontainers are created from images, and they’re like the actual virtual machine that runs the application. Images are what you create when you run docker build they’re stored in a container registry like the Docker Hub, and contain all the files and code to run an app. The Difference Between Images and Containers
We’ll talk about the commands Docker provides for handling data, and how you can use them to access image and container files.
Docker uses two kinds of formats to represent running processes-images, and containers, and both store data on your computer’s drive.