-
Notifications
You must be signed in to change notification settings - Fork 4.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
github.com/godbus/dbus/homedir_dynamic.go is linked into static binary #1422
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
r2d4
added a commit
to r2d4/minikube
that referenced
this issue
May 1, 2017
Fixes kubernetes#1422 godbus requires the static_build tag when building. Normal static compliation doesn't add this go build tag automatically.
Building with the static suffix doesn't actually enable this build tag. It has to be enabled manually, I added a PR that enables it in localkube. Let me know if that works for you. |
Thanks for fixing this! |
dalehamel
pushed a commit
to dalehamel/minikube
that referenced
this issue
May 3, 2017
Fixes kubernetes#1422 godbus requires the static_build tag when building. Normal static compliation doesn't add this go build tag automatically.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For some reason, the localkube static binary compiles in the version of
homedir.go
intented for dynamic linking which lacks proper protection when callingcurrent()
. The panic is attached below.The original issue is described here:
golang/go#13470
And the fix that went into godbus is here:
godbus/dbus@da6051a
which split homedir.go into a dynamic and static version selected using
+build static_build
For some reason, the localkube binary is built and linked against the dynamic version as seen in the panic stacktrace.
https://github.com/godbus/dbus/blob/master/homedir_dynamic.go
I'm using:
go version go1.7.4 darwin/amd64
Any indication why the
+build static_build
invendor/github.com/godbus/dbus/homedir_dynamic.go
is not effective? Are the vendor packages compiled for minikube first which is not statically linked?The text was updated successfully, but these errors were encountered: