Day 21: Docker – The Missing Tutorial(openshift.com)
openshift.com
Day 21: Docker – The Missing Tutorial
https://www.openshift.com/blogs/day-21-docker-the-missing-tutorial
11 comments
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...
[1]: https://groups.google.com/d/msg/docker-dev/OcpLrYti64Q/Ue6vP... [2]: https://groups.google.com/d/msg/docker-user/4acVRnOd9Dw/RZRc...
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.)
Is there any use for Docker in this case?
Is there any use for Docker in this case?
I think there's someone already working on this use case, check out: https://github.com/makinacorpus/salt/blob/develop/salt/state...
very interested to look at it - I'm trying to figure out between ansible and salt. Do you have your salt scripts on github somewhere ?
I'm not sure this is really the missing tutorial...it seems pretty much the same as the other tutorials I've read/watched.
Then again I've been working with docker a lot lately so maybe I was looking harder.
Then again I've been working with docker a lot lately so maybe I was looking harder.
> You can test the express application by curl as shown below.
I haven't seen one tutorial or piece of documentation that tells me how to access that app from my host machine.
I haven't seen one tutorial or piece of documentation that tells me how to access that app from my host machine.
wouldn't you just ssh into the container?
I meant from a browser.
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?