Skip to content

Commit 80a7649

Browse files
committed
docs(srv): update
1 parent 7b3c684 commit 80a7649

File tree

1 file changed

+13
-3
lines changed

1 file changed

+13
-3
lines changed

pages/serverless-containers/faq.mdx

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -139,6 +139,12 @@ Ensure that your code avoids heavy computations or long-running initialization a
139139

140140
* **Use sandbox v2**: We recommend you use sandbox v2 (advanced settings) to reduce cold starts.
141141

142+
### Which Linux syscalls are supported?
143+
144+
- [Sandbox](/serverless-containers/concepts/#sandbox) v1 guarantees a full compatibility with Linux syscalls.
145+
146+
- [Sandbox](/serverless-containers/concepts/#sandbox) v2 relies on [gVisor](https://gvisor.dev/), which implements a selection of syscalls. Refer to the [official gVisor documentation](https://gvisor.dev/docs/user_guide/compatibility/linux/amd64/) for a comprehensive list of supported syscalls.
147+
142148
### What are the limitations of Serverless Containers?
143149

144150
Refer to our dedicated page about [Serverless Containers limitations and configuration restrictions](/serverless-containers/reference-content/containers-limitations/) for more information.
@@ -171,9 +177,13 @@ You can copy an image from an external registry using the Docker CLI, or open so
171177
A Serverless Container is set to `ready` once the specified port is correctly bound to the container, and will start receiving traffic. If your application needs to perform some tasks before receiving traffic (e.g. connect to a database), it is important to run them before binding to the port (starting the webserver).
172178
For now, the `HEALTHCHECK` Docker directive has no impact on container readiness. In the future, the health check will be customizable for your applications.
173179

174-
### How can I make my application compatible with Google Cloud Run ?
180+
### How can I make my application compatible with Serverless Containers ?
181+
182+
You can make your application compatible with Serverless Containers by:
183+
184+
- listening on port 0.0.0.0
185+
- responding to HTTP or gRPC requests.
175186

176-
You can make your application compatible with Cloud Run using **http2¨¨** and gRPC.
177187
## Features
178188

179189
## Network and storage
@@ -204,7 +214,7 @@ To add network restrictions on your resource, refer to the [list of prefixes use
204214

205215
### Can I use my own TLS certificates?
206216

207-
No.
217+
No, you cannot use your own TLS certificates.
208218

209219
### Can I connect to my container using SSH?
210220

0 commit comments

Comments
 (0)