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
TypeError: Cannot read property 'start' on exec #7
Comments
The error isn't really descriptive and I should probably improve on this. In this case the container that you've specified doesn't exist. Docker-ssh provides ssh for another already existing container. Which container this is is configurable by the CONTAINER environment option. It looks like you've specified 'my-container' but a container with that name doesn't exist. First figure out which containers are running with |
The container exists and is running. I tried changing the But I think I found why: I'm running Docker on Windows, and connection the docker daemon is not accessible at /var/run/docker.sock (the volume) but with tcp on port 2376. [edit] Hum. Nevermind, I tried installing docker into a container, and running it with the /var/run/docker.sock volume I can do docker stuff (not just Back to beginning. |
Are you sure that when you install docker in a container you're not running the docker daemon in the container as well (docker in docker)? Maybe the docker socket isn't at /var/run/docker.sock in boot2docker. |
I also have this problem on Windows and agree that it shouldn't be a problem because the boot2docker VM provides the socket, and is at I wonder if it affects OS X? |
I just wrote a quick dockerfile
For some reason, I had to force that curl version, as otherwise it installed 7.38 which doesn't have sockets support. I was able to successfully run commands like I tested the same commands on a Linux box and Note: The single forward slashes are necessary for curl socket requests as far as I know |
@SacredSkull Thanks for all the testing, really appreciated. I did some online search, and one scenario which could trigger a 404 could be a version mismatch between the Docker server and the docker client (it was changed and now returns 400 since Docker 1.7 (API version 1.19). Here's the page: https://docs.docker.com/engine/reference/api/docker_remote_api/ There's an |
The /version request returned I can't explain it, now the standard |
Ran into the same problem. Unfortunately the code does not check I'll see if I can figure out what's going on. |
The unexpected happened, doing nothing but adding error handling and rebuilding the image (available as sspinc/docker-ssh:handle-errors in Docker Hub) made the problem go away. Running jeroenpeeters/docker-ssh:1.2.2 errors out. Given that Node is being used, I would make large bets on an @jeroenpeeters let me know if you're open to a PR that adds some extra error handling and I'll open it upstream as well. |
@rgabo, please send me the PR. I would be more than happy to integrate it! |
Hello,
I tried using it but I kept getting "Connection to my_container closed by remote host."
I looked up the log of docker-ssh and this is what I have:
I can try things if you tell me :)
The text was updated successfully, but these errors were encountered: