efficient docker build with editable dependencies in pixi configuration?

[gieses]

Dear *,

This is not necessarily a pixi problem / challenge but I am wondering how to handle best the following use case. Assume, we have a very complicated environment to build (meaning its just large in file size because of cuda and many dependencies) where our 'working package' (our dev package) is frequently undergoing changes.

How can we efficiently build a docker here if we want to avoid that the docker layer with the pixi environment creation is re-run everytime we change our package code?

To make it more clear, here is the conda way that does not create problems in a docker file.

conda way:

# regular env creation
COPY environment.yml environment.yml
mamba create -f environment.yml
# frequently changing files while developing the package
COPY SRC SRC
pip install -e SRC

pixi way?

We usually define the editable dependency in pixi like shown here. That means the code that frequently changes would need to be present at environment creation.

# regular env creation
COPY pix.toml pixi.toml
COPY pixi.lock pixi.lock
pixi install -e prod --frozen <---- already needs the code that is frequently changed?
COPY SRC SRC
pixi run pip install -e SRC <---- we could remove the editable install from the toml file and do this?

For reference, the linked editable install snippet for pixi.

[tool.pixi.feature.dev.pypi-dependencies]
# Built editable in development mode
docker-project = { path = ".", editable = true }