next build Hangs Forever in Docker Build

[mike-weiner]

I have a basic Dockerfile that currently hangs when doing kamal deploy and the build gets to npm run build: https://github.com/mike-weiner/kenyonwx/blob/main/Dockerfile

When I build the image manually using the desktop-linux v0.17.3 builder via docker buildx build --builder desktop-linux --no-cache -t test ., the build finishes without issue.

When I build the image manually using the kamal-local-desktop-container v0.18.2 builder via docker buildx build --builder kamal-local-docker-container --no-cache -t test ., the build finishes without issue.

However, when I attempt to do a kamal deploy -d staging, the build hangs forever at:

 DEBUG [bdce3573] 	#11 [builder 7/7] RUN npm run build
 DEBUG [bdce3573] 	#11 0.453 
 DEBUG [bdce3573] 	#11 0.453 > kenyonwx@0.0.3 build
 DEBUG [bdce3573] 	#11 0.453 > next build
 DEBUG [bdce3573] 	#11 0.453 
 DEBUG [bdce3573] 	#11 1.204 Attention: Next.js now collects completely anonymous telemetry regarding usage.
 DEBUG [bdce3573] 	#11 1.204 This information is used to shape Next.js' roadmap and prioritize features.
 DEBUG [bdce3573] 	#11 1.204 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
 DEBUG [bdce3573] 	#11 1.204 https://nextjs.org/telemetry
 DEBUG [bdce3573] 	#11 1.205 
 DEBUG [bdce3573] 	#11 1.250    ▲ Next.js 15.1.6
 DEBUG [bdce3573] 	#11 1.250 
 DEBUG [bdce3573] 	#11 1.252    Linting and checking validity of types ...
 DEBUG [bdce3573] 	#11 1.628    Creating an optimized production build ...

Does anyone have any suggestions?

[mike-weiner]

This discussion held the answer to my problem: vercel/next.js#37825

In Docker Desktop -> Settings -> General -> Under the Virtual Machine Options section I disabled the Use Rosetta for x86_64/amd64 emulation on Apple Silicon setting.

A save of this setting change and a restart of Docker yielded a successful kamal deploy -d staging.

I have zero clue why I suddenly needed to disable this setting. This had been working flawlessly for several months. 🤷🏻‍♂️

Hopefully leaving this as a note will help someone else later.