github.com/demonoid81/moby@v0.0.0-20200517203328-62dd8e17c460/project/ARM.md (about) 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 deb 16 - make bundles 17 - make default 18 - make shell 19 - make test-unit 20 - make test-integration 21 - make 22 23 The Makefile does include logic to determine on which OS and architecture the Docker Development Image is built. 24 Based on OS and architecture it chooses the correct Dockerfile. 25 For the ARM 32bit architecture it uses `Dockerfile.armhf`. 26 27 So for example in order to build a Docker binary one has to: 28 1. clone the Docker/Docker repository on an ARM device `git clone https://github.com/demonoid81/moby.git` 29 2. change into the checked out repository with `cd docker` 30 3. execute `make binary` to create a Docker Engine binary for ARM 31 32 ## Kernel modules 33 A few libnetwork integration tests require that the kernel be 34 configured with "dummy" network interface and has the module 35 loaded. However, the dummy module may be not loaded automatically. 36 37 To load the kernel module permanently, run these commands as `root`. 38 39 modprobe dummy 40 echo "dummy" >> /etc/modules 41 42 On some systems you also have to sync your kernel modules. 43 44 oc-sync-kernel-modules 45 depmod