From 7fe1f7e36336ac6da9b274352abef4ab6b74e5c2 Mon Sep 17 00:00:00 2001
From: Ventz Petkov <ventz_petkov@harvard.edu>
Date: Mon, 12 Feb 2018 16:50:11 -0500
Subject: [PATCH] Added detailed instructions around building your own image
 and thus customizing some of the arguments, versus pulling down the default
 dockerhub binary.

---
 README.md | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/README.md b/README.md
index 2bd2a33..28e65bd 100644
--- a/README.md
+++ b/README.md
@@ -26,6 +26,33 @@ The misp-modules extensions functionality has been included and can be
 accessed from http://[dockerhostip]:6666/modules.
 (thanks to Conrad)
 
+# Build Docker container vs using Dockerhub binary?
+
+We always recommend building your own Docker MISP image using our "build.sh" script.
+This allows you to change all the passwords and customize a few config options.
+
+That said, you can pull down the Dockerhub binary image, but this is
+_not_ supported or recommended. It's there purely for convenience, and so that you can "get
+a feel" for MISP without building it. It will by default contain "LOCALHOST" as all configured host everywhere, and this will only work on the same system or if you proxy/port forward.
+
+
+Building your own MISP Docker image is incredibly simple:
+```
+git clone https://github.com/harvard-itsecurity/docker-misp.git
+cd docker-misp
+
+# modify build.sh, specifically for:
+# 1.) all passwords (ROOT, MYSQL)
+# 2.) change at LEAST "MISP_FQDN" to your FQDN (domain)
+
+# Build the docker image - will take a bit, but it's a one time thing!
+# Run this from the root of "docker-misp"
+./build.sh
+```
+
+This will produce an image called: ```harvard-itsecurity/docker-misp```
+```
+
 # How to run it in 3 steps:
 
 ## 1. Initialize Database