This is what I'm afraid of, too. Maybe things are working well and seamless, but the last thing I want to do is have to worry about being the first dev on my team using non-X86, and pushing Arm versions of Docker images all over the place or having to modify my Dockerfiles to use Arm versions instead of X86.
One of the reasons Mac was so nice was that everything worked the same locally as it did on Linux prod machines, whereas even today there are subtle bugs with naive Java or Python code that doesn't deal with paths or line endings correctly. On big multi-team projects, there are always some junior devs on Windows that just don't get it right.
This seems like another problem waiting to happen as more devs start using Arm, while the majority of developers and environments still use X86.
I've been using x86_64 docker containers with the QEMU emulation just fine, and most open source available docker containers are ARM compatible these days.
I don't push containers from my laptop to anywhere, instead those are built on CI/CD... and we are building both x86_64 and ARM containers these days as we are launching new workloads on Amazon's Graviton because it is cheaper and more cost effective.
It isn't too bad in my experience, having been using an m1 Air since release.
For images with an Arm version available, and that's seemingly quite a lot, it mostly just works(TM). No Dockerfile changes needed.
If you have no other options, you can even run x64 stuff with a bit of low impact futzing. Docker Desktop will use QEMU to do this for you, nearly seamlessly. (though rather slowly)
The biggest gripe I have is the local volume perf, which is "tolerable." This is a problem for Intel Macs too, although to a lesser extent.
One of the reasons Mac was so nice was that everything worked the same locally as it did on Linux prod machines, whereas even today there are subtle bugs with naive Java or Python code that doesn't deal with paths or line endings correctly. On big multi-team projects, there are always some junior devs on Windows that just don't get it right.
This seems like another problem waiting to happen as more devs start using Arm, while the majority of developers and environments still use X86.