ENOENT when accessing WORKLOADURI with Node.js module on Windows containers

I’m attempting to use Node.js modules using Windows as the underlying host operating system.

I’ve successfully booted the module under the IoT Edge environment, but now I have an issue where I get the following error when running Client.fromEnvironment:

Error: connect ENOENT /C:/ProgramData/iotedge/workload/sock
    at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)

I noticed that there’s a forward slash at the beginning of the path and that is probably part of the problem.

Expected Behavior

Client.fromEnvironment should work without any issues.

Current Behavior

Client.fromEnvironment throws an exception:

Error: connect ENOENT /C:/ProgramData/iotedge/workload/sock
    at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)

Steps to Reproduce

1. Run the example Node.js module solution create by the Azure IoT Edge Visual Studio Code extension under a Windows machine.
2. Get the error showing up under “iotedge logs <module>”.

Context (Environment)

Device (Host) Operating System

Windows 10 Enterprise 1809

Architecture

windows-amd64

Container Operating System

Windows containers

Runtime Versions

iotedged

1.0.6.1

Edge Agent

1.0

Edge Hub

1.0

Docker

Client: Docker Engine - Community Version: 18.09.2 API version: 1.39 Go version: go1.10.8 Git commit: 6247962 Built: Sun Feb 10 04:12:31 2019 OS/Arch: windows/amd64 Experimental: false

Server: Docker Engine - Community Engine: Version: 18.09.2 API version: 1.39 (minimum version 1.24) Go version: go1.10.6 Git commit: 6247962 Built: Sun Feb 10 04:28:48 2019 OS/Arch: windows/amd64 Experimental: false

[Griffrez]

Sounds good to me.

[avranju]

This should work once support for Unix Domain Sockets lands in the Node.js SDK on Windows. Do you think its OK to close this issue here and continue tracking this on the Node SDK repo?