Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker for Mac and Windows Is Now Generally Available and Ready for Production

blog.docker.com

Post reply on HN
Print view View original

41–50 of 169 posts

Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production

#41

Post by dcosson »

senex wrote: post #2

I've been tracking the beta for a while. I'm confused about this announcement. These issues still seem unresolved? (1) docker can peg the CPU until it's restarted https://forums.docker.com/t/com-docker-xhyve-and-com-docker-... (2) pinata was removed, so it can't be configured from CLI scripts https://forums.docker.com/t/pinata-missing-in-latest-mac-bet... (3) it's not possible to establish an ip-level route from the…

I had a similar experience trying to switch to docker-machine as it sounds like you've had with the new apps, and ended up giving up.

It's super simple through Vagrant though, just vagrant up and set DOCKER_HOST to the static IP. Plus there are vagrant plugins that let you sync a directory to the vm in a way that gives you inotify events so live build/update tools can run in your containers (which btw is huge, I can't believe the official apps haven't even attempted to address that, as far as I've seen).

Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production

#42

Post by RussianCow »

dcosson wrote: post #41
senex wrote: post #2

I've been tracking the beta for a while. I'm confused about this announcement. These issues still seem unresolved? (1) docker can peg the CPU until it's restarted https://forums.docker.com/t/com-docker-xhyve-and-com-docker-... (2) pinata was removed, so it can't be configured from CLI scripts https://forums.docker.com/t/pinata-missing-in-latest-mac-bet... (3) it's not possible to establish an ip-level route from the…

I had a similar experience trying to switch to docker-machine as it sounds like you've had with the new apps, and ended up giving up. It's super simple through Vagrant though, just vagrant up and set DOCKER_HOST to the static IP. Plus there are vagrant plugins that let you sync a directory to the vm in a way that gives you inotify events so live build/update tools can run in your containers (which btw is huge, I can'…

> Plus there are vagrant plugins that let you sync a directory to the vm in a way that gives you inotify events so live build/update tools can run in your containers (which btw is huge, I can't believe the official apps haven't even attempted to address that, as far as I've seen).

If you don't mind, what are these plugins? This is one thing that's sorely missed when I do development with Vagrant. I did a small amount of searching and trial and error, but couldn't find a solution that worked for me.

Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production

#44

Post by zwily »

dcosson wrote: post #41
senex wrote: post #2

I've been tracking the beta for a while. I'm confused about this announcement. These issues still seem unresolved? (1) docker can peg the CPU until it's restarted https://forums.docker.com/t/com-docker-xhyve-and-com-docker-... (2) pinata was removed, so it can't be configured from CLI scripts https://forums.docker.com/t/pinata-missing-in-latest-mac-bet... (3) it's not possible to establish an ip-level route from the…

I had a similar experience trying to switch to docker-machine as it sounds like you've had with the new apps, and ended up giving up. It's super simple through Vagrant though, just vagrant up and set DOCKER_HOST to the static IP. Plus there are vagrant plugins that let you sync a directory to the vm in a way that gives you inotify events so live build/update tools can run in your containers (which btw is huge, I can'…

The official apps do do that. It's one reason their shared fs performance is abysmal so far.

Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production

#45

Post by RussianCow »

gtirloni wrote: post #11
yladiz wrote: post #8

I don't use Docker much now, but in my experience the reliance on Virtualbox (on Mac) was a little clunky and annoying, and I really wished for native support without Virtualbox. I'm super happy to see that's here!

I think it makes sense to depend on the "native" virtualization solutions for each operating system (Hyper-V and xhyve). We have been using Vagrant and VirtualBox heavily and the new Docker for Windows/Mac is making us reconsider that since you can't easily use more than one hypervisor on the same dev machine without some hassle. We might be building our Vagrant boxes for these other hypervisors soon. VirtualBox stil…

In my experience, Windows is the only OS that makes it difficult to run multiple different hypervisors. I'm running multiple on my Linux and OS X machines without problems.

Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production

#47

Post by slidese »

senex wrote: post #2

I've been tracking the beta for a while. I'm confused about this announcement. These issues still seem unresolved? (1) docker can peg the CPU until it's restarted https://forums.docker.com/t/com-docker-xhyve-and-com-docker-... (2) pinata was removed, so it can't be configured from CLI scripts https://forums.docker.com/t/pinata-missing-in-latest-mac-bet... (3) it's not possible to establish an ip-level route from the…

I always thought of production ready to be stable, of all things. Feature complete is not a part of it.

Basically, if you can live with the shortcomings a release has (bugs, performance, lack of features) you can use it in production as long as it's stable (and secure).

Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production

#48

Post by hueving »

slidese wrote: post #47
senex wrote: post #2

I've been tracking the beta for a while. I'm confused about this announcement. These issues still seem unresolved? (1) docker can peg the CPU until it's restarted https://forums.docker.com/t/com-docker-xhyve-and-com-docker-... (2) pinata was removed, so it can't be configured from CLI scripts https://forums.docker.com/t/pinata-missing-in-latest-mac-bet... (3) it's not possible to establish an ip-level route from the…

I always thought of production ready to be stable, of all things. Feature complete is not a part of it. Basically, if you can live with the shortcomings a release has (bugs, performance, lack of features) you can use it in production as long as it's stable (and secure).

I wouldn't consider pegging a CPU until restart to be 'stable'.

Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production

#49

Post by gkop »

dcosson wrote: post #41
senex wrote: post #2

I've been tracking the beta for a while. I'm confused about this announcement. These issues still seem unresolved? (1) docker can peg the CPU until it's restarted https://forums.docker.com/t/com-docker-xhyve-and-com-docker-... (2) pinata was removed, so it can't be configured from CLI scripts https://forums.docker.com/t/pinata-missing-in-latest-mac-bet... (3) it's not possible to establish an ip-level route from the…

I had a similar experience trying to switch to docker-machine as it sounds like you've had with the new apps, and ended up giving up. It's super simple through Vagrant though, just vagrant up and set DOCKER_HOST to the static IP. Plus there are vagrant plugins that let you sync a directory to the vm in a way that gives you inotify events so live build/update tools can run in your containers (which btw is huge, I can'…

The company claimed back in March [0] that Docker for Mac addresses the filesystem events. I observed that it works.

While Docker for Mac has improved somewhat over the beta, unfortunately it's still quite rough. For example, it was only last week that they pushed a fix for the DNS timeout issue [1] (I think maybe it was fixed? I can't check because Docker for Mac is not open source).

[0] https://blog.docker.com/2016/03/docker-for-mac-windows-beta/

[1] https://forums.docker.com/t/intermittent-dns-resolving-issue...

Re: Docker for Mac and Windows Is Now Generally Available and Ready for Production

#50

Post by slidese »

hueving wrote: post #48
slidese wrote: post #47

Earlier quoted context omitted.

I always thought of production ready to be stable, of all things. Feature complete is not a part of it. Basically, if you can live with the shortcomings a release has (bugs, performance, lack of features) you can use it in production as long as it's stable (and secure).

I wouldn't consider pegging a CPU until restart to be 'stable'.

True. So that gives us one issue then?
Post reply on HN