Skip to content

docs(srv): remove sandbox limitation for VPC MTA-6287 #5279

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 16, 2025
Merged

docs(srv): remove sandbox limitation for VPC MTA-6287 #5279

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions pages/serverless-containers/reference-content/containers-limitations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,7 @@ Do not have your containers listen on these ports, as they are used by our servi
* 9091

### Reserved environment variables

* `PORT`: Value of the port defined in the Container settings, which the container has to listen on. You can use this environment variable inside your Container for easier deployments.
* `SCW_*`: Reserved for product configuration (for example: token validation)

Expand All @@ -92,11 +93,9 @@ Scaleway Serverless Containers support [Virtual Private Cloud (VPC)](/vpc/) and

### Limitations

- VPC is only compatible with containers using [sandbox](/serverless-containers/reference-content/container-sandbox/) V1 for the moment.

- VPC works with Namespaces that have **VPC support enabled**. VPC support can only be enabled at [namespace creation](/serverless-functions/how-to/create-manage-delete-containers-namespace/#creating-a-serverless-containers-namespace), and cannot be updated afterward.
- VPC works with Namespaces that have **VPC support enabled**. VPC support can only be enabled at [namespace creation](/serverless-containers/how-to/create-manage-delete-containers-namespace/#creating-a-serverless-containers-namespace), and cannot be updated afterward.

- Only one Private Network can be attached to a function.
- Only one Private Network can be attached to a container.

## Default values for CPU and memory limits

Expand Down
2 changes: 0 additions & 2 deletions pages/serverless-functions/reference-content/functions-limitations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,8 +72,6 @@ Scaleway Serverless Functions support [Virtual Private Cloud (VPC)](/vpc/) and c

### Limitations

- VPC is only compatible with functions using [sandbox](/serverless-functions/reference-content/functions-sandbox/) V1 for the moment.

- VPC works with Namespaces that have **VPC support enabled**. VPC support can only be enabled at [namespace creation](/serverless-functions/how-to/create-manage-delete-functions-namespace/#creating-a-serverless-functions-namespace), and cannot be updated afterward.

- Only one Private Network can be attached to a function.
Expand Down