Skip to main content
This page summarizes common runtime settings used when deploying with Air Container.

Supported registries

  • GCP Artifact Registry
  • AWS ECR
  • GitHub Container Registry
  • Docker Hub
Private registries require authentication.

Common configuration fields

Start command

The command used to start the container process.

Port

The port your service listens on for external requests.

Health check URL

A path used to verify the container is healthy.

Metrics path

The path your application exposes metrics on, for example /metrics.

Health check timeout

How long to wait for a health check response. Default: 300 seconds.

Startup timeout

The maximum time allowed for the container to start successfully. Default: 600 seconds.

Environment variables

Key-value configuration required by your application. AirCloud also injects AIRCLOUD_AUTHORIZED_KEYS at deploy time, containing the SSH public keys registered for the container. See Connect with SSH.

Shared memory (/dev/shm)

The size of /dev/shm, for workloads that use shared memory such as a PyTorch DataLoader. Off by default, in which case half the instance memory applies. When set, it can range from 1 GB up to the instance’s memory size.

Container ID

The container’s identifier. Generated automatically, but you can set a fixed slug (lowercase letters, numbers, and hyphens). It becomes part of the container’s public URL.

Public URL

Deployed containers are served at https://ap-1.aieev.cloud/endpoints/<container-id>. The create form previews the URL as you edit the container ID.

Operational recommendations

  • Manage public vs. private registry settings explicitly
  • Validate ports and health check paths before deployment
  • Re-check production environment variables before deploying
  • After changes, review logs and usage together

Deploy a Container

Deployment flow and configuration steps.

Monitoring

What to check in Usage, Logs, and Settings.