You get the same workflow in Docker Desktop and the Docker CLI with all the container compute you want.

Docker Desktop includes Docker App, developer tools, Kubernetes and version synchronization to production Docker Engines.

Docker Desktop allows you to leverage certified images and templates and your choice of languages and tools.

Development workflows leverage Docker Hub to extend your development environment to a secure repository for rapid auto-building, continuous integration and secure collaboration.

Build and run the same applications everywhere with the only platform that can provide trusted and certified end-to-edge security.

Windows or Linux; legacy or cloud-native; IDE or text editorDocker Desktop and Desktop Enterprise puts you in control.

Docker makes it easy to get up and running in minutes and rapidly code, test, and collaborate while ensuring consistency between development and production.

You get certified Kubernetes and Docker, for developers of all levels of container expertise.

Pre-defined and customizable application templates adhere to corporate standards and automate configuration, eliminating error-prone manual setup.

Intuitive Application Designer facilitates the packaging, installing, and managing of multi-service applications as a shareable package.

For example, we could start an nginx container that serves files from the host using a volume.

Now theres a new thing, Docker Toolbox, that makes it super easy.

Or you can read it if you want, I think its a pretty good blog post and youll learn some stuff.

Even my dads like, whats Docker I saw someone twitter about it on the Facebook.

It has the potential to change all aspects of server-side applications, from development and testing to deployment and scaling.

Its a top notch book and I highly recommend it, but Ive had some problems running the examples on OS X.

After a certain point, the book assumes youre using Linux and skips some of the extra configuration required to make the examples work on OS X.

This isnt the books fault; rather, it speaks to underlying issues with how Docker works on OS X.

Its not meant to be a tutorial on Docker itself, but I encourage you to follow along and type in all the commands.

Youll get a better understanding of how Docker works in general and on OS X specifically.

Plus, if you decide to dig deeper into Docker on your Mac, youll be saved hours of troubleshooting.

The Docker server is a daemon that does all the heavy lifting: building and downloading images, starting and stopping containers, and the like.

The host can be any machineyour laptop, a server in the Cloud, etcbut, because Docker uses features only available to Linux, that machine must be running Linux (more specifically, the Linux kernel).

It doesnt have the kernel features required to run Docker containers natively.

This also means boot2docker, not OS X, is the Docker host, not OS X.

I prefer homebrew because I like to manage my environment from the command line.

You probably want to add that environment variable to your shell config.

The VM runs the Docker server, and were communicating with it using the Docker client on OS X.

If we were on Linux, our Docker host would be localhost, but we arent, so its not.

Its our VM.

The (boot2docker ip) subcommand captures standard output but not standard error, which still goes to the terminal.

If youre only using one VM, it should always get the same IP, but if youre VMing on the reg, it could change.

Soon, inception. You should really just use the VMs IP address mmkay.

Volumes are one way to give your container access to resources in the outside world.

Boot2Docker Vs Docker For Mac