From 1e2bf57f48c9a09109991cb35a1518bb9aa7bb26 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Mon, 5 May 2025 14:50:47 +0200 Subject: [PATCH 01/14] docs(srv): update doc on sandbox environments MTA-6006 --- .../containers-limitations.mdx | 8 ++++++-- .../reference-content/containers-sandbox.mdx | 17 +++++++++++++++++ 2 files changed, 23 insertions(+), 2 deletions(-) create mode 100644 pages/serverless-containers/reference-content/containers-sandbox.mdx diff --git a/pages/serverless-containers/reference-content/containers-limitations.mdx b/pages/serverless-containers/reference-content/containers-limitations.mdx index ba1462d844..045cb932c4 100644 --- a/pages/serverless-containers/reference-content/containers-limitations.mdx +++ b/pages/serverless-containers/reference-content/containers-limitations.mdx @@ -23,7 +23,7 @@ This section contains usage limits that apply when using Serverless Containers. | Total container memory\** | Max size | 600 GiB | Organization | | Custom domains | Max number | 50 | Container | | Recommended maximum uncompressed image size | Max size | 1 GB | Container | -| Temporary disk size ¨ | Max size | 24 000 MiB | Container | +| Temporary disk size ¨ | Max size | 24 000 MiB | Container | | Invocation rate | Max number | 1000 per second | Container | | Concurrency | Max | 80 | Container Instance | | Max Scale (simultaneous Container instances) | Max | 50 | Container | @@ -98,7 +98,7 @@ When container CPU and/or memory are not provided by the client, these default v | Resources | Default value | |-----------|----------------| | CPU | 1000 mvCPU | -| Memory | 2048 MB | +| Memory | 2048 MB | ## Architecture @@ -127,3 +127,7 @@ Below is an example than illustrates this behavior: * Time +2H: Despite the failed deployment, the first container is still handling incoming requests. * Time +25H: The 24-hour window expires, and both the first working container and the failed container are removed, leading to service disruption until a new successful deployment is made. + +## Containers sandbox + +Refer to the [dedicated documentation](/serverless-containers/reference-content/containers-sandbox/) for more information on the limitations of sandbox environments for Serverless Containers. diff --git a/pages/serverless-containers/reference-content/containers-sandbox.mdx b/pages/serverless-containers/reference-content/containers-sandbox.mdx new file mode 100644 index 0000000000..339764c8f3 --- /dev/null +++ b/pages/serverless-containers/reference-content/containers-sandbox.mdx @@ -0,0 +1,17 @@ +--- +meta: + title: Containers sandbox + description: Learn more about the sandboxing environments of Scaleway Serverless Containers. +content: + h1: Containers sandbox + paragraph: Learn more about the sandboxing environments of Scaleway Serverless Containers. +tags: containers sandbox sandboxing gvisor isolation mechanism serverless v1 v2 +dates: + validation: 2025-03-13 + posted: 2021-10-12 +categories: + - serverless + - containers +--- + +In the context of Scaleway Serverless Containers, a sandbox environment is a critical security mechanism that isolates each container from others, ensuring that they operate in a secure and controlled space. Containers run in dedicated execution environments that preventing unauthorized access and potential interference between different resources. From cdd732f4581931c81220c68d4a10c61f01081bf0 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Tue, 6 May 2025 17:30:21 +0200 Subject: [PATCH 02/14] docs(srv): update --- pages/serverless-containers/concepts.mdx | 2 ++ pages/serverless-containers/faq.mdx | 6 +++++- .../reference-content/containers-sandbox.mdx | 16 +++++++++++++++- 3 files changed, 22 insertions(+), 2 deletions(-) diff --git a/pages/serverless-containers/concepts.mdx b/pages/serverless-containers/concepts.mdx index 872b60ac87..e8a06602f5 100644 --- a/pages/serverless-containers/concepts.mdx +++ b/pages/serverless-containers/concepts.mdx @@ -196,6 +196,8 @@ A sandbox is an isolation area for your container. Serverless Containers offer t - **v2** - Recommended for faster cold starts. Can introduce some overhead on specific workflows with consequent amount of *syscalls*. - **v1** - Legacy sandboxing with slower cold starts, but fully supports Linux system call interface. Prefer this option when processing large amounts of *syscalls*. + + ## Scale to zero One of the advantages of Serverless Containers is that when your container is not triggered, it does not consume any resources, which enables great savings. diff --git a/pages/serverless-containers/faq.mdx b/pages/serverless-containers/faq.mdx index 8b8a32811a..92c4f1c57d 100644 --- a/pages/serverless-containers/faq.mdx +++ b/pages/serverless-containers/faq.mdx @@ -144,9 +144,13 @@ Ensure that your code avoids heavy computations or long-running initialization a ### Which Linux syscalls are supported? +Serverless Containers offer two sandboxing environments: + - [Sandbox](/serverless-containers/concepts/#sandbox) v1 guarantees full compatibility with Linux syscalls. -- [Sandbox](/serverless-containers/concepts/#sandbox) v2 relies on [gVisor](https://gvisor.dev/), which implements a selection of syscalls. Refer to the [official gVisor documentation](https://gvisor.dev/docs/user_guide/compatibility/linux/amd64/) for a comprehensive list of supported syscalls. +- [Sandbox](/serverless-containers/concepts/#sandbox) v2 relies on [gVisor](https://gvisor.dev/), which implements a selection of syscalls. + +Refer to the [dedicated documentation](/serverless-containers/reference-content/containers-sandbox/) for more information on sandboxing environments. ### What are the limitations of Serverless Containers? diff --git a/pages/serverless-containers/reference-content/containers-sandbox.mdx b/pages/serverless-containers/reference-content/containers-sandbox.mdx index 339764c8f3..64f595e091 100644 --- a/pages/serverless-containers/reference-content/containers-sandbox.mdx +++ b/pages/serverless-containers/reference-content/containers-sandbox.mdx @@ -14,4 +14,18 @@ categories: - containers --- -In the context of Scaleway Serverless Containers, a sandbox environment is a critical security mechanism that isolates each container from others, ensuring that they operate in a secure and controlled space. Containers run in dedicated execution environments that preventing unauthorized access and potential interference between different resources. +In the context of Scaleway Serverless Containers, a [Sandbox environment](/serverless-containers/concepts/#sandbox) is a critical security mechanism that isolates each container from others, ensuring that they operate in a secure and controlled space. Containers run in dedicated execution environments that preventing unauthorized access and potential interference between different resources. + +Scaleway Serverless Containers offers two sandbox environment options: + +- Sandbox v1 (legacy) +- Sandbox v2 (recommended) + +## Sandbox v1 + +Sandbox v1 is Serverless Containers' legacy sandboxing environment with slower [cold starts](/serverless-containers/concepts/#cold-start), but fully supports Linux system call interface. This option is recommended when processing large amounts of *syscalls*. + +## Sandbox v2 + +Sandbox v2 is a modern isolation environment that relies on [gVisor](https://gvisor.dev/). This option offers faster [cold starts](/serverless-containers/concepts/#cold-start), but only implements a selection of Linux syscalls. +Refer to the [official gVisor documentation](https://gvisor.dev/docs/user_guide/compatibility/linux/amd64/) for a comprehensive list of supported syscalls. \ No newline at end of file From 1cb6731d51828b1a5f6ad7fc5c92eaed0c0353fb Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 7 May 2025 11:03:07 +0200 Subject: [PATCH 03/14] docs(srv): update --- .../reference-content/containers-sandbox.mdx | 8 ++++-- .../troubleshooting/container-clock-drift.mdx | 27 +++++++++++++++++++ 2 files changed, 33 insertions(+), 2 deletions(-) create mode 100644 pages/serverless-containers/troubleshooting/container-clock-drift.mdx diff --git a/pages/serverless-containers/reference-content/containers-sandbox.mdx b/pages/serverless-containers/reference-content/containers-sandbox.mdx index 64f595e091..dd89a10e3c 100644 --- a/pages/serverless-containers/reference-content/containers-sandbox.mdx +++ b/pages/serverless-containers/reference-content/containers-sandbox.mdx @@ -5,7 +5,7 @@ meta: content: h1: Containers sandbox paragraph: Learn more about the sandboxing environments of Scaleway Serverless Containers. -tags: containers sandbox sandboxing gvisor isolation mechanism serverless v1 v2 +tags: containers sandbox sandboxing gvisor isolation mechanism serverless v1 v2 clock drift skew dates: validation: 2025-03-13 posted: 2021-10-12 @@ -14,7 +14,7 @@ categories: - containers --- -In the context of Scaleway Serverless Containers, a [Sandbox environment](/serverless-containers/concepts/#sandbox) is a critical security mechanism that isolates each container from others, ensuring that they operate in a secure and controlled space. Containers run in dedicated execution environments that preventing unauthorized access and potential interference between different resources. +In the context of Scaleway Serverless Containers, a [Sandbox environment](/serverless-containers/concepts/#sandbox) is a critical security mechanism that isolates each container from others, ensuring that they operate in a secure and controlled space. Containers run in dedicated execution environments that prevent unauthorized access and potential interference between different resources. Scaleway Serverless Containers offers two sandbox environment options: @@ -25,6 +25,10 @@ Scaleway Serverless Containers offers two sandbox environment options: Sandbox v1 is Serverless Containers' legacy sandboxing environment with slower [cold starts](/serverless-containers/concepts/#cold-start), but fully supports Linux system call interface. This option is recommended when processing large amounts of *syscalls*. + +Sandbox v1 are known to experience clock drift over time. A difference of approximately **two seconds** can be observed after 24 hours of uninterrupted execution. This issue especially affects long-running containers, whereas short-lived containers are much less impacted. + + ## Sandbox v2 Sandbox v2 is a modern isolation environment that relies on [gVisor](https://gvisor.dev/). This option offers faster [cold starts](/serverless-containers/concepts/#cold-start), but only implements a selection of Linux syscalls. diff --git a/pages/serverless-containers/troubleshooting/container-clock-drift.mdx b/pages/serverless-containers/troubleshooting/container-clock-drift.mdx new file mode 100644 index 0000000000..a1dcdc4833 --- /dev/null +++ b/pages/serverless-containers/troubleshooting/container-clock-drift.mdx @@ -0,0 +1,27 @@ +--- +meta: + title: I am experiencing clock drift with my container + description: Discover the causes and solutions to clock drift issues in Scaleway Serverless Containers. +content: + h1: I am experiencing clock drift with my container + paragraph: Discover the causes and solutions to clock drift issues in Scaleway Serverless Containers. +tags: containers clock drift serverless troubleshooting +dates: + validation: 2025-05-07 + posted: 2025-05-07 +categories: + - serverless + - containers +--- + +## Problem + +The clock of my Serverless Container is slowly drifting. + +## Cause + +The internal clock of a Serverless Container executed in a [Sandbox v1](/serverless-containers/reference-content/containers-sandbox/) environment is known to slowly drift over time, to reach a clock skew of approximately **two seconds** after 24 hours. + +## Solution + +[Update the sandbox environment](/how-to/manage-a-container/#how-to-manage-a-container-deployment) of your Serverless Container to [Sandbox v2](/serverless-containers/reference-content/containers-sandbox/#sandbox-v2) to solve clock drift issues. \ No newline at end of file From 8670248eb632004e0c69aa41fd76b5d491c04c20 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 7 May 2025 11:08:03 +0200 Subject: [PATCH 04/14] docs(srv): update --- pages/serverless-containers/concepts.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/serverless-containers/concepts.mdx b/pages/serverless-containers/concepts.mdx index e8a06602f5..6517877da6 100644 --- a/pages/serverless-containers/concepts.mdx +++ b/pages/serverless-containers/concepts.mdx @@ -193,10 +193,10 @@ This process ensures a seamless update experience, minimizing user disruption du ## Sandbox A sandbox is an isolation area for your container. Serverless Containers offer two sandboxing environments: -- **v2** - Recommended for faster cold starts. Can introduce some overhead on specific workflows with consequent amount of *syscalls*. -- **v1** - Legacy sandboxing with slower cold starts, but fully supports Linux system call interface. Prefer this option when processing large amounts of *syscalls*. - +- **v1** - Legacy sandboxing with slower cold starts, but fully supports Linux syscall interface. +- **v2** - Recommended for faster cold starts, but only supports a selection of Linux syscalls. +Refer to the [dedicated documentation](/serverless-containers/reference-content/containers-sandbox/) for more information on sandbox environments. ## Scale to zero From 7b284295771d87df6383bb7aefa5b84ab5033be2 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 7 May 2025 11:12:36 +0200 Subject: [PATCH 05/14] docs(srv): update --- menu/navigation.json | 8 ++++++++ pages/serverless-containers/troubleshooting/index.mdx | 1 + 2 files changed, 9 insertions(+) diff --git a/menu/navigation.json b/menu/navigation.json index 5440dec029..faded07f87 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -3929,6 +3929,10 @@ "label": "Functions autoscaling", "slug": "functions-autoscaling" }, + { + "label": "Functions sandbox", + "slug": "functions-sandbox" + }, { "label": "Code examples", "slug": "code-examples" @@ -4097,6 +4101,10 @@ "label": "Containers port parameter", "slug": "port-parameter-variable" }, + { + "label": "Containers sandbox", + "slug": "containers-sandbox" + }, { "label": "Differences between Jobs, Functions and Containers", "slug": "difference-jobs-functions-containers" diff --git a/pages/serverless-containers/troubleshooting/index.mdx b/pages/serverless-containers/troubleshooting/index.mdx index 9f1d06a04f..41879fb8bf 100644 --- a/pages/serverless-containers/troubleshooting/index.mdx +++ b/pages/serverless-containers/troubleshooting/index.mdx @@ -69,3 +69,4 @@ categories: - [I cannot retrieve an external image for my container](/serverless-containers/troubleshooting/cannot-retrieve-external-image/) - [My container stopped working after a redeploy](/serverless-containers/troubleshooting/container-stopped-after-redeploy/) - [Tests fail on Serverless Containers](/serverless-containers/troubleshooting/tests-fail-on-container/) +- [I am experiencing clock drift with my Serverless Containers](/serverless-containers/troubleshooting/container-clock-drift/) \ No newline at end of file From c9e80e8bc0567a2e1e6d2df97197fe1a2522fc92 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 7 May 2025 11:25:29 +0200 Subject: [PATCH 06/14] docs(srv): update --- .../reference-content/containers-sandbox.mdx | 38 ++----------------- .../reference-content/functions-sandbox.mdx | 35 +++++++++++++++++ .../troubleshooting/function-clock-drift.mdx | 27 +++++++++++++ 3 files changed, 65 insertions(+), 35 deletions(-) create mode 100644 pages/serverless-functions/reference-content/functions-sandbox.mdx create mode 100644 pages/serverless-functions/troubleshooting/function-clock-drift.mdx diff --git a/pages/serverless-containers/reference-content/containers-sandbox.mdx b/pages/serverless-containers/reference-content/containers-sandbox.mdx index dd89a10e3c..0acc956b42 100644 --- a/pages/serverless-containers/reference-content/containers-sandbox.mdx +++ b/pages/serverless-containers/reference-content/containers-sandbox.mdx @@ -1,35 +1,3 @@ ---- -meta: - title: Containers sandbox - description: Learn more about the sandboxing environments of Scaleway Serverless Containers. -content: - h1: Containers sandbox - paragraph: Learn more about the sandboxing environments of Scaleway Serverless Containers. -tags: containers sandbox sandboxing gvisor isolation mechanism serverless v1 v2 clock drift skew -dates: - validation: 2025-03-13 - posted: 2021-10-12 -categories: - - serverless - - containers ---- - -In the context of Scaleway Serverless Containers, a [Sandbox environment](/serverless-containers/concepts/#sandbox) is a critical security mechanism that isolates each container from others, ensuring that they operate in a secure and controlled space. Containers run in dedicated execution environments that prevent unauthorized access and potential interference between different resources. - -Scaleway Serverless Containers offers two sandbox environment options: - -- Sandbox v1 (legacy) -- Sandbox v2 (recommended) - -## Sandbox v1 - -Sandbox v1 is Serverless Containers' legacy sandboxing environment with slower [cold starts](/serverless-containers/concepts/#cold-start), but fully supports Linux system call interface. This option is recommended when processing large amounts of *syscalls*. - - -Sandbox v1 are known to experience clock drift over time. A difference of approximately **two seconds** can be observed after 24 hours of uninterrupted execution. This issue especially affects long-running containers, whereas short-lived containers are much less impacted. - - -## Sandbox v2 - -Sandbox v2 is a modern isolation environment that relies on [gVisor](https://gvisor.dev/). This option offers faster [cold starts](/serverless-containers/concepts/#cold-start), but only implements a selection of Linux syscalls. -Refer to the [official gVisor documentation](https://gvisor.dev/docs/user_guide/compatibility/linux/amd64/) for a comprehensive list of supported syscalls. \ No newline at end of file + "label": "Containers sandbox", + "slug": "containers-sandbox" + }, \ No newline at end of file diff --git a/pages/serverless-functions/reference-content/functions-sandbox.mdx b/pages/serverless-functions/reference-content/functions-sandbox.mdx new file mode 100644 index 0000000000..dd9ab0d3b9 --- /dev/null +++ b/pages/serverless-functions/reference-content/functions-sandbox.mdx @@ -0,0 +1,35 @@ +--- +meta: + title: Functions sandbox + description: Learn more about the sandboxing environments of Scaleway Serverless Functions. +content: + h1: Functions sandbox + paragraph: Learn more about the sandboxing environments of Scaleway Serverless Functions. +tags: functions sandbox sandboxing gvisor isolation mechanism serverless v1 v2 clock drift skew +dates: + validation: 2025-03-13 + posted: 2021-10-12 +categories: + - serverless + - functions +--- + +In the context of Scaleway Serverless Functions, a [Sandbox environment](/serverless-functions/concepts/#sandbox) is a critical security mechanism that isolates each function from others, ensuring that they operate in a secure and controlled space. Functions run in dedicated execution environments that prevent unauthorized access and potential interference between different resources. + +Scaleway Serverless Functions offers two sandbox environment options: + +- Sandbox v1 (legacy) +- Sandbox v2 (recommended) + +## Sandbox v1 + +Sandbox v1 is Serverless Functions' legacy sandboxing environment with slower [cold starts](/serverless-functions/concepts/#cold-start), but fully supports Linux system call interface. This option is recommended when processing large amounts of *syscalls*. + + +Sandbox v1 are known to experience clock drift over time. A difference of approximately **two seconds** can be observed after 24 hours of uninterrupted execution. This issue especially affects long-running functions, whereas short-lived functions are much less impacted. + + +## Sandbox v2 + +Sandbox v2 is a modern isolation environment that relies on [gVisor](https://gvisor.dev/). This option offers faster [cold starts](/serverless-functions/concepts/#cold-start), but only implements a selection of Linux syscalls. +Refer to the [official gVisor documentation](https://gvisor.dev/docs/user_guide/compatibility/linux/amd64/) for a comprehensive list of supported syscalls. \ No newline at end of file diff --git a/pages/serverless-functions/troubleshooting/function-clock-drift.mdx b/pages/serverless-functions/troubleshooting/function-clock-drift.mdx new file mode 100644 index 0000000000..19eae44c2f --- /dev/null +++ b/pages/serverless-functions/troubleshooting/function-clock-drift.mdx @@ -0,0 +1,27 @@ +--- +meta: + title: I am experiencing clock drift with my function + description: Discover the causes and solutions to clock drift issues in Scaleway Serverless Functions. +content: + h1: I am experiencing clock drift with my function + paragraph: Discover the causes and solutions to clock drift issues in Scaleway Serverless Functions. +tags: functions clock drift serverless troubleshooting +dates: + validation: 2025-05-07 + posted: 2025-05-07 +categories: + - serverless + - functions +--- + +## Problem + +The clock of my Serverless Function is slowly drifting. + +## Cause + +The internal clock of a Serverless Function executed in a [Sandbox v1](/serverless-functions/reference-content/functions-sandbox/) environment is known to slowly drift over time, to reach a clock skew of approximately **two seconds** after 24 hours. + +## Solution + +[Update the sandbox environment](/how-to/manage-a-function/#how-to-manage-a-function-deployment) of your Serverless Function to [Sandbox v2](/serverless-functions/reference-content/functions-sandbox/#sandbox-v2) to solve clock drift issues. \ No newline at end of file From 4bf8f4832ddc9e18dab6087f8b253546a91100f8 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 7 May 2025 11:34:00 +0200 Subject: [PATCH 07/14] docs(srv): update --- .../troubleshooting/cannot-deploy-image.mdx | 2 +- pages/serverless-functions/concepts.mdx | 6 ++++-- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/pages/serverless-containers/troubleshooting/cannot-deploy-image.mdx b/pages/serverless-containers/troubleshooting/cannot-deploy-image.mdx index 086a72d5bb..e954ff1689 100644 --- a/pages/serverless-containers/troubleshooting/cannot-deploy-image.mdx +++ b/pages/serverless-containers/troubleshooting/cannot-deploy-image.mdx @@ -19,7 +19,7 @@ I am unable to deploy my image using Serverless Containers. ## Possible solutions -- Make sure the container is listening on the specified PORT for HTTP requests (or use variable `$PORT`). +- Make sure the container is listening on the specified PORT for HTTP requests (or use variable `$PORT`). Refer to the [dedicated documentation](/serverless-containers/reference-content/port-parameter-variable/) for more information. - Make sure the container is bound to `0.0.0.0`. diff --git a/pages/serverless-functions/concepts.mdx b/pages/serverless-functions/concepts.mdx index 445438926a..4b1a41d305 100644 --- a/pages/serverless-functions/concepts.mdx +++ b/pages/serverless-functions/concepts.mdx @@ -153,8 +153,10 @@ The runtime is the execution environment of your function. Regarding Serverless ## Sandbox A sandbox is an isolation area for your function. Serverless Functions offer two sandboxing environments: -- **v2** - Recommended for faster cold starts. -- **v1** - Legacy sandboxing with a slower cold start, but fully supports Linux system call interface. +- **v1** - Legacy sandboxing with slower cold starts, but fully supports Linux syscall interface. +- **v2** - Recommended for faster cold starts, but only supports a selection of Linux syscalls. + +Refer to the [dedicated documentation](/serverless-functions/reference-content/functions-sandbox/) for more information on sandbox environments. ## Scale to zero From c17b36aa81c8eaad4173a39c9c06957457afb241 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 7 May 2025 11:36:51 +0200 Subject: [PATCH 08/14] docs(srv): update --- .../reference-content/containers-sandbox.mdx | 38 +++++++++++++++++-- 1 file changed, 35 insertions(+), 3 deletions(-) diff --git a/pages/serverless-containers/reference-content/containers-sandbox.mdx b/pages/serverless-containers/reference-content/containers-sandbox.mdx index 0acc956b42..9da0955938 100644 --- a/pages/serverless-containers/reference-content/containers-sandbox.mdx +++ b/pages/serverless-containers/reference-content/containers-sandbox.mdx @@ -1,3 +1,35 @@ - "label": "Containers sandbox", - "slug": "containers-sandbox" - }, \ No newline at end of file +--- +meta: + title: Containers sandbox + description: Learn more about the sandboxing environments of Scaleway Serverless Containers. +content: + h1: Containers sandbox + paragraph: Learn more about the sandboxing environments of Scaleway Serverless Containers. +tags: containers sandbox sandboxing gvisor isolation mechanism serverless v1 v2 clock drift skew +dates: + validation: 2025-05-07 + posted: 2025-05-07 +categories: + - serverless + - containers +--- + +In the context of Scaleway Serverless Containers, a [Sandbox environment](/serverless-containers/concepts/#sandbox) is a critical security mechanism that isolates each container from others, ensuring that they operate in a secure and controlled space. Containers run in dedicated execution environments that prevent unauthorized access and potential interference between different resources. + +Scaleway Serverless Containers offers two sandbox environment options: + +- Sandbox v1 (legacy) +- Sandbox v2 (recommended) + +## Sandbox v1 + +Sandbox v1 is Serverless Containers' legacy sandboxing environment with slower [cold starts](/serverless-containers/concepts/#cold-start), but fully supports Linux system call interface. This option is recommended when processing large amounts of *syscalls*. + + +Sandbox v1 are known to experience clock drift over time. A difference of approximately **two seconds** can be observed after 24 hours of uninterrupted execution. This issue especially affects long-running containers, whereas short-lived containers are much less impacted. + + +## Sandbox v2 + +Sandbox v2 is a modern isolation environment that relies on [gVisor](https://gvisor.dev/). This option offers faster [cold starts](/serverless-containers/concepts/#cold-start), but only implements a selection of Linux syscalls. +Refer to the [official gVisor documentation](https://gvisor.dev/docs/user_guide/compatibility/linux/amd64/) for a comprehensive list of supported syscalls. From c9783fec9816a5f3d2c02f2ce213698af93e3e41 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 7 May 2025 12:01:24 +0200 Subject: [PATCH 09/14] docs(srv): update --- .../reference-content/containers-sandbox.mdx | 2 +- .../troubleshooting/container-clock-drift.mdx | 2 +- .../reference-content/functions-sandbox.mdx | 2 +- .../troubleshooting/function-clock-drift.mdx | 2 +- pages/serverless-functions/troubleshooting/index.mdx | 3 ++- 5 files changed, 6 insertions(+), 5 deletions(-) diff --git a/pages/serverless-containers/reference-content/containers-sandbox.mdx b/pages/serverless-containers/reference-content/containers-sandbox.mdx index 9da0955938..baa3fffd8f 100644 --- a/pages/serverless-containers/reference-content/containers-sandbox.mdx +++ b/pages/serverless-containers/reference-content/containers-sandbox.mdx @@ -26,7 +26,7 @@ Scaleway Serverless Containers offers two sandbox environment options: Sandbox v1 is Serverless Containers' legacy sandboxing environment with slower [cold starts](/serverless-containers/concepts/#cold-start), but fully supports Linux system call interface. This option is recommended when processing large amounts of *syscalls*. -Sandbox v1 are known to experience clock drift over time. A difference of approximately **two seconds** can be observed after 24 hours of uninterrupted execution. This issue especially affects long-running containers, whereas short-lived containers are much less impacted. +Sandbox v1 are known to experience clock drift over time. A difference of approximately **two seconds** can be observed after 24 hours of uninterrupted execution. This issue especially affects long-running containers, whereas short-lived containers are much less impacted. Update to sandbox v2 to solve the issue. ## Sandbox v2 diff --git a/pages/serverless-containers/troubleshooting/container-clock-drift.mdx b/pages/serverless-containers/troubleshooting/container-clock-drift.mdx index a1dcdc4833..8ab8b671f9 100644 --- a/pages/serverless-containers/troubleshooting/container-clock-drift.mdx +++ b/pages/serverless-containers/troubleshooting/container-clock-drift.mdx @@ -24,4 +24,4 @@ The internal clock of a Serverless Container executed in a [Sandbox v1](/serverl ## Solution -[Update the sandbox environment](/how-to/manage-a-container/#how-to-manage-a-container-deployment) of your Serverless Container to [Sandbox v2](/serverless-containers/reference-content/containers-sandbox/#sandbox-v2) to solve clock drift issues. \ No newline at end of file +[Update the sandbox environment](/serverless-containers/how-to/manage-a-container/#how-to-manage-a-container-deployment) of your Serverless Container to [Sandbox v2](/serverless-containers/reference-content/containers-sandbox/#sandbox-v2) to solve clock drift issues. \ No newline at end of file diff --git a/pages/serverless-functions/reference-content/functions-sandbox.mdx b/pages/serverless-functions/reference-content/functions-sandbox.mdx index dd9ab0d3b9..f6d0b3578d 100644 --- a/pages/serverless-functions/reference-content/functions-sandbox.mdx +++ b/pages/serverless-functions/reference-content/functions-sandbox.mdx @@ -26,7 +26,7 @@ Scaleway Serverless Functions offers two sandbox environment options: Sandbox v1 is Serverless Functions' legacy sandboxing environment with slower [cold starts](/serverless-functions/concepts/#cold-start), but fully supports Linux system call interface. This option is recommended when processing large amounts of *syscalls*. -Sandbox v1 are known to experience clock drift over time. A difference of approximately **two seconds** can be observed after 24 hours of uninterrupted execution. This issue especially affects long-running functions, whereas short-lived functions are much less impacted. +Sandbox v1 are known to experience clock drift over time. A difference of approximately **two seconds** can be observed after 24 hours of uninterrupted execution. This issue especially affects long-running functions, whereas short-lived functions are much less impacted. Update to sandbox v2 to solve the issue. ## Sandbox v2 diff --git a/pages/serverless-functions/troubleshooting/function-clock-drift.mdx b/pages/serverless-functions/troubleshooting/function-clock-drift.mdx index 19eae44c2f..bef936d573 100644 --- a/pages/serverless-functions/troubleshooting/function-clock-drift.mdx +++ b/pages/serverless-functions/troubleshooting/function-clock-drift.mdx @@ -24,4 +24,4 @@ The internal clock of a Serverless Function executed in a [Sandbox v1](/serverle ## Solution -[Update the sandbox environment](/how-to/manage-a-function/#how-to-manage-a-function-deployment) of your Serverless Function to [Sandbox v2](/serverless-functions/reference-content/functions-sandbox/#sandbox-v2) to solve clock drift issues. \ No newline at end of file +[Update the sandbox environment](/how-to/manage-a-function/) of your Serverless Function to [Sandbox v2](/serverless-functions/reference-content/functions-sandbox/#sandbox-v2) to solve clock drift issues. \ No newline at end of file diff --git a/pages/serverless-functions/troubleshooting/index.mdx b/pages/serverless-functions/troubleshooting/index.mdx index 9f82c9e9d4..3a9f9f8b5a 100644 --- a/pages/serverless-functions/troubleshooting/index.mdx +++ b/pages/serverless-functions/troubleshooting/index.mdx @@ -71,4 +71,5 @@ categories: - [Unable to find the function handler](/serverless-functions/troubleshooting/handler-not-found/) - [Tests fail on Serverless Functions](/serverless-functions/troubleshooting/tests-fail-on-function/) - [I am experiencing timeout errors](/serverless-functions/troubleshooting/timeout-error/) -- [My function fails after trying too many times](/serverless-functions/troubleshooting/too-many-retries/) \ No newline at end of file +- [My function fails after trying too many times](/serverless-functions/troubleshooting/too-many-retries/) +- [I am experiencing clock drift with my Serverless Functions](/serverless-functions/troubleshooting/function-clock-drift/) \ No newline at end of file From 154292a8835d4b804046730e0b76d3ea2803f725 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 7 May 2025 13:51:06 +0200 Subject: [PATCH 10/14] docs(srv): update --- .../troubleshooting/container-clock-drift.mdx | 2 +- .../troubleshooting/function-clock-drift.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/serverless-containers/troubleshooting/container-clock-drift.mdx b/pages/serverless-containers/troubleshooting/container-clock-drift.mdx index 8ab8b671f9..0cafe8db75 100644 --- a/pages/serverless-containers/troubleshooting/container-clock-drift.mdx +++ b/pages/serverless-containers/troubleshooting/container-clock-drift.mdx @@ -5,7 +5,7 @@ meta: content: h1: I am experiencing clock drift with my container paragraph: Discover the causes and solutions to clock drift issues in Scaleway Serverless Containers. -tags: containers clock drift serverless troubleshooting +tags: containers clock drift skew error time difference serverless troubleshooting dates: validation: 2025-05-07 posted: 2025-05-07 diff --git a/pages/serverless-functions/troubleshooting/function-clock-drift.mdx b/pages/serverless-functions/troubleshooting/function-clock-drift.mdx index bef936d573..073628d855 100644 --- a/pages/serverless-functions/troubleshooting/function-clock-drift.mdx +++ b/pages/serverless-functions/troubleshooting/function-clock-drift.mdx @@ -5,7 +5,7 @@ meta: content: h1: I am experiencing clock drift with my function paragraph: Discover the causes and solutions to clock drift issues in Scaleway Serverless Functions. -tags: functions clock drift serverless troubleshooting +tags: functions clock drift skew serverless difference time troubleshooting dates: validation: 2025-05-07 posted: 2025-05-07 From 305a89a9b95942dcd912e35455cf87e15227f6e2 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Mon, 12 May 2025 10:43:15 +0200 Subject: [PATCH 11/14] Update pages/serverless-containers/reference-content/containers-sandbox.mdx Co-authored-by: Thomas TACQUET --- .../reference-content/containers-sandbox.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/serverless-containers/reference-content/containers-sandbox.mdx b/pages/serverless-containers/reference-content/containers-sandbox.mdx index baa3fffd8f..6aa9724565 100644 --- a/pages/serverless-containers/reference-content/containers-sandbox.mdx +++ b/pages/serverless-containers/reference-content/containers-sandbox.mdx @@ -23,7 +23,7 @@ Scaleway Serverless Containers offers two sandbox environment options: ## Sandbox v1 -Sandbox v1 is Serverless Containers' legacy sandboxing environment with slower [cold starts](/serverless-containers/concepts/#cold-start), but fully supports Linux system call interface. This option is recommended when processing large amounts of *syscalls*. +Sandbox v1 is Serverless Containers' legacy sandboxing environment with slower [cold starts](/serverless-containers/concepts/#cold-start), but fully supports Linux system call interface. Sandbox v1 are known to experience clock drift over time. A difference of approximately **two seconds** can be observed after 24 hours of uninterrupted execution. This issue especially affects long-running containers, whereas short-lived containers are much less impacted. Update to sandbox v2 to solve the issue. From a5285a2d4789a318353ec4c008843d1cb0e2e683 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Mon, 12 May 2025 10:43:23 +0200 Subject: [PATCH 12/14] Update pages/serverless-functions/reference-content/functions-sandbox.mdx Co-authored-by: Thomas TACQUET --- .../reference-content/functions-sandbox.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/serverless-functions/reference-content/functions-sandbox.mdx b/pages/serverless-functions/reference-content/functions-sandbox.mdx index f6d0b3578d..f353c31a49 100644 --- a/pages/serverless-functions/reference-content/functions-sandbox.mdx +++ b/pages/serverless-functions/reference-content/functions-sandbox.mdx @@ -23,7 +23,7 @@ Scaleway Serverless Functions offers two sandbox environment options: ## Sandbox v1 -Sandbox v1 is Serverless Functions' legacy sandboxing environment with slower [cold starts](/serverless-functions/concepts/#cold-start), but fully supports Linux system call interface. This option is recommended when processing large amounts of *syscalls*. +Sandbox v1 is Serverless Functions' legacy sandboxing environment with slower [cold starts](/serverless-functions/concepts/#cold-start), but fully supports Linux system call interface. Sandbox v1 are known to experience clock drift over time. A difference of approximately **two seconds** can be observed after 24 hours of uninterrupted execution. This issue especially affects long-running functions, whereas short-lived functions are much less impacted. Update to sandbox v2 to solve the issue. From be378d47016c4ded8c40a07f487452761b262c0e Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Mon, 12 May 2025 14:14:23 +0200 Subject: [PATCH 13/14] Update pages/serverless-containers/reference-content/containers-limitations.mdx Co-authored-by: Benedikt Rollik --- .../reference-content/containers-limitations.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/serverless-containers/reference-content/containers-limitations.mdx b/pages/serverless-containers/reference-content/containers-limitations.mdx index 045cb932c4..1b2db19df4 100644 --- a/pages/serverless-containers/reference-content/containers-limitations.mdx +++ b/pages/serverless-containers/reference-content/containers-limitations.mdx @@ -23,7 +23,7 @@ This section contains usage limits that apply when using Serverless Containers. | Total container memory\** | Max size | 600 GiB | Organization | | Custom domains | Max number | 50 | Container | | Recommended maximum uncompressed image size | Max size | 1 GB | Container | -| Temporary disk size ¨ | Max size | 24 000 MiB | Container | +| Temporary disk size | Max size | 24 000 MiB | Container | | Invocation rate | Max number | 1000 per second | Container | | Concurrency | Max | 80 | Container Instance | | Max Scale (simultaneous Container instances) | Max | 50 | Container | From 569cda9dba6587e3fd9b5deaf4fc0d3ef74cccce Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Mon, 12 May 2025 14:14:54 +0200 Subject: [PATCH 14/14] Apply suggestions from code review Co-authored-by: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> --- .../reference-content/containers-sandbox.mdx | 2 +- .../reference-content/functions-sandbox.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/serverless-containers/reference-content/containers-sandbox.mdx b/pages/serverless-containers/reference-content/containers-sandbox.mdx index 6aa9724565..65b622c8b2 100644 --- a/pages/serverless-containers/reference-content/containers-sandbox.mdx +++ b/pages/serverless-containers/reference-content/containers-sandbox.mdx @@ -26,7 +26,7 @@ Scaleway Serverless Containers offers two sandbox environment options: Sandbox v1 is Serverless Containers' legacy sandboxing environment with slower [cold starts](/serverless-containers/concepts/#cold-start), but fully supports Linux system call interface. -Sandbox v1 are known to experience clock drift over time. A difference of approximately **two seconds** can be observed after 24 hours of uninterrupted execution. This issue especially affects long-running containers, whereas short-lived containers are much less impacted. Update to sandbox v2 to solve the issue. +Sandbox v1 is known to experience clock drift over time. A difference of approximately **two seconds** can be observed after 24 hours of uninterrupted execution. This issue especially affects long-running containers, whereas short-lived containers are much less impacted. Update to sandbox v2 to solve the issue. ## Sandbox v2 diff --git a/pages/serverless-functions/reference-content/functions-sandbox.mdx b/pages/serverless-functions/reference-content/functions-sandbox.mdx index f353c31a49..988cc85aa2 100644 --- a/pages/serverless-functions/reference-content/functions-sandbox.mdx +++ b/pages/serverless-functions/reference-content/functions-sandbox.mdx @@ -26,7 +26,7 @@ Scaleway Serverless Functions offers two sandbox environment options: Sandbox v1 is Serverless Functions' legacy sandboxing environment with slower [cold starts](/serverless-functions/concepts/#cold-start), but fully supports Linux system call interface. -Sandbox v1 are known to experience clock drift over time. A difference of approximately **two seconds** can be observed after 24 hours of uninterrupted execution. This issue especially affects long-running functions, whereas short-lived functions are much less impacted. Update to sandbox v2 to solve the issue. +Sandbox v1 is known to experience clock drift over time. A difference of approximately **two seconds** can be observed after 24 hours of uninterrupted execution. This issue especially affects long-running functions, whereas short-lived functions are much less impacted. Update to sandbox v2 to solve the issue. ## Sandbox v2