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

51–60 of 250 posts

Re: Docker for Mac and Windows Beta

#51

Post by knz »

nzoschke wrote: post #19

Very excited about this. Docker Machine and VirtualBox can be a rough experience. > Many of the OS-level integration innovations will be open sourced to the Docker community when these products are made generally available later this year. Does this mean it is closed right now?

I found docker-machine and VirtualBox quite stable (running multiple Flask, Python, and PostgreSQL containers). The only major issue I had was from a 5 year old VirtualBox bug and sendFile. That said, I won't miss the extra steps of running eval docker-machine etc.

Re: Docker for Mac and Windows Beta

#53

Post by knz »

_query wrote: post #35
mbrock wrote: post #26

Earlier quoted context omitted.

Nix is more difficult. With Docker, you don't need to learn much new stuff, since images are created from sequences of ordinary shell commands running on familiar distributions. Nix requires you to familiarize yourself with a new package manager and its somewhat arcane definition language. And then also the specific Nix tools for working with npm, ghc, or whatever you want to use. So the experience is very different.

In this case you could still pick homebrew as your package manager of choice. It works pretty well, is available cross platform ( https://github.com/Linuxbrew/linuxbrew ) and is far more simple than docker. You just have write a short shell script which installs all the dependencies via brew when not installed already (much like you'd do in a Dockerfile).

Is Docker that difficult? The Dockerfile is a nice single file that defines all container dependencies and then it's three commands (build, create, and start) to be able to easily work in the exact same environment for dev, qa, and production regardless of whether the host is running OSX or a flavour of linux.

Re: Docker for Mac and Windows Beta

#54

Post by wslh »

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 able to run isolated applications on the same computer.

Re: Docker for Mac and Windows Beta

#55

Post by tzaman »

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…

Will do, I've signed up for the beta (same username as here)

Re: Docker for Mac and Windows Beta

#56

Post by Someone1234 »

RubyPinch wrote: post #24
howfun wrote: post #17

Why would be Windows Pro required?

Hyper-V VMs require Professional and higher OSes which is usually like, what most people would have, and would consider the standard windows install. Windows Home is... very nutered to say the least

I judge Microsoft a bit for not just discontinuing Home.

Some of the missing features in Home are what I'd describe as "immoral." In that they aren't just luxuries, they're important parts of the OS or security features e.g.

- Group Policy Editor: This is the primary place to modify hundreds of local computer settings. They could have left out Domain Join, and kept the local Group Policy Editor.

- Start Screen Control with Group Policy: Adds more group policy options to modify the start screen/menu look/feel.

- Enterprise Mode Internet Explorer: Name notwithstanding, this allows people to use legacy webapps with modern IE.

- AppLocker: Security feature (isn't even in pro incidentally!). I'd turn it on.

- Bitlocker: Full drive encryption (with different decryption options).

- Credential Guard: Not used to protected non-domain credentials.

- Trusted Boot: Because home users don't get rootkits?

Windows 10 Home is categorically less secure than Windows 10 Pro, which is in turn less secure than Windows 10 Enterprise. Features like AppLocker, Credential Guard, Trusted Boot, are features that all versions of Windows could benefit from, and Bitlocker should be available and on by default.

When you have a "security" category in the feature list and are differentiating different versions of the OS then you really have to ask yourself how high you prioritise security in general.

Re: Docker for Mac and Windows Beta

#58

Post by Alex3917 »

avsm wrote: post #8
rogeryu wrote: post #4

> Faster and more reliable: no more VirtualBox! I'm a Docker n00b, still don't know what it can do exactly. Can Docker replace Virtualbox? I guess only for Linux apps, and suppose it won't provide a GUI, won't run Windows to use Photoshop?!

Let me explain Docker for Mac in a little more detail [I work on this project at Docker]. Previously in order to run Linux containers on a Mac, you needed to install VirtualBox and have an embedded Linux virtual machine that would run the Docker containers from the Mac CLI. There would be a network endpoint on your Mac that pointed at the Linux VM, and the two worlds are quite separate. Docker for Mac is a native Mac…

> the networking publishes ports to either `docker.local` or `localhost` depending on the configuration.

Perfect. We had to ditch Kitematic on OS X due to the lack of port forwarding, since we couldn't get OAuth redirects to work when developing locally.

Re: Docker for Mac and Windows Beta

#59

Post by avsm »

trendnet wrote: post #44
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…

Does it mean no `VBox shares` mmap bug limiting the use of volumes in Cassandra and MongoDB containers?

Yes that should work fine with osxfs (the new filesystem engine). Do you have a pointer to the specific bug in vbox so we can add it to our test suite?

Re: Docker for Mac and Windows Beta

#60

Post by goldbrick »

_query wrote: post #20

If you're using docker on mac, you're probably not using it there for easy scaling (which was the reason docker was created back then), but for the "it just works" feeling when using your development environment. But docker introduces far too much incidental complexity compared to simply using a good package manager. A good package manager can deliver the same "it just works" feeling of docker while being far more li…

With respect, I'm not sure you really grok the value prop of docker as it relates to operations and delivery. (The "easy scaling" part is incidental to that, and not the primary purpose of Docker). Nix, while cool, does not address those issues.
Post reply on HN