mirror of https://github.com/docker/docs.git
Updated from 2.1 to 3.0 (#9162)
This commit is contained in:
Olly P
GitHub
parent
513e600842
commit
d626941413
|
|
@ -6,13 +6,14 @@ redirect_from:
|
|||
- /datacenter/ucp/3.0/guides/admin/configure/join-nodes/join-windows-nodes-to-cluster/
|
||||
---
|
||||
|
||||
Docker Enterprise 2.1 supports worker nodes that run on Windows Server 2016, 1709,
|
||||
or 1803. Only worker nodes are supported on Windows, and all manager nodes in the cluster
|
||||
must run on Linux.
|
||||
Docker Enterprise 3.0 supports worker nodes that run on Windows Server 2016 and
|
||||
Windows Server 2019. Only worker nodes are supported on Windows, and all
|
||||
manager nodes in the cluster must run on Linux. Additionally Windows worker
|
||||
nodes can only be used by the Swarm Orchestrator.
|
||||
|
||||
Follow these steps to enable a worker node on Windows.
|
||||
|
||||
1. Install Docker Engine - Enterprise on Windows Server 2016, 1709, or 1803.
|
||||
1. Install Docker Engine - Enterprise on Windows Server 2016 or 2019.
|
||||
2. Configure the Windows node.
|
||||
3. Join the Windows node to the cluster.
|
||||
|
||||
|
|
@ -20,9 +21,10 @@ Follow these steps to enable a worker node on Windows.
|
|||
|
||||
## Install Docker Engine - Enterprise on Windows Server
|
||||
|
||||
[Install Docker Engine - Enterprise](/engine/installation/windows/docker-ee/#use-a-script-to-install-docker-ee)
|
||||
on a Windows Server 2016, 1709 or 1803 instance to enable joining a cluster that's managed by
|
||||
Docker Enterprise 2.1.
|
||||
[Install Docker Engine -
|
||||
Enterprise](/engine/installation/windows/docker-ee/#use-a-script-to-install-docker-ee)
|
||||
on a Windows Server 2016 or 2019 instance before joining the node to a Docker
|
||||
Enterprise Cluster.
|
||||
|
||||
## Configure the Windows node
|
||||
|
||||
|
|
@ -47,14 +49,20 @@ docker container run --rm {{ page.ucp_org }}/{{ page.ucp_repo }}:{{ page.ucp_ver
|
|||
{{ page.ucp_org }}/ucp-dsinfo-win:{{ page.ucp_version }}
|
||||
```
|
||||
|
||||
On Windows Server 2016, in a PowerShell terminal running as Administrator,
|
||||
log in to Docker Hub with the `docker login` command and pull the listed images.
|
||||
On a Windows Server node, in a PowerShell terminal running as Administrator,
|
||||
log in to Docker Hub with the `docker login` command and pull the listed
|
||||
images.
|
||||
|
||||
```powershell
|
||||
docker image pull {{ page.ucp_org }}/ucp-agent-win:{{ page.ucp_version }}
|
||||
docker image pull {{ page.ucp_org }}/ucp-dsinfo-win:{{ page.ucp_version }}
|
||||
```
|
||||
|
||||
If the cluster is deployed in an offline site, where the nodes do not have
|
||||
access to the Docker Hub, UCP images can be sideloaded onto the Windows Server
|
||||
nodes. Follow the instructions on the [install
|
||||
offline](/ee/ucp/admin/install/install-offline/) page to sideload the images.
|
||||
|
||||
### Run the Windows node setup script
|
||||
|
||||
You need to open ports 2376 and 12376, and create certificates
|
||||
|
|
@ -89,12 +97,12 @@ to the corresponding files in `C:\ProgramData\docker\daemoncerts`:
|
|||
```json
|
||||
{
|
||||
...
|
||||
"debug": true,
|
||||
"tls": true,
|
||||
"tlscacert": "C:\ProgramData\docker\daemoncerts\ca.pem",
|
||||
"tlscert": "C:\ProgramData\docker\daemoncerts\cert.pem",
|
||||
"tlskey": "C:\ProgramData\docker\daemoncerts\key.pem",
|
||||
"tlsverify": true,
|
||||
"debug": true,
|
||||
"tls": true,
|
||||
"tlscacert": "C:\ProgramData\docker\daemoncerts\ca.pem",
|
||||
"tlscert": "C:\ProgramData\docker\daemoncerts\cert.pem",
|
||||
"tlskey": "C:\ProgramData\docker\daemoncerts\key.pem",
|
||||
"tlsverify": true,
|
||||
...
|
||||
}
|
||||
```
|
||||
|
|
@ -191,12 +199,9 @@ The `dockerd` service and the Windows environment are now configured to join a D
|
|||
|
||||
## Windows nodes limitations
|
||||
|
||||
Some features are not yet supported on Windows nodes:
|
||||
The following features are not yet supported on Windows Server 2016 or 2019:
|
||||
|
||||
* Networking
|
||||
* The cluster mode routing mesh can't be used on Windows nodes. You can expose
|
||||
a port for your service in the host where it is running, and use the HTTP
|
||||
routing mesh to make your service accessible using a domain name.
|
||||
* Encrypted networks are not supported. If you've upgraded from a previous
|
||||
version, you'll also need to recreate the `ucp-hrm` network to make it
|
||||
unencrypted.
|
||||
|
|
@ -211,6 +216,15 @@ Some features are not yet supported on Windows nodes:
|
|||
* Mounts
|
||||
* On Windows, Docker can't listen on a Unix socket. Use TCP or a named pipe
|
||||
instead.
|
||||
* Orchestration
|
||||
* Windows Containers can only be scheduled by the Docker Swarm orchestrator.
|
||||
|
||||
The following features are not yet supported on Windows Server 2016:
|
||||
|
||||
* Networking
|
||||
* The cluster mode routing mesh can't be used on Windows nodes. You can expose
|
||||
a port for your service in the host where it is running, and use the HTTP
|
||||
routing mesh to make your service accessible using a domain name.
|
||||
|
||||
## Known Issues
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue