Docker Cookbook

2.11 Running a Private Registry | 61

---

2.12 Setting Up an Automated Build on Docker Hub for
Continuous Integration/Deployment
Problem
You have access to 
Docker Hub
(see 
Recipe 2.9
) and already pushed an image to it.
However, this is a manual process. You want to automate the build of this image every
time you commit a change to it.
Solution
Instead of setting up a standard repository, create an 
Automated Build
repository and
point to your application on 
GitHub
 or 
Bitbucket
.
On your Docker Hub page, click the Add Repository button and select Automated
Build (
Figure 2-2
). You will then have the choice between GitHub and Bitbucket
(
Figure 2-3
).
Figure 2-2. Create an automated build repository
62 | Chapter 2: Image Creation and Sharing

---

Figure 2-3. Choosing between GitHub and Bitbucket
Docker Hub allows you to set up an automated build as a public or
private repository pointing to a public or private code repository. If
you are setting up a private automated build, Docker Hub will need
read and write access to your GitHub account.
After selecting the type of online version control system you want to use, you can
select the project you want to build from (
Figure 2-4
). This should be a project on
GitHub or Bitbucket that contains the Dockerfile you want to build. Next, you can
give a name to the Docker Hub repository you are creating, select the branch, and
specify the location of the Dockerfile. This is handy, as it allows you to maintain sev‐
eral Dockerfiles inside a single GitHub/Bitbucket repository. Docker Hub creates a
GitHub hook in your GitHub repository.