I have been working with Virtual machines for quite a while, most of my testing and demo environments are on VirtualBox. The problem I’ve always faced is the storage and resources requirements to run multiple VMs. Running VMs on a MAC works well, however we all know that MAC storage is a premium that not all of us have. I have always kept my VMs in an external drive, but quite honestly every time I am on a client or want to demos something, I usually don’t have the drive with me. With that I have been looking for alternatives and for quite a while I wanted to try Docker. With some available time today, I decided to give it a shot and it worked really well. Below I am demonstrating what I did to get started.

Here are my Steps: Download and Install Docker for Mac from the Docker Store Install it Double-click Docker.dmg to start the install process. When the installation completes and Docker starts, the whale in the top status bar shows that Docker is running, and accessible from a terminal. Run it Open a command-line terminal, and try out some Docker commands. Run $docker version to check that you have the latest release installed. Run $docker run hello-world to verify that Docker is pulling images and running as expected.

If you are running Docker For Mac edge, and you are on at least version 17.06.0-rc1-ce-mac13, then you should be able to resolve the following DNS name: docker.for.mac.localhost It is expected that this will be in the stable branch once 17.06 hits stable. If you are using Docker on MacOS or Windows 10 Pro, chances are that you use the dedicated Docker for Mac or Docker for Windows products. Both of them use a hypervisor (xhyve / HyperV) to run a VM.

More information on how to run and install Docker on Mac can be found here: Now that I have downloaded and installed Docker successfully, I will download an existing Database 12c Image public available. Follow Alex's Blog Enter your email address to follow this blog and receive notifications of new posts by email.

Unless you've setup DNS or a hosts file entry for that address, you shouldn't expect it to work. You can configure the website to respond for docker.for.mac.localhost in addition to localhost.mywebsite.com or make it reply with your website regardless of the domain name (i.e. The default if no host match is found) ~~ e.g. Anything hitting port 9999 gets your website regardless of hostname. This is the default setup in most cases if only one website is being served by the server.

Tunein radio app for mac. If you can't ping docker.for.mac.localhost.mywebsite.com from inside the container then the request will never leave the container.