I'm not sure, but given that the M1 Macs come with Big Sur as the first OS installed, I would wait a bit until the software has matured a bit.
By then, I could not only get a newer generation of Macs probably having an M1X or M2 chip, it would probably be running a newer version macOS, with all these issues, bugs and panics fixed and the developer ecosystem also catching up with Apple Silicon based Macs.
I had a kernel panic on Sunday. It was the second day of owning my M1 MacBook Air. There was barely anything installed on the machine. The panic happened when I was running Firefox. The screen turned a weird color and instantly rebooted.
That said, I've tried to keep it as a "dumb browser machine" at the moment (for unrelated reasons), so I haven't pushed it in any meaningful way so far.
By then, I could not only get a newer generation of Macs probably having an M1X or M2 chip, it would probably be running a newer version macOS, with all these issues, bugs and panics fixed and the developer ecosystem also catching up with Apple Silicon based Macs.
1) Docker images are not virtual machines (see this link: https://www.docker.com/resources/what-container)
2) Maybe the Docker Engine (the service that bootstraps the images) caused the panic?
That said, I've tried to keep it as a "dumb browser machine" at the moment (for unrelated reasons), so I haven't pushed it in any meaningful way so far.