Can someone please explain what is the purpose of this. Why dockerize a python app vs. just running on a Linux instance. Also, do you get forever hooked on Amazon services in the process?
Hey, funny, I've spent the last two days doing something like this.<p>We have a large Laravel app that we've created, and want to run CI/CD on it, along with acceptance tests (all in Strider CD). The thing is, it has some annoying outdated dependencies, and I need a way to spin up an actual instance of our app, with MySQL, Apache and everything else to be able to run Huxley and Selenium on it.<p>So, I turned to Docker! I'm nearly at a point where we can just do a `docker pull <appname>` and then run the commands we want to from there, but I'm not there yet. It's really interesting, although the focus on "single process that runs in the foreground" stumps me a little. I'd love a way to running `httpd` and other services in the background, but still use `docker run /var/www/vendor/bin/phpunit` -- anyone got any luck doing something similar?
Here is a real world example of a run command to set up MongoDB[<a href="http://docs.docker.io/examples/mongodb/" rel="nofollow">http://docs.docker.io/examples/mongodb/</a>] with docker that shares a common db located on the host dir "/srv/pool/db" in my scenario.<p><pre><code> MONGO_ID=$(sudo docker run -d -v /srv/pool/db:/srv/data/db:rw jradd/mongodb)
</code></pre>
Same usage can apply to postgres, mysql, redis, etc…