docs(srv): split troubleshootings into multiple pages MTA-5198

menu/navigation.json

@@ -3703,16 +3703,6 @@
                 "label": "API/CLI",
                 "slug": "api-cli"
               },
-              {
-                "items": [
-                  {
-                    "label": "Common errors",
-                    "slug": "common-errors"
-                  }
-                ],
-                "label": "Troubleshooting",
-                "slug": "troubleshooting"
-              },
               {
                 "items": [
                   {
@@ -3766,6 +3756,40 @@
                 ],
                 "label": "Additional Content",
                 "slug": "reference-content"
+              },
+              {
+                "items": [
+                  {
+                    "label": "Unable to create a namespace",
+                    "slug": "cannot-create-namespace"
+                  },
+                  {
+                    "label": "I cannot inject secrets or variables in my job",
+                    "slug": "cannot-inject-secret-variable"
+                  },
+                  {
+                    "label": "My function is in an error state",
+                    "slug": "function-in-error-state"
+                  },
+                  {
+                    "label": "My function stopped working after a redeploy",
+                    "slug": "function-stopped-after-redeploy"
+                  },
+                  {
+                    "label": "Handler not found",
+                    "slug": "handler-not-found"
+                  },
+                  {
+                    "label": "I am experiencing timeout errors",
+                    "slug": "timeout-error"
+                  },
+                  {
+                    "label": "My function fails after too many retries",
+                    "slug": "too-many-retries"
+                  }
+                ],
+                "label": "Troubleshooting",
+                "slug": "troubleshooting"
               }
             ],
             "label": "Functions",
@@ -3861,16 +3885,6 @@
                 "label": "API/CLI",
                 "slug": "api-cli"
               },
-              {
-                "items": [
-                  {
-                    "label": "Common errors",
-                    "slug": "common-errors"
-                  }
-                ],
-                "label": "Troubleshooting",
-                "slug": "troubleshooting"
-              },
               {
                 "items": [
                   {
@@ -3908,6 +3922,32 @@
                 ],
                 "label": "Additional Content",
                 "slug": "reference-content"
+              },
+              {
+                "items": [
+                  {
+                    "label": "I cannot create a namespace",
+                    "slug": "cannot-create-namespace"
+                  },
+                  {
+                    "label": "I cannot deploy my image",
+                    "slug": "cannot-deploy-image"
+                  },
+                  {
+                    "label": "I cannot inject secrets or variables in my job",
+                    "slug": "cannot-inject-secret-variable"
+                  },
+                  {
+                    "label": "I cannot retrieve external images",
+                    "slug": "cannot-retrieve-external-image"
+                  },
+                  {
+                    "label": "My container stopped working after a redeploy",
+                    "slug": "container-stopped-after-redeploy"
+                  }
+                ],
+                "label": "Troubleshooting",
+                "slug": "troubleshooting"
               }
             ],
             "label": "Containers",
@@ -3965,16 +4005,6 @@
                 "label": "How to",
                 "slug": "how-to"
               },
-              {
-                "items": [
-                  {
-                    "label": "Common errors",
-                    "slug": "common-errors"
-                  }
-                ],
-                "label": "Troubleshooting",
-                "slug": "troubleshooting"
-              },
               {
                 "items": [
                   {
@@ -4006,6 +4036,24 @@
                 ],
                 "label": "Additional Content",
                 "slug": "reference-content"
+              },
+              {
+                "items": [
+                  {
+                    "label": "My job is in an error state",
+                    "slug": "job-in-error-state"
+                  },
+                  {
+                    "label": "I cannot inject secrets or variables in my job",
+                    "slug": "cannot-inject-secret-variable"
+                  },
+                  {
+                    "label": "I cannot retrieve external images",
+                    "slug": "cannot-retrieve-external-image"
+                  }
+                ],
+                "label": "Troubleshooting",
+                "slug": "troubleshooting"
               }
             ],
             "label": "Jobs",

serverless/containers/troubleshooting/cannot-create-namespace.mdx

@@ -0,0 +1,30 @@
+---
+meta:
+  title: I am unable to create a Serverless Containers namespace
+  description: Troubleshoot problems encountered while creating namespaces for Scaleway Serverless Containers.
+content:
+  h1: I am unable to create a Serverless Containers namespace
+  paragraph: Troubleshoot problems encountered while creating namespaces for Scaleway Serverless Containers.
+tags: serverless Containers troubleshooting issue error namespace creation unable
+dates:
+  validation: 2024-11-06
+  posted: 2024-11-06
+categories:
+  - serverless
+---
+
+## Problem
+
+I cannot create a Serverless Containers namespace.
+
+### Cause
+
+This issue can happen for the following reasons:
+
+- You have created too many namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-containers).
+
+- You have created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry).
+
+### Possible solutions
+
+Make sure that you have not exceeded the maximum number of allowed namespaces with the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-containers/#path-namespaces-list-all-your-namespaces).

