Why splitting the data container from the database container is better than setting the data size from disk

As such, it is very common for the docker community to split the data container from the database container that is using that data. The main reason I've heard is that if you need to update the database, you can access the same data from the new database container. I am trying to understand why this is better than just mounting the volume from disk to the database container, and if you upgrade the container, mount the same volume to the new database container. These processes are basically the same thing. Is there any use case I can't see?


This link tries to explain the benefits, but still, the same can happen with installation volumes.


source to share

1 answer

You can --link

in (or attach

in) the data container, even after dropping the database container. This decouples the lifecycle of the (bindable) data container from the lifecycle of the database container.



All Articles