|
...
|
...
|
@@ -40,22 +40,24 @@ with the name of branch or revision number.
|
|
40
|
40
|
|
|
41
|
41
|
## Build the Environment
|
|
42
|
42
|
|
|
43
|
|
-This following command will build a development environment using the
|
|
44
|
|
-Dockerfile in the current directory. Essentially, it will install all
|
|
|
43
|
+This following command builds a development environment using the
|
|
|
44
|
+Dockerfile in the current directory. Essentially, it installs all
|
|
45
|
45
|
the build and runtime dependencies necessary to build and test Docker.
|
|
46
|
|
-This command will take some time to complete when you first execute it.
|
|
|
46
|
+Your first build will take some time to complete. On Linux systems:
|
|
47
|
47
|
|
|
48
|
48
|
$ sudo make build
|
|
|
49
|
+
|
|
|
50
|
+On Mac OS X, from within the `boot2docker` shell:
|
|
|
51
|
+
|
|
|
52
|
+ $ make build
|
|
|
53
|
+
|
|
|
54
|
+> **Note**:
|
|
|
55
|
+> On Mac OS X, **do not** build Docker make targets such as `build`, `binary`, and `test`
|
|
|
56
|
+> under root (sudo).
|
|
49
|
57
|
|
|
50
|
58
|
If the build is successful, congratulations! You have produced a clean
|
|
51
|
59
|
build of docker, neatly encapsulated in a standard build environment.
|
|
52
|
60
|
|
|
53
|
|
-> **Note**:
|
|
54
|
|
-> On Mac OS X, make targets such as `build`, `binary`, and `test`
|
|
55
|
|
-> must **not** be built under root. So, for example, instead of the above
|
|
56
|
|
-> command, issue:
|
|
57
|
|
->
|
|
58
|
|
-> $ make build
|
|
59
|
61
|
|
|
60
|
62
|
## Build the Docker Binary
|
|
61
|
63
|
|