From e85868c70c7b4299097332f14a3ebafa743ee320 Mon Sep 17 00:00:00 2001 From: Alexandre Beslic Date: Fri, 29 Jan 2016 11:28:43 -0800 Subject: [PATCH] docs: add note for the case of the daemon being started through ssh Signed-off-by: Alexandre Beslic --- docs/install-manual.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/install-manual.md b/docs/install-manual.md index 263b0a5b84..9cc5d3ec28 100644 --- a/docs/install-manual.md +++ b/docs/install-manual.md @@ -36,6 +36,13 @@ Docker engine as registered. To workaround this problem, you can generate a new ID for each node with affected by this issue. To do this stop the daemon on a node, delete its `/etc/docker/key.json` file, and restart the daemon. +If you use `ssh` to start the Engine `daemon`, make sure the daemon runs in the +background. You can do this using `disown` or `nohup` in combination with the `&` +(ampersand). Or you could launch the `daemon` through `systemd` or any other +Linux-distribution-specific method. Regardless of which launch method you +choose, make sure the daemon process does not stop when your session on a node +ends. + You can run Docker Swarm on Linux 64-bit architectures. You can also install and run it on 64-bit Windows and Max OSX but these architectures are *not* regularly tested for compatibility.