Re:Day 21: Docker – The Missing Tutorial
by powertower on Monday November 18, 2013 @03:46PM
(#6756877)
Out of the 10 or 20 posts about Docker that made it to front-page on HN in the last year, this is the first one that has been able to show me what Docker is.
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?
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.
Re:Day 21: Docker – The Missing Tutorial
by alco on Monday November 18, 2013 @05:56PM
(#6757908)
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.
Re:Day 21: Docker – The Missing Tutorial
by chrishenn on Monday November 18, 2013 @02:21PM
(#6756263)
How do provisioning systems compare to Docker? Right now I have a development environment that consists of salt stack provisioning Vagrant. Spinning up a production server just means running salt on the host (Rackspace, DO, whatever.)
Re:Day 21: Docker – The Missing Tutorial
by Sikul on Monday November 18, 2013 @06:45PM
(#6758158)
A container can expose ports that the application is running on to the host. For instance, one of my web server containers might expose 9000 to the host. You could access 9000 directly from the host or you can setup nginx to forward 80 to 9000 if that's what you want. Something like that.
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?
[1]: https://groups.google.com/d/msg/docker-dev/OcpLrYti64Q/Ue6vP... [2]: https://groups.google.com/d/msg/docker-user/4acVRnOd9Dw/RZRc...
Is there any use for Docker in this case?
Then again I've been working with docker a lot lately so maybe I was looking harder.
I haven't seen one tutorial or piece of documentation that tells me how to access that app from my host machine.