ops image create missing arm switch

[eyberg]

it appears 'ops run' is intelligent enough to run (prob based on underlying arch) but need the ability to do images as well

I don't think there are any outstanding blockers to do cross-arch builds via flag (eg: x86 to arm) as native mkfs support was added to ops

[girishramnani]

should we consider adding a --arch flag to ops image create command?

[eyberg]

I think the default should be whatever underlying architecture the user is on currently but yeh I'd be in favor of having an arch flag; just not sure how many people would actually take advantage of that since the underlying binary still needs to be tied to the arch of choice

[ponokys]

PR #1265 auto get architecture based on "CloudConfig.Flavor"

[eyberg]

just to be clear this is in the use-case that someone is sitting on an x86 box and wants to build arm images with say a statically linked go arm binary (or vice-versa) - the #1265 only covers the case where you are building against aws on the same architecture - it doesn't actually know that you have a local x86 or arm build - it assumes you are on arm already

[eyberg]

https://github.com/nanovms/ops/pull/1380 adds support for downloading and using arm builds for arm related targets - also allows just grabbing latest arm release