docs(srv): update

Author: SamyOubouaziz

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*.
 
+<Message type="important">
+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.
+</Message>
+
 ## 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.

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.