Deploy a container

This guide deploys a single-container HTTP application using the RDC Cloud Console.

Before you beginCopy Anchor Link

• Sign in and select a workspace and project you can access.
• Ensure the project has an active billing account with positive, unexpired credits.
• Prepare a container image and identify the HTTP port on which its application listens.
• Determine the environment variables and persistent storage paths the application requires.

Create the resourceCopy Anchor Link

1. Open Container Engine in the selected project, then choose Create resource.
2. Enter a Resource name, choose a Deployment environment (Production by default), select a Region, and choose a Resource plan. Review its CPU, memory, and displayed price.
3. Select an image source. For External image, enter the Docker image name and Image tag. For Artifact Registry, select a repository and image version from this project.
4. Leave Command, Entrypoint, and Working directory empty to use the image defaults. Otherwise, follow Configure runtime settings.
5. Enter any persistent volume mount paths.
6. Set Internal HTTP port to the port the application listens on. Add the required environment variables.
7. Review the resource summary and submit the creation form.

For a basic web server example, use nginx as the image name, alpine as the tag, and 80 as the internal HTTP port. Leave runtime overrides empty. The tag identifies a mutable image version; use an explicit release tag or an Artifact Registry digest when you need a reproducible deployment.

Environment variables and the selected internal port are configured before the initial deployment starts. After the request succeeds, the Console returns to the container list.

Deployment environmentCopy Anchor Link

Use Deployment environment to organize containers as Production, Staging, or Development. New containers default to Production. Review the selected environment in Summary before creating the resource.

The environment is displayed in the resource list and details. Existing containers retain their current environment until you change it.

Change an existing container's environmentCopy Anchor Link

1. Open the container in Container Engine.
2. Select General.
3. Choose production, staging, or development in Deployment environment.
4. Save your changes and confirm the updated environment.

The container stays in the same project and is not recreated or restarted. Changing this setting does not set runtime variables such as NODE_ENV; configure those on the Environment page. Shared variables associated with the selected environment apply on the next deployment.

If the change cannot be savedCopy Anchor Link

Wait for any ongoing resource operation to finish before changing the environment. If the instance is unavailable, only the settings currently available in Console can be edited.

If saving fails, refresh the resource and check its current environment before retrying. Other settings submitted together may already have been applied. If the error persists, contact support with the resource ID and displayed error.

Verify the deploymentCopy Anchor Link

1. Open the new container and check Overview for its runtime status.
2. Open Deployments and inspect the latest deployment and its logs.
3. Open Domain & DNS and find the default domain.
4. Open that hostname over HTTPS and verify that the application responds.

If the resource appears in the list but does not respond, check Troubleshoot containers. Resource creation and application readiness are separate steps.

Next stepsCopy Anchor Link

Connect a custom domain or configure a firewall policy. To remove a test resource, follow Delete a container.

Plan availabilityCopy Anchor Link

Plans are specific to Container Engine. A plan with the same name in another RDC Cloud product can have different capacity or pricing. Review the plan offered for the selected region. If a previously selected plan is no longer available, refresh the creation page and select an available plan again.

Workspace availabilityCopy Anchor Link

The selected workspace determines which regions and plans you can choose. A plan must also be available in the selected region. If an option disappears before you submit, refresh the page and choose an available option. Contact support if your workspace needs access to an unavailable option.

Changes to availability do not delete existing resources or prevent you from viewing, stopping, or deleting them. Changing a container plan requires a plan currently available to the workspace in that region.