Added troubleshooting to README

local/linux/README.md

@@ -7,6 +7,14 @@ These playbooks will do the following in a local environment:
   * Install [Ansible Service Broker](https://github.com/fusor/ansible-service-broker) on Origin
 
 ### Pre-Reqs
+  * Docker installed and configured
+
+    * Suggestion, to ease usage we allow our regular user to access the docker server by doing the below:
+
+      * ```sudo groupadd docker```
+      * ```sudo usermod -aG docker $USER```
+      * ```sudo systemctl restart docker```
+
   * Ansible needs to be installed so its source code is available to Python.
     * Check to see if Ansible modules are available to Python
       ```bash
@@ -80,3 +88,44 @@ These playbooks will do the following in a local environment:
 ### Tested with
   * ansible 2.3.0.0
     * Problems were seen using ansible 2.2 and lower
+
+
+### Troubleshooting
+
+#### pull() got an unexpected keyword argument 'decode'
+
+```
+Error pulling image docker.io/ansibleplaybookbundle/ansible-service-broker-apb:summit - pull() got an unexpected keyword argument 'decode'
+```
+
+This is a problem with having docker-py installed, and at a specific version. More info in https://github.com/ansible/ansible-modules-core/issues/5515.
+The recommended fix for this is to uninstall docker-py, as there is an ansible task for installing docker using pip.
+
+```
+<sudo> pip uninstall docker-py
+```
+
+#### APBs not visible from OpenShift Web UI
+
+In some cases APBs won't be visible from the OpenShift Console after `./run_setup_local.sh`.
+This can happen when the catalog is unable to talk to the broker due to an issue with iptables.
+
+The recommended fix is to flush iptables rules and reset the catasb environment.
+```
+sudo iptables -F
+./reset_environment.sh
+```
+
+#### Cannot connect to the Docker daemon. Is the docker daemon running on this host
+
+```
+TASK [openshift_setup : Resetting cluster, True]
+ ****************
+"error: cannot communicate with Docker"
+```
+
+This may be a permission issue, we recommend relaxing permissions on docker so your regular user is able to access docker.  The following will allow your regular user to access docker:
+
+  * ```sudo groupadd docker```
+  * ```sudo usermod -aG docker $USER```
+  * ```sudo systemctl restart docker```