enroot import - Cannot write: no space left on device
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
Start with the enroot import command and its image-extraction path, using the supplied trace to investigate which filesystem or quota receives temporary writes. Reproduce the import with filesystem and inode availability checks; done means identifying why the reported storage limit is reached and documenting a confirmed remedy.
Written by the indexing model from the issue text.
Description
When I try to run enroot import, I get plenty of "No space left" errors. However I got a lot of free storage.
Here is the trace (from vdi)
$sudo enroot import -o nccl-bisection-1.sqsh dockerd://<container_uri>
[INFO] Fetching image
f245d1d0aefaa279f91f008ae7b1a0e0ed4d2e5a944bd9d00a27a96384d41411
[INFO] Extracting image content...
tar: usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.9.7: Cannot write: No space left on device
tar: usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.9.7: Cannot write: No space left on device
tar: usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.9.7: Cannot write: No space left on device
tar: usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4.7.0: Cannot write: No space left on device
...
It continues like this for hundreds of lines
Any suggestion ?
- Dominant language
- Shell
- Stars
- 1.1k
- Forks
- 139
- PR merge metrics
- No merged PRs in 30d
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.
More from NVIDIA/enroot
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
Update Vish to 1.1.5 Openpackage-update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oSoWoSo/vOid_Community_repOsitory#144 · 1 comment ·
-
help wanted new command
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tldr-pages/tldr#24151 ·
-
PacReq: Rune IDE Openpackage request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pacstall/pacstall-programs#9402 ·
-
[BUG] ci: the first prefetch-images.sh call runs before shard.txt exists, so it is always a no-op Openbug github-actions
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
update-request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
msys2/MINGW-packages#31768 ·