Hi, The docker image currently maintained in the project does have room for further optimization. amoro: This is the core image of the project. It provides AMS deployment in early versions. After this PR will be merged (https://github.com/apache/amoro/pull/2695), it can also directly provide the deployment of Optimizer on K8S. , this should also be the recommended using in the future. I recommend maintaining this image in the apache repo in the future, using apache/amoro as the image name. Here you can refer to kyuubi (https://hub.docker.com/r/apache/kyuubi) optimizer-flink/optimizer-spark: Provides images of optimizer deployment under different computing engines. I also recommend that these two images be maintained under the apache repo, using apache/amoro-flink-optimizer and apache/amoro-spark-optimizer as the image id. quickstart: Used to demonstrate the QuickStart part of the official website. This image is based on the amoro image and includes computing engines such as flink/spark and connectors such as iceberg. It is recommended to use amoro's repo maintenance for this part and use amoro/quickstart as the image name. namenode/datanode: These two images are used to provide an HDFS environment in the qucikstart demonstration. I suggest modifying the current quickstart process, using minio as the quickstart environment, and no longer maintaining these two images. The above are my personal suggestions.
Kind Regards, baiyangtx ---- Replied Message ---- | From | Gang Huang<tcodehu...@gmail.com> | | Date | 4/26/2024 17:03 | | To | <dev@amoro.apache.org> | | Subject | Adjust docker images of apache amoro project | Hi, Currently, there are up to 6 docker images in apache amoro project. But in my opinion, only amoro, optimizer-flink and optimizer-spark maybe are needed. Furthermore, we have to change the images' final names(amoro-ams, amoro-optimizer-flink, amoro-optimizer-spark) to identify them when uploading them into docker hub. Thus, we can simplify the quick start process for better user experience, just like iceberg/risingwave quickstart: https://iceberg.apache.org/spark-quickstart/ https://docs.risingwave.com/docs/current/get-started/ Please feel free to contribute your suggestions. Kind Regards, Gang Huang
