Ask HN: Best practices for OS X dev environments

Re:Ask HN: Best practices for OS X dev environments by mateuszf on Saturday February 14, 2015 @09:09AM (#9049660)

It's called Docker.

[ Parent | on HN ]

Re:Ask HN: Best practices for OS X dev environments by keslag on Saturday February 14, 2015 @09:32AM (#9049708)

Docker just spins up a VM on OS X with boot2docker so you don't get any real benefit here.

[ Parent | on HN ]

Re:Ask HN: Best practices for OS X dev environments by ithkuil on Saturday February 14, 2015 @10:42AM (#9049902)

Yep, although it creates only one you can run a bunch of containers in it.

It feels almost as a native support, but the hack is betrayed by the networking setup.

I wish it would be possible to just expose ports on the real localhost.

[ Parent | on HN ]

Re:Ask HN: Best practices for OS X dev environments by keslag on Saturday February 14, 2015 @07:09PM (#9051249)

Absolutely, I should have specified 'a single vm' in my response. I didn't understand that when I was first trying to understand boot2docker, and now I'm using imprecise language to help confuse others. Thanks for clarifying.

[ Parent | on HN ]

Re:Ask HN: Best practices for OS X dev environments by Jean-Philipe on Saturday February 14, 2015 @09:38AM (#9049728)

Docker is not a VM and only works on Linux.

[ Parent | on HN ]

Re:Ask HN: Best practices for OS X dev environments by billdstrong on Monday February 16, 2015 @02:58AM (#9055813)

boot2docker is a commandline interface to docker that works on Windows, Mac and Linux. (Maybe *BSDs too.)

On non Linux systems, it downoads a prebuilt VM, and runs it with Virtualbox.

This is how Docker currently works on other OSes.

[ Parent | on HN ]