This is a Swift server application. Direct docker build works just fine. Fly local deploy takes too long and fails. In the above example I didn’t wait for it to fail.
A similar app worked fine with remote builder, after failing with the local fly deploy.
fly deploy --local-only makes a container image for x86_64 (aka Intel) on Apple silicon, whereas docker-compose up app --build builds a container images for Apple silicon by default. So the emulation process on the former may make the build slower.
We need to have container images for x86_64, because all our servers are x86_64.