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

Doesn't seem to work on MacOS Sierra #6

Open
gdiggs opened this issue Jan 10, 2017 · 10 comments
Open

Doesn't seem to work on MacOS Sierra #6

gdiggs opened this issue Jan 10, 2017 · 10 comments

Comments

@gdiggs
Copy link

gdiggs commented Jan 10, 2017

Ever since upgrading to Sierra, this doesn't work for me anymore. Anyone else seeing this / have a workaround?

@BlinkyStitt
Copy link

BlinkyStitt commented Jan 24, 2017

It think it used to work for me on Sierra, but now it isn't working anymore. I'm on Sierra 10.12.2 and Docker Version 1.13.0-beta38 (15084). I'm going to try to go through backups and see what version of Docker last worked

$ docker --version
Docker version 1.13.0, build 49bf474
$ pinata-ssh-mount
cat: /Users/bwstitt/.pinata-sshd/agent_socket_path: No such file or directory
-v /Users/bwstitt/.pinata-sshd/:/tmp/ssh-agent.sock --env SSH_AUTH_SOCK=/tmp/ssh-agent.sock

$ ls ~/.pinata-sshd
known_hosts

@ABaldwinHunter
Copy link

@gordondiggs what's the error you're seeing? I'm not sure if this is related, but I started seeing:

docker: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: \"/usr/bin/tini\": stat /usr/bin/tini: no such file or directory"

Also using docker 1.13.0, git commit 49bf474, but OS X Yosemite 10.10.5

@BlinkyStitt
Copy link

BlinkyStitt commented Jan 27, 2017

@ABaldwinHunter the tini error is fixed by #7.

Unfortunately, that fix wasn't enough for me. Now the container just uses 200% CPU as soon as I try to ssh in.

@BlinkyStitt
Copy link

BlinkyStitt commented Jan 27, 2017

I fixed my local system!

Something was wrong inside Docker. I updated to the latest version (1.13.0) and then went into preferences and clicked the "Reset" bomb and then "Reset to factory defaults" and now its working again (well after I did a bunch of other cleanup things on https://github.com/uber-common/docker-ssh-agent-forward)

@ABaldwinHunter
Copy link

@wysenynja thanks for the update! glad your system is working well. Going to try out the bug fix you mentioned and see how it goes

@chad-10e
Copy link

PR #15 includes the fix linked by @wysenynja.

@jeffrey-aguilera
Copy link

Just reset docker to factory defaults (17.0.3.1-ce-mac5) and still have the same issue:

docker: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: \"/usr/bin/tini\": stat /usr/bin/tini: no such file or directory".

@micmart
Copy link

micmart commented Jun 21, 2017

#15 fixed the error above. But now I get this error:
ssh_exchange_identification: Connection closed by remote host

@rawrgulmuffins
Copy link

Also hitting this unfortunately.

@BlinkyStitt
Copy link

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