Oooh yes, I love Docker. Right now, I do most of my dev work outside Docker (because I don't want to rebuild the image every time I change a file..unless there's a way?). I do use Docker at intervals to make sure everything still works.

The shell being closer to production was more for familiarity sake. For me, I used to think I was going to be Mac for a long time because "Mac has a bash shell." Windows has a bash shell. In practice, I mostly use the ssh command! :)

Oh and the console window in Windows is now resizable! That drove me crazy.

> because I don't want to rebuild the image every time I change a file..unless there's a way?

I believe the current strategy is to have a container that contains your full build environment, push your source files in by mounting a folder, and then use file watchers to automatically rebuild/rerun.

How do you run Ubuntu binaries on Mac by using Docker? As far as I know it's not a virtualization layer.

Docker on Mac runs in a VM, either by one of the traditional virtualisation solutions (Virtualbox, VMWare, Parallels) or via xhyve. The VM acts as a Docker server, so the client on the mac side just passes options to the Docker VM. See: https://docs.docker.com/engine/installation/mac/

Docker now also has a native Mac client that doesn't require docker-machine

What does "native" mean in this context? The Mac client still runs containers in a Linux VM.

Thanks both! I believe the native Mac announcement is what put me off track.

Which gets pretty bad the moment you need to use shared volumes.