-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Cannot build image natively from macOS #32
Comments
We "should" switch to using the upstream k8s container asap. /assign @johnSchnake @stevesloka |
I can look into this one. |
Hi @stevesloka, I'm also happy to look into things. One big happy family, right? :) FWIW, the problem is very straight-forward. It's one of the very first issues I encountered when joining the K8s community -- the Darwin client bits have not been published to the public GCS bucket in a very long time. Aside from that, the Darwin client should never be used with this regardless. Since the K8s script doesn't allow for overriding the client OS/arch, you have to run it in a Linux container or on a Linux host. |
PR is up for switching to the upstream already. Phasing it in but if it merges I don’t anticipate needing to release this again and we can archive it: see vmware-tanzu/sonobuoy#617 |
Hi @stevesloka, Please see kubernetes/kubernetes#74889 for an upstream change that will solve this PR (@johnSchnake's comment notwithstanding). |
What steps did you take and what happened:
Run
make
on macOS fails because thegetbins
target fails when executing the Kubernetesget-kube-binaries.sh
script due to how the K8s client bits are auto-detected and cannot be overridden. For several versions now Kubernetes no longer publishes the Darwinkubectl
with builds. Even if it did, it would be the incorrect version to use when building the image.What did you expect to happen:
A new
kube-conformance
image should be built.Anything else you would like to add:
A workaround is to use Docker like so:
The above command executes the
getbins
target inside of a Linux container and then executes the default target,containers
, natively on the host system.Please note, the
golang
image was used simply because it includes the GNU developer toolchain and themake
command. Any image that hasmake
could be used in place ofgolang
in the above command.The above command succeeds like so:
Environment:
sonobuoy version
): NAkubectl version
): NA/etc/os-release
): NAThe text was updated successfully, but these errors were encountered: