docs(srv): update container ephemeral storage documentation

serverless/containers/concepts.mdx

@@ -32,14 +32,18 @@ Container Registry is the place where your images are stored before being deploy
 
 A CRON trigger is a mechanism used to automatically invoke a Serverless Function at a specific time on a recurring schedule. It works similarly to a traditional Linux [cron job](https://en.wikipedia.org/wiki/Cron), using the `* * * * *` format, and uses the **UTC** time zone. Refer to our [cron schedules reference](/serverless/containers/reference-content/cron-schedules/) for more information.
 
-## GB-s
-
-Unit used to measure the resource consumption of a container. It reflects the amount of memory consumed over time.
-
 ## Environment variables
 
 An environment variable is a variable whose value is set outside the program, typically through functionality built into the operating system or microservice. An environment variable is made up of a name/value pair, and any number may be created and available for reference at a point in time.
 
+## Ephemeral storage
+
+In addition to VCPU and RAM, Serverless Containers also provide a storage volume for the duration of the task. This storage space allows to hold the data retrieved by the job, and disappears once the execution is complete. The maximum size of the ephemeral storage is tied to the allocated memory.
+
+## GB-s
+
+Unit used to measure the resource consumption of a container. It reflects the amount of memory consumed over time.
+
 ## Image
 
 An image is a blueprint from which an arbitrary number of brand-new containers can be started. You can start a container from an image, perform operations in it, and save another image based on the latest state of the container.

serverless/containers/how-to/deploy-a-container-from-external-container-registry.mdx

@@ -38,6 +38,9 @@ For now, Serverless Containers only supports public images.
     - Choose the [port](/serverless/containers/concepts/#port) your container is listening on. We recommend configuring your container to listen on the `$PORT` environment variable.
     - Choose a **name** for your container and, optionally, a **description**. The name must only contain alphanumeric characters and dashes.
     - Choose the **resources** to be allocated to your container at runtime. These define the performance characteristics of your container.
+        <Message type="note">
+        Available memory depends on allocated VCPU, and maximum ephemeral storage value depends on allocated memory.
+        </Message>
     - Set your [scaling](/serverless/containers/concepts/#scaling) preferences, or leave them at default values. The Scaleway platform autoscales the number of available instances of your container to match the incoming load, depending on the settings you define here.
     - Click **Advanced options** to define any [environment variables](/serverless/containers/concepts/#environment-variables) you want to inject into your container. For each environment variable, click **+Add variable** and enter the key/value pair.
     - Add [secrets](/serverless/containers/concepts/#secrets) for your container. Secrets are environment variables which are injected into your container, but the values are not retained or displayed by Scaleway after initial validation.

serverless/containers/how-to/deploy-a-container-from-scaleway-container-registry.mdx

@@ -36,6 +36,9 @@ You can deploy a container from the [Scaleway Container Registry](/containers/co
     - Choose the [port](/serverless/containers/concepts/#port) your container is listening on. We recommend configuring your container to listen on the `$PORT` environment variable.
     - Choose a **name** for your container and, optionally, a **description**. The name must only contain alphanumeric characters and dashes.
     - Choose the **resources** to be allocated to your container at runtime. These define the performance characteristics of your container.
+        <Message type="note">
+        Available memory depends on allocated VCPU, and maximum ephemeral storage value depends on allocated memory.
+        </Message>
     - Set your [scaling](/serverless/containers/concepts/#scaling) preferences, or leave them at default values. The Scaleway platform autoscales the number of available instances of your container to match the incoming load, depending on the settings you define here.
     - Click **Advanced options** to define any [environment variables](/serverless/containers/concepts/#environment-variables) you want to inject into your container. For each environment variable, click **+Add variable** and enter the key/value pair.
     - Add [secrets](/serverless/containers/concepts/#secrets) for your container. Secrets are environment variables which are injected into your container, but the values are not retained or displayed by Scaleway after initial validation.