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

81–90 of 169 posts

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

#81

Post by justincormack »

jonesetc wrote: post #14
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 have also yet to see a reasonable solution for connecting out of a container back to the host with Docker.app. On linux and OSX with docker-machine this is easy with: docker run --add-host host:ip.for.docker.interface foo But there is no equivalent to the docker0 interface or the vboxnet interface for Docker.app. EDIT: I don't use this for any production environments, but it is very useful for debugging and testing…

The best solution is to add a new stable, unconflicting IP address to the loopback interface on the Mac and connect to that.

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

#82

Post by justincormack »

amazingman wrote: post #59
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…

Not to mention the lack of host:container socket sharing and the fact that the Moby VM time drifts due to system sleep. I love Docker for Mac, I use it every day, and it's definitely still beta quality.

How much does your time drift? We changed the mechanism so that it should sync from the OSX ntp server now, which seems to be giving good results. If you are having problems can you create an issue and we can look into it.

Host container socket sharing will come, but it is complex as sockets only exist with in a single operating system, so we have to bridge them across two. We are using this for the docker socket, and debugging the issues across Mac and Windows, so it is in the roadmap.

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

#83

Post by justincormack »

010a wrote: post #4
hijinks wrote: post #3

Earlier quoted context omitted.

I was an early user of the mac beta and the 100% cpu would happen 2-3 times daily. Now it maybe happens once every 2 weeks. Not sure about the others but the CPU isn't much an issue anymore. Maybe its just me being use to how bad it was.

I've been heavily using it since what must have been early closed beta, and cannot recall ever having this issue. Might be something that isn't quite so widespread.

It only happens with a few users, and not at all to the majority. It seems to happen more on older OSX versions, but beyond that there has not been anything identifiable in common about the systems it happens on unfortunately.

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

#84

Post by justincormack »

adamhepner wrote: post #67
ktzar wrote: post #58

Earlier quoted context omitted.

Short answer, yes. Medium answer, images your Dockerfile is based on are still run in a Linux environment, even if it's virtualised differently.

Wait now, hold on a minute. I'm very confused and curious how does this work? Can I run any linux-based container on Windows? Can I run (are there any?) windows-based containers? If so, does it work the other way around: windows container on linux host? Does it somehow use the recently published Linux Subsystem for Windows, or is it completely different compatibility layer? If it is different, doesn't it seem like a…

Native Windows containers are in beta and will be released later this year. You cannot run them on Linux hosts. They do not use the Windows subsystem for Linux, they are really native for Windows.

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

#85

Post by ckastner »

mrmondo wrote: post #56
vbernat wrote: post #29

Earlier quoted context omitted.

Unfortunately, nobody has stepped for SELinux maintainance. If this is important for you, you should help to maintain those policies. All your remaining points are vague at best.

Oh believe me, we did try to contribute to Debian, in recent years the community has aged poorly and become toxic and hostile, where the Redhat / CentOS community has grown, is more helpful and we have found them to be more accepting of people offering their time than ever.

Most people I have spoken to about this say exactly the opposite. In 2014, the project even ratified a Code of Conduct [0].

The only major contentious issue I can recall was the systemd-as-default-init discussion, but that was expected.

[0] https://www.debian.org/code_of_conduct

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

#86

Post by sigjuice »

amorphid wrote: post #36
gtirloni wrote: post #11

Earlier quoted context omitted.

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…

I believe xhyve works fine with recent versions of VirtualBox, since xhyve is a pure userland app (aka no kernel extensions). Check out the issues section in the xhyve readme... https://github.com/mist64/xhyve/blob/master/README.md

xhyve needs to interact with all kinds of low-level things so there has to be kernel code involved. xhyve does not install kernel extensions of its own like VirtualBox or VMWare Fusion. xhyve uses the kernel extensions provided by Apple (com.apple.driver.AppleHV and possibly others).

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

#87

Post by tazjin »

sudhirj wrote: post #64
statictype wrote: post #62

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.

> Linux or CoreOS

Well, now I'm confused

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

#88

Post by mh-cx »

jimlei wrote: post #70
adamhepner wrote: post #67

Earlier quoted context omitted.

Wait now, hold on a minute. I'm very confused and curious how does this work? Can I run any linux-based container on Windows? Can I run (are there any?) windows-based containers? If so, does it work the other way around: windows container on linux host? Does it somehow use the recently published Linux Subsystem for Windows, or is it completely different compatibility layer? If it is different, doesn't it seem like a…

> 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!)

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

#89

Post by ZenoArrow »

HerpDerpLerp wrote: post #80

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

That'll be because Windows 10 is the first desktop Windows OS with support for Hyper-V.

If you didn't want to use Windows 10, perhaps you might have some more luck with a Windows Server OS. Does anyone know if the latest version of Docker will work on Windows Server 2012?

Post reply on HN