Book Image

Continuous Delivery with Docker and Jenkins - Second Edition

By : Rafał Leszko
Book Image

Continuous Delivery with Docker and Jenkins - Second Edition

By: Rafał Leszko

Overview of this book

Continuous Delivery with Docker and Jenkins, Second Edition will explain the advantages of combining Jenkins and Docker to improve the continuous integration and delivery process of an app development. It will start with setting up a Docker server and configuring Jenkins on it. It will then provide steps to build applications on Docker files and integrate them with Jenkins using continuous delivery processes such as continuous integration, automated acceptance testing, and configuration management. Moving on, you will learn how to ensure quick application deployment with Docker containers along with scaling Jenkins using Kubernetes. Next, you will get to know how to deploy applications using Docker images and testing them with Jenkins. Towards the end, the book will touch base with missing parts of the CD pipeline, which are the environments and infrastructure, application versioning, and nonfunctional testing. By the end of the book, you will be enhancing the DevOps workflow by integrating the functionalities of Docker and Jenkins.
Table of Contents (18 chapters)
Title Page
Dedication
About Packt
Contributors
Preface
Index

Chapter 2: Introducing Docker


  1.  Containerization does not emulate the whole operating system; it uses the host operating system instead. The benefits of providing an application as a Docker image
  2. The benefits of providing an application as a Docker image are as follows:
    1. No issues with dependencies: The application is provided together with its dependencies
    2. Isolation: The application is isolated from the other applications running on the same machine
    3. Portability: The application runs everywhere, no matter which environment dependencies are present
  1. No, Docker Daemon can run natively only on the Linux machines. However, there are well-integrated virtual environments for both Windows and Mac.
  2. Docker image is a stateless serialized collection of files and the recipe of how to use them; Docker container is a running instance of the Docker image.
  3. A Docker image is built on top of another Docker image, which makes the layered structure. This mechanism is user-friendly and saves bandwidth and storage.
  4. Docker commit and Dockerfile.
  5. docker build
  6.  docker run
  7. Publishing a port means that the host's port is forwarded to the container's port.
  8. A Docker volume is the Docker host's directory mounted inside the container.