Simplifying Docker on OS X • Hacker News Board

Re: Simplifying Docker on OS X

#11

Post by shlant » Mon, Jan 25, 2016, 8:12 PM UTC

From someone who has wasted many hours trying to get B2D working, I have ended up using https://github.com/codekitchen/dinghy

Easier to use, more reliable and some nice features like the OPs .docker DNS and NFS shares. The maintainer is very responsive and I recommend it to anyone who is struggling with docker on OSX.

Re: Simplifying Docker on OS X

#12

Post by Diederich » Mon, Jan 25, 2016, 8:13 PM UTC

mr337 wrote: post #7

corybrown wrote: post #2

Pretty cool trick to make the OS X docker hacks feel transparent. I've been tempted into getting a Linux laptop just because using Docker on OS X feels so hacky.

I did and never looked back. Lenovo X1 Carbon Gen 3

Been using Linux on my work macbooks since 2009. There are some bumps involved, but it works really well on the awesome Apple hardware.

Re: Simplifying Docker on OS X

#13

Post by beat » Mon, Jan 25, 2016, 8:15 PM UTC

I used to struggle with this. Then I set up a Vagrantfile and put my docker code in a Vagrant instance. It's just far and away better than any other hack I've tried. File mount point transparency problems? Solved!

Re: Simplifying Docker on OS X

#14

Post by heurist » Mon, Jan 25, 2016, 8:21 PM UTC

`eval $(docker-machine env docker)` is great, I can stick it in scripts and separate my development environment from testing, staging, and production for every project I need to track. It works on Windows, OS X, and Linux so all my developers can use whatever OS they want and I still have one platform-agnostic environment setup script that gets people up and running in less than 15 minutes. The only problem with docker-machine is you can't share environments without copying over the entire machine configuration, which is somewhat baffling in the case of EC2 machines but is by no means a deal-breaker.

Re: Simplifying Docker on OS X

#15

Post by ossreality » Mon, Jan 25, 2016, 8:25 PM UTC

So, now your OS X scripts are basically non-portable, (worse really). All to save exporting a variable?

And now I'm ALWAYS running a Linux VM no matter why I logged into my Mac?

Solution in search of a problem.

Re: Simplifying Docker on OS X

#16

Post by e40 » Mon, Jan 25, 2016, 8:27 PM UTC

sneak wrote: post #4

Docker does run natively on OSX. Just forward a port with ssh/socat/etc and set the environment variable correctly to point to your build host that can run lxc. There is so much over-engineering going on in this arena. :/

There is no definition of "native" where your statement is true.

Re: Simplifying Docker on OS X

#17

Post by beat » Mon, Jan 25, 2016, 8:27 PM UTC

corybrown wrote: post #2

Pretty cool trick to make the OS X docker hacks feel transparent. I've been tempted into getting a Linux laptop just because using Docker on OS X feels so hacky.

Just use Vagrant! Start a Vagrant VM on your Mac and do the Docker stuff inside it.

Re: Simplifying Docker on OS X

#18

Post by abhv » Mon, Jan 25, 2016, 8:27 PM UTC

So I imagine the solution is using xhyve to run a simple linux.

Why is the xhyve virtualization framework through low-level go-bindings better than using VirtualBox for the same task?

Re: Simplifying Docker on OS X

#19

Post by corybrown » Mon, Jan 25, 2016, 8:32 PM UTC

Diederich wrote: post #12

mr337 wrote: post #7

Earlier quoted context omitted.

I did and never looked back. Lenovo X1 Carbon Gen 3

Been using Linux on my work macbooks since 2009. There are some bumps involved, but it works really well on the awesome Apple hardware.

How's the battery life?

Re: Simplifying Docker on OS X

#20

Post by biehl » Mon, Jan 25, 2016, 8:34 PM UTC

abhv wrote: post #18

So I imagine the solution is using xhyve to run a simple linux. Why is the xhyve virtualization framework through low-level go-bindings better than using VirtualBox for the same task?

It is more light-weight?