Skip to content

Windows container named pipe issues #70

@1480c1

Description

@1480c1

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions