Skip to content

Commit d334889

Browse files
committed
docs(srv): update
1 parent 8e6f4be commit d334889

File tree

3 files changed

+78
-0
lines changed

3 files changed

+78
-0
lines changed

menu/navigation.json

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3781,6 +3781,10 @@
37813781
{
37823782
"label": "My function fails after too many retries",
37833783
"slug": "too-many-retries"
3784+
},
3785+
{
3786+
"label": "Tests fail on private functions",
3787+
"slug": "tests-fail-on-private-function"
37843788
}
37853789
],
37863790
"label": "Troubleshooting",
@@ -3838,6 +3842,10 @@
38383842
"label": "Secure a container",
38393843
"slug": "secure-a-container"
38403844
},
3845+
{
3846+
"label": "Test a container",
3847+
"slug": "test-a-container"
3848+
},
38413849
{
38423850
"label": "Monitor container logs and metrics",
38433851
"slug": "monitor-container"
@@ -3939,6 +3947,10 @@
39393947
{
39403948
"label": "My container stopped working after a redeploy",
39413949
"slug": "container-stopped-after-redeploy"
3950+
},
3951+
{
3952+
"label": "Tests fail on private containers",
3953+
"slug": "tests-fail-on-ùprivate-container"
39423954
}
39433955
],
39443956
"label": "Troubleshooting",
Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
---
2+
meta:
3+
title: How to test a container
4+
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+
<Macro id="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.
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
meta:
3+
title: Tests fail on private Serverless Containers
4+
description: I get error messages when testing private Serverless Containers using the Scaleway Console
5+
content:
6+
h1: Tests fail on private Serverless Containers
7+
paragraph: I get error messages when testing private Serverless Containers using the Scaleway Console
8+
tags: serverless containers private troubleshooting issue error test authentication token unable
9+
dates:
10+
validation: 2025-01-14
11+
posted: 2025-01-14
12+
categories:
13+
- serverless
14+
---
15+
16+
## Problem
17+
18+
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

Comments
 (0)