From 32d060a1f38e85e5a0cfe6b3a98b9cfca16585cf Mon Sep 17 00:00:00 2001 From: Anne Henmi <41210220+ahh-docker@users.noreply.github.com> Date: Wed, 24 Oct 2018 09:27:56 -0600 Subject: [PATCH] Update ce-ee-node-activate.md --- engine/ce-ee-node-activate.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/engine/ce-ee-node-activate.md b/engine/ce-ee-node-activate.md index 57b73092ec..166febef48 100644 --- a/engine/ce-ee-node-activate.md +++ b/engine/ce-ee-node-activate.md @@ -101,9 +101,6 @@ Successfully activated engine. Restart docker with 'systemctl restart docker' to complete the activation. ``` -**NOTE:** If the Docker EE engines are in a swarm cluster, you only need to activate the license on the -manager node. This action stores the license as a swarm configuration, which is compatible with UCP. - 5. Check the Docker Engine version. The engine server will become EE, and the engine client will stay CE. ``` @@ -129,6 +126,8 @@ Server: **NOTE**: Your output may vary slightly from what is displayed on this page. +6. If you are running a Swarm cluster with CE, please repeat these steps on each node. + ## Offline CE-EE node activation For offline CE-EE node activation, you'll need to get the Docker Enterprise Engine onto the system. The recommended model is to download the EE `.deb` or `.rpm` packages manually and copy them to the target systems. Afterward, download the license manually, and copy that license to the target systems. Use the `--license ` command line option to the activate command.