mirror of
https://github.com/oneclickvirt/oneclickvirt.github.io.git
synced 2026-07-01 01:36:12 +08:00
fix: 修复排版错误
This commit is contained in:
@@ -85,8 +85,6 @@ curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt
|
||||
After the execution is completed, there will be a prompt that needs to be filled in the Controller panel side of the content.
|
||||
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.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### NetworkManager Version Issue
|
||||
|
||||
You might see this error during installation:
|
||||
@@ -111,7 +109,7 @@ After installation, a **Token** will be generated for adding the compute node to
|
||||
|
||||
Path: `Admin Panel > Computers > Add`
|
||||
|
||||
### Add IP Mapping for the Created Virtual Machine
|
||||
### Add Public IPV4 Ports Mapping for the Created Virtual Machine
|
||||
|
||||
Assume your virtual machine appears in the user control panel as:
|
||||
|
||||
@@ -152,6 +150,8 @@ iptables -I INPUT -p tcp --dport 3322 -j ACCEPT
|
||||
|
||||
Now the internal virtual machine is exposed to the internet and can be accessed remotely.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### Troubleshooting Adding Compute Node
|
||||
|
||||
On the Controller node, execute:
|
||||
@@ -206,7 +206,7 @@ docker logs webvirtcloud-backend -f
|
||||
|
||||
Then trigger the error from the frontend; the log will now display the corresponding error in real time.
|
||||
|
||||
### Restarting Docker Containers After Controller Reboot
|
||||
### Docker containers do not restart themselves after a Controller reboot
|
||||
|
||||
If Docker containers don't auto-restart after a system reboot, run:
|
||||
|
||||
@@ -214,7 +214,7 @@ If Docker containers don't auto-restart after a system reboot, run:
|
||||
docker start $(docker ps -a -q)
|
||||
```
|
||||
|
||||
### Disadvantages
|
||||
## Disadvantages
|
||||
|
||||
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.
|
||||
|
||||
|
||||
@@ -89,8 +89,6 @@ bash install_hypervisor.sh x.x.x.x
|
||||
|
||||
面板端要填入Hostname的是当前计算节点的IPV4地址,还有要填入Token识别节点。
|
||||
|
||||
## 问题排查
|
||||
|
||||
### NetworkManager 版本问题
|
||||
|
||||
安装过程中可能会出现以下错误:
|
||||
@@ -115,7 +113,7 @@ Error: Failed to add 'br-ext' connection: connection.autoconnect-ports: unknown
|
||||
|
||||
路径: `Admin Panel > Computers > Add`
|
||||
|
||||
### 给开设的虚拟机添加IP映射
|
||||
### 给开设的虚拟机添加公网IP端口映射
|
||||
|
||||
假设此时你的虚拟机在用户端控制面板显示为
|
||||
|
||||
@@ -156,6 +154,8 @@ iptables -I INPUT -p tcp --dport 3322 -j ACCEPT
|
||||
|
||||
这样内网的虚拟机就被映射出来,可以直接远程登录使用了。
|
||||
|
||||
## 问题排查
|
||||
|
||||
### 添加计算节点错误排查
|
||||
|
||||
在Controller控制端执行:
|
||||
@@ -210,7 +210,7 @@ docker logs webvirtcloud-backend -f
|
||||
|
||||
然后前端去触发错误的位置,这块日志实时加载就会看到对应的报错了
|
||||
|
||||
### Controller 重启后 Docker 容器重启
|
||||
### Controller 重启后 Docker 容器不自重启
|
||||
|
||||
如果 Docker 容器在系统重启后没有自动重启,执行以下命令:
|
||||
|
||||
@@ -218,7 +218,7 @@ docker logs webvirtcloud-backend -f
|
||||
docker start $(docker ps -a -q)
|
||||
```
|
||||
|
||||
### 缺点
|
||||
## 缺点
|
||||
|
||||
系统镜像是写死的,没法使用自己制作的自定义镜像,也没办法导出使用,同时原始的镜像没有设置远程可用密码登录和ROOT登录可用
|
||||
|
||||
|
||||
Reference in New Issue
Block a user