chore(cli): reduce the docker image size

[ysfscream]

PR Checklist

If you have any questions, you can refer to the Contributing Guide

What is the current behavior?

Please describe the current behavior and link to a relevant issue.

Issue Number

Example: #123

What is the new behavior?

This Dockerfile incorporates several common practices to optimize the image size and reduce the final image's overall size:

1. Multi-stage builds: It uses multiple build stages (build and runtime) to separate the build process from the final runtime image. The build stage is responsible for compiling and building the application, while only necessary files are copied from it to the runtime stage. This helps to avoid including build tools and dependencies in the final image, resulting in a smaller image size.

2. Lightweight base image: The Dockerfile selects node:16-alpine as the base image. The Alpine version of the Node.js image is relatively smaller. Alpine Linux is a lightweight Linux distribution that provides the required functionality while keeping the image size minimal.

3. Avoid unnecessary file copying: Only the necessary files are copied from the build stage to the final runtime stage. By copying only the required files, redundant content is minimized, reducing the overall size of the image.

4. Use of --frozen-lockfile flag: The yarn --frozen-lockfile command is used in the build stage to install dependencies. This flag ensures that the versions specified in the lockfile (yarn.lock) remain frozen, providing better reproducibility of the build.

By implementing these optimization techniques, the Dockerfile effectively reduces the image size, resulting in more efficient image building and deployment processes.

Please describe the new behavior or provide screenshots.

Does this PR introduce a breaking change?

• Yes
• No

Specific Instructions

Are there any specific instructions or things that should be known prior to review?

Other information

[github-actions]

with the code review.

The patch adds two new build stages, which is a good idea for separating the build processes from running the application. The first stage copies the package.json and yarn.lock files and runs the yarn command to install the dependencies. The second stage copies the built application from the first stage and links the dependencies with yarn link. Finally, the CMD command in the second stage is changed from /bin/bash to /bin/ash.

Overall, the patch looks good. However, it is important to test the application after the changes are applied to make sure everything works as expected. Good luck!