I've noticed some pretty extreme performance penalties with Docker for Mac. Wherein VirtualBox would spin I'm going to guess it'll get better in time. It would be nice to get some insight into just what is burning CPU cycles. The experience besides that was really top notch IMO.
Docker for Mac Beta Review
31–40 of 367 posts
Re: Docker for Mac Beta Review
#32So it uses xhyve...does this mean Docker runs up a full hypervisor per Docker process you run? That seems a bit excessive.
Re: Docker for Mac Beta Review
#33Why 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…
If you want to run services in docker containers with Docker Toolbox (e.g. a mysql db), and you want the db stored on the Mac host, then you have to worry about 2 layers of folder mounts (one from host -> vm, one from vm -> container), another 2 layers of port forwarding (same as above), to make it 'feel' like your're running mysql locally.
With the beta, all of that is taken care for you with a couple of settings, and it's just much simpler to get up and running.
Re: Docker for Mac Beta Review
#34This "review" is the technical equivalent of a YouTube unboxing video. Screenshot, screenshot, something I already knew from reading the press release, screenshot, platitude, one big technical error in the conclusion, and done. If it really worked (especially on Windows) Docker would post the binaries instead of treating this like Wonka Golden Tickets. Love Docker, am actually waiting to be approved so I can get to b…
> If it really worked That's why it's a beta .
Beta means "feature complete" not "wait a month/win a lottery to get a chance at using the bits."
Re: Docker for Mac Beta Review
#35This "review" is the technical equivalent of a YouTube unboxing video. Screenshot, screenshot, something I already knew from reading the press release, screenshot, platitude, one big technical error in the conclusion, and done. If it really worked (especially on Windows) Docker would post the binaries instead of treating this like Wonka Golden Tickets. Love Docker, am actually waiting to be approved so I can get to b…
Disclaimer: I work at Docker. The reason we are keeping the beta private is because we don't believe the quality is good enough yet to "open the floodgates". We are sending as many invites as the engineers are comfortable with - currently that's several thousands per day. As we hit more and more edge cases (performance, stability, support for unusual configurations...) we are expanding the pool as fast as we can.
I appreciate this but in that case you should collect configuration data as part of requesting the bits. If I'm on a machine that's known borked, I'll wait. If not, gimme and I'll help you fix. Otherwise it feels like you're just using this as a marketing trick to build buzz.
Re: Docker for Mac Beta Review
#36Can anybody in HN provide a quickpath into the beta? I signed up when it was first announced (seems to be over 30 days ago: https://news.ycombinator.com/item?id=11352389 ) but haven't heard anything back yet.
Same. I even reached out to them on Twitter and didn't hear anything back.
Re: Docker for Mac Beta Review
#37Can anybody in HN provide a quickpath into the beta? I signed up when it was first announced (seems to be over 30 days ago: https://news.ycombinator.com/item?id=11352389 ) but haven't heard anything back yet.
I am in the same boat.
I'm actually holding up a wider scope for Docker deployment within our organization until we can use Docker for Mac.
Re: Docker for Mac Beta Review
#38So it uses xhyve...does this mean Docker runs up a full hypervisor per Docker process you run? That seems a bit excessive.
That's not the case - there's only one virtual machine shared by all containers.
Re: Docker for Mac Beta Review
#39I'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?
when you have 15 of those things start to make sense. I used vagrant in school just so that I wouldn't have any lasting tweaks of db's and weird things you end up doing. Also, with a provisioning script, I can get my projects running to this day. My snobol, smalltalk and scheme projects all can be run by just running vagrant up. I don't have to make sure that my current machine has all of the dependencies.
When we developed an angular and java site, I set up vagrant to configure tomcat, node, java, and all of the plugins required to get tomcat and maven to be nice together. Did it once, and then everyone else with a unixy platform were able to not spend time on dealing with that. Now that the class is over, all of that is removed from my machine but I can always just crank it back up in the time it takes to install all of those dependencies.
Re: Docker for Mac Beta Review
#40Why 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…
If you want to run services in docker containers with Docker Toolbox (e.g. a mysql db), and you want the db stored on the Mac host, then you have to worry about 2 layers of folder mounts (one from host -> vm, one from vm -> container), another 2 layers of port forwarding (same as above), to make it 'feel' like your're running mysql locally. With the beta, all of that is taken care for you with a couple of settings, a…
Even boot2docker (docker machines predecessor) could do that. It shared the folders correctly and managed port forwarding. Of course localhost stop working but I just added the ip in /etc/hosts and enter docker.local instead (the docks say the IP might change but that's never happened to me).