diff --git a/docs/GettingStarted.md b/docs/GettingStarted.md
index dc2b2f7..7e7caf8 100644
--- a/docs/GettingStarted.md
+++ b/docs/GettingStarted.md
@@ -69,4 +69,4 @@ That should open https://www.hello.local in a new browser's tab, with a fresh Dr
 ```
 ce-dev shell
 ```
-Will open a shell in the 'web' container. You can then `cd ~/deploy/live.local` and run a `drush uli` to grab a login link.
+Will open a shell in the 'web' container. You can then `cd ~/deploy/live.local` and run a `vendor/drush/drush/drush uli` to grab a login link.
diff --git a/docs/Troubleshooting.md b/docs/Troubleshooting.md
index c35541a..147f0b4 100644
--- a/docs/Troubleshooting.md
+++ b/docs/Troubleshooting.md
@@ -24,3 +24,23 @@ sudo update-initramfs -c -k all
 ```
 
 They will take a while to run (about 10 minutes), but once complete reboot your machine and delete any created containers that velong to the ce_dev image. When you rebuild the ce-dev controller (by running any command) it should create fine.
+
+## VM Networking issue
+If you're running ce-dev from within a Virtual Machine (eg. KVM/qemu), Docker container network ports are only 'exposed' to the hypervisor (ie the VM), and are not published for external access.
+In order to access sites/files deployed by ce-dev, the ports needs to be published so that the Docker containers can be accessed from your workstation.
+After running ```ce-dev init``` (before ```ce-dev start```) edit the ~/project/ce-dev/docker-compose.yml
+
+Replace;
+```
+    expose:
+      - 443
+      - 80
+      - '22'
+```
+With;
+```
+    ports:
+      - '443:443'
+      - '80:80'
+      - '22'
+```