Search for a command to run...
Yusuf Adeyemo is a DevOps Engineer from Nigeria. He loves helping startups deliver better software and provide more control over their environment and software development process with the help of modern tools and automation.
No comments yet. Be the first to comment.
We’ve all been there. You spend hours perfectly tuning your OpenWrt configuration, setting up your captive portals, and hardening your firewall. Then, six months later, the system hangs. Why? Because
This article started from a tweet. Someone on Twitter said they "lowkey want to understand the technology behind Google Authenticator" and I dropped a quick reply - explaining that it's basically TOTP: your device and the server share a secret key, b...
Have you ever sat there waiting for your CodeBuild project to rebuild your entire Docker image... again? Even though you only changed a single line of code? Yeah, me too. And it's frustrating. Today, I'm going to show you how I reduced our Docker bui...
After you complete this article, you will have a solid understanding of: Why deploying Next.js SSR on Cloudflare is different from traditional hosting The real difference between Cloudflare Pages with next-on-pages and OpenNext adapter How the fre...
After you complete this article, you will have a solid understanding of: What L1, L2, and L3 constructs actually are and when to use each Why AWS created three different abstraction levels (and the hidden benefits) How to avoid the most common CDK...
Docker is a popular open-source containerization platform that allows users to package and deploy applications in lightweight containers. These containers are isolated from each other and provide a consistent environment for running applications, regardless of the host operating system.
One of the key features of Docker is the ability to use volumes to persist data generated by and used by Docker containers. In this article, we will explore what Docker volumes are, how they work, and how to use them with an example.
A Docker volume is a persistent storage location for data that is accessed by Docker containers. This data is stored outside the containers and is not deleted when the container is removed. This allows you to persist data generated by and used by your containers, even if the container itself is deleted.
Volumes are useful for a variety of purposes, including storing database data, configuration files, and other data that needs to be persisted outside the container.
When you run a Docker container, you can use the -v or --volume flag to specify a volume that should be mounted into the container. This flag takes the following format:
-v /host/path:/container/path This tells Docker to mount the host path /host/path into the container at /container/path. This means that anything written to the /container/path location inside the container will be written to the /host/path location on the host machine.
In addition to mounting host paths, you can also use Docker volumes, which are managed by Docker itself. To create a Docker volume, you can use the docker volume create command, like this:
docker volume create my-volume This will create a new Docker volume named my-volume. You can then mount this volume into a container using the -v or --volume flag, like this:
docker run -v my-volume:/container/path my-image This will mount the my-volume volume into the container at the /container/path location. Any data written to this location inside the container will be stored in the my-volume volume and will be persisted even if the container is deleted.
One common use case for Docker volumes is storing the data for a database. For example, suppose you want to run a MySQL database inside a Docker container. You could use a Docker volume to persist the data for the database, even if the container is deleted.
To do this, you would first create a Docker volume to store the database data:
docker volume create db-data Next, you would run the MySQL container and mount the db-data volume into it, like this:
docker run -v db-data:/var/lib/mysql mysql This will run the MySQL container and mount the db-data volume at the /var/lib/mysql location inside the container. This is the default location where MySQL stores its data, so any data written to this location inside the container will be written to the db-data volume on the host machine.
Even if the MySQL container is deleted, the data in the db-data volume will be persisted, and you can use it with a new MySQL container by simply mounting the volume into the new container.
In conclusion,
Docker volumes are a powerful and useful tool for managing data in Docker containers. They allow you to persist data generated by and used by your containers, even if the containers themselves are deleted. Volumes can be used to store a wide variety of data, including database data, configuration files, and more. By using Docker volumes, you can ensure that your data is persisted and easily accessible, even as you deploy and update your containers.
