[feature] support for pixi lock and toml files#1064
Open
jpfeuffer wants to merge 6 commits into
Open
Conversation
- Add CONDA_PIXI_LOCK_V1 build template constant - Create PixiLockHelper for lock file detection and dispatch - Add Docker/Singularity templates for URL and file-based pixi lock builds - Wire into ContainerHelper.containerFileFromRequest dispatch - Handle pixi lock content in condaFileFromRequest (raw passthrough) - Templates use pixi install --frozen with inline minimal pixi.toml
4 tasks
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
2 participants
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.
What this adds
Two new multi-stage build templates that build containers from existing Pixi artifacts instead of re-solving a Conda definition:
conda/pixi-lock:v1— builds from a providedpixi.lockviapixi install --frozen. No re-solve, so the image matches the lock byte-for-byte (fully reproducible). When no manifest is supplied, a minimalpixi.tomlis reconstructed from the lock; a user-provided manifest can be passed through and used instead.conda/pixi-toml:v1— builds from a providedpixi.tomlmanifest.Both support lock/manifest delivered as a remote URL or as inline file content, in Dockerfile and Singularity flavors.
How it differs from the existing Pixi support
The existing
conda/pixi:v1template builds from a Conda definition (conda.yml/ package list): Pixi imports and re-solves it at build time (pixi init --import conda.yml), generating a fresh lock during the build — so resolved versions depend on when/where the build runs. The new templates build from already-resolved Pixi artifacts the user supplies, making builds reproducible and bringing nativepixi.toml/pixi.lockworkflows to Wave.Base-packages peculiarity
For
conda/pixi:v1, base packages (defaultconda-forge::procps-ng, providing thepsbinary Nextflow needs) are added straight into the env viapixi add— fine, because the lock is generated during the build. For lock builds that would invalidate the frozen lock, so base packages are installed into an isolatedpixi globalprefix and copied into the final image, leaving the locked env unchanged. This only covers CLI tools likeps; Python-level deps (e.g.psutil) must be in the user'spixi.tomlbefore locking.Changes
PixiLockHelperandPixiTomlHelper;ContainerHelperdispatch.TemplateUtilsrendering +pixi global installbase-packages path.conda-pixi-lock-v1/andconda-pixi-toml-v1/(Dockerfile + Singularity, file + url).BuildTemplateconstants andPixiOpts(manifestfield).I also have a wave-cli branch ready.