Skip to content

Commit 1e78365

Browse files
committed
fix: 修复排版错误
1 parent 18d9d22 commit 1e78365

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

docs/en/incomplete/webvirtcloud.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -85,8 +85,6 @@ curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt
8585
After the execution is completed, there will be a prompt that needs to be filled in the Controller panel side of the content.
8686
Panel side to fill in the Hostname is the IPV4 address of the current computing node, as well as to fill in the Token to identify the node.
8787

88-
## Troubleshooting
89-
9088
### NetworkManager Version Issue
9189

9290
You might see this error during installation:
@@ -111,7 +109,7 @@ After installation, a **Token** will be generated for adding the compute node to
111109

112110
Path: `Admin Panel > Computers > Add`
113111

114-
### Add IP Mapping for the Created Virtual Machine
112+
### Add Public IPV4 Ports Mapping for the Created Virtual Machine
115113

116114
Assume your virtual machine appears in the user control panel as:
117115

@@ -152,6 +150,8 @@ iptables -I INPUT -p tcp --dport 3322 -j ACCEPT
152150

153151
Now the internal virtual machine is exposed to the internet and can be accessed remotely.
154152

153+
## Troubleshooting
154+
155155
### Troubleshooting Adding Compute Node
156156

157157
On the Controller node, execute:
@@ -206,15 +206,15 @@ docker logs webvirtcloud-backend -f
206206

207207
Then trigger the error from the frontend; the log will now display the corresponding error in real time.
208208

209-
### Restarting Docker Containers After Controller Reboot
209+
### Docker containers do not restart themselves after a Controller reboot
210210

211211
If Docker containers don't auto-restart after a system reboot, run:
212212

213213
```bash
214214
docker start $(docker ps -a -q)
215215
```
216216

217-
### Disadvantages
217+
## Disadvantages
218218

219219
The VM image is written to death, there is no way to use your own custom image, and there is no way to export it, and the original image does not have password login and ROOT login available.
220220

docs/incomplete/webvirtcloud.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -89,8 +89,6 @@ bash install_hypervisor.sh x.x.x.x
8989

9090
面板端要填入Hostname的是当前计算节点的IPV4地址,还有要填入Token识别节点。
9191

92-
## 问题排查
93-
9492
### NetworkManager 版本问题
9593

9694
安装过程中可能会出现以下错误:
@@ -115,7 +113,7 @@ Error: Failed to add 'br-ext' connection: connection.autoconnect-ports: unknown
115113

116114
路径: `Admin Panel > Computers > Add`
117115

118-
### 给开设的虚拟机添加IP映射
116+
### 给开设的虚拟机添加公网IP端口映射
119117

120118
假设此时你的虚拟机在用户端控制面板显示为
121119

@@ -156,6 +154,8 @@ iptables -I INPUT -p tcp --dport 3322 -j ACCEPT
156154

157155
这样内网的虚拟机就被映射出来,可以直接远程登录使用了。
158156

157+
## 问题排查
158+
159159
### 添加计算节点错误排查
160160

161161
在Controller控制端执行:
@@ -210,15 +210,15 @@ docker logs webvirtcloud-backend -f
210210

211211
然后前端去触发错误的位置,这块日志实时加载就会看到对应的报错了
212212

213-
### Controller 重启后 Docker 容器重启
213+
### Controller 重启后 Docker 容器不自重启
214214

215215
如果 Docker 容器在系统重启后没有自动重启,执行以下命令:
216216

217217
```bash
218218
docker start $(docker ps -a -q)
219219
```
220220

221-
### 缺点
221+
## 缺点
222222

223223
系统镜像是写死的,没法使用自己制作的自定义镜像,也没办法导出使用,同时原始的镜像没有设置远程可用密码登录和ROOT登录可用
224224

0 commit comments

Comments
 (0)