When you deploy applications to Kubernetes clusters through Enterprise Distributed Application Service (EDAS), the container runs the startup command defined in your Dockerfile by default. To override this default -- for example, to pass custom JVM arguments or change the entrypoint binary -- configure a startup command in the EDAS console.
How startup commands map to Docker directives
The EDAS console fields map directly to Docker directives:
| EDAS console field | Docker equivalent | Description |
|---|---|---|
| Startup Command | ENTRYPOINT | The executable that runs when the container starts |
| Startup Parameters | CMD | Arguments passed to the startup command |
The following table describes the override behavior when you set these fields in the EDAS console:
| Configuration | Behavior |
|---|---|
| Startup Command only | Overrides the Dockerfile ENTRYPOINT. The Dockerfile CMD is ignored (not passed as arguments). |
| Startup Parameters only | The Dockerfile ENTRYPOINT runs with the parameters you specified, replacing the Dockerfile CMD. |
| Both fields | Replaces the full ENTRYPOINT + CMD combination from the Dockerfile. |
| Neither field | The container uses the Dockerfile ENTRYPOINT and CMD as-is. |
Because only one ENTRYPOINT takes effect at runtime, the values in the EDAS console always take precedence over the Dockerfile.
If you are unfamiliar with the ENTRYPOINT or CMD directives in your Dockerfile, do not customize the startup command. Invalid commands prevent the application from being created.
Example
Given this Dockerfile:
FROM ubuntu
ENTRYPOINT [nginx, '-g', 'daemon off;']The equivalent EDAS console configuration is:
| Field | Value |
|---|---|
| Startup Command | nginx |
| Startup Parameters | -g (first row), daemon off; (second row) |
To run a complex command that involves pipes or shell features, wrap it in a shell invocation:
| Field | Value |
|---|---|
| Startup Command | /bin/sh |
| Startup Parameters | -c (first row), your-script.sh && echo done (second row) |
Configure a startup command during application creation
Log on to the EDAS console.
In the left-side navigation pane, choose Application Management > Applications.
In the top navigation bar, select a region. In the upper part of the page, select a namespace.
In the upper-left corner, click Create Application.
In the Basic Information step, set Cluster Type to Kubernetes Clusters and select an Application Runtime Environment, then click Next.
Runtime environment When to use Java > Custom Deploy with a custom image Java > Java Deploy a Dubbo or Spring Boot application from a JAR package. Set the Java Environment parameter after selection. Java > Tomcat Deploy a Dubbo or Spring application from a WAR package. Set the Java Environment and Container Version parameters after selection. Java > EDAS-Container (HSF) Deploy a High-speed Service Framework (HSF) application from a WAR or FatJar package. Set the Java Environment, Pandora Version, and Ali-Tomcat Version parameters after selection. PHP Deploy a PHP application on Apache HTTP Server Node.js, C++, Go, and Other Languages Deploy with a custom image. The configuration process for multi-language applications is not described in this topic. In the Configurations step, configure the environment, basic information, deployment method, and resource parameters, then click Next.
In the Advanced Settings step, expand Startup Command and set the following parameters:
Parameter Description Startup Command The executable to run, for example, nginx.Startup Parameters One argument per row. Click Add to add more rows. For example, enter -gin one row anddaemon off;in the next.
Click Create Application.
On the Creation Completed page, review the settings in the Basic Information, Configurations, and Advanced Settings sections, then click Create Application. In the upper part of the Application Overview page, click View Details. On the Change List page, view the application change process. Wait a few minutes for deployment to complete. After the change process is complete, check the instance status in the Basic Information section of the Application Overview page. If a pod is running, the application is deployed.
Configure a startup command for a deployed application
Updating the startup command triggers an application restart. Perform this operation during off-peak hours.
Log on to the EDAS console.
In the left-side navigation pane, choose Application Management > Applications.
In the top navigation bar, select a region. In the upper part of the page, select a namespace.
From the Cluster Type drop-down list, select Container Service or Serverless Kubernetes Cluster.
Click the application name to open its details page.
In the upper-right corner of the Overview or Basic information page, choose Deploy > Deploy.
On the Select Deployment Mode page, select a deployment mode and click Start Deployment.
Specify the deployment package and environment, expand Startup Command, and configure the parameters described in the following table. Then click OK.
Parameter Description Startup Command The executable to run, for example, nginx.Startup Parameters One argument per row. Click Add to add more rows. For example, enter -gin one row anddaemon off;in the next.
The application restarts after you click OK. Perform this operation during off-peak hours.
Verify the result
After deployment completes, confirm the startup command took effect using one of the following methods:
Check change records: In the left-side navigation pane of the application details page, click Change Records. If the Change Status column shows Success, the configuration is applied.
Check pod status: On the Application Overview page, click Running Pods (Click View) next to Running Status. In the Pod section of the App Configurations panel, check the Status column. A green dot indicates the application is running with the new configuration.