fix(docs): update docs docker image (#1482)

* fix(docs): update docs docker image

Signed-off-by: Jianxiang Ran <rxan_embedded@163.com>

* fix(docs): update docs docker image

Signed-off-by: Jianxiang Ran <rxan_embedded@163.com>

Signed-off-by: Jianxiang Ran <rxan_embedded@163.com>

docs/en_US/operation/manager-ui/overview.md

@@ -24,16 +24,16 @@ From eKuiper version 0.9.1, whenever a new version of eKuiper is released, the c
 
 ### Install eKuiper
 
-- Pull eKuiper's Docker image from [Docker Image Library](https://hub.docker.com/r/lfedge/ekuiper/tags). Since it is required to install the plugin in this article, you must use the `ekuiper:1.5-slim` image (`ekuiper:1.5-alpine` image is relatively small and easy to install, but due to the lack of some necessary library files, the plug-in cannot run normally. The `ekuiper:1.5` image is the development version, which is suitable for use in the development phase).
+- Pull eKuiper's Docker image from [Docker Image Library](https://hub.docker.com/r/lfedge/ekuiper/tags). Since it is required to install the plugin in this article, you must use the `ekuiper:1.7-slim` image (`ekuiper:1.7-alpine` image is relatively small and easy to install, but due to the lack of some necessary library files, the plug-in cannot run normally. The `ekuiper:1.7-dev` image is the development version, which is suitable for use in the development phase).
 
   ```shell
-  docker pull lfedge/ekuiper:1.5-slim
+  docker pull lfedge/ekuiper:1.7-slim
   ```
 
 - Run the eKuiper container (for convenience, we will use the public MQTT server provided by [EMQ](https://www.emqx.io), and the address can be set by the `-e` option when running the container). If you want to access the eKuiper instance through the host, you can expose port 9081 by adding the `-p 9081:9081` parameter when starting the container.
 
   ```shell
-  # docker run -d --name kuiper -e MQTT_SOURCE__DEFAULT__SERVER="tcp://broker.emqx.io:1883" lfedge/ekuiper:1.5-slim
+  # docker run -d --name kuiper -e MQTT_SOURCE__DEFAULT__SERVER="tcp://broker.emqx.io:1883" lfedge/ekuiper:1.7-slim
   ```
   
   When the container is running, the MQTT server address can be set through the `-e` option, and the data is written to the MQTT source configuration file, which can be viewed by the following command:
@@ -56,16 +56,16 @@ From eKuiper version 0.9.1, whenever a new version of eKuiper is released, the c
 
 ### Install management console
 
-- Pull the Docker image of kuiper-manager from [Docker Image Library](https://hub.docker.com/r/emqx/ekuiper-manager/tags), and `1.5-ief` is a dedicated image for Huawei IEF users, This example uses the `1.5` image.
+- Pull the Docker image of kuiper-manager from [Docker Image Library](https://hub.docker.com/r/emqx/ekuiper-manager/tags), and `1.7-ief` is a dedicated image for Huawei IEF users, This example uses the `1.7` image.
 
   ```shell
-  docker pull emqx/ekuiper-manager:1.5
+  docker pull emqx/ekuiper-manager:1.7
   ```
 
 - Run the Kuiper-manager container and expose port 9082.
 
   ```shell
-  docker run --name kuiperManager -d -p 9082:9082 emqx/ekuiper-manager:1.5
+  docker run --name kuiperManager -d -p 9082:9082 emqx/ekuiper-manager:1.7
   ```
 
 ## Getting started

docs/en_US/operation/manager-ui/plugins_in_manager.md

@@ -116,7 +116,7 @@ In `etc/kuiper.yaml`, there is a `pluginHosts` configuration item, and users can
 https://$host/$folder/$version/$os/$type/$plugin.zip
 ```
 
-Example:  https://127.0.0.1:9090/kuiper-plugins/1.3.1/debian/sinks/file.zip
+Example:  https://127.0.0.1:9090/kuiper-plugins/1.7.1/debian/sinks/file.zip
 
 Among them:
 
@@ -129,8 +129,8 @@ Among them:
 
 Due to the limitation of `Go` language plugin mechanism, the compilation environment of the plugin must be the same as the `eKuiper` environment. Therefore, it is recommended that the plugin be compiled in a `Docker` container of the same version as `eKuiper`. At the same time, because some libraries in the `alpine` environment are missing, it is not recommended to run plugins on it. Therefore, if you need to install and run the plugin, it is recommended to use the following container:
 
-- eKuiper: Use slim image, such as `1.3.1-slim`
-- Plugin: compile with the default image of the corresponding version, such as `1.3.1`
+- eKuiper: Use slim image, such as `1.7.1-slim`
+- Plugin: compile with the default image of the corresponding version, such as `1.7.1-dev`
 
 ### Summary
 

docs/zh_CN/extension/native/develop/plugins_tutorial.md

@@ -229,7 +229,7 @@ require (
 
 #### Docker编译
 
-eKuiper 提供了开发版本 docker 镜像。其中， 0.4.0及之后版本的开发镜像为x.x.x，例如`lfedge/ekuiper:0.4.0`；与运行版本相比，开发版提供了 go 开发环境，使得用户可以在编译出在 eKuiper 正式发布版本中完全兼容的插件。Docker 中编译步骤如下：
+eKuiper 提供了开发版本 docker 镜像。从 1.7.1 开始，开发镜像为 x.x.x-dev (0.4.0 到 1.7.0 之间版本的开发镜像为x.x.x，例如`lfedge/ekuiper:0.4.0`。)；与运行版本相比，开发版提供了 go 开发环境，使得用户可以在编译出在 eKuiper 正式发布版本中完全兼容的插件。Docker 中编译步骤如下：
 1. 运行 eKuiper 开发版本 docker。需要把本地插件目录 mount 到 docker 里的目录中，这样才能在 docker 中访问插件项目并编译。笔者的插件项目位于本地 `/var/git` 目录。下面的命令中，我们把本地的 `/var/git`目录映射到 docker 内的 `/home` 目录中。
     ```go
     docker run -d --name kuiper-dev --mount type=bind,source=/var/git,target=/home lfedge/ekuiper:1.3.0

docs/zh_CN/operation/manager-ui/overview.md

@@ -24,16 +24,16 @@
 
 ### 安装 eKuiper
 
-- 从 [Docker 镜像库](https://hub.docker.com/r/lfedge/ekuiper/tags)拉取 eKuiper 的 Docker 镜像。由于本文中要安装插件，必须使用`ekuiper:1.5-slim`镜像（`ekuiper:1.5-alpine` 镜像比较小，安装比较方便，但是由于缺少一些必要的库文件，插件无法正常运行；而 `ekuiper:1.5` 镜像是开发版本的镜像，适合于开发阶段使用）。
+- 从 [Docker 镜像库](https://hub.docker.com/r/lfedge/ekuiper/tags)拉取 eKuiper 的 Docker 镜像。由于本文中要安装插件，必须使用`ekuiper:1.7-slim`镜像（`ekuiper:1.7-alpine` 镜像比较小，安装比较方便，但是由于缺少一些必要的库文件，插件无法正常运行；而 `ekuiper:1.7-dev` 镜像是开发版本的镜像，适合于开发阶段使用）。
 
   ```shell
-  docker pull lfedge/ekuiper:1.5-slim
+  docker pull lfedge/ekuiper:1.7-slim
   ```
 
 - 运行 eKuiper 容器（为了方便，我们将使用由 [EMQ](https://www.emqx.cn) 提供的公有 MQTT 服务器，在运行容器时可通过 `-e` 选项设置地址）。如果您想通过主机访问 eKuiper 实例，可以通过在启动容器的时候加入 `-p 9081:9081` 参数来暴露 9081 端口。
 
   ```shell
-  # docker run -d --name kuiper -e MQTT_SOURCE__DEFAULT__SERVER="tcp://broker.emqx.io:1883" lfedge/ekuiper:1.5-slim
+  # docker run -d --name kuiper -e MQTT_SOURCE__DEFAULT__SERVER="tcp://broker.emqx.io:1883" lfedge/ekuiper:1.7-slim
   ```
   
   在运行容器时通过 `-e` 选项设置了 MQTT 服务器地址，数据写到了 MQTT 源配置文件中，通过以下命令可以查看：
@@ -56,16 +56,16 @@
 
 ### 安装管理控制台
 
-- 从 [Docker 镜像库](https://hub.docker.com/r/emqx/ekuiper-manager/tags) 拉取 kuiper-manager 的 Docker 镜像 ，`1.5-ief` 为华为 IEF 用户专用镜像，本例使用`1.5` 镜像。
+- 从 [Docker 镜像库](https://hub.docker.com/r/emqx/ekuiper-manager/tags) 拉取 kuiper-manager 的 Docker 镜像 ，`1.7-ief` 为华为 IEF 用户专用镜像，本例使用`1.7` 镜像。
 
   ```shell
-  docker pull emqx/ekuiper-manager:1.5
+  docker pull emqx/ekuiper-manager:1.7
   ```
 
 - 运行 Kuiper-manager 容器并暴露 9082 端口。
 
   ```shell
-  docker run --name kuiperManager -d -p 9082:9082 emqx/ekuiper-manager:1.5
+  docker run --name kuiperManager -d -p 9082:9082 emqx/ekuiper-manager:1.7
   ```
 
 ## 开始使用

docs/zh_CN/operation/manager-ui/plugins_in_manager.md

@@ -116,7 +116,7 @@ Function 元数据详细配置请参考 [sink 元数据配置](../../extension/n
 https://$host/$folder/$version/$os/$type/$plugin.zip
 ```
 
-例如： https://127.0.0.1:9090/kuiper-plugins/1.3.1/debian/sinks/file.zip
+例如： https://127.0.0.1:9090/kuiper-plugins/1.7.1/debian/sinks/file.zip
 
 其中：
 
@@ -129,8 +129,8 @@ https://$host/$folder/$version/$os/$type/$plugin.zip
 
 由于`Go`语言插件机制的限制，插件的编译环境必须与`eKuiper`环境相同。因此，建议插件在`eKuiper`相同版本的`Docker` 容器中进行编译。同时，由于`alpine` 环境部分库缺失，不建议在上面运行插件。因此，若需要插件安装运行，建议使用如下容器：
 
-- eKuiper: 使用 slim 镜像，例如 `1.3.1-slim`
-- 插件：使用对应版本默认镜像进行编译，例如 `1.3.1`
+- eKuiper: 使用 slim 镜像，例如 `1.7.1-slim`
+- 插件：使用对应版本默认镜像进行编译，例如 `1.7.1-dev`
 
 ## 总结