`astro deploy` results in segmentation fault

Astronomer - Describe the bug Upon starting a new project and deploying it, the image building step fails with a segmentation fault.

The fix

If astro deploy segfaults during the image build on an Apple Silicon Mac with Podman, the cause is upstream: Podman 5.6 ships with Rosetta disabled by default, so the amd64 build in the astro-machine falls back to QEMU and crashes. Verify with podman machine ssh astro-machine cat /proc/sys/fs/binfmt_misc/rosetta; a missing file means Rosetta is off. Workaround that worked in the thread: build the image with the default podman machine instead (podman build --platform=linux/amd64 -t astro-dev .) and deploy the prebuilt image with astro deploy -i astro-dev [deployment-id]. Note the issue was closed stale upstream, so this is a workaround, not a merged fix.

Thread: gh:astronomer/astro-cli#1967

In gh:astronomer/astro-cli#1967 (https://github.com/astronomer/astro-cli/issues/1967), the issue reported: Describe the bug Upon starting a new project and deploying it, the image building step fails with a segmentation fault. ``console ~/tmp$ mkdir astro ~/tmp$ cd astro ~/tmp/astro$ astro dev init Initialized empty Astro project in [HOME]/... ~/tmp/astro$ astro dev start ✔ Astro machine initialized ✔ Project image has been updated ✔ Project started - Airflow UI: http://your host:8080 - Postgres Database: postgresql://your host:5432/postgres - The default Postgres DB credentials are: postgres:postgres ~/tmp/astro$ astro deploy Authenticated to Astro Select a Deployment #... The verified answer: If astro deploy segfaults during the image build on an Apple Silicon Mac with Podman, the cause is upstream: Podman 5.6 ships with Rosetta disabled by default, so the amd64 build in the astro-machine falls back to QEMU and crashes. Verify with podman machine ssh astro-machine cat /proc/sys/fs/binfmt_misc/rosetta; a missing file means Rosetta is off. Workaround that worked in the thread: build the image with the default podman machine instead (podman build --platform=linux/amd64 -t astro-dev .) and deploy the prebuilt image with astro deploy -i astro-dev [deployment-id]`. Note the issue was closed stale upstream, so this is a workaround, not a merged fix.