Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when executing pixi shell ("The current system has a mismatching virtual package...") #1905

Closed
2 tasks done
apcamargo opened this issue Aug 25, 2024 · 3 comments
Closed
2 tasks done
Labels
🐞 bug Something isn't working

Comments

@apcamargo
Copy link

Checks

  • I have checked that this issue has not already been reported.

  • I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example

$ pixi --version
pixi 0.28.0
$ pixi init test-project
$ cd test-project
$ pixi shell
  × The current system has a mismatching virtual package. The project requires '__glibc' to be at
  │ least version '2.28' but the system has version '2.26'

Issue description

I face the error mentioned above every time I create a new project and try to execute pixi shell within it. To solve this, I need to add the following to my pixi.toml file (based on the solution provided here):

[system-requirements]
libc = { family="glibc", version="2.26" }

My setup is straightforward, with my $HOME/.config/pixi/config.toml only containing the following:

default-channels = ["conda-forge", "bioconda"]

I am running Amazon Linux release 2 (Karoo).

Expected behavior

pixi shell should start a new shell in the project's environment.

@apcamargo apcamargo added the 🐞 bug Something isn't working label Aug 25, 2024
@ruben-arts
Copy link
Contributor

We have a solution in mind that is high on the list of things we need to solve. I acknowledge that this is not a comfortable way to use pixi. The solution is explained here: #346 (comment).

Closing this as a duplicate. Thanks for writing down your current work around for future issue searchers.

@apcamargo
Copy link
Author

Thanks for the answer!

I did read that bug report, but since the mismatch was different (glibc, rather than the OS), I decided to open up another issue. Good to know that you guys are working on it.

@ruben-arts
Copy link
Contributor

Yeah no problem! Thanks for being an proactive user!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants