Configure runtime settings
Set a command, entrypoint, and working directory when creating a container.
Runtime overrides are creation-time settings. Leave a field empty to preserve the corresponding image default. Use an image that contains the executable and working directory you specify.
Set the command and entrypoint
In Create resource, enter the command and its arguments in Command. Use Entrypoint only when you need to replace the image's entrypoint.
The Console splits command-line text into executable arguments. Quotes keep an argument containing spaces together. For example:
node server.js --message "Hello from RDC Cloud"No shell is started automatically. Variable expansion, pipes, and redirection are not evaluated by the command parser. If your application explicitly requires a shell, the image must contain it. For example, set Entrypoint to /bin/sh and Command to:
-c 'exec node server.js'Do not apply these shell instructions to health check commands, which have separate restrictions.
Set the working directory
Enter an absolute container path such as /app in Working directory. The path refers to the container filesystem, not the host server. Supported path characters are letters, numbers, underscores, hyphens, dots, and path separators.
Limits and verification
Command and entrypoint each accept up to 100 arguments, with at most 4,096 characters per argument. The working directory accepts at most 512 characters.
After creation, inspect Deployments and Runtime Log to confirm that the process starts successfully. The current Console does not expose these runtime overrides for editing after creation.
Change CPU and memory
Open the container's General settings and choose Change plan. Select an available plan for the current server, compare CPU, memory and hourly price, then choose Apply changes.
Plan changes are available for running managed applications with an assigned plan. You need both update and deployment permissions, an active billing account and available credit. Imported resources without a plan and Compose services are not supported by this action.
Applying a plan changes CPU and memory limits on the running container without restarting or recreating it. Container files, runtime environment values and persistent volumes remain in place. This action does not resize storage or move the application to another server. Separately redeploying or replacing the container can still discard files outside persistent storage.
Before reducing memory, RDC checks current usage with safety headroom. If the smaller plan cannot accommodate it, reduce memory usage or select a larger plan. This check cannot prevent later workload growth from exhausting the new limit.
The existing rate remains in effect until the plan change is verified. While a change is running, wait for its result before requesting another lifecycle operation. If the new plan is rejected before applying changes, the current plan remains unchanged and you can try another plan. If verification is required, contact support with the resource ID; CPU and memory limits may already have changed even if the operation has not finished.