Book Image

Developing with Docker

By : Jaroslaw Krochmalski, Jarosław Krochmalski
Book Image

Developing with Docker

By: Jaroslaw Krochmalski, Jarosław Krochmalski

Overview of this book

This fast-paced practical guide will get you up and running with Docker. Using Docker, you will be able to build, ship, and run many distributed applications in real time. You will start with quickly installing Docker and start working with images and containers. We will present different types of containers and their applications, and show you how to find and build images. You will learn how you can contribute to the image repository by publishing different images. This will familiarize you with the image building process and you will be able to successfully run your programs within containers. By finishing this book, you will be well equipped in deploying your applications using Docker and will have a clear understanding of concepts, techniques, and practical methods to get it running in production systems.
Table of Contents (16 chapters)
Developing with Docker
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface

Hardware requirements


To use Docker, you will need some reasonably new machine, that supports hardware-level virtualization: VT-x for Intel-based PCs and AMD-V for AMD processors. Most of the Mac machines support it out of the box, but for PC you will need to make sure it's turned on and perhaps enable it in the BIOS settings. It will be different for different BIOS, just look for VT-x / AMD-V switch.

In Windows 8, you can check virtualization support in the task manager in the Performance tab:

If you want to check whether your PC supports the hardware level virtualization in Windows 7, look for Microsoft Hardware-Assisted Virtualization Detection Tool. Its free, tiny utility is used to check whether your system supports virtualization. Download and run it to see the report:

If the report is different for you, saying that hardware-assisted virtualization is not enabled, you will need to check the BIOS settings on your machine, maybe the hardware-assisted virtualization support is just switched...