-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
runtime: bsdthread_register error on macOS 12.6.9 #62686
Comments
is your docker-machine command built locally? |
Yes I executed eval on macOS terminal. |
that's not what I asking, how did you get the docker-machine binary built? |
See https://github.com/golang/go/wiki/MacOS12BSDThreadRegisterIssue . Your docker or a program it invokes must be built with an old version of Go. See also #49425, where a few candidate of old programs were mentioned. Thanks. |
@cherrymui Unfortunately, I have tried all the methods documented online, but none of them worked.
|
@taojiaenx you ran into this because some binary that your command invokes is built with a very old version of Go. You need to find what binary that is, and rebuild it. Does docker have a verbose/debug mode that prints all the commands it invokes? If so, that could be helpful. This is not a bug in Go, and unfortunately we couldn't help you resolve the problem. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes. I have tried updating go to the latest version, as well as updating to the latest of xcode and command tools. Also ran brew upgrade to make sure everything is updated. Also tried diffrent shells to see if that makes any difference.
I am also running the latest version of docker.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
When running the following command to connect to a server running docker it produces the error. It does not matter if the server is hosted on AWS EC2 or Digital Ocean droplets.
It seems this issue is not related just to Docker, as I am also getting this error when running a command in the terminal inside of Mac OS.
What did you expect to see?
Usually nothing displays which indicates its connected to the server
What did you see instead?
The text was updated successfully, but these errors were encountered: