hope 1.3 will be soon in the homebrew, we're migrating tomorrow to docker and all of our office is OSX. that is regarding new standard folder sharing feature.
Your entire office is OS X and you're migrating to a Linux-only non-portable technology stack that requires a VM to run on your desktop?
Is this really cheaper and more effective than cleaning up your code base so that it doesn't require complete ownership of the host environment in order to run?
Why assume that they are using Docker because they have a portability problem?
They probably like OS X as a workstation OS, and want to use Docker for the DevOps benefits that they gain from it. boot2docker is just a lightweight solution for running Docker locally.
...maybe I'm confused... Is your premise that they will only run their application/service internally?
Normally what I've seen is, develop on OSX and then push to Heroku (Linux) / <infrastructure provider of choice, running a Linux VM>. Why then wouldn't the natural progression be, develop in boot2docker and push to <docker PASS of preference>?
But almost always the module or service that you work on relies on other services and datastores. boot2docker can help you pull down an entire stack to your workstation and not rely on connecting to an external network. You can essentially work on Airplane mode.
Or, you can architect your module/service to run the things it depends on in a self-contained manner and avoid creating a hard dependency on virtualization of Linux.
Comments
hope 1.3 will be soon in the homebrew, we're migrating tomorrow to docker and all of our office is OSX. that is regarding new standard folder sharing feature.
Your entire office is OS X and you're migrating to a Linux-only non-portable technology stack that requires a VM to run on your desktop?
Is this really cheaper and more effective than cleaning up your code base so that it doesn't require complete ownership of the host environment in order to run?
Why assume that they are using Docker because they have a portability problem?
They probably like OS X as a workstation OS, and want to use Docker for the DevOps benefits that they gain from it. boot2docker is just a lightweight solution for running Docker locally.
...maybe I'm confused... Is your premise that they will only run their application/service internally?
Normally what I've seen is, develop on OSX and then push to Heroku (Linux) / <infrastructure provider of choice, running a Linux VM>. Why then wouldn't the natural progression be, develop in boot2docker and push to <docker PASS of preference>?
Why would you want to "develop in boot2docker" ?
Developing an app in boot2docker is questionable.
But almost always the module or service that you work on relies on other services and datastores. boot2docker can help you pull down an entire stack to your workstation and not rely on connecting to an external network. You can essentially work on Airplane mode.
Or, you can architect your module/service to run the things it depends on in a self-contained manner and avoid creating a hard dependency on virtualization of Linux.
Looks like it's almost there https://github.com/Homebrew/homebrew/pull/33225