Docker is a light-weight virtual machine with excellent cross-platform support. This allows us to run something very close to the ev3dev OS on any desktop or notebook computer. This means that we get the same versions of all of the libraries running on the EV3 but compile with the power of a desktop processor.
This will only work on 64-bit operating systems. We do not maintain images for 32-bit operating systems.
Docker has excellent documentation, so we will just send you to their download page. Come back when you have Docker installed for Windows, Mac or Linux.
Docker for Linux has quite a bit of information to read. This may help you sort through it. The most important parts are:
Also, you will need to install
qemu-user-static on your host computer, otherwise
you will get an error:
exec user process caused "exec format error".
We provide a Docker image with the most common developer tools already installed. Download it by running…
docker pull ev3dev/debian-jessie-cross
This will take some time. The download is nearly 1GB!
When it is finished, we can give it a shorter name…
docker tag ev3dev/debian-jessie-cross ev3cc
Docker images are immutable. You can always revert back to this image after making changes without having to download it again.
You can see a list of images you have downloaded by running…
… and delete them with…
docker rmi <image-name-or-hash>
But don’t delete the one you just downloaded yet!
Let’s do the classic hello world program in C. Create a new, empty directory
wherever you like. In your favorite text editor, paste this and save it as
hello.c. For this example, we will be using
If you are using Windows, you must explicitly allow shared drives in the Docker control panel first!
Unless you are using Windows 10 Pro edition, you may have received the following error when trying to install Docker using
HyperV is not available on home editions. Please use Docker Toolbox.
This is fine, you can just download Docker Toolbox instead.
Docker Toolbox however handles shared drives differently; there is no whale icon in the system tray. Instead, Docker Toolbox automatically allows sharing of your
C:\Users\myname folder. Also, the path handling is different, you have to use paths in linux style, so the command below has to be changed:
docker run --rm --it -v /c/Users/myname/example/:/src -w /src ev3cc
Now, we compile using the docker image. First we run a new docker container…
docker run --rm -it -v C:\Users\myname\example\:/src -w /src ev3cc
Let’s break down the command:
runmeans we are running a new container.
--rmindicates that we want to throw away the container when we are done. If you don’t do this, docker saves a new container from each
runcommand, which takes up space on your hard drive.
-itis two options, it means “interactive” and “tty”. This will let us use the command prompt inside of the container.
-v <host-path>:<container-path>lets us use a directory from our host computer inside of the container.
-w <container-path>is the working directory inside of the container.
ev3ccis the name of the docker image we are using.
Now we can compile our program…
arm-linux-gnueabi-gcc -o hello hello.c
Note: For BeagleBone and Raspberry Pi 2/3 use
gnueabihf instead of
Since this program does not depend on any hardware drivers, we can actually run
this program inside of the Docker container! There are some caveats though…
You must be running Docker >= 1.12 and if you are using a Linux host you must
have the proper format registered with
This will output:
Also, a binary file called
hello will now exist in
on your host computer. You can copy this file to your EV3 and run it!
To exit the docker container, simply type…
If you need to install additional libraries, you need to be sure to install
armel version (or
armhf for BeagleBone and Raspberry Pi 2/3). Example:
sudo apt-get install libsomething-dev:armel
The same example also shows a trick of how to keep a Docker container running so that you can run builds without starting a new container each time.
gdb is the GNU debugger. TODO: need to find a good link for intro to gdb.
Although it is possible to run gdb directly on the EV3, you will quickly run out of memory. To get around this, we will do remote debugging.
On your EV3, install
sudo apt-get install gdbserver
Now, let’s debug our “hello world” program. First, we need to make sure we compile
with debugging symbols (thats the
-g flag). You will need to copy the new
executable to the EV3 too if you haven’t done the mounting a remote file system
arm-linux-gnueabi-gcc -g -o hello hello.c
On the EV3, run
host is the name or IP address of your host
computer (or VM) and
3333 is an arbitrary TCP port.
gdbserver host:3333 hello
Then back in the brickstrap shell run gdb.
target remote tells gdb to connect
to your EV3. Host name resolution seems to have issues in the brickstrap shell,
so you are better off using the IP address of your EV3 (192.168.0.100 in this
example). And of course, the port number needs to match what you used with
This starts an interactive gdb session. You have to type in the commands
on each line that starts with
(gdb); the other lines are output and
you should not type them.
... Reading symbols from /host-rootfs/home/david/work/brickdm/build/hello...done. ... (gdb) target remote 192.168.0.100:3333 Remote debugging using 192.168.0.144:1234 ... (gdb) break hello.c:5 Breakpoint 1 at 0x8428: file hello.c, line 5. (gdb) c Continuing. Breakpoint 1, main () at hello.c:5 5 printf("Hello World!\n"); (gdb) c Continuing. [Inferior 1 (process 1821) exited normally] qemu: Unsupported syscall: 26 (gdb) q