Docker Desktop provides npipe:////./pipe/dockerDesktopWindowsEngine as the DOCKER_HOST in the desktop-windows context, which is automatically set in config.json, but this causes issue when attempting to run systemPing() from a client initalized using fromDockerConfig() as the sdk doesn't like the npipe://// prefix.
[cause]: Error: connect ENOENT ////./pipe/dockerDesktopWindowsEngine
at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1645:16)
at PipeConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
errno: -4058,
code: 'ENOENT',
syscall: 'connect',
address: '////./pipe/dockerDesktopWindowsEngine'
}
I did confirm that if I manually set DOCKER_HOST as npipe://./pipe/dockerDesktopWindowsEngine, it will fix the issue and systemPing() does show '1.53'.
Relevant files for me were ~\.docker\config.json and ~\.docker\contexts\meta\20cca48ece26c362e388a0f192667c1ed683f9fa5f4425a88d4fea84e001311e\meta.json
Docker Desktop provides
npipe:////./pipe/dockerDesktopWindowsEngineas theDOCKER_HOSTin the desktop-windows context, which is automatically set in config.json, but this causes issue when attempting to runsystemPing()from a client initalized usingfromDockerConfig()as the sdk doesn't like thenpipe:////prefix.I did confirm that if I manually set
DOCKER_HOSTasnpipe://./pipe/dockerDesktopWindowsEngine, it will fix the issue andsystemPing()does show'1.53'.Relevant files for me were
~\.docker\config.jsonand~\.docker\contexts\meta\20cca48ece26c362e388a0f192667c1ed683f9fa5f4425a88d4fea84e001311e\meta.json