Browse code
Move arm info to project/
Signed-off-by: Michael Crosby <crosbymichael@gmail.com>
Michael Crosby authored on 2015/11/24 06:54:17Showing 2 changed files
| 1 | 1 |
deleted file mode 100644 |
| ... | ... |
@@ -1,27 +0,0 @@ |
| 1 |
-# ARM support |
|
| 2 |
- |
|
| 3 |
-The ARM support should be considered experimental. It will be extended step by step in the coming weeks. |
|
| 4 |
- |
|
| 5 |
-Building a Docker Development Image works in the same fashion as for Intel platform (x86-64). |
|
| 6 |
-Currently we have initial support for 32bit ARMv7 devices. |
|
| 7 |
- |
|
| 8 |
-To work with the Docker Development Image you have to clone the Docker/Docker repo on a supported device. |
|
| 9 |
-It needs to have a Docker Engine installed to build the Docker Development Image. |
|
| 10 |
- |
|
| 11 |
-From the root of the Docker/Docker repo one can use make to execute the following make targets: |
|
| 12 |
-- make validate |
|
| 13 |
-- make binary |
|
| 14 |
-- make build |
|
| 15 |
-- make bundles |
|
| 16 |
-- make default |
|
| 17 |
-- make shell |
|
| 18 |
-- make |
|
| 19 |
- |
|
| 20 |
-The Makefile does include logic to determine on which OS and architecture the Docker Development Image is built. |
|
| 21 |
-Based on OS and architecture it chooses the correct Dockerfile. |
|
| 22 |
-For the ARM 32bit architecture it uses `Dockerfile.arm`. |
|
| 23 |
- |
|
| 24 |
-So for example in order to build a Docker binary one has to |
|
| 25 |
-1. clone the Docker/Docker repository on an ARM device `git clone git@github.com:docker/docker.git` |
|
| 26 |
-2. change into the checked out repository with `cd docker` |
|
| 27 |
-3. execute `make binary` to create a Docker Engine binary for ARM |
| 28 | 1 |
new file mode 100644 |
| ... | ... |
@@ -0,0 +1,27 @@ |
| 0 |
+# ARM support |
|
| 1 |
+ |
|
| 2 |
+The ARM support should be considered experimental. It will be extended step by step in the coming weeks. |
|
| 3 |
+ |
|
| 4 |
+Building a Docker Development Image works in the same fashion as for Intel platform (x86-64). |
|
| 5 |
+Currently we have initial support for 32bit ARMv7 devices. |
|
| 6 |
+ |
|
| 7 |
+To work with the Docker Development Image you have to clone the Docker/Docker repo on a supported device. |
|
| 8 |
+It needs to have a Docker Engine installed to build the Docker Development Image. |
|
| 9 |
+ |
|
| 10 |
+From the root of the Docker/Docker repo one can use make to execute the following make targets: |
|
| 11 |
+- make validate |
|
| 12 |
+- make binary |
|
| 13 |
+- make build |
|
| 14 |
+- make bundles |
|
| 15 |
+- make default |
|
| 16 |
+- make shell |
|
| 17 |
+- make |
|
| 18 |
+ |
|
| 19 |
+The Makefile does include logic to determine on which OS and architecture the Docker Development Image is built. |
|
| 20 |
+Based on OS and architecture it chooses the correct Dockerfile. |
|
| 21 |
+For the ARM 32bit architecture it uses `Dockerfile.arm`. |
|
| 22 |
+ |
|
| 23 |
+So for example in order to build a Docker binary one has to |
|
| 24 |
+1. clone the Docker/Docker repository on an ARM device `git clone git@github.com:docker/docker.git` |
|
| 25 |
+2. change into the checked out repository with `cd docker` |
|
| 26 |
+3. execute `make binary` to create a Docker Engine binary for ARM |