deno_docker

Problem Running the output of inside the Alpine image fails since the 2.7.8 image: Fixes denoland/deno#35683. Root cause This is an image regression, not a binary bug. I confirmed the compiled binaries are identical in their ELF dependencies across versions (both need , no rpath) — the difference is purely the image: A binary compiled by 2.7.8 runs fine on the 2.7.7 image. A binary compiled by 2.7.7 fails on the 2.7.8 image. Commit 01a6547 (#523, first shipped in the 2.7.8 image) isolated glibc libs into , dropped , and rpath-patched only and . A output binary gets neither the rpath nor , so its glibc loader can't find in the isolated (non-searched) directory. Re-adding would reintroduce the exact musl-package conflict #523 fixed, because musl's loader also honors and would then load the incompatible glibc . Fix Generate a glibc pointing at . The glibc loader consults it, so rpath-less compiled binaries resolve their libs — while musl's loader ignores entirely, so the isolation from #523 is fully preserved and no conflict returns. The cache is built with the already present in the existing build stage (no new base image). Verification (full image build, ) ✅ runs ✅ output runs (the reported failure) ✅ + still runs — no glibc/musl conflict reintroduced