From 937bf99c3aaa7112424cb937da4720fed32d2671 Mon Sep 17 00:00:00 2001
From: Erwin Ried <1091420+eried@users.noreply.github.com>
Date: Tue, 5 May 2020 14:32:14 +0200
Subject: [PATCH] Updated Compile firmware (markdown)

---
 Compile-firmware.md | 15 +++++++++++++--
 1 file changed, 13 insertions(+), 2 deletions(-)

diff --git a/Compile-firmware.md b/Compile-firmware.md
index 268e9fb..8298fc3 100644
--- a/Compile-firmware.md
+++ b/Compile-firmware.md
@@ -1,7 +1,18 @@
-The easiest way is to use Docker.
+The easiest way is to use Docker. After you install Docker in your machine, if you are inclined for using the command line, you can try the following:
 
 For building:
+
 `docker build -t portapackccache -f dockerfile-nogit .`
 
 For running (in the root of the repo):
-`docker run -it -v ${PWD}:/havoc portapackccache`
\ No newline at end of file
+
+`docker run -it -v ${PWD}:/havoc portapackccache`
+
+# Using Docker Hub and Kitematic
+The required Docker image is also in Docker Hub, browse for it in [Kitematic](https://github.com/docker/kitematic):
+
+[[img/Kitematic_MChWCyp6g1.png]]
+
+You need to configure the path to the source code from the Volumes of the container as show in the image below. Everytime you run this container, it will compile the source and (if successful) leave the results in `build/firmware/`
+
+[[img/Kitematic_VL5an8rufV.png]]
\ No newline at end of file