In the example, which host directory maps to the container's MySQL data directory?

In the example, which host directory maps to the container's MySQL data directory?

• A. /var/dbfiles mapped to /var/lib/mysql
• B. /var/lib/mysql mapped to /var/dbfiles
• C. /var/dbfiles mapped to /var/data
• D. /var/data mapped to /var/lib/mysql

Answer: (A)

Persistent storage for a containerized MySQL instance relies on mounting a host directory to the container’s data directory. The MySQL data inside the container lives at /var/lib/mysql, so to persist it on the host you map a host path to that container path. Mapping /var/dbfiles on the host to /var/lib/mysql inside the container ensures all MySQL data files are stored under /var/dbfiles on the host, while the container continues to use /var/lib/mysql for its data. The other options either place the data in the wrong location inside the container, swap the host and container paths, or map to a different directory that isn’t the MySQL data directory, which would not persist MySQL data correctly.

Persistent storage for a containerized MySQL instance relies on mounting a host directory to the container’s data directory. The MySQL data inside the container lives at /var/lib/mysql, so to persist it on the host you map a host path to that container path. Mapping /var/dbfiles on the host to /var/lib/mysql inside the container ensures all MySQL data files are stored under /var/dbfiles on the host, while the container continues to use /var/lib/mysql for its data. The other options either place the data in the wrong location inside the container, swap the host and container paths, or map to a different directory that isn’t the MySQL data directory, which would not persist MySQL data correctly.