docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update ce-ee-node-activate.md

This commit is contained in:
Anne Henmi 2018-10-24 09:27:56 -06:00 committed by GitHub
parent d9599eb932
commit 32d060a1f3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
engine/ce-ee-node-activate.md
View File

@ -101,9 +101,6 @@ Successfully activated engine.
Restart docker with 'systemctl restart docker' to complete the activation. 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. 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. **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 ## 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 <path/to/license.file>` command line option to the activate command. 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 <path/to/license.file>` command line option to the activate command.