pyxis enroot import failed to extract squashfs image disk quota exceeded

Enroot exhausted the user or filesystem quota while importing and extracting the SquashFS image. Free space elsewhere on the node does not help when the configured cache or data path has a separate quota. This entry explains how to confirm the cause, apply the fix, and separate it from adjacent containers failures.

Symptom

pyxis enroot import failed to extract squashfs image disk quota exceeded

Root cause

Enroot exhausted the user or filesystem quota while importing and extracting the SquashFS image. Free space elsewhere on the node does not help when the configured cache or data path has a separate quota. The decisive evidence is the first log line that precedes "pyxis enroot import failed to extract squashfs image disk quota exceeded" and differs from a healthy run.

Recommended fix

inspect quota and free inodes on the Enroot cache, data, and temporary paths, then remove only unreferenced cached images or select a path with sufficient quota.

How Denpex helps

Denpex investigates pyxis enroot import failed to extract squashfs image disk quota exceeded using the evidence you provide or your connected workload collects. Earlier rank, host or application evidence is needed to distinguish an initiating failure from a downstream report.

The literal signature is "pyxis enroot import failed to extract squashfs image disk quota exceeded". It is a environment failure associated with NVIDIA Container Toolkit, device plugins, Enroot, and Pyxis. The line identifies the failing operation or subsystem, while the surrounding evidence decides whether it is the initiating fault or a downstream symptom.

Enroot exhausted the user or filesystem quota while importing and extracting the SquashFS image. Free space elsewhere on the node does not help when the configured cache or data path has a separate quota. The failure becomes visible at this call site because the operation first requires the missing resource, valid state, healthy peer, or correct result. Earlier log lines and a known-good control carry more causal value than the final wrapper exception.

• The workload stops or loses forward progress after emitting "pyxis enroot import failed to extract squashfs image disk quota exceeded".
• A retry on the same configuration reproduces the failure because the causal state has not changed.
• The outer framework exception can hide the rank, node, allocation, or dependency that failed first.
• Increasing timeouts or reducing workload size can suppress the symptom without correcting the cause.

• NVIDIA Container Toolkit, device plugins, Enroot, and Pyxis
• production-shaped multi-accelerator workloads
• containerized and bare-metal deployments of the same stack

Use this checklist to test the hypothesis against a small reproduction. No single line proves the root cause, so preserve the preceding events and compare one variable at a time.

• ✓Find the first occurrence of "pyxis enroot import failed to extract squashfs image disk quota exceeded" and preserve at least 100 lines before it.
• ✓Identify which rank, node, device, or process emitted the first related warning.
• ✓print ENROOT_CACHE_PATH, ENROOT_DATA_PATH, and ENROOT_TEMP_PATH in the Slurm job because login and compute nodes may resolve them differently.
• ✓Repeat the same input after the targeted change and require the signature to disappear.
• ✓Resume from container import after quota and cache paths are corrected only after the control passes.

• Enroot exhausted the user or filesystem quota while importing and extracting the SquashFS image. Free space elsewhere on the node does not help when the configured cache or data path has a separate quota.
• The decisive evidence is the first log line that precedes "pyxis enroot import failed to extract squashfs image disk quota exceeded" and differs from a healthy run.
• A nearby failure remains a competing hypothesis until a control separates configuration, capacity, transport, and hardware causes.

pyxis enroot import failed to extract squashfs image disk quota exceeded

Use this text as a lookup key in logs and upstream issue trackers. It is not presented as a captured customer log. Confirm the cause from your own preceding events, versions, configuration and the cited references.

inspect quota and free inodes on the Enroot cache, data, and temporary paths, then remove only unreferenced cached images or select a path with sufficient quota. This changes the condition in the causal diagnosis instead of hiding the outer exception. The repeated control proves ownership before recovery from container import after quota and cache paths are corrected.

# Preserve evidence before restarting
kubectl describe pod <pod>
kubectl get events --sort-by=.lastTimestamp
kubectl logs <pod> --all-containers

# Find the exact signature in the complete log
rg -n -F -- "pyxis enroot import failed to extract squashfs image disk quota exceeded" <log-file>

Adapt the snippet to your framework. The same pattern holds for PyTorch Lightning, Hugging Face Trainer, DeepSpeed, Megatron-LM, and vLLM training wrappers. Where the wrapper exposes a config flag (for examplelr_scheduler_type in Trainer), prefer the flag over the imperative API to keep the schedule declarative and reproducible.

Select the traceback or open the failed terminal, then run Denpex locally to see the initiating rank, collateral failures, exact fix, and verification command without uploading the log.