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

Using Docker volumes


Imagine that you would like to run the database as a container. You can start such a container and enter the data. Where is it stored?What happens when you stop the container or remove it? You can start the new one, but the database will be empty again. Unless it's your testing environment, you'd expect to have your data persisted permanently.

Docker volume is the Docker host's directory mounted inside the container. It allows the container to write to the host's filesystem as if it was writing to its own. The mechanism is presented in the following diagram:

Docker volume enables the persistence and sharing of the container's data. Volumes also clearly separate the processing from the data. Let's start with an example:

  1. Specify the volume with the -v <host_path>:<container_path> option and then connect to the container:
$ docker run -i -t -v ~/docker_ubuntu:/host_directory ubuntu:18.04 /bin/bash
  1. Create an empty file in host_directory in the container:
root@01bf73826624...