Fix Docker build: resolve Julia sys.so not found when embedding via pyjuliacall#901
Closed
dependabot[bot] wants to merge 2 commits into
Closed
Fix Docker build: resolve Julia sys.so not found when embedding via pyjuliacall#901dependabot[bot] wants to merge 2 commits into
dependabot[bot] wants to merge 2 commits into
Conversation
dependabot
Bot
added
dependencies
Copilot
AI
changed the title
Bump actions/checkout from 6 to 7 in the core-actions group
Fix Docker build: resolve Julia sys.so not found when embedding via pyjuliacall
Jun 21, 2026
Bumps the core-actions group with 1 update: [actions/checkout](https://github.com/actions/checkout). Updates `actions/checkout` from 6 to 7 - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v6...v7) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major dependency-group: core-actions ... Signed-off-by: dependabot[bot] <support@github.com>
alongd
force-pushed
the
dependabot/github_actions/core-actions-640176b5ab
branch
from
2da4527 to
babd719
Compare
Contributor
Author
|
Looks like actions/checkout is updatable in another way, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/github_actions/core-actions-640176b5ab
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Root Cause
The Docker build was failing at the
install_rms.shstep with:~/.juliaup/bin/juliais the juliaup launcher binary, not the actual Julia binary. Wheninstall_rms.shsetsPYTHON_JULIAPKG_EXE=$(which julia), pyjuliacall receives the launcher path and computes the Julia library paths relative to it. This produces~/.juliaup/lib/julia/sys.so, which does not exist. The real Julia binary (and itssys.so) resides under~/.juliaup/julia/<version>/.Fix
In the
Dockerfile, theRUNstep that sourcesinstall_rms.shnow:julia -e "print(Sys.BINDIR)"— running the actual Julia 1.10 via the juliaup launcher — to obtain the real Julia binary directory.PATHso thatwhich juliainsideinstall_rms.shresolves to the actual Julia binary rather than the juliaup launcher.bash -c '...'instead of double-quoted so that the$(...)command substitution is evaluated inside the micromamba environment (not by the outer shell beforemicromamba runactivates the environment).With the actual Julia binary on
PATH, pyjuliacall correctly computessys.soas~/.juliaup/julia/<version>/lib/julia/sys.soand Julia embeds successfully.