Skip to content

Commit

Permalink
add healthcheck notice
Browse files Browse the repository at this point in the history
  • Loading branch information
thomas-tacquet committed Jun 27, 2024
1 parent ecb36cc commit 8741dd3
Showing 1 changed file with 6 additions and 1 deletion.
7 changes: 6 additions & 1 deletion faq/serverless-containers.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -98,4 +98,9 @@ Protocol switching is currently not available in the console but can be changed

## Why does my gRPC container not respond?

Containers use http1 by default, yet the gRPC protocol requires http2. You can upgrade the protocol to http2 (`h2c`).
Containers use http1 by default, yet the gRPC protocol requires http2. You can upgrade the protocol to http2 (`h2c`).

## How does Serverless Container healthcheck work ?

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 DB), it's important to run them before binding to the port (starting the webserver).
For now, the `HEALTHCHECK` Docker directive has no impact on container readiness. In the future, the healthcheck will be customizable for your applications.

0 comments on commit 8741dd3

Please sign in to comment.