Jump toSuggest an edit

Containers limitations

Reviewed on 01 March 2024Published on 12 October 2021

This section contains usage limits that apply when using Serverless Containers.

NamespacesMax number100*Project
ContainersMax number1000*Organization
Total container memory**Max size600 GiBOrganization
Image size compressedMax size250 MiBContainer
Image size uncompressedMax size1 GiBContainer
Temporary disk sizeMax size1024 MiBContainer
Invocation rateMax number1000 per secondContainer
ConcurrencyMax80Container Instance
Scale (simultaneous Container Instances)Max20Container
CPUMin/max70 to 2240 mvCPUContainer
MemoryMin/Max128 to 4096 MiBContainer
Environment variablesMax number100Container + namespace
Environment variablesMax size1000 charsEnvironment variable
Secret environment variablesMax number100Container + namespace
Secret environment variablesMax size65536 bytesSecret environment variable
Time before scale to zeroTime15 minutesInstance
Time before scale downTime30 secondsInstance
TimeoutMax15 minutesRequest
LogsLogs30000 per minuteProject

* 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.

Configuration Restrictions

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.
    • 8008
    • 8012
    • 8013
    • 8022
    • 9090
    • 9091
  • 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)

Default values for CPU and memory limits

When container CPU and/or memory are not provided by the client, these default values are automatically used:

ResourcesDefault value
CPU140 mvCPU
Memory256 MiB


Scaleway Containers only supports amd64 architecture for images.

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 amd64 architecture.

Docs APIScaleway consoleDedibox consoleScaleway LearningScaleway.comPricingBlogCarreer
© 2023-2024 – Scaleway