I have limited experience with podman on M1, having only pivoted recently thanks to the docker license issues but my experience so far on an M1 Mac was I couldn

I have limited experience with podman on M1, having only pivoted recently thanks to the docker license issues but my experience so far on an M1 Mac was I couldn't initialize or start the application from the gui. Initialize timed out due to slow proxy speeds, so I had to use "podman machine start" at the command line to wait for the image download and install to complete. For whatever reason I couldn't start using the UI after a reboot because I got an EACCESS error and again command line worked which was then acknowledged as running via the UI. This is in an environment where the end-user has no root and podman is running in rootless mode. Once I got it running, I was able to crank up x86 http and postgres containers from the command line mostly with no issues, although pod termination seems to work better from the UI. In fact starting containers at command line throws a warning that your container architecture doesn't match your host architecture but that's it and podman just carries on after that. When you say x86-64, is there something special about 64-bit containers that makes them only work via the UI?