Reworded on review feedback

This commit is contained in:
Bryan Boreham committed 2017-09-26 09:39:04 +00:00
1 parent d63a21363e
commit a69546c9ee
1 file changed
+10 -10
+10 -10
View File
@@ -293,22 +293,22 @@ restart.
## <a name="v2plugin"></a>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