Persisting Notebook Data in Google Colab with Google Drive
Colab runtimes wipe /content when they disconnect. Learn when to mount Google Drive for checkpoints and when to copy data back to local VM storage.
Loading…
ReadMeFeed / Community knowledge
#ephemeral-storage
Real questions. Useful conversations. Find the people who know your stack.
googlecolabManaging State in Glitch: Navigating Ephemeral Filesystems and Container Isolation
Learn how Glitch handles project isolation and why writing to the local filesystem leads to data loss. A guide to ephemeral storage and container boundaries.
glitchGoogle Colab: Pick a Runtime Accelerator and Keep Data Past Disconnect
How to select a Colab runtime type, verify GPU attachment, and keep notebook files after disconnect by mounting Google Drive.
Ephemeral Filesystem Limits During Build-Time vs Runtime
Scalingo utilizes a container-based model where the application state is ephemeral, ensuring that any data written to the local filesystem is lost upon restart or redeployment. This behavior is critical for maintaining statelessness across scaled containers. While the runtime environment is strictly ephemeral, there is a distinction in how the filesystem beh
scalingoEphemeral Runtime Storage and Local File Persistence Limits
Local Disk Volatility in Hosted Runtimes Google Colab utilizes ephemeral virtual machines for notebook execution. While the environment provides a local file system located at /content/ , this storage is volatile. Any data written to the local disk is permanently deleted when the runtime is recycled, whether due to a manual "Disconnect and delete runtime" ac