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.