Live data from Hacker News

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

blog.docker.com

91–100 of 169 posts

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

#91

On Windows, Hyper-V doesn't really play nicely with laptops. If you've got it enabled and bridged to your wifi adapter, Windows 10 may think that your connection is Ethernet and turn off all bandwidth saving features. I only found out after Windows Update had exhausted my monthly LTE quota.

Speaking about Windows, it is also disabled on Windows 10 Home and only available on Pro edition. Hope they'll maintain VirtualBox support as a first-class citizen (well, given that it was the most mature option during the beta period, suppose they will).

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

#92
post #88
post #70

Earlier quoted context omitted.

> Can I run any linux-based container on Windows? No, on windows you still have to run a Linux vm which the containers will run inside. Meaning all containers actually run on a Linux host. The new Docker for Windows app only abstract away some stuff so it feels easier working with. > does it work the other way around No

> No, on windows you still have to run a Linux vm which the containers will run inside. I don't think, that's correct. To me that's the whole point of having a native Windows / Mac version of docker. From their feature list: > Faster and more reliable – native development environment using hypervisors built into each operating system. (No more VirtualBox!)

No, GP got it right.

The quoted part is that instead of VirtualBox one can use Hyper-V. In either case, it's handled by docker-machine which runs a GNU/Linux VM with Docker (host) tools installed, and containers are ran on that VM.

I would be surprised if there aren't plans to support WSL (to run Linux-targetting binaries on Windows "natively", thus have "native" Docker containers) but don't think that's available yet.

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

#93
post #5

Earlier quoted context omitted.

Sadly, the state of things, be it the Docker ecosystem or others, "ready for production" means something much different than it did years ago. For me, the definition of ready for production, Debian is a good example of the opposite end of Docker.

I think by 'production', they mean 'ready for general use on developer laptops'. No one in their right mind is deploying actual production software on Docker, on OS X/Windows. I've been using it on my laptop daily for a month or two now, and it's been great. Certainly much better than the old Virtualbox setup.

The fact that I can have Bash up and running in any distro I feel like within minutes blows my friggin mind. Docker is the stuff of the future. We were considering moving our development environment to Docker for some Fun, but we're still holding off until it is more stable and speedy.

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

#94
post #5

Earlier quoted context omitted.

Sadly, the state of things, be it the Docker ecosystem or others, "ready for production" means something much different than it did years ago. For me, the definition of ready for production, Debian is a good example of the opposite end of Docker.

I think by 'production', they mean 'ready for general use on developer laptops'. No one in their right mind is deploying actual production software on Docker, on OS X/Windows. I've been using it on my laptop daily for a month or two now, and it's been great. Certainly much better than the old Virtualbox setup.

On the other hand I find my old setup with VMware much more reliable and performant. And I can continue to use the great tools to manage the VM instead of being limited to what docker provides. Some advanced network configuration is simply impossible in docker's VM.

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

#95
post #64

Earlier quoted context omitted.

>No one in their right mind is deploying actual production software on Docker, on OS X/Windows. Since the whole point of Docker would be to deploy these in production and not just for development, I don't see how the term 'ready for production' can be used. Isn't this just a beta?

I doubt the problems mentioned happen on Linux or CoreOS, which is likely what a production environment will run on.

Docker for Windows is to isolate Windows software.

It's not a tool to test Linux containers on Windows.

The deployment target for Docker containers for Windows will be a Windows OS.

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

#96
post #38

Can I run my usual VirtualBox VMs I have running for everything else (non-docker related) alongside Docker for Windows yet? When I tried one of the betas it enabled Hyper-V which prevented me from using any of my other VMs.

You can have just one hypervisor working at any given time. So, no, you can't use your VirtualBox VMs while a Docker container is running in this way (because it'd be using Hyper-V/xhyve).

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

#97

"This version of Docker requires Windows 10 Pro, Enterprise or Education edition with a minimum build number of 10586. Please use Docker Toolbox." :(

Meaning it doesn't run on LTSB as well (10240). Too bad, it's the only sane version of Windows 10 yet.

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

#98
An interesting fact I think is worth mentioning is that Docker for Mac uses a forked and currently closed version of xhyve, and not the same xhyve that we can find on Github. The last commit to open source xhyve was May 27.

With that said Docker has plans to open source it, I wonder if that will happen soon as they declare Docker for Mac ready for production. That would imply that the xhyve port also should be ready be contributed back or spin out into a new project (the quote below said they were not sure if they wanted to contribute back or make a new project).

Personally I think the "right thing to do" would be to contribute back to xhyve, at the same time I have a feeling it's more valuable for Docker Inc to "own" and control their own fork/project so I would guess they will go down that path instead (it would still be open source, just under a different project name).

Source: https://news.ycombinator.com/item?id=11356293

EDIT: I stand corrected, see talex5 comment below, I had missed the hyperkit announcement.

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

#100
post #64

Earlier quoted context omitted.

I doubt the problems mentioned happen on Linux or CoreOS, which is likely what a production environment will run on.

Docker for Windows is to isolate Windows software. It's not a tool to test Linux containers on Windows. The deployment target for Docker containers for Windows will be a Windows OS.

Sadly, no, they're using the name "Docker for Windows" to refer to the Docker-on-Linux-in-a-VM-on-Windows version.

Real native Windows containers and a Docker shim to manage them are coming: [1] but not released yet.

[1] https://msdn.microsoft.com/en-us/virtualization/windowsconta...

Post reply on HN