-
Notifications
You must be signed in to change notification settings - Fork 201
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
failed to link 'share/terminfo/N/NCR260VT300WPP' #234
Comments
The log statement
indicates that rattler correctly discovered that hardlinks are not allowed. The actual error seems to originate here: Is readlink not allowed on a mounted docker volume? |
It looks like that is indeed an issue: https://stackoverflow.com/a/40322275 I guess using a copy fallback is then the only way.. |
Confirmed that this also happens on my M1. |
After some more digging we have to go back to the drawing board on this one. It has nothing to do with either hardlinks or softlinks. It appears the error happens when opening the file or memory mapping it. The IO error 5 likely indicates a permission denied error. I also cannot reproduce this in WSL. @ruben-arts will check under Linux. |
I assume that since the cache is actually filled, reading and writing from the mounted volume does work. So this would indicate that the error occurs when memory mapping the file. |
It works for me when I remove the |
I created a PR for rattler to add some more error information. Hopefully that allows us to pinpoint the error a little better: conda/rattler#273 |
After some more debugging, we figured out that the issue was that the specific package that failed ( This is a macOS-specific issue that only occurs when mounting a docker volume into a Linux-based docker container and installing packages that expect a case-sensitive filesystem. Because of this pixi (or rattler) will never be able to install such a package in this scenario correctly. So I'm closing this issue. Thanks for the patience and help @pavelzw ! |
@baszalmstra what was the resolution to this? i think i'm running into the exact same issue:
i tried dropping the |
I think as long as both the cache and the pixi environment are not installed on mounted volumes (so on a case sensitive volume) it should work. |
yes, thank you, i was about to say this too. for future readers: this fix is to make sure the mounted volume is case-sensitive. if you're on macOS, you need to make a new volume, and use that to mount into docker |
@baszalmstra hey, I might be missing something, but does this mean that you won't be able to use pixi in such scenarios from vscode devcontainers in windows/wsl? I don't think devcontainers can work without mounting the project directory and pixi enforces environments being created in the project directory. |
you are still able to use devcontainers if you specify i should really get going to write some docs... #1386 |
I want to run a docker container with pixi installed and a custom directory mounted as
$HOME
. This is not possible at the moment.Dockerfile.test
Steps to reproduce (I used macOS with M1 Pro)
The text was updated successfully, but these errors were encountered: