Docker Cookbook

110 | Chapter 4: Docker Configuration and Development

---

build the 
docker:master
image defined in 
/tmp/docker/Dockerfile
. This can take a bit
of time the first time you do it:
$ vagrant ssh
$ cd /tmp/docker
$ sudo make binary
docker build -t "docker:master" .
Sending build context to Docker daemon 55.95 MB
Sending build context to Docker daemon
Step 0 : FROM ubuntu:14.04
...
Once this completes, you will have a new Docker binary:
$ cd bundles/1.9.0-dev/binary/docker
$ ls
docker docker-1.9.0-dev docker-1.9.0-dev.md5 docker-1.9.0-dev.sha256
See Also
• How to contribute to Docker on 
GitHub
4.3 Running the Docker Test Suite for Docker
Development
Problem
You have made some changes to the Docker source and have successfully built a new
binary. You also need to make sure that you pass all the tests.
Solution
Use the Makefile 
test
target to run the four sets of tests present in the Docker source.
Alternatively, pick only the set of tests that matters to you:
$ cat Makefile
...
test: build
$(DOCKER_RUN_DOCKER) hack/make.sh binary cross \
test-unit test-integration \
test-integration-cli test-docker-py
test-unit: build
$(DOCKER_RUN_DOCKER) hack/make.sh test-unit
test-integration: build
$(DOCKER_RUN_DOCKER) hack/make.sh test-integration
test-integration-cli: build
4.3 Running the Docker Test Suite for Docker Development | 111

---

$(DOCKER_RUN_DOCKER) hack/make.sh binary test-integration-cli
test-docker-py: build
$(DOCKER_RUN_DOCKER) hack/make.sh binary test-docker-py
...
You can see in the Makefile that you can choose which set of tests you want to run. If
you run all of them with 
make test
, it will also build the binary:
$ sudo make test
....
---> Making bundle: test-docker-py (in bundles/1.9.0-dev/test-docker-py)
+++ exec docker --daemon --debug --storage-driver vfs \
-exec-driver native \
--pidfile \
/go/src/github.com/docker/docker/bundles/1.9.0-dev/ \
test-docker-py/docker.pid
........................................................
----------------------------------------------------------------------
Ran 56 tests in 75.366s
OK
Depending on test coverage, if all the tests pass, you have some confidence that your
new binary works.