Windows container named pipe issues
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 70/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- docker, node.js, typescript
- Domain
- devtools
Research direction
Start by comparing the DOCKER_HOST values in ~/.docker/config.json and the desktop-windows context meta.json, then trace how fromDockerConfig() passes the named-pipe host to systemPing(). Reproduce the failure with the npipe://// prefix and confirm that systemPing() succeeds using the Docker Desktop Windows engine configuration.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- TypeScript
- Stars
- 107
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker/node-sdk
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Podman compatibility Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100