Use a custom image to create a tailored build environment-Alibaba Cloud DevOps(Alibaba Cloud DevOps)-阿里云帮助中心

If the pre-configured build environments in Flow do not meet your requirements, you can create a custom image to tailor your build environment.

Create a custom image

Write a Dockerfile for your build environment to install required software and set environment variables. Here is an example:

FROM registry.cn-beijing.aliyuncs.com/rdc-builds/base:1.0   
RUN cd /tmp && \    
   wget http://rdc-public-software.oss-cn-hangzhou.aliyuncs.com/jdk-7u80-linux-x64.tar.gz && \ 
   mkdir -p /srv/java && \    
   tar xf jdk-7u80-linux-x64.tar.gz -C /srv/java && \    
   ln -s /srv/java/jdk* /srv/java/jdk 
ENV JAVA_HOME=/srv/java/jdk \    
    PATH=${PATH}:/srv/java/jdk/bin:/srv/java

Note

If you do not use registry.cn-beijing.aliyuncs.com/rdc-builds/base:1.0 as your base image, make sure that your image includes jq and bash, and that the default user is root.

Build your custom image, debug it in your local environment, and then push the image to Alibaba Cloud Container Registry or another publicly accessible registry.
```
docker build -t myimage:latest -f /path/to/a/Dockerfile .
```
Note
This command builds an image. You can customize the image name myimage and the tag latest. The . specifies the context path. If you run the command from the same directory as the Dockerfile, you can omit the -f option, which specifies the path to the Dockerfile.
Run the following command to verify that a container starts correctly from the image. If successful, you can use the image in the Flow build environment.
```
docker run -w /root/workspace --entrypoint=/bin/bash -it $image
```

Configure a custom image build node

In Pipeline Orchestration, configure a custom image build node.
Enter your custom image address and build command. If you are using a private image, you must also provide authentication credentials.

Troubleshooting: "Failed to pull image" error

Verify that the image exists in the private repository.
Verify that the service connection or authentication key is correct.

Troubleshooting: No run logs for the build step

Verify that jq is installed in the private image.
Ensure that the default user for the private image is root.