search

kubernetes-sigs / sig-windows-dev-tools

This is a batteries included local development environment for Kubernetes on Windows.
Apache License 2.0
80 stars 46 forks source link

Add instructions for OS X Arm arch, M2 Macs with virtualbox to sig-windows-dev-tools README #218

Closed pramitagautam closed 1 year ago

pramitagautam commented 1 year ago

I have been following the README on https://github.com/kubernetes-sigs/sig-windows-dev-tools. But the ubuntu control plane is not coming up but rather is always in aborted state.

bash-5.2$ vagrant status
cni:
calico
Current machine states:

controlplane              aborted (virtualbox)
winw1                     not created (virtualbox)

I tried bringing it up but its failing with the below error:-

bash-5.2$ vagrant up
cni:
calico
Bringing machine 'controlplane' up with 'virtualbox' provider...
Bringing machine 'winw1' up with 'virtualbox' provider...
==> controlplane: Checking if box 'roboxes/ubuntu2004' version '4.2.4' is up to date...
==> controlplane: Clearing any previously set forwarded ports...
==> controlplane: Clearing any previously set network interfaces...
==> controlplane: Preparing network interfaces based on configuration...
    controlplane: Adapter 1: nat
    controlplane: Adapter 2: hostonly
==> controlplane: Forwarding ports...
    controlplane: 22 (guest) => 2222 (host) (adapter 1)
==> controlplane: Running 'pre-boot' VM customizations...
==> controlplane: Booting VM...
==> controlplane: Waiting for machine to boot. This may take a few minutes...
    controlplane: SSH address: 127.0.0.1:2222
    controlplane: SSH username: vagrant
    controlplane: SSH auth method: private key
    controlplane: Warning: Connection reset. Retrying...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'aborted' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.

I have 1) arm 64 arch 2) MAC OS 3)I had to install Dev Preview beta version of virtualbox as the link says so :- https://www.virtualbox.org/wiki/Downloads

bash-5.2$ brew install --cask virtualbox
==> Downloading https://download.virtualbox.org/virtualbox/7.0.4/VirtualBox-7.0.4-154605-OSX.dmg
Already downloaded: /Users/gpramita/Library/Caches/Homebrew/downloads/f25294560ad1eeb0b6ad82e4551be058867a3e07a6e19e423c9871ad5028fce1--VirtualBox-7.0.4-154605-OSX.dmg
Error: Cask virtualbox depends on hardware architecture being one of [{:type=>:intel, :bits=>64}], but you are running {:type=>:arm, :bits=>64}.
jayunit100 commented 1 year ago

We got a path moving forward:

NOW

vagrant -> Vbox amd64 VM win -> kubelet, amd64
VM ubuntu -> k8s control plane, kubelet amd64

ARM Problem

vagrant -> Vbox arm64 VM ubunut arm64 --> fails no os for arm VM win arm64 --> fails no os for arm

Solution: QEMU

vagrant -> qemu -> qemu.mac/qemu.linux->libvirt/qemu.windows->hyperv ?

Next step is: See if we can get qemu vagrant provider working on macs, and update a README on how to do that. ill file a separate issue for that.

aravindhp commented 1 year ago

sig-windows threads [1,2] that discuss moving to vagrant-libvirt

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 1 year ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/sig-windows-dev-tools/issues/218#issuecomment-1537166435): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.