Container Engine overview
Run a single-container application from an image in your RDC Cloud project.
Container Engine lets you deploy an application from a container image, select a region and resource plan, and manage its configuration in the Console.
How deployment works
Choose an external image or an image from your project's Artifact Registry. Configure the application's internal HTTP port and any environment variables before deployment. You can also set a command, entrypoint, working directory, and persistent volume mount paths when creating the resource.
Each new resource runs one application container. The creation flow does not accept Docker Compose definitions, additional services, host port mappings, host bind mounts, or arbitrary Docker options.
The resource plan specifies CPU and memory capacity. CPU is shared; the displayed vCPU amount is a usage limit, not a dedicated core allocation. Available regions, plans, and prices are shown in the Console.
Configure and operate a container
Open Container Engine in your project and select a container. Its detail pages provide:
- Overview for resource and runtime status.
- Deployments and Runtime Log for deployment progress and application output.
- Environment for environment variables.
- Network, Firewall Policy, and Domain & DNS for connectivity.
- Healthcheck for supported health check settings.
- General for names, descriptions, and supported image settings.
- Danger Zone for deletion.
Settings available for imported resources can differ from those available for newly created applications. An accepted operation does not mean that the application is ready; inspect the deployment and runtime status afterward.