3 ms·
We use docker for: - running graphite (can't say it was less pain launching it, since Dockerfile was outdated a bit, and I also had to additionally figure out
by k_bx 12y ago
We use docker for:
- running graphite (can't say it was less pain launching it, since Dockerfile was outdated a bit, and I also had to additionally figure out persistency issues, but overall I'm happy it's all virtualized and not living on server itself)
- building our haskell projects for specific feature (your run a container per feature, this way you omit pain switching between features when you need to build one)
- running tests (per each feature we start container with whole infrastructure inside (all databases, projects etc.))
- running staging, also container per feature
Very useful stuff, comparing to alternatives, I should say. And quite easy to work with after you play a bit with docker's api.
- rev_bird 12y agoSo you're using containers in only staging? I can see why it would be appealing, but have you run into complications with staging being structured so differently from production?
- k_bx 12y agoI had no problems with staging being different than production (which is kind of multi-machine multi-environment rather than "everything in one docker"), because it all uses same fabric scripts and supervisor configs for deploy and maintainance.
- markcartertm 12y agoIn VMware, we use Docker for automated build and test of several of open source efforts as well as for a production IT business management mobile cost analysis SaaS offering we provide. Docker has demonstrated value in ensuring the app remains consistent across environments. I'm very interested in feedback from any of you on what VMware can do to make Docker CI and Docker production use easier in general and on vSphere, fusion and vCloud Air. We are engaged with Docker and the open source projects and would love to hear your feedback. Please email me at carterm at vmware dot com with any feedback, comments or ideas. Thanks, Mark
- zwischenzug 12y agoInteresting that you say that the Dockerfile was out of date - I've found that this is a common problem; the vast majority I try are buggy.