[jeppesen-io]

Wow, that was fast. I was expecting to wait unil January.

Key takeaway for me is the ability to run/build both x86 and Arm images on a M1.

Can't see any reason M1s can't be used for everyone at my work now. Very nice.

[Demiurge]

I just tried to build an image from a work project, and it crashed. So, not yet.

  #10 11.95 Starting Installer ...                                                                                                                                      
  #10 13.14 qemu: uncaught target signal 11 (Segmentation fault) - core dumped

[flarex]

Had a similar issue with an image I tried.

qemu: uncaught target signal 4 (Illegal instruction) - core dumped

[ogre_codes]

It won't be more than a tech preview until after Go is stable on the M1 which is likely to be January/ February. Once that happens, it should be pretty quick.

[yjftsjthsd-h]

If you can run x86 programs, just use that for Go?

[ogre_codes]

This certainly works for Home-brew apps. I think Docker is a bit of a different cookie though. Talking to a VM over the Virtualization Framework likely requires being a little more native.

[tonyhb]

Docker have had inside access to the whole M1 release since before it was announced. This is incredibly slow.

[geerlingguy]

Adobe and Microsoft took months/years after Apple's PowerPC and Intel transitions... complex software is complex, it's not like they get the new machines, flip a few toggles, and hit compile.

[joshstrange]

Source? The developer machines Apple shipped out didn't have virtualization support so they couldn't start on that until after the M1 and I haven't seen anything that says Docker got M1's early.