-
Notifications
You must be signed in to change notification settings - Fork 58
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
Comments
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
|
@gordondiggs what's the error you're seeing? I'm not sure if this is related, but I started seeing:
Also using docker 1.13.0, git commit 49bf474, but OS X Yosemite 10.10.5 |
@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. |
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) |
@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 |
PR #15 includes the fix linked by @wysenynja. |
Just reset docker to factory defaults (17.0.3.1-ce-mac5) and still have the same issue:
|
#15 fixed the error above. But now I get this error: |
Also hitting this unfortunately. |
Ever since upgrading to Sierra, this doesn't work for me anymore. Anyone else seeing this / have a workaround?
The text was updated successfully, but these errors were encountered: