book

Docker in Practice, Second Edition

by Ian Miell, Aidan Sayers

April 2019

Intermediate to advanced

384 pages

17h 6m

English

Manning Publications

Read now

Unlock full access

1.1. The what and why of Docker1.2. Building a Docker applicationSummary

2.1. Docker’s architecture2.2. The Docker daemon2.3. The Docker client2.4. Docker registries2.5. The Docker HubSummary
3.1. From VM to container3.2. Saving and restoring your work3.3. Environments as processesSummary
4.1. Building imagesSummary
5.1. Running containers5.2. Volumes—a persistent problemSummary
6.1. Staying ship-shapeSummary
7.1. Configuration management and Dockerfiles7.2. Traditional configuration management tools with Docker7.3. Small is beautifulSummary
8.1. Docker Hub automated builds8.2. More efficient builds8.3. Containerizing your CI processSummary
9.1. Interacting with other teams in the CD pipeline9.2. Facilitating deployment of Docker images9.3. Configuring your images for environments9.4. Upgrading running containersSummary
10.1. Container communication: Beyond manual linking10.2. Using Docker to simulate real-world networking10.3. Docker and virtual networksSummary
11.1. Simple single-host Docker11.2. Manual multi-host Docker11.3. Service discovery: What have we here?Summary
12.1. Multi-host DockerSummary
13.1. Organizational choice factors13.2. Areas to consider when adopting Docker13.3. Vendors, organizations, and productsSummary
14.1. Docker access and what it means14.2. Security measures in Docker14.3. Securing access to Docker14.4. Security from outside DockerSummary
15.1. Monitoring15.2. Resource control15.3. Sysadmin use cases for DockerSummary
16.1. Performance: You can’t ignore the tin16.2. When containers leak—debugging DockerSummary

Content preview from Docker in Practice, Second Edition

Chapter 8. Continuous integration: Speeding up your development pipeline

This chapter covers

Using the Docker Hub workflow as a CI tool
Speeding up your I/O-heavy builds
Using Selenium for automated testing
Running Jenkins within Docker
Using Docker as a Jenkins slave
Scaling your available compute with your dev team

In this chapter we’re going to look at various techniques that will use Docker to enable and improve your continuous integration (CI) efforts.

By now you should understand how Docker is well suited to being used for automation. Its lightweight nature, and the power it gives you to port environments from one place to another, can make it a key enabler of CI. We’ve found the techniques in this chapter to ...