From 0c2c75716065f278b90a302253c1378b130bb475 Mon Sep 17 00:00:00 2001
From: Alex Ellis <alexellis2@gmail.com>
Date: Wed, 31 May 2017 08:47:42 +0100
Subject: [PATCH] Add intro to managing images page.

---
 docs/managing-images.md | 22 ++++++++++++++++++++--
 1 file changed, 20 insertions(+), 2 deletions(-)

diff --git a/docs/managing-images.md b/docs/managing-images.md
index 3e969cd2..3b1771e8 100644
--- a/docs/managing-images.md
+++ b/docs/managing-images.md
@@ -1,5 +1,14 @@
 # Managing images
 
+Any Docker images you build for your FaaS functions need to be accessible by any Docker Swarm worker or manager in your cluster. The only exception is during development - when you may have a single-node cluster and the image is in your local image library.
+
+All images should be pushed to either a private repository or the Docker Hub:
+
+* Manually built FaaS images
+* Images build with the FaaS-CLI
+
+Repositories that need authentication will require configuration when deploying your FaaS functions.
+
 ## Using private Docker registries
 
 FaaS supports running functions from Docker images in private Docker registries.
@@ -19,11 +28,20 @@ curl -XPOST /system/functions -d {
 ```
 
 Base64-encoded basic auth can be resolved using your registry username and password:
+
 ````
-echo -n "user:password" | base64
+$ echo -n "user:password" | base64
 ````
 
-You can also find it in your `~/.docker/config.json` Docker credentials store, as a result of the `docker login` command:
+or (to prevent tracking in `history` command):
+
+```
+$ base64 -
+(type in) user:password (hit control+D twice)
+```
+
+You can also find this string your `~/.docker/config.json` file. Docker stores credentials here after you run the `docker login` command:
+
 ```
 cat ~/.docker/config.json
 {