Fixed documentation on mapping of ~/.lnd

* Would have caused problems because ~/.loop wasn't mapped
* Now map entire home directory

DOCKER.md

@@ -32,13 +32,13 @@ Docker is very flexible so you can use that information however you choose. This
 
 One way of running `loopd` is 
 ```
-docker run --rm -it --name loopd -v $HOME/.lnd:/root/.lnd loop:latest loopd --network=testnet --lnd.host <my-lnd-ip-address>:10009
+docker run --rm -it --name loopd -v $HOME:/root loop:latest loopd --network=testnet --lnd.host <my-lnd-ip-address>:10009
 ```
 
 Things to note from this docker command:
 * You can stop the server with Control-C, and it'll clean up the associated stopped container automatically.
 * The name of the running container is 'loopd' (which you may need to know to run the `loop` command).
-* The '.lnd' directory in your home directory is mapped into the container, and `loopd` will look for your tls.cert and macaroon in the default locations. If this isn't appropriate for your case you can map whatever directories you choose and override where `loopd` looks for them using additional command-line parameters.
+* Your home directory is mapped into the container as the container user's home directory. `loopd` will look for your tls.cert and macaroon in the default locations in ~/.lnd, and will store its own data in ~/.loop. If mapping your home directory isn't appropriate for your case you can map whatever directories you choose and override where `loopd` looks for files using additional command-line parameters.
 * You probably need to specify your LND server host and port explicitly, since by default `loopd` looks for it on localhost and there is no LND server on localhost within the container.
 * No ports are mapped, so it's not possible to connect to the running `loopd` from outside the container. (This is deliberate. You can map ports 8081 and 11010 to connect from outside the container if you choose.)