From a69546c9ee97f5847fb1c6aacd9258f436fa1461 Mon Sep 17 00:00:00 2001 From: Bryan Boreham Date: Tue, 26 Sep 2017 09:39:04 +0000 Subject: [PATCH] Reworded on review feedback --- site/troubleshooting.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/site/troubleshooting.md b/site/troubleshooting.md index 8f6f6c9c..f47180ef 100644 --- a/site/troubleshooting.md +++ b/site/troubleshooting.md @@ -293,22 +293,22 @@ restart. ## Troubleshooting the V2 plugin -If you have installed Weave Net via `docker plugin install`, then you -will need to download the `weave` script to run `weave status`, `weave ps` -or `weave report` as above. Do this as described in the -[install instructions](/site/install/installing-weave.md). +If Weave Net is installed via `docker plugin install`, download the +`weave` script to run `weave status`, `weave ps` or `weave report` as +above. Install Weave Net by following the [install +instructions](/site/install/installing-weave.md). -Docker "v2" plugins run as containers, but at a lower level within the -Docker environment, so you cannot view them with `docker ps`, `docker -inspect`, etc. +Docker "v2" plugins do run as containers, but at a lower level within +the Docker environment. Because of this, you cannot view them with +`docker ps`, `docker inspect`, etc. Do not run `weave launch`, `weave stop` or similar commands when using this plugin; use the `docker plugin` commands instead. You can run `weave reset`, but only after disabling the plugin via `docker plugin disable`. -Diagnostic logs from the plugin will go to the same place as the -Docker daemon, which will depend on your Linux install. For example, -if it uses `systemd`, then do this to view the Docker and plugin logs: +Diagnostic logs from the plugin go to the same place as the Docker +daemon, which will depend on your Linux install. For example, if it +uses `systemd`, then do this to view the Docker and plugin logs: sudo journalctl -u docker