Table of Contents

Developing with Docker

Credits

About the Author

About the Reviewer

www.PacktPub.com

Why subscribe?

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Errata

Piracy

Questions

1. Introduction to Docker

The basic idea

Containerization versus virtualization

Traditional virtualization

Containerization

Benefits of using Docker

Speed and size

Reproducible and portable builds

Immutable and agile infrastructure

Tools and APIs

Tools overview

Docker Engine and Docker Engine client

Docker Machine

Kitematic

Docker compose

Oracle VirtualBox

Git

Summary

2. Installing Docker

Hardware requirements

Installing on Windows

Installing on Mac OS

Installing on Linux

Installing on the cloud — AWS

Summary

3. Understanding Images and Containers

Images

Layers

Containers

Saving changes to a container

Docker registry, repository and index

Summary

4. Networking and Persistent Storage

Docker networking

Default networks

No networking

Host network

Bridged network

Creating a network

Running a container in a network

Creating multi-host networking

Swarm mode

Key-value store overlay networking

Exposing and mapping ports

Linking containers

Networking plugins

Docker volumes

Creating a volume

Removing a volume

Volume drivers

Summary

5. Finding Images

The Docker Hub

Docker Hub account

Organization account and teams

Collaborators

Private Repositories

Logging into Docker Hub

Searching for images

Image naming and tags

Searching through the web interface

Searching using the command line

Docker Hub and docker registry REST API

Summary

6. Creating Images

Dockerfile instructions

FROM

MAINTAINER

ADD

COPY

CMD

ENTRYPOINT

LABEL

EXPOSE

RUN

USER

VOLUME

WORKDIR

ARG

ONBUILD

STOPSIGNAL

HEALTHCHECK

SHELL

Using Dockerfiles

Summary

7. Running Containers

Runtime modes - detached and foreground

Detached

Foreground

Identifying images and containers

PID settings

UTS settings

Overriding default commands from Dockerfile

Overriding the CMD

Overriding the ENTRYPOINT

Executing arbitrary commands with exec

Monitoring containers

Viewing logs

Container events

Inspecting a container

Statistics

Container exit codes and restart policies

no

always

on-failure

unless-stopped

Updating a restart policy on a running container

Runtime constraints on resources

Memory

Processors

Updating constraints on a running container

Docker Swarm mode

The purpose

Terminology

Swarm mode commands

Summary

8. Publishing Images

Publishing images

Tagging

Untagging the image

Pushing the image

Webhooks and automated builds

Setting up the automated build

Build Triggers

Webhooks and continuous deployments

Summary

9. Using Docker in Development

Using Docker with Maven

Spotify's Maven Docker plugin

fabric8io Maven Docker plugin

Spring Boot application in Docker container

Packaging Angular.js application

Summary

Appendix A. More Resources

Official documentation

Awesome Docker

Training

Developing with Docker

Developing with Docker

Copyright © 2016 Packt Publishing

All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews.

Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book.

Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information.

First published: November 2016

Production reference: 1241116

Published by Packt Publishing Ltd.

Livery Place

35 Livery Street

Birmingham 

B3 2PB, UK.

ISBN 978-1-78646-990-8

www.packtpub.com

Credits

About the Author

Jarosław Krochmalski is a passionate software designer and developer who specializes in the financial business domain. He has over 12 years of experience in software development. He is a clean-code and software craftsmanship enthusiast. He is a Certified Scrum Master and a fan of Agile. His professional interests include new technologies in web application development, design patterns, enterprise architecture, and integration patterns.

He has been designing and developing software professionally since 2000 and has been using Java as his primary programming language since 2002. In the past, he worked for companies such as Kredyt Bank (KBC) and Bank BPS on many large-scale projects such as international money orders, express payments, and collection systems. He currently works as a consultant at Danish company 7N as an infrastructure architect for the Nykredit bank. You can reach him via Twitter at @jkroch or by e-mail at jarek@finsys.pl.

I would like to say hello to my friends at 7N and Nykredit—keep up the great job!

About the Reviewer

