Live data from Hacker News

Docker for Mac and Windows Beta

blog.docker.com

181–190 of 250 posts

Re: Docker for Mac and Windows Beta

#181
post #68

The last time I used xhyve, it kernel panic'ed my mac. Researching this on the xhyve github account [1] showed that it was determined that it's due to a bug with Virtualbox. That is, if you've started a virtual machine since your last reboot with Virtualbox, subsequent starts of xhyve panic. So, buyer beware, especially if said buyer also uses tools like Vagrant. [1] https://github.com/mist64/xhyve/issues/5 I've said…

Who downvoted this? This is a real experience report, expressing valid concerns, citing an issue tracker for more information. Is this type of comment discouraged on HN? If so, why?

I'd bet it has to do with criticizing the Docker developers for a bug which is actually in one of two independent projects, and doing so in reaction to an announcement of something explicitly billed as a way to avoid that problem.

I doubt it would be getting downvotes if the comment was just a statement of fact without the somewhat random slam against the Docker developers.

Re: Docker for Mac and Windows Beta

#182
post #97
post #54

Can someone explain in simple terms how Docker for Windows is different from Application Virtualization products like VMware ThinApp, Microsoft App-V, Spoon, Cameyo, etc? Also, why does it require Hyper-V activated in Windows 10? I found this: https://docs.docker.com/machine/overview/ but I don't understand if you need separate VMs for separate configurations or they have a containerization technology where you are a…

Thanks for exposing me to ThinApp and the rest. I took a quick look, these are Microsoft based technologies designed to run Windows apps, however conceptually I don't see much difference. Docker is a containerization standard that relies on various Linux capabilities to isolate application runtimes (or containers if you will). On Mac and Linux it used to be achieved by running a small Linux VM in VirtualBox, but look…

ThinApp is really about packaging existing Windows desktop apps with the appropriate OS bits that the application needs. Then you can run that "thinapped app" on a different version of Windows or from a USB drive. Considered app level virtualization. #1 use case was to run IE6 based apps on newer Windows OS.

Re: Docker for Mac and Windows Beta

#183

The last time I used xhyve, it kernel panic'ed my mac. Researching this on the xhyve github account [1] showed that it was determined that it's due to a bug with Virtualbox. That is, if you've started a virtual machine since your last reboot with Virtualbox, subsequent starts of xhyve panic. So, buyer beware, especially if said buyer also uses tools like Vagrant. [1] https://github.com/mist64/xhyve/issues/5 I've said…

I've had similar experiences as well as times where xhyve made it so my laptop could not come out of sleep.

xhyve is wonderful but still needs some work and it seems like the main dev isn't interested in continuing work on it at this point[1]. Hopefully Docker's usage will spur more work on xhyve.

[1] Last commit on xhyve is December 28th, 2015 https://github.com/mist64/xhyve/commits/master

Re: Docker for Mac and Windows Beta

#186
post #18

Earlier quoted context omitted.

We'd love to get your feedback on the new filesystem engine in the Docker for Mac app. It's been a ton of work to get right, and there a few corner cases in the current beta that we're squashing, but overall things "just work" for my day-to-day Linux development on my Mac using the current beta. At this stage, pointing it to the weirdest and most wonderful filesystem stressers you can find is welcome. We'll leap on a…

Is this using the normal VirtualBox "shared folders" functionality? For Vagrant we had to drop VirtualBox in favour of VMware Fusion because VirtualBox suffered cache corruption almost every day. You would write a file on the host, and the file would be corrupt inside the VM. Last I checked, this bug was still open, but I'm not certain (on my phone right now), but it still makes me wary of using VirtualBox again. Hav…

No it does not use any virtualbox code.

Re: Docker for Mac and Windows Beta

#187
post #3

If I had a yearly quota on HN for upvotes, I'd use all of them on this. > Volume mounting for your code and data: volume data access works correctly, including file change notifications (on Mac inotify now works seamlessly inside containers for volume mounted directories). This enables edit/test cycles for “in container” development. This (filesystem notifications) was one of the major drawbacks for using Docker on M…

Anywhere I see Docker on Mac mentioned, I always point people to Dinghy. It has solved a lot of the issues the vanilla solutions had (NFS, fsevents etc) and the maintainer is incredibly responsive.

I would love to see Docker come up with something that rivals Dinghy as I would prefer not to have to use a third party tool, but considering their reputation for stability and the comments being made about xhyve, I am happy to continue using (and gushing about) Dinghy for the foreseeable future.

Re: Docker for Mac and Windows Beta

#189

Earlier quoted context omitted.

Until you, say, want to print something, or run one of the bajillion pieces of useful software that aren't available for Linux.

As a long time Linux user, I don't know about useful software that won't run on Linux. All the useful software I need runs just fine. Edit: Oh, and I don't understand the comment about printing. Cups works.

cups is only one part of the puzzle; every application has to manage its own method of rendering and talking to some printing agent.

It may also work for your particular device scenario, but there are thousands of scenarios (networks, devices, etc) in which its functionality may be limited or practically non-existent.

Re: Docker for Mac and Windows Beta

#190

I wonder if (and hope that!) this fixes the issues[1] with (open)VPN. I can't use xhyve (or veertu) at work because of this. [1] https://github.com/mist64/xhyve/issues/84

There is a mode that should work, which is likely to become the default soon. We do want feedback on this as it is hard to test all VPN setups.
Post reply on HN