Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

On Windows npipe protocol support

See original GitHub issue

I suspect I know the answer to this but just wanted to confirm with you guys one way or the other. Trying to use npipe URL on windows 10 with docker throws the below exception. Is it possible to add support for this or is this currently being worked on by @marcuslinke and his work with unixsockets/jnr/etc.?

Caused by: com.github.dockerjava.api.exception.DockerClientException: Unsupported protocol scheme found: 'npipe:////./pipe/docker_engine'. Only 'tcp://' or 'unix://' supported.
        at com.github.dockerjava.core.DefaultDockerClientConfig.checkDockerHostScheme(DefaultDockerClientConfig.java:96)
        at com.github.dockerjava.core.DefaultDockerClientConfig.<init>(DefaultDockerClientConfig.java:82)
        at com.github.dockerjava.core.DefaultDockerClientConfig$Builder.build(DefaultDockerClientConfig.java:431)
        at com.github.dockerjava.core.DefaultDockerClientConfig$Builder$build$1.call(Unknown Source)

Issue Analytics

State:
Created 7 years ago
Reactions:1
Comments:44 (31 by maintainers)

Top GitHub Comments

2reactions

kadwanevcommented, Jul 24, 2017

This is currently a requirement to be able to use docker-java on Azure as a managed app service. +1

2reactions

gesellixcommented, May 12, 2017

I’m aware that a Netty implementation will look different. Yet, there are at least two different Docker/Npipe client implementations to get some inspiration:

for Apache HttpClient: https://github.com/fabric8io/docker-maven-plugin/tree/f766cdbdd3d2ef353604dc3bd0a38c51f5e88c45/src/main/java/io/fabric8/maven/docker/access/hc/win
for Square’s OkHttp: https://github.com/docker-client/docker-filesocket/tree/9cc1ad1a0bce51ceb6b561ddef4a3664ac3c629a/src/main/groovy/de/gesellix/docker/client/filesocket (yep, the same self plug as already mentioned above.)

Though I personally wouldn’t prefer Windows as dev platform, the necessary code to ease Windows devs working without additional setup is more or less the same like for Unix domain sockets. Maybe the recent changes on the Netty side for Unix sockets will help with the Named pipe, too?