You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to install a Pixi environment in a docker container based on the image ate ghcr.io/prefix-dev/pixi:latest. I have a pyproject.toml that looks something like
Of interest here is the the dependency installed from a git repo. The container in question does not have git installed—however, I believe this shouldn't matter as in the container I install the default environment with
RUN pixi install -e default
This step, however, results in this error:
=> ERROR [base build 4/5] RUN pixi install -e prod 68.7s
------
> [base build 4/5] RUN pixi install -e prod:
68.59 × failed to solve the pypi requirements of 'default''linux-64'
68.59 ├─▶ Failed to download and build `dsrepo-backend @ git+ssh://68.59 │ git@url/custom-dev-dep.git@revision`
68.59 ├─▶ Git operation failed
68.59 ╰─▶ Git executable not found. Ensure that Git is installed and available.
68.59
I don't get this error if I comment out the custom-dev-dep line in the pyproject.toml. This seems to suggest that Pixi is trying to fetch the requirements of the dev environment, even when I'm not asking for it—I feel like this isn't the expected behavior?
The text was updated successfully, but these errors were encountered:
I'm trying to install a Pixi environment in a docker container based on the image ate
ghcr.io/prefix-dev/pixi:latest
. I have apyproject.toml
that looks something likeOf interest here is the the dependency installed from a git repo. The container in question does not have git installed—however, I believe this shouldn't matter as in the container I install the
default
environment withThis step, however, results in this error:
I don't get this error if I comment out the
custom-dev-dep
line in thepyproject.toml
. This seems to suggest that Pixi is trying to fetch the requirements of thedev
environment, even when I'm not asking for it—I feel like this isn't the expected behavior?The text was updated successfully, but these errors were encountered: