-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Open
Labels
co/docker-driverIssues related to kubernetes in container help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bugCategorizes issue or PR as related to a bug. lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness. priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.
@snickell
Description
What Happened?
I'm using a MacOS ARM64 ("apple silicon") laptop as my dev machine, but I do builds on a remote Docker Linux AMD64 host using DOCKER_HOST="tcp://192.168.1.44". If I create the minikube-in-docker while sshed into the Linux machine, minikube installs an AMD64 docker build. However, if I try to minikube start from my Mac initially, while it pulls an x86_64 docker image, the kubeadm and kubectl binaries in /var/lib/minikube/binaries/v1.22.3/kubeadm are NOT x86_64 but arm64, which won't run on my AMD64 docker host (it gets wrongly sniffed as a shell script and fails to run, but see below its an ELF just wrong architecture).
root@minikube:/var/lib/minikube/binaries/v1.22.3# file kubeadm
kubeadm: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, Go BuildID=Ix-qGg0m4Y1_wbf6TIrB/IthoOfPXT3QgQ194kYq7/518O26hpL0jI16q3MMZ0/cj371ZbZEp94cJXf24Pn, stripped
Attach the log file
Operating System
macOS (Default)
Driver
Docker
Metadata
Metadata
Assignees
Labels
co/docker-driverIssues related to kubernetes in container help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bugCategorizes issue or PR as related to a bug. lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness. priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.