Jeeva S. Chelladhurai has been working as a DevOps specialist at the IBM Global Cloud Center of Excellence (CoE) for the last 8 years. He is the co-author of Learning Docker published by PacktPub, UK. He has more than 20 years of IT industry experience. He has technically managed and mentored diverse teams across the globe in envisaging and building pioneering telecommunication products. He specializes in DevOps and cloud solution delivery, with a focus on data center optimization, software-defined environments (SDEs), and distributed application development, deployment, and delivery using the newest Docker technology. Jeeva is also a strong proponent of the agile methodologies, DevOps, and IT automation. He holds a master's degree in computer science from Manonmaniam Sundaranar University and a graduation certificate in project management from Boston University, USA. Besides his official responsibilities, he writes book chapters and authors research papers. He has been instrumental in crafting reusable technical assets for IBM solution architects and consultants. Currently, he is contributing for the second edition of the Docker book. He speaks in technical forums on DevOps technologies and tools. His Linked in profile can be found at https://www.linkedin.com/in/JeevaChelladhurai.

www.PacktPub.com

For support files and downloads related to your book, please visit www.PacktPub.com.

Did you know that Packt offers eBook versions of every book published, with PDF and ePub files available? You can upgrade to the eBook version at www.PacktPub.com and as a print book customer, you are entitled to a discount on the eBook copy. Get in touch with us at service@packtpub.com for more details.

At www.PacktPub.com, you can also read a collection of free technical articles, sign up for a range of free newsletters and receive exclusive discounts and offers on Packt books and eBooks.

https://www.packtpub.com/mapt

Get the most in-demand software skills with Mapt. Mapt gives you full access to all Packt books and video courses, as well as industry-leading tools to help you plan your personal development and advance your career.

Why subscribe?

Fully searchable across every book published by Packt

Copy and paste, print, and bookmark content

On demand and accessible via a web browser

Preface

Docker has got a lot of attention in the last few years. Today it has thousands of community contributors, countless numbers of containers downloads, and more and more third party projects using it. It seems that its acclaim will grow even more in the next few years. In this book, we will try to explain this extraordinary popularity and show how you can benefit from faster and simpler application development, testing, and deployment. We will learn Docker from a developer’s perspective mostly and focus on creating, running, and publishing Docker images, rather than managing and clustering them. We will begin with the basic ideas and advantages which Docker brings to the developer’s tool set.

What this book covers

Chapter 1, Introduction to Docker, briefly describes what Docker is and how it can be useful in modern software development and deployment. We will point out what advantages come with the tool and why it is helpful. This chapter will also demonstrate how the containers containing code, runtime, system tools, and libraries can speed up the development and deployment, at the same time making it a more enjoyable experience.

Chapter 2, Installing Docker, contains the brief description of the available tools, such as Docker CLI or Kinematic (Docker GUI). Next, we will go straight to the action--installing the tools. The chapter will give precise and practical instructions on how to install the Docker Toolbox on Mac, Linux, and Windows. The chapter will also describe the process of installing Docker in the cloud, such as Amazon AWS.

Chapter 3,  Understanding Images and Containers, talks about the Docker’s architecture. We will explain the terminology related to working with it. After reading this chapter you will understand the concepts and architecture behind Docker; it is a must when going through the next chapters.

Chapter 4, Networking and Persistent Storage, describes the Dockers networking and storage concepts. The chapter will introduce the reader to containers networking and present different kind of containers (open, closed, bridged and joined). The reader will also get familiar with the idea of volumes and their types. Additionally, the reader will learn how to manage, mount, and share Docker volumes.

Chapter 5, Finding Images, describes the process of identifying software, finding and installing it with the Docker Hub, and the alternative sources. After reading this chapter, the reader will be able to find a specified image in the Docker repository and then install it.

Chapter 6, Creating Images, tells the reader how to write a Dockerfile, how to build an image from it, and get familiar with the image build process. The chapter will contain the best practices for writing Dockerfiles and useful tips and tricks for dealing with the images.

Chapter 7, Running Containers, tells us how to run programs within containers. The chapter will describe the concept of starting, stopping, restarting, listing, and viewing the container output. The reader will run multiple programs in a container and get familiar with injecting the configuration into the container. We will also describe the container life cycle and the cleanup process.

Chapter 8, Publishing Images, familiarizes us with the process of packaging software for distribution. After reading this chapter, the reader will be able to create a Docker Hub account & repository. Then, he will push his image up to it so other people with Docker Engine can run it. The chapter will also describe the process of private software distribution. At the end of the chapter, the reader will pull his own image from the repository to test the process.

Chapter 9 , Using Docker in Development,  discusses how to incorporate building Docker images into the Maven build process. To do that, we will utilize docker-maven plugins. We will also package a Java web application running on Spring Boot embedded server. To demonstrate the process of packaging a static web application into Docker container we will also run angular.js application with node.js backend from inside the Docker container.

Appendix A, More resources, directs you to some more useful resources for further reading, such as forums, blogs, and websites related to Docker. The chapter will also mention some useful third party tools related to Docker and show how they can be useful when working with Docker.

What you need for this book

You will need a Mac or PC, running OS X, MS Windows or Linux to be able to setup and run Docker. You can download Docker for free. You can read how to get and install it in Chapter 2, Installing Docker.

Who this book is for

This book is aimed at being a fast-paced and practical guide to get you up and running with Docker. It targets developers, IT professionals, DevOps, or anyone looking to quickly develop and deploy software to production at scale. If you are interested in Docker, DevOps, or containers in general, don’t look any further.

You will start with installing Docker and start working with images and containers. We will present different types of containers, their applications and show how to find and build images. This will allow you to familiarize 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.

Conventions

In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: Mount the downloaded WebStorm-10*.dmg disk image file as another disk in your system.

A block of code is set as follows:

html, body, #map {

height: 100%;

margin: 0;

padding: 0

}

Any command-line input or output is written as follows:

$ mkdir css $ cd css

New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: The shortcuts in this book are based on the Mac OS X 10.5+ scheme.

Note

Warnings or important notes appear in a box like this.

Tip

Tips and tricks appear like this.

Reader feedback

Feedback from our readers is always welcome. Let us know what you think about this book--what you liked or disliked. Reader feedback is important for us as it helps us develop titles that you will really get the most out of. To send us general feedback, simply e-mail feedback@packtpub.com, and mention the book's title in the subject of your message. If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide at www.packtpub.com/authors.

Customer support

Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.

Errata

Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books-maybe a mistake in the text or the code-we would be grateful if you could report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the Errata Submission Form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded to our website or added to any list of existing errata under the Errata section of that title.

To view the previously submitted errata, go to https://www.packtpub.com/books/content/support and enter the name of the book in the search field. The required information will appear under the Errata section.

Piracy

Piracy of copyrighted material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works in any form on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.

Please contact us at copyright@packtpub.com with a link to the suspected pirated material.

We appreciate your help in protecting our authors and our ability to bring you valuable content.

Questions

If you have a problem with any aspect of this book, you can contact us at questions@packtpub.com, and we will do our best to address the problem.

Chapter 1. Introduction to Docker

At the beginning, Docker was created as an internal tool by a Platform as a Service company called dotCloud. Later on, in March 2013, it was released as open source. Apart from the Docker Inc. team, which is the main sponsor, there are some other big names contributing to the tool—Red Hat, IBM, Microsoft, Google, and Cisco Systems, just to name a few. Software development today needs to be agile and react quickly to changes. We use methodologies such as Scrum, estimate our work in story points, and attend the daily stand-ups. But what about preparing our software for shipment and the deployment? Let's see how Docker fits into that scenario and can help us to be agile.

In this chapter, we will cover the following topics:

The basic idea behind Docker

A difference between virtualization and containerization

Benefits of using Docker

Components available to install

We will begin with the basic idea behind this wonderful tool.

The basic idea

The basic idea behind Docker is to pack an application with all of its dependencies (let it be binaries, libraries, configuration files, scripts, jars, and so on) into a single, standardized unit for software development and deployment. Docker containers wrap up a piece of software in a complete filesystem that contains everything it needs to run: code, runtime, system tools, and system libraries-anything you can install on a server. This guarantees that it will always run in the same way, no matter what environment it will be deployed in. With Docker, you can build a Node.js or Java project (but you are of course not limited to those two) without having to install Node.js or Java on your host machine. Once you're done with it, you can just destroy the Docker image, and it's as though nothing ever happened. It's not a programming language or a framework; rather, think of it as a tool that helps solve common problems such as installing, distributing, and managing the software. It allows programmers and DevOps to build, ship, and run their code anywhere.

You may think that Docker is a virtualization engine, but it's far from it as we will explain in a while.

Containerization versus virtualization

To fully understand what Docker really is, first we need to understand the difference between traditional virtualization and containerization. Let's compare those two technologies now.

Traditional virtualization

A traditional virtual machine, which represents the hardware-level virtualization, is basically a complete operating system running on top of the host operating system. There are two types of virtualization hypervisor: Type 1 and Type 2. Type 1 hypervisors provide server virtualization on bare metal hardware—there is no traditional end user's operating system. Type 2 hypervisors, on the other hand, are commonly used as a desktop virtualization—you run the virtualization engine on