You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Instructions for testing your Serverless Containers on Scaleway.
5
+
content:
6
+
h1: How to test a container
7
+
paragraph: Instructions for testing your Serverless Containers on Scaleway.
8
+
tags: container serverless test-container
9
+
dates:
10
+
validation: 2025-01-14
11
+
posted: 2025-01-15
12
+
categories:
13
+
- serverless
14
+
---
15
+
16
+
This page shows you how to execute Serverless Containers from the [Scaleway console](https://console.scaleway.com). The **Test** feature of a container allows you to run your code using a selection of methods to make sure it behaves as expected.
17
+
18
+
<Macroid="requirements" />
19
+
20
+
- A Scaleway account logged into the [console](https://console.scaleway.com)
21
+
-[Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization
22
+
-[Created a container](/serverless/containers/how-to/deploy-container/)
23
+
24
+
1. Click **Containers** in the **Serverless** section of the side menu. The containers page displays.
25
+
26
+
2. Click the relevant containers namespace. A list of your containers displays.
27
+
28
+
3. Click the name of the container you want to test.
29
+
30
+
4. Open the **Test** tab.
31
+
32
+
5. Select the **method** you want to use from the drop-down menu.
33
+
34
+
6. Enter the **path** to your container. Leave the default `/` value if the host of your container is not located in a specific folder.
35
+
36
+
7. Click **+ Advanced options** to add any required HTTP header or parameter to your container.
37
+
38
+
8. Click **Run**.
39
+
40
+
The **Output** section displays the response from your container and the status code.
I get error messages when testing private Serverless Containers using the Scaleway Console.
19
+
20
+
### Cause
21
+
22
+
[Private](/serverless/containers/concepts/#privacy-policy) containers require a `X-Auth-Token` HTTP header when being run or tested.
23
+
24
+
### Possible solutions
25
+
26
+
Make sure that you have [created an authentication token](/serverless/containers/how-to/create-auth-token-from-console/) from the Scaleway console, and passed it as a HTTP header while [testing your container](/serverless/containers/how-to/test-a-container).
0 commit comments