fix pic show issue (#821)

* prepare for release 1.8.0

* fix picture show problems

* update version

* fix image show issue

* update gitignore

* fix blog picture show issue

---------

Co-authored-by: aiceflower <[email protected]>
Co-authored-by: Casion <[email protected]>

Author: 3 people

blog/2022-02-21-linkis-deploy.md

@@ -373,7 +373,7 @@ wds.linkis.admin.password= #Password
 
 After logging in, check whether the yarn queue resources can be displayed normally (if you want to use the spark/hive/flink engine)
 Normally as shown below:    
-![yarn-normal](https://user-images.githubusercontent.com/7869972/159955494-2f305a38-a3d6-4798-83aa-58cde23bc436.png)
+![yarn-normal](/Images/blog/159955494-2f305a38-a3d6-4798-83aa-58cde23bc436.png)
 
 If it cannot be displayed:  
 #### 1 Check whether the yarn address is configured correctly
@@ -416,7 +416,7 @@ Available yarn queues can be viewed at rmWebAddress:http://xx.xx.xx.xx:8088
 select * from linkis_cg_engine_conn_plugin_bml_resources
 ````
 normal as follows  
-![bml](https://user-images.githubusercontent.com/29391030/156343249-9f6dca8f-4e0d-438b-995f-4f469270a22d.png)
+![bml](/Images/blog/156343249-9f6dca8f-4e0d-438b-995f-4f469270a22d.png)
 
 
 Check whether the material record of the engine exists (if there is an update, check whether the update time is correct).  
@@ -489,7 +489,7 @@ select * from linkis_cg_engine_conn_plugin_bml_resources
 
   step1: Find the startup deployment directory of the engine  
     Method 1: If it is displayed in the execution log, you can view it on the management console as shown below:     
-    ![engine-log](https://user-images.githubusercontent.com/29391030/156343802-9d47fa98-dc70-4206-b07f-df439b291028.png)    
+    ![engine-log](/Images/blog/156343802-9d47fa98-dc70-4206-b07f-df439b291028.png)
     Method 2: If it is not found in method 1, you can find the parameter of `wds.linkis.engineconn.root.dir` configured in `conf/linkis-cg-engineconnmanager.properties`, which is the directory where the engine is started and deployed. The user of the execution engine is isolated (taskId). If you do not know the taskid, you can select it after sorting by time. ll -rt /appcom/tmp/${executing user}/workDir
     
     cd /appcom/tmp/${executing user}/workDir/${taskId}  
@@ -530,9 +530,9 @@ select * from linkis_cg_engine_conn_plugin_bml_resources
   Troubleshoot basic problems according to some of the scenarios listed above  
   [QA documentation](https://docs.qq.com/doc/DSGZhdnpMV3lTUUxq) Find out if there is a solution, link: https://docs.qq.com/doc/DSGZhdnpMV3lTUUxq  
   See if you can find a solution by searching the content in the issue    
-  ![issues](https://user-images.githubusercontent.com/29391030/156343419-81cc25e0-aa94-4c06-871c-bb036eb6d4ff.png)   
+  ![issues](/Images/blog/156343419-81cc25e0-aa94-4c06-871c-bb036eb6d4ff.png)
   Through the official website document search, for some problems, you can search for keywords through the official website, such as searching for "deployment". (If 404 appears,   please refresh your browser)     
-  ![search](https://user-images.githubusercontent.com/29391030/156343459-7911bd05-4d8d-4a7b-b9f8-35c152d52c41.png)     
+  ![search](/Images/blog/156343459-7911bd05-4d8d-4a7b-b9f8-35c152d52c41.png)
 
 
 ## 7. How to obtain relevant information

blog/2022-03-20-openlookeng.md

@@ -19,11 +19,11 @@ That is, tasks submitted by multiple users can run in one EC process at the same
 The specific implementation is that openLooKengEngineConnExecutor inherits from ConcurrentComputationExecutor, supports multi-user multi-task concurrency, and supports docking to multiple different openLooKeng clusters.
 ## Architecture
 Architecture diagram:
-![image](https://user-images.githubusercontent.com/7869972/166736911-c0f50968-3996-40d0-afdf-52b35d4cd71c.png)
+![image](/Images/blog/166736911-c0f50968-3996-40d0-afdf-52b35d4cd71c.png)
 
 
 The task flow diagram is as follows:
-  ![image](https://user-images.githubusercontent.com/7869972/166737177-57f8f84a-b16d-44bd-b7cf-a61fc2cc160c.png)
+  ![image](/Images/blog/166737177-57f8f84a-b16d-44bd-b7cf-a61fc2cc160c.png)
 
 The capabilities based on Linkis and openLooKeng can provide the following capabilities:
 - 1. The connection capability of the computing middleware layer based on Linkis allows upper-layer application tools to quickly connect to openLooKeng, submit tasks, and obtain logs, progress, and results.

i18n/zh-CN/docusaurus-plugin-content-blog/2022-02-21-linkis-deploy.md

@@ -384,7 +384,7 @@ wds.linkis.admin.password= #密码
 
 登录后查看能否正常显示yarn队列资源(点击页面右下角按钮)  
 正常如下图所示:    
-![yarn-normal](https://user-images.githubusercontent.com/7869972/159955494-2f305a38-a3d6-4798-83aa-58cde23bc436.png)
+![yarn-normal](/Images/blog/159955494-2f305a38-a3d6-4798-83aa-58cde23bc436.png)
 
 若如果无法显示：可以按以下指引调整 
 
@@ -430,7 +430,7 @@ select *  from linkis_cg_engine_conn_plugin_bml_resources
 ```
 
 正常如下： 
-![bml](https://user-images.githubusercontent.com/29391030/156343249-9f6dca8f-4e0d-438b-995f-4f469270a22d.png)
+![bml](/Images/blog/156343249-9f6dca8f-4e0d-438b-995f-4f469270a22d.png)
 
 查看引擎的物料记录是否存在(如果有更新,查看更新时间是否正确)。
 
@@ -512,7 +512,7 @@ less log/* |grep -5n exception(或则less log/* |grep -5n ERROR)
 
 ** step1:找到引擎的启动部署目录 **  
 方式1：如果执行日志中有显示，可以在管理台上查看到 如下图:        
-![engine-log](https://user-images.githubusercontent.com/29391030/156343802-9d47fa98-dc70-4206-b07f-df439b291028.png)
+![engine-log](/Images/blog/156343802-9d47fa98-dc70-4206-b07f-df439b291028.png)
 方式2:如果方式1中没有找到，可以通过找到`conf/linkis-cg-engineconnmanager.properties`配置的`wds.linkis.engineconn.root.dir`的参数，该值就是引擎启动部署的目录，子目录按执行引擎的用户进行了隔离。
 ```shell script
 如果不清楚taskid，可以按时间排序后进行选择 ll -rt /appcom/tmp/${执行的用户}/workDir   
@@ -548,7 +548,7 @@ CDH本身不是使用的官方标准的hive/spark包,进行适配时，最好修
 - 方式1 可以开启[免登陆模式指引](/docs/latest/api/login-api/#2免登录配置)  
 - 方式2 postman中的，请求头带上登陆成功的cookie值
 cookie值可以在浏览器端登陆成功后，获取
-![bml](https://user-images.githubusercontent.com/7869972/157619718-3afb480f-6087-4d5c-9a77-5e75c8cb4a3c.png)
+![bml](/Images/blog/157619718-3afb480f-6087-4d5c-9a77-5e75c8cb4a3c.png)
 
 ```shell script
 Cookie: bdp-user-ticket-id=xxxxxxxxxxxxxxxxxxxxxxxxxxx
@@ -566,9 +566,9 @@ Token-User:hadoop
 按上述罗列的一些场景的方式进行基础问题的排查  
 [QA文档](https://docs.qq.com/doc/DSGZhdnpMV3lTUUxq)中查找是否有解决方案，链接：https://docs.qq.com/doc/DSGZhdnpMV3lTUUxq  
 通过搜索issue中的内容,看是否能找到解决方案        
-![issues](https://user-images.githubusercontent.com/29391030/156343419-81cc25e0-aa94-4c06-871c-bb036eb6d4ff.png)    
+![issues](/Images/blog/156343419-81cc25e0-aa94-4c06-871c-bb036eb6d4ff.png)
 通过官网文档搜索，对于某些问题，可以通过官网搜索关键字进行查询，比如搜索"部署"相关。(如果出现404,请浏览器中刷新一下)          
-![search](https://user-images.githubusercontent.com/29391030/156343459-7911bd05-4d8d-4a7b-b9f8-35c152d52c41.png)  
+![search](/Images/blog/156343459-7911bd05-4d8d-4a7b-b9f8-35c152d52c41.png)
 
 
 ## 10. 相关的资料如何获取 

i18n/zh-CN/docusaurus-plugin-content-blog/2022-03-20-openlookeng.md

@@ -19,11 +19,11 @@ openLooKeng ec的实现基于Linkis的EngineConn Plugin（ECP）进行扩展，
 具体实现为openLooKengEngineConnExecutor继承于ConcurrentComputationExecutor，支持多用户多任务并发，并且支持对接到多个不同的openLooKeng集群。
 ## 架构
 架构图：
-![image](https://user-images.githubusercontent.com/7869972/166736911-c0f50968-3996-40d0-afdf-52b35d4cd71c.png)
+![image](/Images/blog/166736911-c0f50968-3996-40d0-afdf-52b35d4cd71c.png)
 
 
 任务流转图如下：
-  ![image](https://user-images.githubusercontent.com/7869972/166737177-57f8f84a-b16d-44bd-b7cf-a61fc2cc160c.png)
+  ![image](/Images/blog/166737177-57f8f84a-b16d-44bd-b7cf-a61fc2cc160c.png)
 
 基于Linkis和openLooKeng的能力可以提供如下能力：
 - 1.基于Linkis的计算中间件层的连接能力可以让上层应用工具快速对接使用openLooKeng，提交任务，并获取日志、进度、结果。

i18n/zh-CN/docusaurus-plugin-content-blog/2022-05-12-release-1.1.1.md

@@ -38,7 +38,7 @@ openLooKeng用于支持数据探索、即席查询和批处理，具有100+毫
 ### 新特性4 引擎进程日志文件页面查看
 对于启动的引擎进程，能够在管理台>ECM管理>某ECM具体引擎列表页面，直接查看进程的运行日志文件内容。方便某些异常问题的排查，以及引擎运行时，关键日志信息的查看。
 
-![image](https://user-images.githubusercontent.com/7869972/168042702-1d0f998d-59d8-4a19-8803-a2a913bd4e5f.png)
+![image](/Images/blog/168042702-1d0f998d-59d8-4a19-8803-a2a913bd4e5f.png)
 
 ## 增强点