This document discusses using named volumes with Docker containers to manage data. It outlines creating a MySQL container with a volume named "mysql-db" to store database data, adding data to the database, stopping and removing the container, and then starting a new MySQL container with the existing "mysql-db" volume to verify that the data persists across containers. The goal is to demonstrate how named volumes allow database upgrades while preserving user data.
This document discusses using named volumes with Docker containers to manage data. It outlines creating a MySQL container with a volume named "mysql-db" to store database data, adding data to the database, stopping and removing the container, and then starting a new MySQL container with the existing "mysql-db" volume to verify that the data persists across containers. The goal is to demonstrate how named volumes allow database upgrades while preserving user data.
This document discusses using named volumes with Docker containers to manage data. It outlines creating a MySQL container with a volume named "mysql-db" to store database data, adding data to the database, stopping and removing the container, and then starting a new MySQL container with the existing "mysql-db" volume to verify that the data persists across containers. The goal is to demonstrate how named volumes allow database upgrades while preserving user data.
➤ Create mysql container with some specific version with Volume named mysql-db ➤ After Starting the Container Verify Container Status ➤ Go to Database and Create Some Data ➤ Stop and remove the Container ➤ Strat new MqSQL Container with existing Volume and Verify the Data. Will see you in Next Lecture…