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 behaves during the build phase versus the execution phase. Specifically, when buildpacks generate artifacts or temporary files during the deployment process, these files are packaged into the final slug.

When managing large temporary datasets during the build process, it is unclear where the hard limit for the ephemeral disk space resides before the build process is terminated by the platform.

• What is the maximum disk space allocation for the ephemeral filesystem during the build phase?
• Does the platform apply the same storage quotas to the build container as it does to the runtime container?