Re:Day 21: Docker – The Missing Tutorial
by BHSPitMonkey on Monday November 18, 2013 @04:02PM
(#6756998)
My understanding is that keeping your database in a separate container from your application(s) is a more preferred topology. In theory, you could easily spin up/spin down application containers as needed, and they can use Docker's service discovery features to automatically become aware of which port the database is listening on.
At first, I was confused too. So I asked on the ML. See [1] and continuation in [2]. You could also browse the docker-user list, there are a number of threads asking to clarify various concepts about Docker.
[1]: https://groups.google.com/d/msg/docker-dev/OcpLrYti64Q/Ue6vP... [2]: https://groups.google.com/d/msg/docker-user/4acVRnOd9Dw/RZRc...
Though I'm still confused on -
Real world examples of tried and proven setups like an environment of Apache, PHP, and MySQL being run inside a Docker container (for example: for setting up shared hosting on a box). Would that even make sense?