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

Docker for Mac and Windows Beta

blog.docker.com

Post reply on HN
Print view View original

171–180 of 250 posts

Re: Docker for Mac and Windows Beta

#171

Post by tra3 »

wslh wrote: post #138
JonathonW wrote: post #131

Earlier quoted context omitted.

As mentioned in the linked blog post, they're using Hyper-V as their hypervisor on Windows (it's a direct counterpart to xhyve on OSX, except entirely built into the OS). The Docker for Mac and Windows beta does not use VirtualBox on either platform.

My original question was if you need to run a separate VM for every Docker configuration or you can run different application versions at the same time. For example, running Outlook 2010, 2013, and 2016 side by side.

You can run multiple containers on a single host (VM).

Re: Docker for Mac and Windows Beta

#172

Post by Grue3 »

I really want to try this, but I'm unable to register. At the page where it says "Create your free Docker ID to get started" after I click Sign Up, the page just refreshes and my chosen ID becomes blank with no indication of what's wrong. I've chosen several different IDs and neither of them worked. Browser is Firefox 45.0.1 on Windows 7.

Re: Docker for Mac and Windows Beta

#173

Post by mathewpeterson »

I'm really excited to see this because I've spent the last few months experimenting with Docker to see if it's a viable alternative to Vagrant.

I work for a web agency and currently, our engineers use customized Vagrant boxes for each of the projects that they work on. But that workflow doesn't scale and it's difficult to maintain a base box and all of the per project derivatives. This is why Docker seems like a no-brainer for us.

However, it became very clear that we would have to implement our own tooling to make a similar environment. Things like resolving friendly domain names (project-foo.local or project-bar.local) and adding in a reverse proxy to have multiple projects use port 80.

Docker for Mac looks like it will solve at least the DNS issue.

Can't wait to try it out.

edit: words

Re: Docker for Mac and Windows Beta

#176

Post by hinkley »

ownagefool wrote: post #167
hinkley wrote: post #159

Earlier quoted context omitted.

The glaring security hole in Docker is that it has not designed a solution for keeping secret data necessary to build an image from being in the image at run time. They also haven't solved the general case of keeping transient build data out of the final image either, but that's a broader problem that doesn't necessarily involve security concerns. For now not a lot of people are concerned about either problem so it's…

They have build args for this in now. Thus, you'd do something like: docker build --build-arg OAUTH_TOKEN=blah -t example .

I think you just proved my point. We're all of us running around with our pants down because we think Docker is taking care of this stuff but it's merely a bunch of features that look like they should be fit for that purpose but aren't.

And this is why I am stuck with a separate build and package phase, because I have to have that separation between the data available at build time and what ends up shipped, but even there I'm pretty sure I'm making mistakes, due to some of the design decisions Docker made thinking they were helping but actually made things worse.

For instance, there's no really solid mechanism for guaranteeing that none of your secret files end up in your docker image, because they decided that symlinks were forbidden. So I have to maintain a .dockerignore file and I can never really be sure from one build to the next that I haven't screwed it up somehow. Which I will, sooner or later.

I'm always one bad merge away from having to revoke my signing keys. It's a backlash waiting to happen.

Re: Docker for Mac and Windows Beta

#177

Post by lobster_johnson »

avsm wrote: post #18
tzaman wrote: 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…

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. Have you dealt with this issue at all?

Edit: Or is this not using any VirtualBox code at all?

Re: Docker for Mac and Windows Beta

#178

Post by itpragmatik »

BradRuderman wrote: post #158
jaequery wrote: post #114

Earlier quoted context omitted.

yep same for me here. yes on chrome with js and adblock disabled

Has anyone actually gotten to download the thing? I just get a we'll be in touch.

Thanks! We'll be in touch soon! => That's what I get too.

Re: Docker for Mac and Windows Beta

#179

Post by cicloid »

falcolas wrote: post #64

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 think this was related with a kernel bug which was fixed with the latest release from OSX (released yesterday).

I personally discovered this bug while using dlite, which uses xhyve behind the scenes.

Re: Docker for Mac and Windows Beta

#180

Post by lobster_johnson »

djsumdog wrote: post #133
wslh wrote: 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…

Docker uses LXC containers. In Linux, these aren't VMs and are light weight user-land separations that use things like cgroups and lots of really special kernel modules for security. Unfortunately, this means Docker only runs on Linux .. not even Linux...special Docker Kernel Linux (all the features they need are in the stock Kernel tree, but it's still a lot of modules). In Windows/Mac, you still need to run in a vi…

Docker does not use LXC. It's a separate project. LXC is similar, but has gone in a different direction.
Post reply on HN