Issue #1896 Move the pixi environment folder out of the mounted source folder. - #1897
Merged
JoerivanEngelen merged 1 commit intoAug 3, 2026
Merged
Conversation
…e sure the host system isn;t affecting it
Manangka
changed the title
Manangka
changed the title
|
JoerivanEngelen
approved these changes
Aug 3, 2026
JoerivanEngelen
left a comment
JoerivanEngelen
left a comment
Contributor
There was a problem hiding this comment.
Given that we used the detached-environments in other jobs, I think this is worth trying.
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.
Fixes #1896
Description
The Pixi update build step has been failing for several weeks now.
A file is being accessed by multiple processes.
My suspicion is that the host system is also accessing the pixi environment (virus scanner?)
In this PR is move the pixi environment location out of the source folder (The source folder lives on the host system and is mounted into the docker container). After this change only the container has access to the environment.
If it still fails then the issue is somewhere in the container
As an added benefit this will also bring some performance improvements. We already use this setting in the main pipeline.
Checklist
Issue #nr, e.g.Issue #737pixi run generate-sbomand committed changes