Live data from Hacker News

Docker for Mac Beta Review

medium.com

11–20 of 367 posts

Re: Docker for Mac Beta Review

#11
post #5

Earlier quoted context omitted.

VirtualBox and VMWare are hardly "tiny." I've never had a good experience with VirtualBox on any platform. Thing is constantly broken and endlessly updated to break in newer, less Google-able ways and just causes never-ending grief in unexpected places for me.

By contrast, I've never once had an issue with VirtualBox. Vagrant and VirtualBox are my best buddies.

I know who I'm inviting to Vegas next trip. Assuming you haven't used up all your luck. https://www.virtualbox.org/wiki/Changelog

Re: Docker for Mac Beta Review

#12

Why do people value that so much? I really don't care if a tiny VMis running in the background. Also, running that VM gives me more confidence that it will also run on the production machine (since they use the same kernel and the same docker version). The only problem I had with docker was that I did not use to support shared volumes that are outside the home folder on Mac (I think they changed that now, but I'm not…

Running a VM means you have to allocate X amount of RAM regardless if how much is actually needed by the containerized processes.

Re: Docker for Mac Beta Review

#14
Same experience here, both on Mac and Windows. They've done a great job making it "just work". The user interface pieces are a bit raw -- perhaps "minimalist" or "unobtrusive" would put that in a better light! -- but clearly most of the work has gone into the lower level integration, where it shines.

Docker for Mac/Windows, once released, will nuke the ick factor on those platforms from orbit, which can only lead to even more adoption.

Re: Docker for Mac Beta Review

#15
post #5

Earlier quoted context omitted.

VirtualBox and VMWare are hardly "tiny." I've never had a good experience with VirtualBox on any platform. Thing is constantly broken and endlessly updated to break in newer, less Google-able ways and just causes never-ending grief in unexpected places for me.

By contrast, I've never once had an issue with VirtualBox. Vagrant and VirtualBox are my best buddies.

I've had some problems with Virtualbox but I was able to overcome them. I'm sure that using Docker will be much the same.

Re: Docker for Mac Beta Review

#16
post #6

I'm a node.js developer. I understand the benefit of using docker for deployments or CI testing, but I have yet to be convinced of the benefits of using it for development on my local machine. I install node, postgres, and redis natively and it all works fine. What benefits does docker provide to my workflow?

Wait, not even another kind of VM? Have you ever had to work with a team that has an unreliable environment? And had to walk them through debugging an error message for installing one of them, or wanted to add something with further dependencies?

(Not to say Docker's immune from that; the sudden deprecation of docker-compose for docker-machine was a nasty surprise.)

Re: Docker for Mac Beta Review

#17
post #12

Why do people value that so much? I really don't care if a tiny VMis running in the background. Also, running that VM gives me more confidence that it will also run on the production machine (since they use the same kernel and the same docker version). The only problem I had with docker was that I did not use to support shared volumes that are outside the home folder on Mac (I think they changed that now, but I'm not…

Running a VM means you have to allocate X amount of RAM regardless if how much is actually needed by the containerized processes.

You're still running a VM with Docker for Mac/Windows. It's just beautifully integrated and focused on the use case.

Re: Docker for Mac Beta Review

#18
post #6

I'm a node.js developer. I understand the benefit of using docker for deployments or CI testing, but I have yet to be convinced of the benefits of using it for development on my local machine. I install node, postgres, and redis natively and it all works fine. What benefits does docker provide to my workflow?

installing them natively is clunky, they are managed in all different ways depending on how you install them. They need to started and stopped manually. You also are turning your machine into a "snowflake" with unique combinations of os and service versions.

With docker, you can make a dockerfile for your project and make it painless and consistent to run anywhere. You can also create a docker-compose file if you need other services like redis. It really is the holy-grail once it clicks.

Re: Docker for Mac Beta Review

#19
post #12

Why do people value that so much? I really don't care if a tiny VMis running in the background. Also, running that VM gives me more confidence that it will also run on the production machine (since they use the same kernel and the same docker version). The only problem I had with docker was that I did not use to support shared volumes that are outside the home folder on Mac (I think they changed that now, but I'm not…

Running a VM means you have to allocate X amount of RAM regardless if how much is actually needed by the containerized processes.

You're still running a VM with this, just via xhyve and the OSX Hypervisor framework, rather than via Virtualbox or VMWare.

Which actually makes me wonder how they're managing memory for the VM hosting Docker here. Are they specifying a set fixed allocation? Is memory usage configurable somewhere?

Re: Docker for Mac Beta Review

#20
post #6

I'm a node.js developer. I understand the benefit of using docker for deployments or CI testing, but I have yet to be convinced of the benefits of using it for development on my local machine. I install node, postgres, and redis natively and it all works fine. What benefits does docker provide to my workflow?

You might need different node/postgres versions for different projects.

Or indeed for testing the same project against different versions or in different environments.
Post reply on HN