Get-hnsnetwork missing in agent v2.3.[12] for Windows

Rancher 2.x
1

When I try to add a windows worker node to a cluster (via the rancher UI, which gives a powershell command to run), the powershell command fails with the message

get-containernetwork : The term ‘get-containernetwork’ is not recognized as the name of a cmdlet, function, script, file, or operable program

Starting an interactive powershell in the container, I can see that the root cause is that none of the hostnetworkingservice powershell commands are present, specifically get-hnsnetwork.

On the docker host, these commands are available and get-hsnnetwork yields results.

I’m running Windows Server 2019, version 1809 Build 17763.805 with Docker EE.

docker version yields
Client: Docker Engine - Enterprise
Version: 19.03.1
API version: 1.40
Go version: go1.12.5
Git commit: f660560464
Built: 07/25/2019 20:59:52
OS/Arch: windows/amd64
Experimental: false

Server: Docker Engine - Enterprise
Engine:
Version: 19.03.1
API version: 1.40 (minimum version 1.24)
Go version: go1.12.5
Git commit: f660560464
Built: 07/25/2019 20:57:41
OS/Arch: windows/amd64
Experimental: true

I’m basically following the instructions out of the box, although I admit that I’m a beginner with Rancher. Am I missing something, or this an issue?

2

I know this is a few months late, but in case anyone else comes across this:

If you’re running this in an Amazon AWS Windows server, make sure you use Powershell and not Powershell for AWS. Powershell for AWS does not have the required cmdlets.