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.
Choose Production (default), Staging, or Development to organize a container by deployment environment. You can change its environment in General after creation.
Configure and operate a container
Open Container Engine in your project. If the project has no containers, the Console opens Getting started after checking the resource list. Existing projects open Instances. Use the product sidebar to switch between these views at any time; selecting Instances explicitly keeps the list open even when it is empty. The introduction includes deployment guidance and links to the documentation.
Use the list toolbar to create or refresh resources, and filter or sort the table to find a container. The list uses the available screen width; its count and pagination describe the filtered result.
Select a container to open its detail pages:
- 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, deployment environment, 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.
Next steps
Network traffic
View Network Inbound and Network Outbound in the resource details. See Network traffic for collection intervals, permissions, and how to interpret gaps.
CPU and RAM
The Overview page shows the resource name, image and status above a row of environment, region, plan and capacity details. Start, stop, restart, redeploy and refresh controls appear in the header, which stays visible while scrolling. Available actions depend on the resource state and your permissions.
CPU and RAM charts appear side by side. Below them, network charts and resource details share a row on wide screens. On smaller screens, these sections stack vertically.
Charts include time and value axes. Use the range selector and Refresh in each metric section to inspect history. RAM shows used memory, the configured memory limit, and the percentage used. It excludes inactive file cache. CPU shows usage as a percentage of the configured CPU limit; using one full core of a two-core allocation is 50%.
Select the last hour, six hours, day, or week, and use Refresh to load new samples. Samples are collected approximately once per minute and retained for seven days. Longer ranges show averages. CPU requires two consecutive samples; a line requires two adjacent values. New resources may take a few minutes to show a line. RAM can show a current value before its line is ready.
For resources with several running containers, usage is combined. A combined limit is available only when each container has a configured limit. Missing limits and percentages appear as —. Restarting, redeploying, or changing CPU limits can leave gaps in CPU history; unavailable observations are not zero usage. A stale notice means newer observations are not yet available. Refresh again, or contact support with the resource ID if the notice persists.
Viewing these metrics requires permission to view Container Engine instances. Disk usage is not included.