wolfv
commented
5 months ago I think this mainly depends on the "base-image" linux version. Could you try the ubuntu noble based one (24.04)?
That would be pixi:0.20.1-noble or pixi:noble
Closed mjkanji closed 5 months ago
wolfv
commented
5 months ago I think this mainly depends on the "base-image" linux version. Could you try the ubuntu noble based one (24.04)?
That would be pixi:0.20.1-noble or pixi:noble
mjkanji
commented
5 months ago @wolfv That didn't really make a difference. Please see the logs from the CI job below:
wolfv
commented
5 months ago Just to be sure, do you require a Linux version this high? I.e. you could also modify your pixi system-requirements towards something lower, possibly?
I'll take a look!
mjkanji
commented
5 months ago @wolfv But that's the thing, I haven't set anything in the system-requirements table. Please see the pixi.toml in my first comment.
wolfv
commented
5 months ago Sorry! Also I think I might have misled you a bit - I believe the kernel version is dictated by the host system and not the docker container (ref: https://stackoverflow.com/questions/32841982/how-can-docker-run-distros-with-different-kernels).
Let me try to recreate the issue locally.
mjkanji
commented
5 months ago Sorry! Also I think I might have misled you a bit - I believe the kernel version is dictated by the host system and not the docker container (ref: https://stackoverflow.com/questions/32841982/how-can-docker-run-distros-with-different-kernels).
Aah, that explains it. Because I was using the Pixi image elsewhere and never ran into this issue. Then, I guess it's not a Pixi issue but rather an issue with the GitLab runner.
wolfv
commented
5 months ago Yeah so we are actually setting the default linux version to 5.10 (https://github.com/prefix-dev/pixi/blob/58ab590d2b83f618ba544c497feef6de0c1c0b7e/src/project/virtual_packages.rs#L18-L21)
Do you happen to know what Gitlab runner you are using? You could possibly fix it by setting the linux version ot something even lower in the system-requirements table:
[system-requirements]
linux = 5.0Could make it work!
mjkanji
commented
5 months ago Thanks! I'll try and see if I can upgrade the Linux kernel in the GitLab runner (or set the version in system-requirements like you suggested).
Also, closing the issue since it's not really emanating from Pixi.
Checks
[X] I have checked that this issue has not already been reported.
[X] I have confirmed this bug exists on the latest version of pixi, using
pixi --version.Reproducible example
I'm trying to use the official Pixi Docker image for my GitLab CI pipeline, but I'm running into the same error as #346.
Since I'm using the official Docker image, I'm not sure why the version of Linux is not up-to-date.
Here are my config files:
.gitlab-ci.yml
```yml stages: - test precommit-checks: stage: test image: ghcr.io/prefix-dev/pixi variables: PRE_COMMIT_HOME: ${CI_PROJECT_DIR}/.cache/pre-commit GIT_FETCH_EXTRA_FLAGS: $CI_DEFAULT_BRANCH --prune cache: paths: - ${PRE_COMMIT_HOME} before_script: # Install git because the Pixi container doesn't have it - apt update && apt install -y --no-install-recommends git script: - pixi --version - pixi install - pixi run pre-commit --version # Run pre-commit hooks only on the files that are different compared to the default (master) branch. - pixi run pre-commit run --from-ref origin/$CI_DEFAULT_BRANCH --to-ref $CI_COMMIT_SHORT_SHA allow_failure: true # Allow the job to fail without blocking downstream stages ```pixi.toml
```toml [project] name = "my_project" version = "0.1.0" description = "Add a short description here" authors = ["Muhammad Jarir KanjiAnd here's the error I'm getting in the CI job:
Issue description
As described above.
Expected behavior
That the official Docker container has the correct system requirements.