How to deploy a container
This page shows you how to deploy your first Serverless Container. A container is a package of software that includes all dependencies: code, runtime, configuration, and system libraries so that it can run on any host system. This allows you to control your production environment. Scaleway provides you with custom Docker images that are entirely handled for you in the cloud. With Serverless Containers, you can rely on your favorite technologies such as Django or Ruby On Rails.
- Click Containers in the Serverless section of the side menu. The containers page displays.
- Click the relevant containers namespace.
- Click Deploy a Container. The container creation wizard displays.
- Complete the following steps in the wizard:
- Choose an image from your Container Registry. Select the required Container Registry namespace from the dropdown list, and then select the container and tag.
- Choose a name for your container, and optionally a description. The name must only contain alphanumeric characters.
- Choose the Port your container is listening on. We recommend configuring your container to listen on the PORT environment variable.
- Choose the resources to be allocated to your container at runtime. These define the performance characteristics of your container.
- Set your scaling preferences, or leave them at default values. The Scaleway platform autoscales the number of available instances of your container to match the incoming load, depending on the settings you define here.
- Define any environment variables you want to inject into your container. For each environment variable, click +Add and enter the key/value pair.
- Set secret environment variables (optional). Secrets are environment variables which are injected into your container and stored securely, but not displayed in the console after initial validation. Add a key and a value.
- Optionally, use the advanced options to add triggers to your container deployment. Adding triggers enables the container to handle events coming from sources other than an HTTP endpoint, such as CRON (time-based jobs), MQTT queues and more.
- Verify the estimated cost.
- Click Deploy a container to finish.