The Complete Practical Docker Guide - MongoDB Data is Now Deleted after docker-compose Restart

The video tutorial explains how to create a MongoDB database and collection using Docker. It demonstrates stopping and removing Docker containers and networks, and then recreating them. The tutorial highlights the issue of data loss when containers are removed and recreated, and introduces the concept of using Docker volumes to persist data across container restarts.

What command is used to stop all running Docker containers?

• docker stop all

• docker shutdown

• docker compose down

• docker halt

What happens to the containers and network when the Docker compose down command is executed?

• They are completely removed

• They are restarted

• They are backed up

• They are paused

Why is the TMP database not present after restarting the containers?

• The database was not saved due to new container creation

• The database was moved to a different server

• The database was hidden

• The database was corrupted

What is the main reason for data loss when using Docker compose up after Docker compose down?

• Incorrect Docker commands

• New containers have new file systems

• Network issues

• Database errors

How can data be persisted in MongoDB across Docker container restarts?

• By using a different database

• By using Docker volumes

• By increasing container memory

• By using a backup script