Skip to content

fix(docker): move deno libs aside during apk install#270

Merged
raaymax merged 2 commits into
devfrom
fix/docker-build-v3
Feb 9, 2026
Merged

fix(docker): move deno libs aside during apk install#270
raaymax merged 2 commits into
devfrom
fix/docker-build-v3

Conversation

@raaymax
Copy link
Copy Markdown
Owner

@raaymax raaymax commented Feb 9, 2026

Summary

  • Fix Docker multi-arch build failure (amd64 + arm64) caused by denoland/deno:alpine-2.6.8 shipping glibc-linked libs in /usr/local/lib/
  • Move /usr/local/lib aside during apk install, restore after — both apk triggers and Deno work correctly
  • Add workflow_dispatch trigger to dev workflow for manual build testing
  • Guard PR comment step to only run on pull_request events

Context

Previous fixes attempted:

  • LD_LIBRARY_PATH=/usr/lib — fixed apk but not post-install triggers (glib, shared-mime-info, gdk-pixbuf)
  • rm -f /usr/local/lib/lib*.so* — fixed apk but broke Deno (missing libdl.so.2)
  • This fix: moves entire /usr/local/lib out of the way during apk, restores after

Upstream issue: denoland/deno_docker#373
Verified via workflow_dispatch build: both amd64 and arm64 pass.

Test plan

  • Docker build passes on amd64 and arm64 (verified via workflow_dispatch)
  • Deno runs correctly in built container

Previous approach of removing all libs broke deno (missing libdl.so.2).
Now moves /usr/local/lib out of the way during apk install and restores
it after, so both apk triggers and deno work correctly.

Also adds workflow_dispatch trigger to dev.yml for manual testing.
@raaymax raaymax merged commit 473a58f into dev Feb 9, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant