[justizin]

You can build a docker image in a vagrant VM on OSX and deploy that exact docker image to production.

If your vagrant image resembles production, it's probably fine, but there's a level of confidence to be reached from deploying the exact entire self-contained binary, shipping it through QA and staging, and eventually promoting it to production.

[trustfundbaby]

This should be made into an answer to the OP's question, because this is the use case that I think most people will wind up moving to docker for, if they do.

[pekk]

This is also a use case for not developing on OS X, which doesn't have anything to do with production anyway.

[mdaniel]

Can you clarify? Do you mean that one should only develop upon the platform that will be used in production?

[justizin]

Yes, the previous commenter is a purist with no battery life on their laptop.

Further, if you're in the middle of upgrading your production OS, does this mean that you need two developer machines?

C'mon!