Odroid C2 and Docker images

Quote:

Originally Posted by devilsadvocate

Has anyone here successfully installed Docker with their Odroid C2 running Kali? Or any other ARM hardware platform like the Raspberry Pi or Banana Pi?

I imagine it can be done if the correct repository could be found (or created).

This is desirable due to the fact that the machine name is "aarch64" instead of "arm64". What this means is that there are many Debian packages that aren't, at this time, readily available for Kali on the Odroid C2. (The machine name is viewable by executing "uname -m".)

I have been trying to find a way to install Sublime Text 3 or Atom (nice text editors) in Kali on the Odroid C2 and it occurred to me that Docker could be a good solution. Those text editors aren't readily available for "arm64", nevermind "aarch64". Docker could be a good workaround, but it seems to have the same problem of not being available for the Odroid C2 Kali image.

Related issues that put me on this path:

1. The kernel headers don't seem to be included in the Odroid C2 image, which makes running "make" on some things impossible, in particular any rtl8812au driver for monitor mode capability. I haven't checked the other Odroid or Raspberry Pi images for the presence of "linux-headers", but that's only because I don't own the hardware yet (Odroid XU3, Raspberry Pi 3).
2. What wireless adapters are supported "out of the box" for monitor mode and packet injection for the Odroid C2. For example, AFAIK, the only wireless adapter that supports the a band seems to be the Alfa AWUS051NH and it works very well in the current Odroid C2 Kali ARM image. Other adapters like the AWUS1900 and the AWUS036ACH don't have a working rtl8812au driver that supports monitor mode and packet injection.

I will keep looking for any Debian repositories that could be used to get Docker installed on the Odroid C2 image.

Thanks in advance for any help on how to address these limitations of the Odroid C2 Kali image.

AArch64 is the official architecture name. arm64 is the packaging name.

In regards to 1) the kernel headers are there, they are located in /usr/src/kernel - /lib/modules/3.14.x/ should have the proper symlinks in there. The thing that might be required is to

1) cd /usr/src/kernel
1) cp .config ../odroid-c2.config
2) make mrproper
3) cp ../odroid-c2.config .config
4) make prepare && make modules_prepare

This is unfortunately due to the fact that when you run make modules_prepare while cross compiling the kernel (as we do when building the images) the helper utilities are compiled for the host, and not for arm64.

If a module is complaining that aarch64 is incorrect, that is likely due to an error in the module's build system. Be sure your external module has the latest sources, as they're probably detecting things incorrectly or not making the proper aarch64->arm64 conversion in their build system.

As for docker, because Kali is based upon debian, you can do the following

curl -fsSL https://download.docker.com/linux/debian/gpg | apt-key add -
echo "deb https://download.docker.com/linux/debian stretch stable" >> /etc/apt/sources.list.d/docker.list
apt-get update
apt-get install docker-ce

Then go about using various docker images that are available for arm64.

Please note: what you want to do with sublime text3 or atom won't work because, in the case of sublime, the developer doesn't offer an arm64 binary. In the case of Atom, it's because only bleeding edge versions of Electron support arm64 work and afaik, it hasn't been pushed to a stable release yet. Using docker, doesn't give arm64 the ability to run x86/amd64 binaries, you'd need to use something like qemu for that.

Odroid C2 and Docker images - aarch64