search

flatcar / Flatcar

Flatcar project repository for issue tracking, project documentation, etc.
https://www.flatcar.org/
Apache License 2.0
687 stars 30 forks source link

[RFE] Vagrant artifacts for ARM64 #762

Open amayausky opened 2 years ago

amayausky commented 2 years ago

Current situation

Currently Flatcar only provides Vagrant artifacts, e.g. box files for Parallels and VMWare, for x86.

Impact

As ARM-based processors become more available, e.g. M1 Macs, it becomes more difficult to support high-level virtualization tools like Vagrant + VMWare (or Parallels). These providers only plan to offer ARM64 on ARM64 virtualization support so the x86 artifacts are not helpful.

Ideal future situation

Flatcar releases include Vagrant files for the ARM64 version.

jepio commented 2 years ago

I love the idea. Vagrant also has experimental support for cloud-init which I think could be used to inject ignition data as well, but would require some additional work on ignition (although "ibmcloud" platform already appears to read the cidata iso).

On the flatcar team side we don't have people working on M1 Macs (except @dongsupark?) so that will make it tricky for us to work on this. If anyone on the community side is willing to step up, I'm happy to work with you through matrix/slack to accomplish this.

pothos commented 2 years ago

As first step we can try to generate the same vagrant images as we do for amd64 (definitions in scripts/build_library/vm_image_util.sh and coreos-overlay/coreos-base/oem-vagrant/oem-vagrant-0.0.3.ebuild where currently only amd64 is set in KEYWORDS). In general I think we need to (re-)test Vagrant and update the docs.

iancullinane commented 1 year ago

This came up in my searching was any more thought ever put into it?