🏹 SysImage Exports for General Environments 🏰
Julia's package manager relies on internet access, so it can be challenging to make dependencies available on secure systems.
PackageCompiler.jl compiles Julia code ahead of time, primarily for improved performance in certain workflows.
In particular, generating a sysimage produces a performant stand-alone Julia session, and since its main drawback (version locking) is mitigated on secure systems, it is a good approach for putting a Julia session on a system without internet or ssh access available to users.
The main requirement is an internet-connected build server that has the same architecture as the secure system.
SIEGE takes a Julia project as input and automatically generates a sysimage (using PackageCompiler) for use in secure systems.
It also includes a Bash script that starts an offline Julia session with the new sysimage.
The script sets environment variables and accepts command-line arguments, so it can be aliased to julia by users.
Julia: SIEGE looks for Julia in the package's main directory. The binaries can be downloaded from the official site and uploaded to the secure system. They are not modified in any way by SIEGE, so this only needs to be done by the developer once, or whenever a new version of Julia is needed. The same version of Julia should be used to generate the sysimage.
A Julia Project: Copy the Project file from your Julia projet into env/.
An example Julia project space is already included in env/.
Note that the sysimage produced by SIEGE will only work on systems with matching architecture, since the machine-generated manifest file is what is actually used by PackageCompiler.jl. If the sysimage is intended to be moved to a secure server, the build server and secure server must be as similar as possible.
Additionally, the instructions and code presuppose a *NIX type environment with Bash, but a port for Windows should be possible.
- Read through
src/SIEGE.jlto see what's going on. - Replace the example project file in
env/with the one you want to build into a sysimage. - While you're at it, go ahead and update the paths to Julia and SIEGE in
run_sysimage.sh. - Run
main()fromsrc/SIEGE.jlon the build server to build the sysimage and depot. Any generated files will be found inbuild/.
pkg> activate --temp
pkg> develop Path/To/SIEGE
julia> using SIEGE
julia> main("/Path/To/SIEGE")
- Upload Julia and SIEGE to the secure system.
- Users can now use
run_sysimage.sh. Group and permisson settings might need to be adjusted withchgroupandchmod, since many files need to be executable by users. - (OPTIONAL): Add to
~/.bashrcan alias pointing to the script. It should accept command line arguments just as the Julia binary would.
alias julia='Path/To/run_sysimage.sh'
-
Certain packages download dependencies only after they are called (lazy loading). Try running the sysimage on the build server to see if any additional packages are downloaded at runtime. If required dependencies are left out, these can be added manually:
-
Some packages might just not be relocatable yet and would need to be patched.