How do I resolve "ENOSPC: no space left on device" errors in sandboxes?
Last updated: February 16, 2026
Context
You may encounter "ENOSPC: no space left on device" errors when your sandbox runs out of storage space. This typically happens when your sandbox's filesystem storage needs exceed the available memory allocation, since sandbox storage is by default in-memory for optimal speed.
Answer
There are two main approaches to resolve this storage issue:
Option 1: Increase Memory Allocation
Since memory in a sandbox equals actual memory plus filesystem storage, you can increase your sandbox's memory allocation to provide more storage space. This is the recommended short-term solution.
Tip: If you see "Out of memory: Killed process" errors in your sandbox logs, this indicates your sandbox has exceeded its memory allocation and needs more memory.
Note that increasing memory also increases CPU allocation:
8GB memory = 4 CPU cores
16GB memory = 8 CPU cores
Option 2: Use Volumes for Large Storage Needs
If you need more than 4GB of storage for files alone, consider using the Volume feature for persistent, larger storage. You can find detailed information about Volumes in the Blaxel documentation.
Keep in mind that using Volumes may impact filesystem speed compared to the default in-memory storage.