This section contains usage limits that apply when using Serverless Containers.
|Total container memory**||Max size||600 GiB||Organization|
|Image size compressed||Max size||250 MiB||Container|
|Image size uncompressed||Max size||1 GiB||Container|
|Temporary disk size||Max size||1024 MiB||Container|
|Invocation rate||Max number||1000 per second||Container|
|Scale (simultaneous Container Instances)||Max||20||Container|
|CPU||Min/max||70 to 2240 mvCPU||Container|
|Memory||Min/Max||128 to 4096 MiB||Container|
|Environment variables||Max number||100||Container + namespace|
|Environment variables||Max size||1000 chars||Environment variable|
|Secret environment variables||Max number||100||Container + namespace|
|Secret environment variables||Max size||65536 bytes||Secret environment variable|
|Time before scale to zero||Time||15 minutes||Instance|
|Time before scale down||Time||30 seconds||Instance|
|Logs||Logs||30000 per minute||Project|
* Lower limits may apply before account verification. Contact our support team if you have any questions.
** Total container memory is the sum of the memory allocated to all your containers at their maximum Scale.
These limits are enforced as Organization quotas.
During the execution of the container, if the limits are exceeded, a restart occurs.
In order to ensure the proper functioning of the product, we restrict the use of certain ports and environment variables
- Blocked ports:
- 25: Due to potential abuse (spam), no outbound traffic is allowed through this port.
- 465: Due to potential abuse (spam), no outbound traffic is allowed through this port.
- Unavailable custom ports
Do not make your containers listen on these ports which are used by our service.
- Reserved environment variables:
PORT: Port on which your server should listen to (the default value is 8080)
SCW_*: Reserved for product configuration (for example: token validation)
When container CPU and/or memory are not provided by the client, these default values are automatically used:
Scaleway Containers only supports
amd64 architecture for
For example, if you build an image using an ARM CPU, such as Apple Silicon, your image will be in the
arm64 architecture, and you will have an error message during deployment.
You must ensure to build your image to target