Now, there was some use of data that we added to the MongoDB.
We created the new database DMP, and we added new collection data called Paracels.
And now there was a single document inside of this collection.
Now let's try to restart all containers and see whether after a start, this data will be present here
or not.
Let's go to the terminal.
Let's, first of all, Orion containers using Docker compose down command.
It will stop all four containers, Mongo Express front and the Mongo and the EPA.
This was done.
No containers are being removed.
They were removed.
Notice that this step means complete removal of the containers and corresponding network that Doga created
for communication between those four containers was removed as well.
And now there are no containers, one I could enter.
Docker be a command with option.
This eight the stance for all and output is empty.
There are no Niall Horan and no stopped containers recovered that before I removed.
All previously started containers inside of the Docker desktop.
Now let's go ahead and bring all containers up again.
Docker compose up and let's at option deep detached and notice that this comment will now create brand
new containers because at the moment there are no stop containers or containers were removed after Docker
compose down command.
Let's create brand new containers now.
Great, and can you network because it was removed as well?
Images gallery, the fold.
Creating new containers for all services, Mongo API front and Mongo Express.
All four containers away agree that let's verify that dog appeals, and here the you know, let's go
back to Mongo Express to its graphical user interface and check whether Typekit database is present
here or not.
Let's simply refresh page here.
And I see no DNA database here in this list.
And this very reasonable list, no go to Docker compose file and there are I'll explain to you what
actually happens right now and why we don't see any DMP database here anymore.
Let's go here and recap that we added more on groceries like that.
We simply specified image.
It is more an official image and global of environment variables.
That's it.
And we just seen the Docker compose after bringing down all containers and bringing them up afterwards
creates brand new containers.
Here they are at this moment of time and all those containers that are created from scratch.
Of course, new container IDs, new file systems, and so on.
Everything is new and this way after Docker compose down and Docker compose up commands Mongo container.
Here's actually initial contents of the Mongo image, and there was no custom use of data that we created
before in the previous container because this container that we see right now is completely different
from the container that was running before where we created DMB database.
This very important to understand it means that now we are not persistent data in the Mongo database.
And each time when you create new containers using Docker compose up after Docker compose down command,
Mongo database will be created from scratch.
But of course, if you want to process data, it's possible to achieve that.
And for that, we could use custom volume that we will create inside of the Docker and map.
This custom volume does a Mongo container, and let's do that after the small break.