Container Run Configuration

The CMD / Entry Point tab controls which command is executed when a custom container starts. It can define the main startup command, additional parameters, or both, depending on the configuration provided by the container image.

In this article

Run configuration overview
Entry Point
Run Command
Reset to default values
Expected result

Run Configuration Overview

Open the settings of the required container layer and select the CMD / Entry Point tab. This section contains two fields that determine how the container is launched.

Entry PointDefines the command that is executed when the container starts.

Run CommandDefines the main startup command or additional parameters, depending on whether an Entry Point is specified.

Entry Point

The Entry Point field specifies the executable or command that should be launched when the container starts.

/usr/local/bin/start-application

Use this field when the image requires a specific startup executable, script, or process that differs from the image default.

Run Command

The behavior of the Run Command field depends on whether an Entry Point has been configured.

No Entry PointThe Run Command becomes the command executed when the container launches.

Entry Point definedThe Run Command is passed as one or more additional parameters to the Entry Point command.

Example without an Entry Point

npm start

In this case, the container runs npm start directly during launch.

Example with an Entry Point

Entry Point: /usr/bin/python3 Run Command: /app/main.py –production

The platform executes the Entry Point and appends the Run Command as arguments.

A startup option is required

If the container image does not define a default run command or entry point, you must provide the appropriate startup configuration manually. Otherwise, no application or service will start when the container launches.

Reset to Default Values

After entering a custom value in the Entry Point or Run Command field, a reverse-arrow icon appears beside the modified field.

Click this icon to remove the custom value and restore the startup option provided by the original container image.

✓

Use image defaults where possible

Restore the default settings when the container image already provides a tested startup command and no customization is required.

Expected Result

The container starts using the configured Entry Point and Run Command. The required application or service is launched automatically each time the container is created, restarted, redeployed, or scaled.

Important Notes

Review the container image documentation before overriding its default startup settings.
Use the full executable or script path when the command is not available through the container PATH.
When an Entry Point is defined, the Run Command is treated as an argument or parameter list.
An incorrect command can prevent the container from starting its application.
Use the reset icon to return to the image-defined default values.
Verify that required files, permissions and environment variables are available before applying a custom command.

Common Issues and Solutions

Container starts but the application does not runConfirm that the image contains a default startup command or manually define the correct Entry Point or Run Command.

Command not foundUse the complete path to the executable and verify that it exists inside the container.

Arguments are ignoredCheck whether the Entry Point is defined. When it is present, place additional parameters in the Run Command field.

Container enters a restart loopReview the startup command syntax, file permissions, required variables and application logs.

Default behavior is required againClick the reverse-arrow icon beside the modified field to restore the original image value.