Enterprise Distributed Application Service:Create an application image

HSF applications

HSF applications require an Ali-Tomcat base image with the Pandora middleware container.

# Base: CentOS 7 + OpenJDK 8 + Ali-Tomcat 7 + Pandora 3.5.9
FROM apaas-registry.cn-hangzhou.cr.aliyuncs.com/apaas/edas-centos-openjdk8-alitomcat7:latest
MAINTAINER Alibaba Cloud EDAS Team<edas-**@list.alibaba-inc.com>

ENV TZ="Asia/Shanghai"

# Application directory inside the container
ENV APP_HOME /home/admin/app/

##### Deploy a JAR file (default)
ARG APP_LOCATION=https://edas-hz.oss-cn-hangzhou.aliyuncs.com/prod/demo/HSF_PROVIDER.jar

##### Deploy a WAR file -- uncomment the line below and comment out the JAR line
#ARG APP_LOCATION=https://edas-hz.oss-cn-hangzhou.aliyuncs.com/prod/demo/HSF_PROVIDER.war

##### Deploy from local storage -- uncomment and set the path to your local file
#ARG APP_LOCATION=/path/to/your/HSF_PROVIDER.war

# Copy the application package into the container
ADD ${APP_LOCATION} ${APP_HOME}/

# The startup script and working directory are provided by the base image.
# Entry point: /home/admin/bin/start.sh
# Working directory: /home/admin

Spring Cloud or Dubbo applications

Spring Cloud and Dubbo applications use the standard EDAS base image (without Pandora).

# Base: CentOS 7 + OpenJDK 8 + Tomcat 8
FROM apaas-registry.cn-hangzhou.cr.aliyuncs.com/apaas/edas:latest

# Application directory inside the container
ENV APP_HOME /home/admin/app/

##### Deploy a JAR file (default)
ARG APP_LOCATION=https://edas-hz.oss-cn-hangzhou.aliyuncs.com/prod/demo/DUBBO_PROVIDER.jar

##### Deploy a WAR file -- uncomment the line below and comment out the JAR line
#ARG APP_LOCATION=https://edas-hz.oss-cn-hangzhou.aliyuncs.com/prod/demo/DUBBO_PROVIDER.war

##### Deploy from local storage -- uncomment and set the path to your local file
#ARG APP_LOCATION=/path/to/your/SPRING_CLOUD_PROVIDER.war

# Copy the application package into the container
ADD ${APP_LOCATION} ${APP_HOME}/

Upgrade OpenJDK

Install a newer JDK version directly in the Dockerfile. EDAS supports up to OpenJDK 21 for custom images.

The following example replaces the pre-installed OpenJDK 8 with OpenJDK 9:

# Remove the pre-installed JDK and install OpenJDK 9
RUN yum erase -y java; yum -y install java-1.9.0-openjdk-devel

Upgrade the EDAS Container version (HSF only)

For HSF applications in ACK clusters, upgrade the Pandora and Ali-Tomcat versions to access new middleware features or fixes.

1. Log on to the EDAS console.

2. In the left-side navigation pane, choose Application Management > Applications.

3. On the Applications page, click Create Application. In the Application Runtime Environment section of the Basic Information step, find the available Pandora Version and Ali-Tomcat Version values.

4. Set the target version in the Dockerfile. For example, to upgrade to Pandora 3.5.4:

       # Upgrade the Pandora version
       ENV UPGRADED_CONTAINER_VERSION 3.5.4
       RUN /home/admin/bin/upgradecontainer.sh

5. Rebuild and push the image.

Set JVM startup parameters

Pass JVM parameters through the JAVA_OPTS environment variable:

FROM apaas-registry.cn-hangzhou.cr.aliyuncs.com/apaas/edas:latest

# Set JVM memory parameters
ENV JAVA_OPTS="\
     -Xmx3550m \
     -Xms3550m \
     -Xmn2g \
     -Xss128k"

Configure Spring Boot settings

For FatJar applications, modify Tomcat startup settings through the APP_ARGS environment variable. The base image uses the following defaults:

Override these defaults as needed:

FROM apaas-registry.cn-hangzhou.cr.aliyuncs.com/apaas/edas:latest

# Override Spring Boot defaults
ENV APP_ARGS="--server.context-path=/  \
              --server.tomcat.uri-encoding=ISO-8859-1 \
              --server.port=8080 \
              --server.tomcat.max-threads=400"

Build the image

1. Open a terminal and navigate to the directory that contains your Dockerfile.

2. Run docker build to create the image: Example: If your Dockerfile has a non-default name or location, specify it with the -f flag:

       docker build -t <app-name>:<version> .

       docker build -t hsf-provider:1.0.0 .

       docker build -t hsf-provider:1.0.0 -f /path/to/custom_dockerfile .

3. Verify that the image was created:

       docker images | grep hsf-provider

Push the image to Container Registry

After you build the image, push it to Alibaba Cloud Container Registry.

# Step 1: Log in to Container Registry
# Enter the fixed or temporary password for the default instance in Container Registry, not your Alibaba Cloud account password.
docker login --username=<username> registry.<region-id>.aliyuncs.com

# Step 2: Tag the image
docker tag <image-id> registry.<region-id>.aliyuncs.com/<namespace>/<repository>:<version>

# Step 3: Push the image
docker push registry.<region-id>.aliyuncs.com/<namespace>/<repository>:<version>

docker login --username=td****@gmail.com registry.cn-hangzhou.aliyuncs.com
docker tag 2b64f63601a7 registry.cn-hangzhou.aliyuncs.com/webapps/hsf-provider:1.0.0
docker push registry.cn-hangzhou.aliyuncs.com/webapps/hsf-provider:1.0.0

Service configuration variables

Application runtime variables