serverless/containers/troubleshooting/cannot-deploy-image.mdx

@@ -0,0 +1,37 @@
+---
+meta:
+  title: I am unable to deploy my image
+  description: Troubleshoot errors encountered while deploying images with Scaleway Serverless Containers.
+content:
+  h1: I am unable to deploy my image
+  paragraph: Troubleshoot errors encountered while deploying images with Scaleway Serverless Containers.
+tags: serverless containers troubleshooting issue error message deploy image failed
+dates:
+  validation: 2024-11-07
+  posted: 2024-11-07
+categories:
+  - serveless
+---
+
+## Problem
+
+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 bound to `0.0.0.0`.
+
+- Containers cannot start due to insufficient provisioned resources. Update your container's resources by provisioning more memory and more vCPU.
+
+- Make sure you have built your image for an `amd64` architecture, as `arm64` is not supported. See the [Architecture](/serverless/containers/reference-content/containers-limitations/#Architecture) documentation for more information.
+
+- Make sure your deployment does not exceed the limitations of [Serverless Containers](/serverless/containers/reference-content/containers-limitations/).
+
+  <Message type="tip">
+    Run the [`docker inspect`](https://docs.docker.com/engine/reference/commandline/inspect/) command to get detailed information on your image:
+    ```
+    docker inspect myimage
+    ```
+  </Message>

serverless/containers/troubleshooting/cannot-inject-secret-variable.mdx

@@ -0,0 +1,33 @@
+---
+meta:
+  title: My secrets and variables are not injected properly in my container
+  description: Troubleshoot issues with secrets and environment variables while using Scaleway Serverless Containers.
+content:
+  h1: My secrets and variables are not injected properly in my container
+  paragraph: Troubleshoot issues with secrets and environment variables while using Scaleway Serverless Containers.
+tags: serverless containers troubleshooting issue error image env var environment variables secrets secret manager
+dates:
+  validation: 2024-11-06
+  posted: 2024-11-06
+categories:
+  - serverless
+---
+
+## Problem
+
+My environment variables and secrets are not properly injected in my Serverless Container.
+
+## Cause
+
+Environment variables or secrets that are too large, contain carriage returns and spread over several lines, as shown below, will not be injected properly.
+
+```
+"hello
+world
+.
+"
+```
+
+### Solution 
+
+To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`.

serverless/containers/troubleshooting/cannot-retrieve-external-image.mdx

@@ -0,0 +1,28 @@
+---
+meta:
+  title: I am unable to retrieve an external image for my container
+  description: Troubleshoot errors while retrieving external images while using Scaleway Serverless Containers.
+content:
+  h1: I am unable to retrieve an external image for my container
+  paragraph: Troubleshoot errors while retrieving external images while using Scaleway Serverless Containers.
+tags: serverless containers troubleshooting issue error image retrieve external public registry
+dates:
+  validation: 2024-11-06
+  posted: 2024-11-06
+categories:
+  - serverless
+---
+
+## Problem
+
+I am experiencing issues when retrieving an image stored in an external container registry.
+
+## Cause
+
+Serverless products support external public registries (such as [Docker Hub](https://hub.docker.com/)), but we do not recommend using them due to uncontrolled rate limiting, which can lead to failures when starting resources, unexpected usage conditions, and pricing changes.
+
+## Solution
+
+We recommend using the [Scaleway Container Registry](/containers/container-registry/) instead, as it allows for a seamless integration with Serverless Containers and Containers at a [competitive price](/faq/containerregistry/#how-am-i-billed-for-scaleway-container-registry).
+
+Refer to the [dedicated documentation](/serverless/containers/api-cli/migrate-external-image-to-scaleway-registry/) for more information on how to migrate images to the Scaleway Container Registry. 

serverless/containers/troubleshooting/container-stopped-after-redeploy.mdx

@@ -0,0 +1,26 @@
+---
+meta:
+  title: My container stopped working after a redeploy
+  description: Troubleshoot issues with Scaleway Serverless Containers not working properly following a redeploy.
+content:
+  h1: My container stopped working after a redeploy
+  paragraph: Troubleshoot issues with Scaleway Serverless Containers not working properly following a redeploy.
+tags: serverless containers troubleshooting issue error state failed fail redeploy
+dates:
+  validation: 2024-11-06
+  posted: 2024-11-06
+categories:
+  - serverless
+---
+
+## Problem
+
+My Serverless Container stopped working (up to several hours) after a redeploy.
+
+## Cause
+
+The new deploy failed, and the [fallback mechanism has been triggered](/serverless/containers/reference-content/containers-limitations/#versioning-and-rollback).
+
+## Possible solution
+
+Identify the element that caused the deployment to fail, fix the error, and deploy the container again.