Closed annismckenzie closed 7 years ago
To elaborate on why they segfault: it seems that almost all binaries compiled on pre-Sierra segfault or panic. If you're reading this and you haven't upgraded to Sierra, then please don't (at least not yet).
@annismckenzie thanxs for reporting and for your patience. issue is infortunate and not specific to our tools (vd https://medium.com/@gerred/kubectl-1-3-7-for-macos-sierra-ee2c483e283d#.ajr1i0mx4) . we're working in getting it solved asap. just be aware that @rimusz is on travel so forgive us for a bit more latency than usual.
Thanks for the heads up. Updated a while back and found out this issue myself. Will be waiting on the updated stack.
fixed in #105
I updated to macOS Sierra yesterday (in hindsight, I should've waited) and just fixed all of the included binaries to run correctly on Sierra. After a few hours wrestling with k8s the cluster is now up on macOS Sierra and Go 1.7.1 (compiled from source).
To make someone else's life easier I could fork the repo and provide the updated binaries if you want. The included
fleetctl
,etcdctl
as well askubectl
need to be recompiled. Also, I noticed thatfleetctl
is included twice in the app, is that intended? Found the binaries in/Applications/Kube-Cluster.app/Contents/Resources/bin/
as well as the additionalfleetctl
in/Applications/Kube-Cluster.app/Contents/Resources/files/
.Please advice – thanks for your hard work!