What version of Bun is running?

No response

What platform is your computer?

No response

What steps can reproduce the bug?

2026-Jan-14 15:42:11.632750
#12 0.137 $ tsc -b && vite build
2026-Jan-14 15:42:11.632750
#12 4.610 vite v6.4.1 building for production...
2026-Jan-14 15:42:11.632750
#12 4.813 transforming...
2026-Jan-14 15:42:11.632750
#12 5.951 ============================================================
2026-Jan-14 15:42:11.632750
#12 5.951 Bun v1.3.6 (d530ed9) Linux x64 (baseline)
2026-Jan-14 15:42:11.632750
#12 5.951 Linux Kernel v5.15.0 | glibc v2.41
2026-Jan-14 15:42:11.632750
#12 5.951 CPU: sse42 popcnt
2026-Jan-14 15:42:11.632750
#12 5.951 Args: "node" "/app/node_modules/.bin/vite" "build"
2026-Jan-14 15:42:11.632750
#12 5.951 Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) jsc no_avx2 no_avx spawn tsconfig tsconfig_paths napi_module_register process_dlopen(4)
2026-Jan-14 15:42:11.632750
#12 5.951 Builtins: "bun:main" "node:assert" "node:buffer" "node:child_process" "node:crypto" "node:dns" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:perf_hooks" "node:process" "node:querystring" "node:readline" "node:stream" "node:tls" "node:tty" "node:url" "node:util" "node:vm" "node:zlib" "node:worker_threads" "ws" "node:v8"
2026-Jan-14 15:42:11.632750
#12 5.951 Elapsed: 1886ms | User: 1192ms | Sys: 149ms
2026-Jan-14 15:42:11.632750
#12 5.951 RSS: 1.02GB | Peak: 0.29GB | Commit: 1.02GB | Faults: 161 | Machine: 6.21GB
2026-Jan-14 15:42:11.632750
#12 5.951
2026-Jan-14 15:42:11.632750
#12 5.951 CPU lacks AVX support. Please consider upgrading to a newer CPU.
2026-Jan-14 15:42:11.632750
#12 5.958 panic(main thread): Illegal instruction at address 0x4001FB4
2026-Jan-14 15:42:11.632750
#12 5.962 oh no: Bun has crashed. This indicates a bug in Bun, not your code.
2026-Jan-14 15:42:11.632750
#12 5.962
2026-Jan-14 15:42:11.632750
#12 5.962 To send a redacted crash report to Bun's team,
2026-Jan-14 15:42:11.632750
#12 5.962 please file a GitHub issue using the link below:
2026-Jan-14 15:42:11.632750
#12 5.962
2026-Jan-14 15:42:11.632750
#12 5.962 https://bun.report/1.3.6/Bn1d530ed9imGugggigD+++P__67/0/D_msnt/DwujpiFkuo/mFq7lqqFuup+uF49kiiE__msnt/DwujpiFk1n/mFm+kxjE6j2xoE62oihD60k5+CA3Ao7vggE
2026-Jan-14 15:42:11.632750
#12 5.962
2026-Jan-14 15:42:11.632750
#12 6.303 error: script "build" was terminated by signal SIGILL (Illegal instruction)
2026-Jan-14 15:42:11.632750
#12 6.362 Illegal instruction (core dumped)
2026-Jan-14 15:42:11.632750
#12 ERROR: process "/bin/sh -c bun run build" did not complete successfully: exit code: 132
2026-Jan-14 15:42:11.632750

2026-Jan-14 15:42:11.632750

[fe-builder 6/6] RUN bun run build:
2026-Jan-14 15:42:11.632750
5.958 panic(main thread): Illegal instruction at address 0x4001FB4
2026-Jan-14 15:42:11.632750
5.962 oh no: Bun has crashed. This indicates a bug in Bun, not your code.
2026-Jan-14 15:42:11.632750
5.962
2026-Jan-14 15:42:11.632750
5.962 To send a redacted crash report to Bun's team,
2026-Jan-14 15:42:11.632750
5.962 please file a GitHub issue using the link below:
2026-Jan-14 15:42:11.632750
5.962
2026-Jan-14 15:42:11.632750
5.962 https://bun.report/1.3.6/Bn1d530ed9imGugggigD+++P__67/0/D_msnt/DwujpiFkuo/mFq7lqqFuup+uF49kiiE__msnt/DwujpiFk1n/mFm+kxjE6j2xoE62oihD60k5+CA3Ao7vggE
2026-Jan-14 15:42:11.632750
5.962
2026-Jan-14 15:42:11.632750
6.303 error: script "build" was terminated by signal SIGILL (Illegal instruction)
2026-Jan-14 15:42:11.632750
6.362 Illegal instruction (core dumped)
2026-Jan-14 15:42:11.632750

2026-Jan-14 15:42:11.632750
Dockerfile:31
2026-Jan-14 15:42:11.632750

2026-Jan-14 15:42:11.632750
29 |
2026-Jan-14 15:42:11.632750
30 | COPY . .
2026-Jan-14 15:42:11.632750
31 | >>> RUN bun run build
2026-Jan-14 15:42:11.632750
32 |
2026-Jan-14 15:42:11.632750
33 |
2026-Jan-14 15:42:11.632750

2026-Jan-14 15:42:11.632750
ERROR: failed to build: failed to solve: process "/bin/sh -c bun run build" did not complete successfully: exit code: 132
2026-Jan-14 15:42:11.632750
exit status 1
2026-Jan-14 15:42:11.636639
Error type: RuntimeException
2026-Jan-14 15:42:11.640526
Error code: 0
2026-Jan-14 15:42:11.644320
Location: /var/www/html/app/Traits/ExecuteRemoteCommand.php:243
2026-Jan-14 15:42:11.648185
Stack trace (first 5 lines):
2026-Jan-14 15:42:11.651995
#0 /var/www/html/app/Traits/ExecuteRemoteCommand.php(104): App\Jobs\ApplicationDeploymentJob->executeCommandWithProcess()
2026-Jan-14 15:42:11.655961
#1 /var/www/html/vendor/laravel/framework/src/Illuminate/Collections/Traits/EnumeratesValues.php(271): App\Jobs\ApplicationDeploymentJob->{closure:App\Traits\ExecuteRemoteCommand::execute_remote_command():71}()
2026-Jan-14 15:42:11.659829
#2 /var/www/html/app/Traits/ExecuteRemoteCommand.php(71): Illuminate\Support\Collection->each()
2026-Jan-14 15:42:11.663708
#3 /var/www/html/app/Jobs/ApplicationDeploymentJob.php(3154): App\Jobs\ApplicationDeploymentJob->execute_remote_command()
2026-Jan-14 15:42:11.667625
#4 /var/www/html/app/Jobs/ApplicationDeploymentJob.php(861): App\Jobs\ApplicationDeploymentJob->build_image()
2026-Jan-14 15:42:11.671548

2026-Jan-14 15:42:11.675568
Deployment failed. Removing the new version of your application.

What is the expected behavior?

No response

What do you see instead?

No response

Additional information

No response