Invalid cross-device link (os error 18) when building inside pods due to OverlayFS restrictions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Problem
Hello!
I developing my application on kubernetes. For development, I use minikube, I mount my host repo inside a pod and I build/run from inside it.
However, I have the following issue when building:
Compiling libc v0.2.118
error: failed to write /home/azureuser/..../target/debug/deps/libunicode_xid-8bb8457dab823b6f.rmeta: Invalid cross-device link (os error 18)
error: could not compile unicode-xid due to previous error.
Thanks!
Steps
Install and start minikube.
mount any rust repo:
minikube mount /repo:/repo
Create a deployment to mount the repo inside a pod.
Do cargo build inside the pod
Possible Solution(s)
No response
Notes
No response
Rustup version
rustup 1.24.3 (ce5817a94 2021-05-31)
Installed toolchains
rustc 1.57.0 (f1edd0429 2021-11-29)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is identified. Start by reproducing the minikube mount and in-pod cargo build described in the issue, then determine whether the failure is actionable in rustup or caused by the OverlayFS environment. Done should establish a verified resolution or clear project guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- build-system, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100