[girvo]

Hey, funny, I've spent the last two days doing something like this.

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.

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?

[shykes]

For what it's worth we (Docker maintainers) are working on adding this feature :) In the meantime you can use something like supervisord or runit inside your container.

[girvo]

Yeah runit is the way I think I'm going to tackle it! Cheers :)

Looking forward to it being a feature in the future. I truly think that it's a killer app for us web devs: being able to have a container setup for development, and being able to re-use it for super easy testing and one-click deployment without all the futzing around? Yes please!