Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker (client) and docker-machine binaries hang #30

Closed
atrauzzi opened this issue Apr 7, 2016 · 11 comments
Closed

docker (client) and docker-machine binaries hang #30

atrauzzi opened this issue Apr 7, 2016 · 11 comments

Comments

@atrauzzi
Copy link

atrauzzi commented Apr 7, 2016

Attempting to use the docker client or docker-machine (both go apps) seems to hang my console.

I can ctrl-c to get out, but they're not working.

@jolibert
Copy link

jolibert commented Apr 7, 2016

I'm not a docker expert but the shell can lag a lot while ctrl-c.
Let him do before closing a window.

@russalex
Copy link
Contributor

Docker is not a supported scenario at this time. We have seen some interest. If this is something you'd like to see I recommend going and voting on our User Voice page.

@atrauzzi
Copy link
Author

Hmm, I think you pulled the trigger too quickly here.

I'm not talking about the docker engine. I'm talking about the client.

@bitcrazed

@lewisl9029
Copy link

@russalex I agree with @atrauzzi

Docker engine not being able to run on WSL is completely understandable, but I see no reason why WSL shouldn't support running the Docker client, which is entirely user-mode AFAIK.

Having Docker client running on WSL would allow cross platform teams to maintain only bash scripts as opposed to requiring a separate set of Powershell/CMD scripts.

@tdeckers
Copy link

tdeckers commented Nov 3, 2016

Any chance this can be re-opened. To be clear, no need for full docker (engine) support. I'd like to be able to use the docker client on Bash. That client would connect through TCP to the docker engine running in a VM.

@russalex
Copy link
Contributor

russalex commented Nov 3, 2016

The docker client should be working but it has been some time since I have tested the client. Possible that either we put in a bug or you're running in a configuration I have not tried.

Instead of re-opening this old issue, it would be better to open a new one and fill out the template.

@tdeckers
Copy link

tdeckers commented Nov 3, 2016

After some digging found #1123 to match what I saw. So it's being tracked.

@aseering
Copy link
Contributor

aseering commented Nov 4, 2016

@russalex -- I believe there's evidence on one of these tickets that the Docker client is affected by #610 or #616 , causing it to not build images reliably.

@aseering
Copy link
Contributor

aseering commented Nov 4, 2016

Ah, right, the ticket that @tdeckers found :-)

@longlostbro
Copy link

Just to clarify. Currently docker does not work in BashOnWindows. Right?

@aseering
Copy link
Contributor

aseering commented Nov 9, 2016

@longlostbro --

The Docker service does not work in WSL.

The Docker client (connecting to a copy of the service running on Windows or on another host) has basic functionality, but it tends to hang when building images or otherwise transferring lots of data to or from the Docker service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants