Does it make sense to package the database in a docker container?

Question

Docker

Hello, This is
the third day I've been fiddling with docker, I like it more and more, but in all the tutorials the ideal environment is considered: a clean system or already completely dockerized. What if the system has a long history? This is especially true for a dev machine. In the tutorials, it is advised to work with the database deployed inside the docker container.
How can I be:

1. On a dev machine, if there is already an under-kerned base that several old projects work with. Does it make sense to create a container with a base for a new project?
   
2. On hosting, if the database is running on a separate server. If so, is it necessary to create two containers for production and staging separately?
   

Thanks for the help.

Answer 1

Pack the DBMS itself into the docker, and connect the storage via volume. Otherwise, don't do it.
1) The question of necessity, if you need to have different DBMS on a dev wheelbarrow, I would dockerize them so that the daemon does not eat extra machine resources when they are not needed.
2) You can get by with one, connect volume ...