diff --git a/404.html b/404.html index 78a487e9b4..a96c00aebf 100644 --- a/404.html +++ b/404.html @@ -17,7 +17,7 @@
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

404

PAGE NOT FOUND

But if you don't change your direction, and if you keep looking, you may end up where you are heading.
Take me home
- + \ No newline at end of file diff --git a/assets/case_case1.md.13450359.js b/assets/case_case1.md.40a5c4e9.js similarity index 99% rename from assets/case_case1.md.13450359.js rename to assets/case_case1.md.40a5c4e9.js index 3d94a39bfc..e794298394 100644 --- a/assets/case_case1.md.13450359.js +++ b/assets/case_case1.md.40a5c4e9.js @@ -1,4 +1,4 @@ -import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case1.md","filePath":"case/case1.md","lastUpdated":1747726389000}'),o={name:"case/case1.md"},p=l(`

仓库 ​

Hits

Hits

融合怪测评项目

(GO版本除非必须的环境安装使用shell外无额外shell文件依赖，环境安装只是为了测的更准，极端情况下无环境依赖也可全测项目)

如有问题请 issues 反馈。

Go 版本：https://github.com/oneclickvirt/ecs

Shell 版本：https://github.com/spiritLHLS/ecs

适配系统和架构 ​

编译与测试支持情况 ​

编译支持的架构测试支持的架构编译支持的系统测试支持的系统
amd64amd64LinuxLinux
armarmWindowsWindows
arm64arm64FreeBSDFreeBSD
386386OpenBSD
mipsMacOS
mipsle
s390xs390x
riscv64

功能 ​

本项目初次使用建议查看说明：跳转

使用说明 ​

Linux/FreeBSD/OpenBSD/MacOS ​

一键命令 ​

一键命令将默认安装依赖，默认更新包管理器，默认非互动模式

详细说明 ​

详细说明中的命令可控制是否安装依赖，是否更新包管理器，默认互动模式可进行选择

  1. 下载脚本

    国际用户无加速：

    bash
    curl -L https://raw.githubusercontent.com/oneclickvirt/ecs/master/goecs.sh -o goecs.sh && chmod +x goecs.sh

    国际/国内使用 CDN 加速：

    bash
    curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/ecs/master/goecs.sh -o goecs.sh && chmod +x goecs.sh

    国内用户使用 CNB 加速：

    bash
    curl -L https://cnb.cool/oneclickvirt/ecs/-/git/raw/main/goecs.sh -o goecs.sh && chmod +x goecs.sh

  2. 更新包管理器（可选择）并安装环境

    bash
    ./goecs.sh env

    非互动模式：

    bash
    export noninteractive=true && ./goecs.sh env

  3. 安装 goecs

    bash
    ./goecs.sh install

  4. 升级 goecs

    bash
    ./goecs.sh upgrade

  5. 卸载 goecs

    bash
    ./goecs.sh uninstall

  6. 帮助命令

    bash
    ./goecs.sh -h

  7. 唤起菜单

    bash
    goecs

命令参数化 ​

bash
Usage: goecs [options]
+import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case1.md","filePath":"case/case1.md","lastUpdated":1747730955000}'),o={name:"case/case1.md"},p=l(`
仓库 ​
Hits
Hits
融合怪测评项目
(GO版本除非必须的环境安装使用shell外无额外shell文件依赖，环境安装只是为了测的更准，极端情况下无环境依赖也可全测项目)
如有问题请 issues 反馈。
Go 版本：https://github.com/oneclickvirt/ecs
Shell 版本：https://github.com/spiritLHLS/ecs
适配系统和架构 ​
编译与测试支持情况 ​
编译支持的架构测试支持的架构编译支持的系统测试支持的系统
amd64amd64LinuxLinux
armarmWindowsWindows
arm64arm64FreeBSDFreeBSD
386386OpenBSD
mipsMacOS
mipsle
s390xs390x
riscv64
功能 ​
本项目初次使用建议查看说明：跳转
使用说明 ​
Linux/FreeBSD/OpenBSD/MacOS ​
一键命令 ​
一键命令将默认安装依赖，默认更新包管理器，默认非互动模式
  • 国际用户无加速：
    bash
    export noninteractive=true && curl -L https://raw.githubusercontent.com/oneclickvirt/ecs/master/goecs.sh -o goecs.sh && chmod +x goecs.sh && bash goecs.sh env && bash goecs.sh install && goecs
  • 国际/国内使用 CDN 加速：
    bash
    export noninteractive=true && curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/ecs/master/goecs.sh -o goecs.sh && chmod +x goecs.sh && bash goecs.sh env && bash goecs.sh install && goecs
  • 国内用户使用 CNB 加速：
    bash
    export noninteractive=true && curl -L https://cnb.cool/oneclickvirt/ecs/-/git/raw/main/goecs.sh -o goecs.sh && chmod +x goecs.sh && bash goecs.sh env && bash goecs.sh install && goecs
详细说明 ​
详细说明中的命令可控制是否安装依赖，是否更新包管理器，默认互动模式可进行选择
  1. 下载脚本
    国际用户无加速：
    bash
    curl -L https://raw.githubusercontent.com/oneclickvirt/ecs/master/goecs.sh -o goecs.sh && chmod +x goecs.sh
    国际/国内使用 CDN 加速：
    bash
    curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/ecs/master/goecs.sh -o goecs.sh && chmod +x goecs.sh
    国内用户使用 CNB 加速：
    bash
    curl -L https://cnb.cool/oneclickvirt/ecs/-/git/raw/main/goecs.sh -o goecs.sh && chmod +x goecs.sh
  2. 更新包管理器（可选择）并安装环境
    bash
    ./goecs.sh env
    非互动模式：
    bash
    export noninteractive=true && ./goecs.sh env
  3. 安装 goecs
    bash
    ./goecs.sh install
  4. 升级 goecs
    bash
    ./goecs.sh upgrade
  5. 卸载 goecs
    bash
    ./goecs.sh uninstall
  6. 帮助命令
    bash
    ./goecs.sh -h
  7. 唤起菜单
    bash
    goecs
命令参数化 ​
bash
Usage: goecs [options]
   -backtrace
         Enable/Disable backtrace test (in 'en' language or on windows it always false) (default true)
   -basic
diff --git a/assets/case_case1.md.13450359.lean.js b/assets/case_case1.md.40a5c4e9.lean.js
similarity index 99%
rename from assets/case_case1.md.13450359.lean.js
rename to assets/case_case1.md.40a5c4e9.lean.js
index 3d94a39bfc..e794298394 100644
--- a/assets/case_case1.md.13450359.lean.js
+++ b/assets/case_case1.md.40a5c4e9.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case1.md","filePath":"case/case1.md","lastUpdated":1747726389000}'),o={name:"case/case1.md"},p=l(`
仓库 ​
Hits
Hits
融合怪测评项目
(GO版本除非必须的环境安装使用shell外无额外shell文件依赖，环境安装只是为了测的更准，极端情况下无环境依赖也可全测项目)
如有问题请 issues 反馈。
Go 版本：https://github.com/oneclickvirt/ecs
Shell 版本：https://github.com/spiritLHLS/ecs
适配系统和架构 ​
编译与测试支持情况 ​
编译支持的架构测试支持的架构编译支持的系统测试支持的系统
amd64amd64LinuxLinux
armarmWindowsWindows
arm64arm64FreeBSDFreeBSD
386386OpenBSD
mipsMacOS
mipsle
s390xs390x
riscv64
功能 ​
本项目初次使用建议查看说明：跳转
使用说明 ​
Linux/FreeBSD/OpenBSD/MacOS ​
一键命令 ​
一键命令将默认安装依赖，默认更新包管理器，默认非互动模式
  • 国际用户无加速：
    bash
    export noninteractive=true && curl -L https://raw.githubusercontent.com/oneclickvirt/ecs/master/goecs.sh -o goecs.sh && chmod +x goecs.sh && bash goecs.sh env && bash goecs.sh install && goecs
  • 国际/国内使用 CDN 加速：
    bash
    export noninteractive=true && curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/ecs/master/goecs.sh -o goecs.sh && chmod +x goecs.sh && bash goecs.sh env && bash goecs.sh install && goecs
  • 国内用户使用 CNB 加速：
    bash
    export noninteractive=true && curl -L https://cnb.cool/oneclickvirt/ecs/-/git/raw/main/goecs.sh -o goecs.sh && chmod +x goecs.sh && bash goecs.sh env && bash goecs.sh install && goecs
详细说明 ​
详细说明中的命令可控制是否安装依赖，是否更新包管理器，默认互动模式可进行选择
  1. 下载脚本
    国际用户无加速：
    bash
    curl -L https://raw.githubusercontent.com/oneclickvirt/ecs/master/goecs.sh -o goecs.sh && chmod +x goecs.sh
    国际/国内使用 CDN 加速：
    bash
    curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/ecs/master/goecs.sh -o goecs.sh && chmod +x goecs.sh
    国内用户使用 CNB 加速：
    bash
    curl -L https://cnb.cool/oneclickvirt/ecs/-/git/raw/main/goecs.sh -o goecs.sh && chmod +x goecs.sh
  2. 更新包管理器（可选择）并安装环境
    bash
    ./goecs.sh env
    非互动模式：
    bash
    export noninteractive=true && ./goecs.sh env
  3. 安装 goecs
    bash
    ./goecs.sh install
  4. 升级 goecs
    bash
    ./goecs.sh upgrade
  5. 卸载 goecs
    bash
    ./goecs.sh uninstall
  6. 帮助命令
    bash
    ./goecs.sh -h
  7. 唤起菜单
    bash
    goecs
命令参数化 ​
bash
Usage: goecs [options]
+import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case1.md","filePath":"case/case1.md","lastUpdated":1747730955000}'),o={name:"case/case1.md"},p=l(`
仓库 ​
Hits
Hits
融合怪测评项目
(GO版本除非必须的环境安装使用shell外无额外shell文件依赖，环境安装只是为了测的更准，极端情况下无环境依赖也可全测项目)
如有问题请 issues 反馈。
Go 版本：https://github.com/oneclickvirt/ecs
Shell 版本：https://github.com/spiritLHLS/ecs
适配系统和架构 ​
编译与测试支持情况 ​
编译支持的架构测试支持的架构编译支持的系统测试支持的系统
amd64amd64LinuxLinux
armarmWindowsWindows
arm64arm64FreeBSDFreeBSD
386386OpenBSD
mipsMacOS
mipsle
s390xs390x
riscv64
功能 ​
本项目初次使用建议查看说明：跳转
使用说明 ​
Linux/FreeBSD/OpenBSD/MacOS ​
一键命令 ​
一键命令将默认安装依赖，默认更新包管理器，默认非互动模式
  • 国际用户无加速：
    bash
    export noninteractive=true && curl -L https://raw.githubusercontent.com/oneclickvirt/ecs/master/goecs.sh -o goecs.sh && chmod +x goecs.sh && bash goecs.sh env && bash goecs.sh install && goecs
  • 国际/国内使用 CDN 加速：
    bash
    export noninteractive=true && curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/ecs/master/goecs.sh -o goecs.sh && chmod +x goecs.sh && bash goecs.sh env && bash goecs.sh install && goecs
  • 国内用户使用 CNB 加速：
    bash
    export noninteractive=true && curl -L https://cnb.cool/oneclickvirt/ecs/-/git/raw/main/goecs.sh -o goecs.sh && chmod +x goecs.sh && bash goecs.sh env && bash goecs.sh install && goecs
详细说明 ​
详细说明中的命令可控制是否安装依赖，是否更新包管理器，默认互动模式可进行选择
  1. 下载脚本
    国际用户无加速：
    bash
    curl -L https://raw.githubusercontent.com/oneclickvirt/ecs/master/goecs.sh -o goecs.sh && chmod +x goecs.sh
    国际/国内使用 CDN 加速：
    bash
    curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/ecs/master/goecs.sh -o goecs.sh && chmod +x goecs.sh
    国内用户使用 CNB 加速：
    bash
    curl -L https://cnb.cool/oneclickvirt/ecs/-/git/raw/main/goecs.sh -o goecs.sh && chmod +x goecs.sh
  2. 更新包管理器（可选择）并安装环境
    bash
    ./goecs.sh env
    非互动模式：
    bash
    export noninteractive=true && ./goecs.sh env
  3. 安装 goecs
    bash
    ./goecs.sh install
  4. 升级 goecs
    bash
    ./goecs.sh upgrade
  5. 卸载 goecs
    bash
    ./goecs.sh uninstall
  6. 帮助命令
    bash
    ./goecs.sh -h
  7. 唤起菜单
    bash
    goecs
命令参数化 ​
bash
Usage: goecs [options]
   -backtrace
         Enable/Disable backtrace test (in 'en' language or on windows it always false) (default true)
   -basic
diff --git a/assets/case_case2.md.d392b76a.js b/assets/case_case2.md.729cbff7.js
similarity index 99%
rename from assets/case_case2.md.d392b76a.js
rename to assets/case_case2.md.729cbff7.js
index 432c5ab4d9..8c67a15105 100644
--- a/assets/case_case2.md.d392b76a.js
+++ b/assets/case_case2.md.729cbff7.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case2.md","filePath":"case/case2.md","lastUpdated":1747726389000}'),o={name:"case/case2.md"},p=n(`
仓库 ​
https://github.com/spiritLHLS/one-click-installation-script
Hits
所有脚本如需在国内服务器使用，请在链接前加上https://ghproxy.com/确保命令可以下载本仓库的shell脚本执行
一键修复脚本 ​
运行所有一键修复脚本前注意看说明，以及保证服务器无重要数据，运行后造成的一切后果作者不负任何责任，自行评判风险！
一键尝试修复apt源 ​
  • 支持系统：Ubuntu 12+，Debian 6+
  • 修复apt下载包进程意外退出导致的源锁死
  • 修复apt源broken损坏
  • 修复apt源多进程占用锁死
  • 修复apt源公钥缺失
  • 修复替换系统可用的apt源列表，国内用阿里源，国外用官方源
  • 修复本机的Ubuntu系统是EOL非长期维护的版本(奇数或陈旧的偶数版本)，将替换为Ubuntu官方的old-releases仓库以支持apt的使用
  • 修复只保证apt update不会报错，其他命令报错未修复
  • 如若修复后install还有问题，重启服务器解决问题
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/package.sh -o package.sh && chmod +x package.sh && bash package.sh
一键尝试修复系统时间 ​
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 由于系统时间不准确都是未进行时区时间同步造成的，使用chronyd进行时区时间同步后应当解决了问题
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/modify_time.sh -o modify_time.sh && chmod +x modify_time.sh && bash modify_time.sh
一键尝试修复sudo警告 ​
  • 一键尝试修复sudo: unable to resolve host xxx: Name or service not known警告(爆错)
不要在生产环境上使用该脚本，否则容易造成网络hosts配置错误，配置的host名字不在外网IP上反而在内网IP(127.0.0.1)上
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/check_sudo.sh -o check_sudo.sh && chmod +x check_sudo.sh && bash check_sudo.sh
一键修改系统自带的journal日志记录大小释放系统盘空间 ​
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 1.自定义修改大小，单位为MB，一般500或者1000即可，有的系统日志默认给了5000甚至更多，不是做站啥的没必要 
    • 请注意，修改journal目录大小会影响系统日志的记录，因此，在修改journal目录大小之前如果需要之前的日志，建议先备份系统日志到本地
  • 2.自定义修改设置系统日志保留日期时长，超过日期时长的日志将被清除
  • 3.默认修改日志只记录warning等级(无法自定义)
  • 4.以后日志的产生将受到日志文件大小，日志保留时间，日志保留等级的限制
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/resize_journal.sh -o resize_journal.sh && chmod +x resize_journal.sh && bash resize_journal.sh
一键尝试修复网络 ​
该脚本轻易勿要使用，请确保运行时服务器无重要文件或程序，出现运行bug后续可能需要重装系统
一定要在screen中执行该脚本，否则可能导致修改过程中ssh断链接而修改失败卡住最终SSH无法连接！不在screen中执行后果自负！
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 尝试修复nameserver为google源或cloudflare源
  • 尝试修复为IP类型对应的网络优先级(默认IPV4类型，纯V6类型再替换为IPV6类型)
bash
curl -L https://cdn.spiritlhl.workers.dev/https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/network.sh -o network.sh && chmod +x network.sh && bash network.sh
如果是纯V6的也可以不使用上面脚本的nat64，使用warp添加V4网络
比如：https://github.com/fscarmen/warp
bash
wget -N https://raw.githubusercontent.com/fscarmen/warp/main/menu.sh && bash menu.sh [option] [lisence]
非纯V6的，带V4切换优先级到IPV4可用以下命令
bash
sudo sed -i 's/.*precedence ::ffff:0:0\\/96.*/precedence ::ffff:0:0\\/96  100/g' /etc/gai.conf && sudo systemctl restart networking
一键环境安装脚本 ​
只推荐在新服务器上安装，环境不纯净不保证不出bug
运行所有一键环境安装脚本前注意看说明，以及保证服务器无重要数据，运行后造成的一切后果作者不负任何责任，自行评判风险！
一键安装jupyter环境 ​
  • 本脚本尝试使用Miniconda3安装虚拟环境jupyter-env再进行jupyter和jupyterlab的安装，如若安装机器不纯净勿要轻易使用本脚本！
  • 本脚本为实验性脚本可能会有各种bug，勿要轻易尝试！
  • 验证已支持的系统： 
    • Ubuntu 系 - 推荐，脚本自动挂起到后台
    • Debian 系 - 部分可能需要手动挂起到后台，详看脚本运行安装完毕的后续提示
  • 可能支持的系统(未验证)：centos 7+，Fedora，Almalinux 8.5+
  • 执行脚本，之前有用本脚本安装过则直接打印设置的登陆信息，没安装过则进行安装再打印信息，如果已安装但未启动则自动启动后再打印信息
  • 如果是初次安装无脑输入y回车即可，按照提示进行操作即可，安装完毕将在后台常驻运行，自动添加常用的安装包通道源
  • 安装完毕后，如果需要在lab中安装第三方库需要在lab中使用terminal并使用conda进行下载而不是pip3下载，这是需要注意的一点
  • 安装过程中有判断是否为中国IP，可选择是否使用中国镜像
原始用途是方便快捷的在按小时计费的超大型服务器上部署python环境进行科学计算，充分利用时间别浪费在构建环境上。
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/jupyter.sh -o jupyter.sh && chmod +x jupyter.sh && bash jupyter.sh
一键安装R语言环境 ​
  • 安装前需使用Miniconda3安装虚拟环境jupyter-env，然后进行jupyter和jupyterlab的安装，再然后才能安装本内核
  • 简单的说，需要执行本仓库对应的jupyter安装脚本再运行本脚本安装R语言环境，会自动安装R环境内核和图形设备支持库
  • x11可能需要手动启动一下，执行sudo /usr/bin/Xorg
  • 可能支持的系统(未验证)：centos 7+，Fedora，Almalinux 8.5+
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/R.sh -o R.sh && chmod +x R.sh && bash R.sh
一键安装rust环境 ​
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 加载官方脚本安装，前置条件适配系统以及后置条件判断安装的版本
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/rust.sh -o rust.sh && chmod +x rust.sh && bash rust.sh
一键安装C环境 ​
  • 一键安装C++环境
  • 支持系统：使用apt或者yum作为包管理器的系统
  • 如果未安装则安装，如果有安装则提示升级
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/cplusplus.sh -o cplusplus.sh && chmod +x cplusplus.sh && bash cplusplus.sh
一键安装vnstat环境 ​
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 加载官方文件编译安装，前置条件适配系统以及后置条件判断安装的版本
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/vnstat.sh -o vnstat.sh && chmod +x vnstat.sh && bash vnstat.sh
一键升级低版本debian为debian11 ​
  • 支持系统：debian 6+
  • 升级后需要重启系统加载内核，升级过程中需要选择的都无脑按回车即可
  • 升级是一个版本迭代一个版本，所以如果版本低，每执行一次升级一个版本，直至升级到debian11
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/todebian11.sh -o todebian11.sh && chmod +x todebian11.sh && bash todebian11.sh
一键升级低版本ubuntu为ubuntu22 ​
  • 支持系统：Ubuntu 16+
  • 升级后需要重启系统加载内核，升级过程中需要选择的都无脑按回车即可
  • 升级是一个版本迭代一个版本，所以如果版本低，每执行一次升级一个版本，直至升级到ubuntu22
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/toubuntu22.sh -o toubuntu22.sh && chmod +x toubuntu22.sh && bash toubuntu22.sh
一键安装zipline平台 ​
  • 应该支持的系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 暂时只在Ubuntu上验证无问题
  • 如若要设置反向代理绑定域名，安装前请保证原服务器未安装过nginx，如若已安装过nginx，请自行配置反向代理本机的3000端口
  • 默认一路回车是不启用反代不安装nginx的，自行选择，如需通过本脚本配置反代系统一定要未安装过nginx并在填写y或Y开启安装
  • zipline 平台功能: ShareX，自定义短链接，文件上传分享，多用户校验，高亮显示，阅后即焚，设置简单 (含pastebin)
  • 自动安装docker，docker-compose，如若已安装zipline在/root目录下，则自动更新
  • 反向代理如若已设置成功，还需要在面板设置中填写域名，绑定启用
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/zipline.sh -o zipline.sh && chmod +x zipline.sh && bash zipline.sh
如果需要删除0字节文件，打开/root/zipline文件夹，执行
docker-compose exec zipline yarn scripts:clear-zero-byte
按照提示操作
一键安装filebrowser平台 ​
  • 端口设置为3030了，其他登陆信息详见提示
  • filebrowser平台支持下载上传文件到服务器，批量下载多个文件(自定义压缩格式)，构建文件分享链接，设置分享时长
  • 如果本地有启用IPV6优先级可能绑定到V6去了，使用lsof -i:3030查看绑定情况，切换优先级后再安装就正常了
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/filebrowser.sh -o filebrowser.sh && chmod +x filebrowser.sh && bash filebrowser.sh
一键删除平台监控 ​
  • 一键移除大多数云服务器监控
  • 涵盖阿里云、腾讯云、华为云、UCLOUD、甲骨文云、京东云
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/dlm.sh -o dlm.sh && chmod +x dlm.shh && bash dlm.sh
部分手动命令 ​
一键开启root登陆并替换密码 ​
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
一键屏蔽邮件端口避免被恶意程序使用 ​
bash
iptables -A INPUT -p tcp --dport 25 -j DROP
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case2.md","filePath":"case/case2.md","lastUpdated":1747730955000}'),o={name:"case/case2.md"},p=n(`
仓库 ​
https://github.com/spiritLHLS/one-click-installation-script
Hits
所有脚本如需在国内服务器使用，请在链接前加上https://ghproxy.com/确保命令可以下载本仓库的shell脚本执行
一键修复脚本 ​
运行所有一键修复脚本前注意看说明，以及保证服务器无重要数据，运行后造成的一切后果作者不负任何责任，自行评判风险！
一键尝试修复apt源 ​
  • 支持系统：Ubuntu 12+，Debian 6+
  • 修复apt下载包进程意外退出导致的源锁死
  • 修复apt源broken损坏
  • 修复apt源多进程占用锁死
  • 修复apt源公钥缺失
  • 修复替换系统可用的apt源列表，国内用阿里源，国外用官方源
  • 修复本机的Ubuntu系统是EOL非长期维护的版本(奇数或陈旧的偶数版本)，将替换为Ubuntu官方的old-releases仓库以支持apt的使用
  • 修复只保证apt update不会报错，其他命令报错未修复
  • 如若修复后install还有问题，重启服务器解决问题
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/package.sh -o package.sh && chmod +x package.sh && bash package.sh
一键尝试修复系统时间 ​
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 由于系统时间不准确都是未进行时区时间同步造成的，使用chronyd进行时区时间同步后应当解决了问题
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/modify_time.sh -o modify_time.sh && chmod +x modify_time.sh && bash modify_time.sh
一键尝试修复sudo警告 ​
  • 一键尝试修复sudo: unable to resolve host xxx: Name or service not known警告(爆错)
不要在生产环境上使用该脚本，否则容易造成网络hosts配置错误，配置的host名字不在外网IP上反而在内网IP(127.0.0.1)上
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/check_sudo.sh -o check_sudo.sh && chmod +x check_sudo.sh && bash check_sudo.sh
一键修改系统自带的journal日志记录大小释放系统盘空间 ​
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 1.自定义修改大小，单位为MB，一般500或者1000即可，有的系统日志默认给了5000甚至更多，不是做站啥的没必要 
    • 请注意，修改journal目录大小会影响系统日志的记录，因此，在修改journal目录大小之前如果需要之前的日志，建议先备份系统日志到本地
  • 2.自定义修改设置系统日志保留日期时长，超过日期时长的日志将被清除
  • 3.默认修改日志只记录warning等级(无法自定义)
  • 4.以后日志的产生将受到日志文件大小，日志保留时间，日志保留等级的限制
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/resize_journal.sh -o resize_journal.sh && chmod +x resize_journal.sh && bash resize_journal.sh
一键尝试修复网络 ​
该脚本轻易勿要使用，请确保运行时服务器无重要文件或程序，出现运行bug后续可能需要重装系统
一定要在screen中执行该脚本，否则可能导致修改过程中ssh断链接而修改失败卡住最终SSH无法连接！不在screen中执行后果自负！
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 尝试修复nameserver为google源或cloudflare源
  • 尝试修复为IP类型对应的网络优先级(默认IPV4类型，纯V6类型再替换为IPV6类型)
bash
curl -L https://cdn.spiritlhl.workers.dev/https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/network.sh -o network.sh && chmod +x network.sh && bash network.sh
如果是纯V6的也可以不使用上面脚本的nat64，使用warp添加V4网络
比如：https://github.com/fscarmen/warp
bash
wget -N https://raw.githubusercontent.com/fscarmen/warp/main/menu.sh && bash menu.sh [option] [lisence]
非纯V6的，带V4切换优先级到IPV4可用以下命令
bash
sudo sed -i 's/.*precedence ::ffff:0:0\\/96.*/precedence ::ffff:0:0\\/96  100/g' /etc/gai.conf && sudo systemctl restart networking
一键环境安装脚本 ​
只推荐在新服务器上安装，环境不纯净不保证不出bug
运行所有一键环境安装脚本前注意看说明，以及保证服务器无重要数据，运行后造成的一切后果作者不负任何责任，自行评判风险！
一键安装jupyter环境 ​
  • 本脚本尝试使用Miniconda3安装虚拟环境jupyter-env再进行jupyter和jupyterlab的安装，如若安装机器不纯净勿要轻易使用本脚本！
  • 本脚本为实验性脚本可能会有各种bug，勿要轻易尝试！
  • 验证已支持的系统： 
    • Ubuntu 系 - 推荐，脚本自动挂起到后台
    • Debian 系 - 部分可能需要手动挂起到后台，详看脚本运行安装完毕的后续提示
  • 可能支持的系统(未验证)：centos 7+，Fedora，Almalinux 8.5+
  • 执行脚本，之前有用本脚本安装过则直接打印设置的登陆信息，没安装过则进行安装再打印信息，如果已安装但未启动则自动启动后再打印信息
  • 如果是初次安装无脑输入y回车即可，按照提示进行操作即可，安装完毕将在后台常驻运行，自动添加常用的安装包通道源
  • 安装完毕后，如果需要在lab中安装第三方库需要在lab中使用terminal并使用conda进行下载而不是pip3下载，这是需要注意的一点
  • 安装过程中有判断是否为中国IP，可选择是否使用中国镜像
原始用途是方便快捷的在按小时计费的超大型服务器上部署python环境进行科学计算，充分利用时间别浪费在构建环境上。
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/jupyter.sh -o jupyter.sh && chmod +x jupyter.sh && bash jupyter.sh
一键安装R语言环境 ​
  • 安装前需使用Miniconda3安装虚拟环境jupyter-env，然后进行jupyter和jupyterlab的安装，再然后才能安装本内核
  • 简单的说，需要执行本仓库对应的jupyter安装脚本再运行本脚本安装R语言环境，会自动安装R环境内核和图形设备支持库
  • x11可能需要手动启动一下，执行sudo /usr/bin/Xorg
  • 可能支持的系统(未验证)：centos 7+，Fedora，Almalinux 8.5+
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/R.sh -o R.sh && chmod +x R.sh && bash R.sh
一键安装rust环境 ​
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 加载官方脚本安装，前置条件适配系统以及后置条件判断安装的版本
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/rust.sh -o rust.sh && chmod +x rust.sh && bash rust.sh
一键安装C环境 ​
  • 一键安装C++环境
  • 支持系统：使用apt或者yum作为包管理器的系统
  • 如果未安装则安装，如果有安装则提示升级
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/cplusplus.sh -o cplusplus.sh && chmod +x cplusplus.sh && bash cplusplus.sh
一键安装vnstat环境 ​
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 加载官方文件编译安装，前置条件适配系统以及后置条件判断安装的版本
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/vnstat.sh -o vnstat.sh && chmod +x vnstat.sh && bash vnstat.sh
一键升级低版本debian为debian11 ​
  • 支持系统：debian 6+
  • 升级后需要重启系统加载内核，升级过程中需要选择的都无脑按回车即可
  • 升级是一个版本迭代一个版本，所以如果版本低，每执行一次升级一个版本，直至升级到debian11
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/todebian11.sh -o todebian11.sh && chmod +x todebian11.sh && bash todebian11.sh
一键升级低版本ubuntu为ubuntu22 ​
  • 支持系统：Ubuntu 16+
  • 升级后需要重启系统加载内核，升级过程中需要选择的都无脑按回车即可
  • 升级是一个版本迭代一个版本，所以如果版本低，每执行一次升级一个版本，直至升级到ubuntu22
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/toubuntu22.sh -o toubuntu22.sh && chmod +x toubuntu22.sh && bash toubuntu22.sh
一键安装zipline平台 ​
  • 应该支持的系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 暂时只在Ubuntu上验证无问题
  • 如若要设置反向代理绑定域名，安装前请保证原服务器未安装过nginx，如若已安装过nginx，请自行配置反向代理本机的3000端口
  • 默认一路回车是不启用反代不安装nginx的，自行选择，如需通过本脚本配置反代系统一定要未安装过nginx并在填写y或Y开启安装
  • zipline 平台功能: ShareX，自定义短链接，文件上传分享，多用户校验，高亮显示，阅后即焚，设置简单 (含pastebin)
  • 自动安装docker，docker-compose，如若已安装zipline在/root目录下，则自动更新
  • 反向代理如若已设置成功，还需要在面板设置中填写域名，绑定启用
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/zipline.sh -o zipline.sh && chmod +x zipline.sh && bash zipline.sh
如果需要删除0字节文件，打开/root/zipline文件夹，执行
docker-compose exec zipline yarn scripts:clear-zero-byte
按照提示操作
一键安装filebrowser平台 ​
  • 端口设置为3030了，其他登陆信息详见提示
  • filebrowser平台支持下载上传文件到服务器，批量下载多个文件(自定义压缩格式)，构建文件分享链接，设置分享时长
  • 如果本地有启用IPV6优先级可能绑定到V6去了，使用lsof -i:3030查看绑定情况，切换优先级后再安装就正常了
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/filebrowser.sh -o filebrowser.sh && chmod +x filebrowser.sh && bash filebrowser.sh
一键删除平台监控 ​
  • 一键移除大多数云服务器监控
  • 涵盖阿里云、腾讯云、华为云、UCLOUD、甲骨文云、京东云
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/dlm.sh -o dlm.sh && chmod +x dlm.shh && bash dlm.sh
部分手动命令 ​
一键开启root登陆并替换密码 ​
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
一键屏蔽邮件端口避免被恶意程序使用 ​
bash
iptables -A INPUT -p tcp --dport 25 -j DROP
 iptables -A OUTPUT -p tcp --dport 25 -j DROP
 /sbin/iptables-save
设置语言包 ​
bash
sudo apt-get update
 sudo apt-get install language-pack-en-base
diff --git a/assets/case_case2.md.d392b76a.lean.js b/assets/case_case2.md.729cbff7.lean.js
similarity index 99%
rename from assets/case_case2.md.d392b76a.lean.js
rename to assets/case_case2.md.729cbff7.lean.js
index 432c5ab4d9..8c67a15105 100644
--- a/assets/case_case2.md.d392b76a.lean.js
+++ b/assets/case_case2.md.729cbff7.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case2.md","filePath":"case/case2.md","lastUpdated":1747726389000}'),o={name:"case/case2.md"},p=n(`
仓库 ​
https://github.com/spiritLHLS/one-click-installation-script
Hits
所有脚本如需在国内服务器使用，请在链接前加上https://ghproxy.com/确保命令可以下载本仓库的shell脚本执行
一键修复脚本 ​
运行所有一键修复脚本前注意看说明，以及保证服务器无重要数据，运行后造成的一切后果作者不负任何责任，自行评判风险！
一键尝试修复apt源 ​
  • 支持系统：Ubuntu 12+，Debian 6+
  • 修复apt下载包进程意外退出导致的源锁死
  • 修复apt源broken损坏
  • 修复apt源多进程占用锁死
  • 修复apt源公钥缺失
  • 修复替换系统可用的apt源列表，国内用阿里源，国外用官方源
  • 修复本机的Ubuntu系统是EOL非长期维护的版本(奇数或陈旧的偶数版本)，将替换为Ubuntu官方的old-releases仓库以支持apt的使用
  • 修复只保证apt update不会报错，其他命令报错未修复
  • 如若修复后install还有问题，重启服务器解决问题
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/package.sh -o package.sh && chmod +x package.sh && bash package.sh
一键尝试修复系统时间 ​
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 由于系统时间不准确都是未进行时区时间同步造成的，使用chronyd进行时区时间同步后应当解决了问题
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/modify_time.sh -o modify_time.sh && chmod +x modify_time.sh && bash modify_time.sh
一键尝试修复sudo警告 ​
  • 一键尝试修复sudo: unable to resolve host xxx: Name or service not known警告(爆错)
不要在生产环境上使用该脚本，否则容易造成网络hosts配置错误，配置的host名字不在外网IP上反而在内网IP(127.0.0.1)上
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/check_sudo.sh -o check_sudo.sh && chmod +x check_sudo.sh && bash check_sudo.sh
一键修改系统自带的journal日志记录大小释放系统盘空间 ​
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 1.自定义修改大小，单位为MB，一般500或者1000即可，有的系统日志默认给了5000甚至更多，不是做站啥的没必要 
    • 请注意，修改journal目录大小会影响系统日志的记录，因此，在修改journal目录大小之前如果需要之前的日志，建议先备份系统日志到本地
  • 2.自定义修改设置系统日志保留日期时长，超过日期时长的日志将被清除
  • 3.默认修改日志只记录warning等级(无法自定义)
  • 4.以后日志的产生将受到日志文件大小，日志保留时间，日志保留等级的限制
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/resize_journal.sh -o resize_journal.sh && chmod +x resize_journal.sh && bash resize_journal.sh
一键尝试修复网络 ​
该脚本轻易勿要使用，请确保运行时服务器无重要文件或程序，出现运行bug后续可能需要重装系统
一定要在screen中执行该脚本，否则可能导致修改过程中ssh断链接而修改失败卡住最终SSH无法连接！不在screen中执行后果自负！
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 尝试修复nameserver为google源或cloudflare源
  • 尝试修复为IP类型对应的网络优先级(默认IPV4类型，纯V6类型再替换为IPV6类型)
bash
curl -L https://cdn.spiritlhl.workers.dev/https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/network.sh -o network.sh && chmod +x network.sh && bash network.sh
如果是纯V6的也可以不使用上面脚本的nat64，使用warp添加V4网络
比如：https://github.com/fscarmen/warp
bash
wget -N https://raw.githubusercontent.com/fscarmen/warp/main/menu.sh && bash menu.sh [option] [lisence]
非纯V6的，带V4切换优先级到IPV4可用以下命令
bash
sudo sed -i 's/.*precedence ::ffff:0:0\\/96.*/precedence ::ffff:0:0\\/96  100/g' /etc/gai.conf && sudo systemctl restart networking
一键环境安装脚本 ​
只推荐在新服务器上安装，环境不纯净不保证不出bug
运行所有一键环境安装脚本前注意看说明，以及保证服务器无重要数据，运行后造成的一切后果作者不负任何责任，自行评判风险！
一键安装jupyter环境 ​
  • 本脚本尝试使用Miniconda3安装虚拟环境jupyter-env再进行jupyter和jupyterlab的安装，如若安装机器不纯净勿要轻易使用本脚本！
  • 本脚本为实验性脚本可能会有各种bug，勿要轻易尝试！
  • 验证已支持的系统： 
    • Ubuntu 系 - 推荐，脚本自动挂起到后台
    • Debian 系 - 部分可能需要手动挂起到后台，详看脚本运行安装完毕的后续提示
  • 可能支持的系统(未验证)：centos 7+，Fedora，Almalinux 8.5+
  • 执行脚本，之前有用本脚本安装过则直接打印设置的登陆信息，没安装过则进行安装再打印信息，如果已安装但未启动则自动启动后再打印信息
  • 如果是初次安装无脑输入y回车即可，按照提示进行操作即可，安装完毕将在后台常驻运行，自动添加常用的安装包通道源
  • 安装完毕后，如果需要在lab中安装第三方库需要在lab中使用terminal并使用conda进行下载而不是pip3下载，这是需要注意的一点
  • 安装过程中有判断是否为中国IP，可选择是否使用中国镜像
原始用途是方便快捷的在按小时计费的超大型服务器上部署python环境进行科学计算，充分利用时间别浪费在构建环境上。
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/jupyter.sh -o jupyter.sh && chmod +x jupyter.sh && bash jupyter.sh
一键安装R语言环境 ​
  • 安装前需使用Miniconda3安装虚拟环境jupyter-env，然后进行jupyter和jupyterlab的安装，再然后才能安装本内核
  • 简单的说，需要执行本仓库对应的jupyter安装脚本再运行本脚本安装R语言环境，会自动安装R环境内核和图形设备支持库
  • x11可能需要手动启动一下，执行sudo /usr/bin/Xorg
  • 可能支持的系统(未验证)：centos 7+，Fedora，Almalinux 8.5+
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/R.sh -o R.sh && chmod +x R.sh && bash R.sh
一键安装rust环境 ​
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 加载官方脚本安装，前置条件适配系统以及后置条件判断安装的版本
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/rust.sh -o rust.sh && chmod +x rust.sh && bash rust.sh
一键安装C环境 ​
  • 一键安装C++环境
  • 支持系统：使用apt或者yum作为包管理器的系统
  • 如果未安装则安装，如果有安装则提示升级
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/cplusplus.sh -o cplusplus.sh && chmod +x cplusplus.sh && bash cplusplus.sh
一键安装vnstat环境 ​
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 加载官方文件编译安装，前置条件适配系统以及后置条件判断安装的版本
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/vnstat.sh -o vnstat.sh && chmod +x vnstat.sh && bash vnstat.sh
一键升级低版本debian为debian11 ​
  • 支持系统：debian 6+
  • 升级后需要重启系统加载内核，升级过程中需要选择的都无脑按回车即可
  • 升级是一个版本迭代一个版本，所以如果版本低，每执行一次升级一个版本，直至升级到debian11
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/todebian11.sh -o todebian11.sh && chmod +x todebian11.sh && bash todebian11.sh
一键升级低版本ubuntu为ubuntu22 ​
  • 支持系统：Ubuntu 16+
  • 升级后需要重启系统加载内核，升级过程中需要选择的都无脑按回车即可
  • 升级是一个版本迭代一个版本，所以如果版本低，每执行一次升级一个版本，直至升级到ubuntu22
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/toubuntu22.sh -o toubuntu22.sh && chmod +x toubuntu22.sh && bash toubuntu22.sh
一键安装zipline平台 ​
  • 应该支持的系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 暂时只在Ubuntu上验证无问题
  • 如若要设置反向代理绑定域名，安装前请保证原服务器未安装过nginx，如若已安装过nginx，请自行配置反向代理本机的3000端口
  • 默认一路回车是不启用反代不安装nginx的，自行选择，如需通过本脚本配置反代系统一定要未安装过nginx并在填写y或Y开启安装
  • zipline 平台功能: ShareX，自定义短链接，文件上传分享，多用户校验，高亮显示，阅后即焚，设置简单 (含pastebin)
  • 自动安装docker，docker-compose，如若已安装zipline在/root目录下，则自动更新
  • 反向代理如若已设置成功，还需要在面板设置中填写域名，绑定启用
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/zipline.sh -o zipline.sh && chmod +x zipline.sh && bash zipline.sh
如果需要删除0字节文件，打开/root/zipline文件夹，执行
docker-compose exec zipline yarn scripts:clear-zero-byte
按照提示操作
一键安装filebrowser平台 ​
  • 端口设置为3030了，其他登陆信息详见提示
  • filebrowser平台支持下载上传文件到服务器，批量下载多个文件(自定义压缩格式)，构建文件分享链接，设置分享时长
  • 如果本地有启用IPV6优先级可能绑定到V6去了，使用lsof -i:3030查看绑定情况，切换优先级后再安装就正常了
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/filebrowser.sh -o filebrowser.sh && chmod +x filebrowser.sh && bash filebrowser.sh
一键删除平台监控 ​
  • 一键移除大多数云服务器监控
  • 涵盖阿里云、腾讯云、华为云、UCLOUD、甲骨文云、京东云
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/dlm.sh -o dlm.sh && chmod +x dlm.shh && bash dlm.sh
部分手动命令 ​
一键开启root登陆并替换密码 ​
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
一键屏蔽邮件端口避免被恶意程序使用 ​
bash
iptables -A INPUT -p tcp --dport 25 -j DROP
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case2.md","filePath":"case/case2.md","lastUpdated":1747730955000}'),o={name:"case/case2.md"},p=n(`
仓库 ​
https://github.com/spiritLHLS/one-click-installation-script
Hits
所有脚本如需在国内服务器使用，请在链接前加上https://ghproxy.com/确保命令可以下载本仓库的shell脚本执行
一键修复脚本 ​
运行所有一键修复脚本前注意看说明，以及保证服务器无重要数据，运行后造成的一切后果作者不负任何责任，自行评判风险！
一键尝试修复apt源 ​
  • 支持系统：Ubuntu 12+，Debian 6+
  • 修复apt下载包进程意外退出导致的源锁死
  • 修复apt源broken损坏
  • 修复apt源多进程占用锁死
  • 修复apt源公钥缺失
  • 修复替换系统可用的apt源列表，国内用阿里源，国外用官方源
  • 修复本机的Ubuntu系统是EOL非长期维护的版本(奇数或陈旧的偶数版本)，将替换为Ubuntu官方的old-releases仓库以支持apt的使用
  • 修复只保证apt update不会报错，其他命令报错未修复
  • 如若修复后install还有问题，重启服务器解决问题
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/package.sh -o package.sh && chmod +x package.sh && bash package.sh
一键尝试修复系统时间 ​
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 由于系统时间不准确都是未进行时区时间同步造成的，使用chronyd进行时区时间同步后应当解决了问题
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/modify_time.sh -o modify_time.sh && chmod +x modify_time.sh && bash modify_time.sh
一键尝试修复sudo警告 ​
  • 一键尝试修复sudo: unable to resolve host xxx: Name or service not known警告(爆错)
不要在生产环境上使用该脚本，否则容易造成网络hosts配置错误，配置的host名字不在外网IP上反而在内网IP(127.0.0.1)上
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/check_sudo.sh -o check_sudo.sh && chmod +x check_sudo.sh && bash check_sudo.sh
一键修改系统自带的journal日志记录大小释放系统盘空间 ​
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 1.自定义修改大小，单位为MB，一般500或者1000即可，有的系统日志默认给了5000甚至更多，不是做站啥的没必要 
    • 请注意，修改journal目录大小会影响系统日志的记录，因此，在修改journal目录大小之前如果需要之前的日志，建议先备份系统日志到本地
  • 2.自定义修改设置系统日志保留日期时长，超过日期时长的日志将被清除
  • 3.默认修改日志只记录warning等级(无法自定义)
  • 4.以后日志的产生将受到日志文件大小，日志保留时间，日志保留等级的限制
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/resize_journal.sh -o resize_journal.sh && chmod +x resize_journal.sh && bash resize_journal.sh
一键尝试修复网络 ​
该脚本轻易勿要使用，请确保运行时服务器无重要文件或程序，出现运行bug后续可能需要重装系统
一定要在screen中执行该脚本，否则可能导致修改过程中ssh断链接而修改失败卡住最终SSH无法连接！不在screen中执行后果自负！
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 尝试修复nameserver为google源或cloudflare源
  • 尝试修复为IP类型对应的网络优先级(默认IPV4类型，纯V6类型再替换为IPV6类型)
bash
curl -L https://cdn.spiritlhl.workers.dev/https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/repair_scripts/network.sh -o network.sh && chmod +x network.sh && bash network.sh
如果是纯V6的也可以不使用上面脚本的nat64，使用warp添加V4网络
比如：https://github.com/fscarmen/warp
bash
wget -N https://raw.githubusercontent.com/fscarmen/warp/main/menu.sh && bash menu.sh [option] [lisence]
非纯V6的，带V4切换优先级到IPV4可用以下命令
bash
sudo sed -i 's/.*precedence ::ffff:0:0\\/96.*/precedence ::ffff:0:0\\/96  100/g' /etc/gai.conf && sudo systemctl restart networking
一键环境安装脚本 ​
只推荐在新服务器上安装，环境不纯净不保证不出bug
运行所有一键环境安装脚本前注意看说明，以及保证服务器无重要数据，运行后造成的一切后果作者不负任何责任，自行评判风险！
一键安装jupyter环境 ​
  • 本脚本尝试使用Miniconda3安装虚拟环境jupyter-env再进行jupyter和jupyterlab的安装，如若安装机器不纯净勿要轻易使用本脚本！
  • 本脚本为实验性脚本可能会有各种bug，勿要轻易尝试！
  • 验证已支持的系统： 
    • Ubuntu 系 - 推荐，脚本自动挂起到后台
    • Debian 系 - 部分可能需要手动挂起到后台，详看脚本运行安装完毕的后续提示
  • 可能支持的系统(未验证)：centos 7+，Fedora，Almalinux 8.5+
  • 执行脚本，之前有用本脚本安装过则直接打印设置的登陆信息，没安装过则进行安装再打印信息，如果已安装但未启动则自动启动后再打印信息
  • 如果是初次安装无脑输入y回车即可，按照提示进行操作即可，安装完毕将在后台常驻运行，自动添加常用的安装包通道源
  • 安装完毕后，如果需要在lab中安装第三方库需要在lab中使用terminal并使用conda进行下载而不是pip3下载，这是需要注意的一点
  • 安装过程中有判断是否为中国IP，可选择是否使用中国镜像
原始用途是方便快捷的在按小时计费的超大型服务器上部署python环境进行科学计算，充分利用时间别浪费在构建环境上。
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/jupyter.sh -o jupyter.sh && chmod +x jupyter.sh && bash jupyter.sh
一键安装R语言环境 ​
  • 安装前需使用Miniconda3安装虚拟环境jupyter-env，然后进行jupyter和jupyterlab的安装，再然后才能安装本内核
  • 简单的说，需要执行本仓库对应的jupyter安装脚本再运行本脚本安装R语言环境，会自动安装R环境内核和图形设备支持库
  • x11可能需要手动启动一下，执行sudo /usr/bin/Xorg
  • 可能支持的系统(未验证)：centos 7+，Fedora，Almalinux 8.5+
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/R.sh -o R.sh && chmod +x R.sh && bash R.sh
一键安装rust环境 ​
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 加载官方脚本安装，前置条件适配系统以及后置条件判断安装的版本
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/rust.sh -o rust.sh && chmod +x rust.sh && bash rust.sh
一键安装C环境 ​
  • 一键安装C++环境
  • 支持系统：使用apt或者yum作为包管理器的系统
  • 如果未安装则安装，如果有安装则提示升级
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/cplusplus.sh -o cplusplus.sh && chmod +x cplusplus.sh && bash cplusplus.sh
一键安装vnstat环境 ​
  • 支持系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 加载官方文件编译安装，前置条件适配系统以及后置条件判断安装的版本
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/vnstat.sh -o vnstat.sh && chmod +x vnstat.sh && bash vnstat.sh
一键升级低版本debian为debian11 ​
  • 支持系统：debian 6+
  • 升级后需要重启系统加载内核，升级过程中需要选择的都无脑按回车即可
  • 升级是一个版本迭代一个版本，所以如果版本低，每执行一次升级一个版本，直至升级到debian11
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/todebian11.sh -o todebian11.sh && chmod +x todebian11.sh && bash todebian11.sh
一键升级低版本ubuntu为ubuntu22 ​
  • 支持系统：Ubuntu 16+
  • 升级后需要重启系统加载内核，升级过程中需要选择的都无脑按回车即可
  • 升级是一个版本迭代一个版本，所以如果版本低，每执行一次升级一个版本，直至升级到ubuntu22
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/toubuntu22.sh -o toubuntu22.sh && chmod +x toubuntu22.sh && bash toubuntu22.sh
一键安装zipline平台 ​
  • 应该支持的系统：Ubuntu 18+，Debian 8+，centos 7+，Fedora，Almalinux 8.5+
  • 暂时只在Ubuntu上验证无问题
  • 如若要设置反向代理绑定域名，安装前请保证原服务器未安装过nginx，如若已安装过nginx，请自行配置反向代理本机的3000端口
  • 默认一路回车是不启用反代不安装nginx的，自行选择，如需通过本脚本配置反代系统一定要未安装过nginx并在填写y或Y开启安装
  • zipline 平台功能: ShareX，自定义短链接，文件上传分享，多用户校验，高亮显示，阅后即焚，设置简单 (含pastebin)
  • 自动安装docker，docker-compose，如若已安装zipline在/root目录下，则自动更新
  • 反向代理如若已设置成功，还需要在面板设置中填写域名，绑定启用
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/zipline.sh -o zipline.sh && chmod +x zipline.sh && bash zipline.sh
如果需要删除0字节文件，打开/root/zipline文件夹，执行
docker-compose exec zipline yarn scripts:clear-zero-byte
按照提示操作
一键安装filebrowser平台 ​
  • 端口设置为3030了，其他登陆信息详见提示
  • filebrowser平台支持下载上传文件到服务器，批量下载多个文件(自定义压缩格式)，构建文件分享链接，设置分享时长
  • 如果本地有启用IPV6优先级可能绑定到V6去了，使用lsof -i:3030查看绑定情况，切换优先级后再安装就正常了
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/filebrowser.sh -o filebrowser.sh && chmod +x filebrowser.sh && bash filebrowser.sh
一键删除平台监控 ​
  • 一键移除大多数云服务器监控
  • 涵盖阿里云、腾讯云、华为云、UCLOUD、甲骨文云、京东云
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/one-click-installation-script/main/install_scripts/dlm.sh -o dlm.sh && chmod +x dlm.shh && bash dlm.sh
部分手动命令 ​
一键开启root登陆并替换密码 ​
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
一键屏蔽邮件端口避免被恶意程序使用 ​
bash
iptables -A INPUT -p tcp --dport 25 -j DROP
 iptables -A OUTPUT -p tcp --dport 25 -j DROP
 /sbin/iptables-save
设置语言包 ​
bash
sudo apt-get update
 sudo apt-get install language-pack-en-base
diff --git a/assets/case_case3.md.ca43af74.js b/assets/case_case3.md.abbe9b04.js
similarity index 99%
rename from assets/case_case3.md.ca43af74.js
rename to assets/case_case3.md.abbe9b04.js
index fb6cfcd5ad..98d2ab1187 100644
--- a/assets/case_case3.md.ca43af74.js
+++ b/assets/case_case3.md.abbe9b04.js
@@ -1 +1 @@
-import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case3.md","filePath":"case/case3.md","lastUpdated":1747726389000}'),p={name:"case/case3.md"},n=a('
仓库 ​
https://github.com/spiritLHLS/ecsspeed
Hits
ecsspeed ​
自动更新测速服务器节点列表的网络基准测试脚本
Network benchmarking script that automatically updates the list of speed measurement server nodes
说明 ​
所有组件以及数据均来源于平台或已有的开源项目，无非开源部分，放心食用
对应 speedtest.net 的自动更新测速服务器ID的测速脚本 ​
日常推荐使用
bash <(wget -qO- bash.spiritlhl.net/ecs-net)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-net.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-net.sh)
支持测速的架构：i386, x86_64, amd64, arm64, s390x, riscv64, ppc64le, ppc64
涵盖中国三大运营商、香港、台湾的测速节点，默认的三网测速每个运营商选择本机ping值最低的两个节点测速，详情三网测速才是全测，节点列表大概每7天自动更新一次。
支持国内服务器测试(有判断是否为国内机器)，但由于国内服务器带宽过小，会很慢，详见初次运行的显示
当官方CLI安装失败(如罕见的架构或者官方网站访问失败时)自动使用 speedtest-go 作为替代品测速
对应 speedtest.cn 的自动更新测速服务器ID的测速脚本 ​
单线程测速
bash <(wget -qO- bash.spiritlhl.net/ecs-cn)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-cn.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-cn.sh)
支持测速的架构：i386, x86_64, amd64, arm64, s390x, riscv64, ppc64le, ppc64
涵盖中国三大运营商、香港、台湾的测速节点，默认的三网测速每个运营商选择本机ping值最低的两个节点测速，详情三网测速才是全测，节点列表每天自动更新一次。
支持国内服务器测试(有判断是否为国内机器)，但由于国内服务器带宽过小，会很慢，详见初次运行的显示
自动更新测试服务器列表的三网延迟测试脚本 ​
平均耗时10~15秒
bash <(wget -qO- bash.spiritlhl.net/ecs-ping)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-ping.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-ping.sh)
效果图
图片
功能 ​
  • [x] 自动抓取 speedtest.cn 节点信息结合已有信息去重并更新列表数据
  • [x] 自动抓取 speedtest.net 节点信息结合已有信息去重并更新列表数据
  • [x] 对应 speedtest.net 的自动更新测速服务器列表的测速脚本
  • [x] 对应 speedtest.cn 的自动更新测速服务器列表的测速脚本
  • [x] 自动更新测试服务器列表的三网Ping值测试脚本
.cn数据 ​
仓库：https://github.com/spiritLHLS/speedtest.cn-CN-ID
.net数据 ​
仓库：https://github.com/spiritLHLS/speedtest.net-CN-ID
',44),i=[n];function r(c,l,o,h,d,g){return t(),s("div",null,i)}const m=e(p,[["render",r]]);export{u as __pageData,m as default};
+import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case3.md","filePath":"case/case3.md","lastUpdated":1747730955000}'),p={name:"case/case3.md"},n=a('
仓库 ​
https://github.com/spiritLHLS/ecsspeed
Hits
ecsspeed ​
自动更新测速服务器节点列表的网络基准测试脚本
Network benchmarking script that automatically updates the list of speed measurement server nodes
说明 ​
所有组件以及数据均来源于平台或已有的开源项目，无非开源部分，放心食用
对应 speedtest.net 的自动更新测速服务器ID的测速脚本 ​
日常推荐使用
bash <(wget -qO- bash.spiritlhl.net/ecs-net)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-net.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-net.sh)
支持测速的架构：i386, x86_64, amd64, arm64, s390x, riscv64, ppc64le, ppc64
涵盖中国三大运营商、香港、台湾的测速节点，默认的三网测速每个运营商选择本机ping值最低的两个节点测速，详情三网测速才是全测，节点列表大概每7天自动更新一次。
支持国内服务器测试(有判断是否为国内机器)，但由于国内服务器带宽过小，会很慢，详见初次运行的显示
当官方CLI安装失败(如罕见的架构或者官方网站访问失败时)自动使用 speedtest-go 作为替代品测速
对应 speedtest.cn 的自动更新测速服务器ID的测速脚本 ​
单线程测速
bash <(wget -qO- bash.spiritlhl.net/ecs-cn)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-cn.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-cn.sh)
支持测速的架构：i386, x86_64, amd64, arm64, s390x, riscv64, ppc64le, ppc64
涵盖中国三大运营商、香港、台湾的测速节点，默认的三网测速每个运营商选择本机ping值最低的两个节点测速，详情三网测速才是全测，节点列表每天自动更新一次。
支持国内服务器测试(有判断是否为国内机器)，但由于国内服务器带宽过小，会很慢，详见初次运行的显示
自动更新测试服务器列表的三网延迟测试脚本 ​
平均耗时10~15秒
bash <(wget -qO- bash.spiritlhl.net/ecs-ping)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-ping.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-ping.sh)
效果图
图片
功能 ​
  • [x] 自动抓取 speedtest.cn 节点信息结合已有信息去重并更新列表数据
  • [x] 自动抓取 speedtest.net 节点信息结合已有信息去重并更新列表数据
  • [x] 对应 speedtest.net 的自动更新测速服务器列表的测速脚本
  • [x] 对应 speedtest.cn 的自动更新测速服务器列表的测速脚本
  • [x] 自动更新测试服务器列表的三网Ping值测试脚本
.cn数据 ​
仓库：https://github.com/spiritLHLS/speedtest.cn-CN-ID
.net数据 ​
仓库：https://github.com/spiritLHLS/speedtest.net-CN-ID
',44),i=[n];function r(c,l,o,h,d,g){return t(),s("div",null,i)}const m=e(p,[["render",r]]);export{u as __pageData,m as default};
diff --git a/assets/case_case3.md.ca43af74.lean.js b/assets/case_case3.md.abbe9b04.lean.js
similarity index 99%
rename from assets/case_case3.md.ca43af74.lean.js
rename to assets/case_case3.md.abbe9b04.lean.js
index fb6cfcd5ad..98d2ab1187 100644
--- a/assets/case_case3.md.ca43af74.lean.js
+++ b/assets/case_case3.md.abbe9b04.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case3.md","filePath":"case/case3.md","lastUpdated":1747726389000}'),p={name:"case/case3.md"},n=a('
仓库 ​
https://github.com/spiritLHLS/ecsspeed
Hits
ecsspeed ​
自动更新测速服务器节点列表的网络基准测试脚本
Network benchmarking script that automatically updates the list of speed measurement server nodes
说明 ​
所有组件以及数据均来源于平台或已有的开源项目，无非开源部分，放心食用
对应 speedtest.net 的自动更新测速服务器ID的测速脚本 ​
日常推荐使用
bash <(wget -qO- bash.spiritlhl.net/ecs-net)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-net.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-net.sh)
支持测速的架构：i386, x86_64, amd64, arm64, s390x, riscv64, ppc64le, ppc64
涵盖中国三大运营商、香港、台湾的测速节点，默认的三网测速每个运营商选择本机ping值最低的两个节点测速，详情三网测速才是全测，节点列表大概每7天自动更新一次。
支持国内服务器测试(有判断是否为国内机器)，但由于国内服务器带宽过小，会很慢，详见初次运行的显示
当官方CLI安装失败(如罕见的架构或者官方网站访问失败时)自动使用 speedtest-go 作为替代品测速
对应 speedtest.cn 的自动更新测速服务器ID的测速脚本 ​
单线程测速
bash <(wget -qO- bash.spiritlhl.net/ecs-cn)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-cn.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-cn.sh)
支持测速的架构：i386, x86_64, amd64, arm64, s390x, riscv64, ppc64le, ppc64
涵盖中国三大运营商、香港、台湾的测速节点，默认的三网测速每个运营商选择本机ping值最低的两个节点测速，详情三网测速才是全测，节点列表每天自动更新一次。
支持国内服务器测试(有判断是否为国内机器)，但由于国内服务器带宽过小，会很慢，详见初次运行的显示
自动更新测试服务器列表的三网延迟测试脚本 ​
平均耗时10~15秒
bash <(wget -qO- bash.spiritlhl.net/ecs-ping)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-ping.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-ping.sh)
效果图
图片
功能 ​
  • [x] 自动抓取 speedtest.cn 节点信息结合已有信息去重并更新列表数据
  • [x] 自动抓取 speedtest.net 节点信息结合已有信息去重并更新列表数据
  • [x] 对应 speedtest.net 的自动更新测速服务器列表的测速脚本
  • [x] 对应 speedtest.cn 的自动更新测速服务器列表的测速脚本
  • [x] 自动更新测试服务器列表的三网Ping值测试脚本
.cn数据 ​
仓库：https://github.com/spiritLHLS/speedtest.cn-CN-ID
.net数据 ​
仓库：https://github.com/spiritLHLS/speedtest.net-CN-ID
',44),i=[n];function r(c,l,o,h,d,g){return t(),s("div",null,i)}const m=e(p,[["render",r]]);export{u as __pageData,m as default};
+import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case3.md","filePath":"case/case3.md","lastUpdated":1747730955000}'),p={name:"case/case3.md"},n=a('
仓库 ​
https://github.com/spiritLHLS/ecsspeed
Hits
ecsspeed ​
自动更新测速服务器节点列表的网络基准测试脚本
Network benchmarking script that automatically updates the list of speed measurement server nodes
说明 ​
所有组件以及数据均来源于平台或已有的开源项目，无非开源部分，放心食用
对应 speedtest.net 的自动更新测速服务器ID的测速脚本 ​
日常推荐使用
bash <(wget -qO- bash.spiritlhl.net/ecs-net)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-net.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-net.sh)
支持测速的架构：i386, x86_64, amd64, arm64, s390x, riscv64, ppc64le, ppc64
涵盖中国三大运营商、香港、台湾的测速节点，默认的三网测速每个运营商选择本机ping值最低的两个节点测速，详情三网测速才是全测，节点列表大概每7天自动更新一次。
支持国内服务器测试(有判断是否为国内机器)，但由于国内服务器带宽过小，会很慢，详见初次运行的显示
当官方CLI安装失败(如罕见的架构或者官方网站访问失败时)自动使用 speedtest-go 作为替代品测速
对应 speedtest.cn 的自动更新测速服务器ID的测速脚本 ​
单线程测速
bash <(wget -qO- bash.spiritlhl.net/ecs-cn)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-cn.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-cn.sh)
支持测速的架构：i386, x86_64, amd64, arm64, s390x, riscv64, ppc64le, ppc64
涵盖中国三大运营商、香港、台湾的测速节点，默认的三网测速每个运营商选择本机ping值最低的两个节点测速，详情三网测速才是全测，节点列表每天自动更新一次。
支持国内服务器测试(有判断是否为国内机器)，但由于国内服务器带宽过小，会很慢，详见初次运行的显示
自动更新测试服务器列表的三网延迟测试脚本 ​
平均耗时10~15秒
bash <(wget -qO- bash.spiritlhl.net/ecs-ping)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-ping.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-ping.sh)
效果图
图片
功能 ​
  • [x] 自动抓取 speedtest.cn 节点信息结合已有信息去重并更新列表数据
  • [x] 自动抓取 speedtest.net 节点信息结合已有信息去重并更新列表数据
  • [x] 对应 speedtest.net 的自动更新测速服务器列表的测速脚本
  • [x] 对应 speedtest.cn 的自动更新测速服务器列表的测速脚本
  • [x] 自动更新测试服务器列表的三网Ping值测试脚本
.cn数据 ​
仓库：https://github.com/spiritLHLS/speedtest.cn-CN-ID
.net数据 ​
仓库：https://github.com/spiritLHLS/speedtest.net-CN-ID
',44),i=[n];function r(c,l,o,h,d,g){return t(),s("div",null,i)}const m=e(p,[["render",r]]);export{u as __pageData,m as default};
diff --git a/assets/case_case4.md.857b10dc.js b/assets/case_case4.md.c7b0e7d9.js
similarity index 98%
rename from assets/case_case4.md.857b10dc.js
rename to assets/case_case4.md.c7b0e7d9.js
index a998fec4bc..81b618c765 100644
--- a/assets/case_case4.md.857b10dc.js
+++ b/assets/case_case4.md.c7b0e7d9.js
@@ -1 +1 @@
-import{_ as a,v as e,b as t,R as r}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case4.md","filePath":"case/case4.md","lastUpdated":1747726389000}'),c={name:"case/case4.md"},s=r('
仓库 ​
https://github.com/oneclickvirt/backtrace
Hits
backtrace ​
三网回程路由线路测试
基于 https://github.com/zhanghanyun/backtrace 的重构和优化，与原版存在很大不同
路由的线路判断最终还是得人工判断的才准确，本项目测试结果仅供参考
功能 ​
  • [x] 检测回程显示IPV4地址时的线路，不显示IP地址时显示ASN检测不到，原版backtrace也支持
  • [x] 支持对4837、9929和163线路的判断，原版backtrace也支持
  • [x] 支持对CN2GT和CN2GIA线路的判断，原版backtrace不支持
  • [x] 支持对CMIN2和CMI线路的判断，原版backtrace不支持
  • [x] 支持对整个回程路由进行线路分析，与原版backtrace仅进行一次判断不同
  • [x] 修复原版backtrace对IPV4地址信息获取时json解析失败依然打印信息的问题
  • [x] 增加对全平台的编译支持，原版backtrace仅支持linux平台的amd64和arm64架构
使用 ​
shell
curl https://raw.githubusercontent.com/oneclickvirt/backtrace/main/backtrace_install.sh -sSf | sh
更多架构请查看 https://github.com/oneclickvirt/backtrace/releases/tag/output
概览图 ​
图片
图片
图片
',16),n=[s];function l(o,h,i,p,b,d){return e(),t("div",null,n)}const f=a(c,[["render",l]]);export{u as __pageData,f as default};
+import{_ as a,v as e,b as t,R as r}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case4.md","filePath":"case/case4.md","lastUpdated":1747730955000}'),c={name:"case/case4.md"},s=r('
仓库 ​
https://github.com/oneclickvirt/backtrace
Hits
backtrace ​
三网回程路由线路测试
基于 https://github.com/zhanghanyun/backtrace 的重构和优化，与原版存在很大不同
路由的线路判断最终还是得人工判断的才准确，本项目测试结果仅供参考
功能 ​
  • [x] 检测回程显示IPV4地址时的线路，不显示IP地址时显示ASN检测不到，原版backtrace也支持
  • [x] 支持对4837、9929和163线路的判断，原版backtrace也支持
  • [x] 支持对CN2GT和CN2GIA线路的判断，原版backtrace不支持
  • [x] 支持对CMIN2和CMI线路的判断，原版backtrace不支持
  • [x] 支持对整个回程路由进行线路分析，与原版backtrace仅进行一次判断不同
  • [x] 修复原版backtrace对IPV4地址信息获取时json解析失败依然打印信息的问题
  • [x] 增加对全平台的编译支持，原版backtrace仅支持linux平台的amd64和arm64架构
使用 ​
shell
curl https://raw.githubusercontent.com/oneclickvirt/backtrace/main/backtrace_install.sh -sSf | sh
更多架构请查看 https://github.com/oneclickvirt/backtrace/releases/tag/output
概览图 ​
图片
图片
图片
',16),n=[s];function l(o,h,i,p,b,d){return e(),t("div",null,n)}const f=a(c,[["render",l]]);export{u as __pageData,f as default};
diff --git a/assets/case_case4.md.857b10dc.lean.js b/assets/case_case4.md.c7b0e7d9.lean.js
similarity index 98%
rename from assets/case_case4.md.857b10dc.lean.js
rename to assets/case_case4.md.c7b0e7d9.lean.js
index a998fec4bc..81b618c765 100644
--- a/assets/case_case4.md.857b10dc.lean.js
+++ b/assets/case_case4.md.c7b0e7d9.lean.js
@@ -1 +1 @@
-import{_ as a,v as e,b as t,R as r}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case4.md","filePath":"case/case4.md","lastUpdated":1747726389000}'),c={name:"case/case4.md"},s=r('
仓库 ​
https://github.com/oneclickvirt/backtrace
Hits
backtrace ​
三网回程路由线路测试
基于 https://github.com/zhanghanyun/backtrace 的重构和优化，与原版存在很大不同
路由的线路判断最终还是得人工判断的才准确，本项目测试结果仅供参考
功能 ​
  • [x] 检测回程显示IPV4地址时的线路，不显示IP地址时显示ASN检测不到，原版backtrace也支持
  • [x] 支持对4837、9929和163线路的判断，原版backtrace也支持
  • [x] 支持对CN2GT和CN2GIA线路的判断，原版backtrace不支持
  • [x] 支持对CMIN2和CMI线路的判断，原版backtrace不支持
  • [x] 支持对整个回程路由进行线路分析，与原版backtrace仅进行一次判断不同
  • [x] 修复原版backtrace对IPV4地址信息获取时json解析失败依然打印信息的问题
  • [x] 增加对全平台的编译支持，原版backtrace仅支持linux平台的amd64和arm64架构
使用 ​
shell
curl https://raw.githubusercontent.com/oneclickvirt/backtrace/main/backtrace_install.sh -sSf | sh
更多架构请查看 https://github.com/oneclickvirt/backtrace/releases/tag/output
概览图 ​
图片
图片
图片
',16),n=[s];function l(o,h,i,p,b,d){return e(),t("div",null,n)}const f=a(c,[["render",l]]);export{u as __pageData,f as default};
+import{_ as a,v as e,b as t,R as r}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case4.md","filePath":"case/case4.md","lastUpdated":1747730955000}'),c={name:"case/case4.md"},s=r('
仓库 ​
https://github.com/oneclickvirt/backtrace
Hits
backtrace ​
三网回程路由线路测试
基于 https://github.com/zhanghanyun/backtrace 的重构和优化，与原版存在很大不同
路由的线路判断最终还是得人工判断的才准确，本项目测试结果仅供参考
功能 ​
  • [x] 检测回程显示IPV4地址时的线路，不显示IP地址时显示ASN检测不到，原版backtrace也支持
  • [x] 支持对4837、9929和163线路的判断，原版backtrace也支持
  • [x] 支持对CN2GT和CN2GIA线路的判断，原版backtrace不支持
  • [x] 支持对CMIN2和CMI线路的判断，原版backtrace不支持
  • [x] 支持对整个回程路由进行线路分析，与原版backtrace仅进行一次判断不同
  • [x] 修复原版backtrace对IPV4地址信息获取时json解析失败依然打印信息的问题
  • [x] 增加对全平台的编译支持，原版backtrace仅支持linux平台的amd64和arm64架构
使用 ​
shell
curl https://raw.githubusercontent.com/oneclickvirt/backtrace/main/backtrace_install.sh -sSf | sh
更多架构请查看 https://github.com/oneclickvirt/backtrace/releases/tag/output
概览图 ​
图片
图片
图片
',16),n=[s];function l(o,h,i,p,b,d){return e(),t("div",null,n)}const f=a(c,[["render",l]]);export{u as __pageData,f as default};
diff --git a/assets/case_case5.md.f59a0f5e.js b/assets/case_case5.md.555f9215.js
similarity index 99%
rename from assets/case_case5.md.f59a0f5e.js
rename to assets/case_case5.md.555f9215.js
index 1bf87ac889..30c1b34cee 100644
--- a/assets/case_case5.md.f59a0f5e.js
+++ b/assets/case_case5.md.555f9215.js
@@ -1 +1 @@
-import{_ as e,v as a,b as s,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case5.md","filePath":"case/case5.md","lastUpdated":1747726389000}'),i={name:"case/case5.md"},l=t('
仓库 ​
https://github.com/spiritLHLS/Oracle-server-keep-alive-script
Hits
Oracle-server-keep-alive-script ​
实际不止可以在甲骨文服务器上使用，也可以使用在任意ARM或X86_64架构的系统，用作资源占用
甲骨文服务器保活脚本 ​
适配系统：已在Ubuntu 20+，Debian 10+, Centos 7+, Oracle linux 8+，AlmaLinux 8.5+
上述系统验证无问题，别的主流系统应该也没有问题
可选占用：CPU，内存，带宽
安装完毕后如果有问题请卸载脚本反馈问题(重复卸载也没问题)
所有资源(除了CPU)可选默认配置则动态占用，实时调整，避免服务器有别的任何资源已经超过限额了仍然再占用资源
为避免GitHub的CDN抽风加载不了新内容，所有新更新已使用Gitlab仓库
由于speedtest-go的release依赖于GitHub，所以请检查 www.githubstatus.com ,有问题时无法安装带宽占用
基础开发完毕，测试中，有问题请在issues中反馈 ​
选项1安装，选项2卸载，选项3更新安装引导脚本，选项4退出脚本
安装过程中无脑回车则全部可选的占用都占用，不需要什么占用输入n再回车
如果选择带宽占用，会询问使用speedtest-go占用还是使用wget占用，按照提示进行选择即可
有询问是否需要带宽占用的参数自定义，这时候默认选项就是n，回车就使用默认配置，输入y再回车则需要按照提示自定义参数
curl -L https://gitlab.com/spiritysdx/Oracle-server-keep-alive-script/-/raw/main/oalive.sh -o oalive.sh && chmod +x oalive.sh && bash oalive.sh
或
bash oalive.sh
或
bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/Oracle-server-keep-alive-script/-/raw/main/oalive.sh)
说明 ​
  • 提供两种CPU占用模式：DD模拟占用和科学计算模式，用户可以自由选择，占用范围设置在15%至25%之间，更推荐DD模拟占用
  • DD模拟占用在守护进程中设置了CPU占用的最高限制
  • 默认情况下，CPU占用设置为25%最高值，计算方法是核数乘以12%，如果计算结果低于25%，则设置为该值；如果计算结果高于25%，则按照计算结果的比例进行设置。
  • 内存占用设置为占用总内存的20%，占用时间为300秒，休息时间为300秒。
  • 每300秒检测一次内存占用情况，并根据需要动态调整占用大小。如果内存占用已经大于20%，则不增加占用。
  • 在占用过程中，使用守护进程和开机自启服务，以确保占用任务持续且有效。
  • 默认选项的带宽占用每45分钟下载一次大小在1G至10G之间的文件，只进行下载而不保存。在下载过程中会占用硬盘空间，但在下载完成后会自动释放。
  • 默认选项的带宽占用动态调整实际下载的带宽/速率，限制每次下载的最长时长为6分钟。在每次下载之前，会测试最大可用带宽，并根据实时结果将下载速率设置为30%的带宽。
  • 带宽占用测试使用了speedtest-cli和speedtest-go两种工具，以防其中之一不可用时使用第二种工具，用户可以自定义设置带宽占用，此时详见设置提示。
  • 提供一键卸载所有占用服务的选项，卸载将删除所有脚本、服务、任务、守护进程和开机自启设置。
  • 提供一键检查更新的功能，更新范围仅限于脚本更新。请在更新后重新设置占用服务
  • 对所有进程执行增加唯一性检测，避免重复运行，使用PID文件进行判断。
如若不希望一键的，希望自定义设置时间的，请查看README_CRON.md自行设置定时任务
',26),r=[l];function p(c,o,n,h,d,u){return a(),s("div",null,r)}const v=e(i,[["render",p]]);export{m as __pageData,v as default};
+import{_ as e,v as a,b as s,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case5.md","filePath":"case/case5.md","lastUpdated":1747730955000}'),i={name:"case/case5.md"},l=t('
仓库 ​
https://github.com/spiritLHLS/Oracle-server-keep-alive-script
Hits
Oracle-server-keep-alive-script ​
实际不止可以在甲骨文服务器上使用，也可以使用在任意ARM或X86_64架构的系统，用作资源占用
甲骨文服务器保活脚本 ​
适配系统：已在Ubuntu 20+，Debian 10+, Centos 7+, Oracle linux 8+，AlmaLinux 8.5+
上述系统验证无问题，别的主流系统应该也没有问题
可选占用：CPU，内存，带宽
安装完毕后如果有问题请卸载脚本反馈问题(重复卸载也没问题)
所有资源(除了CPU)可选默认配置则动态占用，实时调整，避免服务器有别的任何资源已经超过限额了仍然再占用资源
为避免GitHub的CDN抽风加载不了新内容，所有新更新已使用Gitlab仓库
由于speedtest-go的release依赖于GitHub，所以请检查 www.githubstatus.com ,有问题时无法安装带宽占用
基础开发完毕，测试中，有问题请在issues中反馈 ​
选项1安装，选项2卸载，选项3更新安装引导脚本，选项4退出脚本
安装过程中无脑回车则全部可选的占用都占用，不需要什么占用输入n再回车
如果选择带宽占用，会询问使用speedtest-go占用还是使用wget占用，按照提示进行选择即可
有询问是否需要带宽占用的参数自定义，这时候默认选项就是n，回车就使用默认配置，输入y再回车则需要按照提示自定义参数
curl -L https://gitlab.com/spiritysdx/Oracle-server-keep-alive-script/-/raw/main/oalive.sh -o oalive.sh && chmod +x oalive.sh && bash oalive.sh
或
bash oalive.sh
或
bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/Oracle-server-keep-alive-script/-/raw/main/oalive.sh)
说明 ​
  • 提供两种CPU占用模式：DD模拟占用和科学计算模式，用户可以自由选择，占用范围设置在15%至25%之间，更推荐DD模拟占用
  • DD模拟占用在守护进程中设置了CPU占用的最高限制
  • 默认情况下，CPU占用设置为25%最高值，计算方法是核数乘以12%，如果计算结果低于25%，则设置为该值；如果计算结果高于25%，则按照计算结果的比例进行设置。
  • 内存占用设置为占用总内存的20%，占用时间为300秒，休息时间为300秒。
  • 每300秒检测一次内存占用情况，并根据需要动态调整占用大小。如果内存占用已经大于20%，则不增加占用。
  • 在占用过程中，使用守护进程和开机自启服务，以确保占用任务持续且有效。
  • 默认选项的带宽占用每45分钟下载一次大小在1G至10G之间的文件，只进行下载而不保存。在下载过程中会占用硬盘空间，但在下载完成后会自动释放。
  • 默认选项的带宽占用动态调整实际下载的带宽/速率，限制每次下载的最长时长为6分钟。在每次下载之前，会测试最大可用带宽，并根据实时结果将下载速率设置为30%的带宽。
  • 带宽占用测试使用了speedtest-cli和speedtest-go两种工具，以防其中之一不可用时使用第二种工具，用户可以自定义设置带宽占用，此时详见设置提示。
  • 提供一键卸载所有占用服务的选项，卸载将删除所有脚本、服务、任务、守护进程和开机自启设置。
  • 提供一键检查更新的功能，更新范围仅限于脚本更新。请在更新后重新设置占用服务
  • 对所有进程执行增加唯一性检测，避免重复运行，使用PID文件进行判断。
如若不希望一键的，希望自定义设置时间的，请查看README_CRON.md自行设置定时任务
',26),r=[l];function p(c,o,n,h,d,u){return a(),s("div",null,r)}const v=e(i,[["render",p]]);export{m as __pageData,v as default};
diff --git a/assets/case_case5.md.f59a0f5e.lean.js b/assets/case_case5.md.555f9215.lean.js
similarity index 99%
rename from assets/case_case5.md.f59a0f5e.lean.js
rename to assets/case_case5.md.555f9215.lean.js
index 1bf87ac889..30c1b34cee 100644
--- a/assets/case_case5.md.f59a0f5e.lean.js
+++ b/assets/case_case5.md.555f9215.lean.js
@@ -1 +1 @@
-import{_ as e,v as a,b as s,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case5.md","filePath":"case/case5.md","lastUpdated":1747726389000}'),i={name:"case/case5.md"},l=t('
仓库 ​
https://github.com/spiritLHLS/Oracle-server-keep-alive-script
Hits
Oracle-server-keep-alive-script ​
实际不止可以在甲骨文服务器上使用，也可以使用在任意ARM或X86_64架构的系统，用作资源占用
甲骨文服务器保活脚本 ​
适配系统：已在Ubuntu 20+，Debian 10+, Centos 7+, Oracle linux 8+，AlmaLinux 8.5+
上述系统验证无问题，别的主流系统应该也没有问题
可选占用：CPU，内存，带宽
安装完毕后如果有问题请卸载脚本反馈问题(重复卸载也没问题)
所有资源(除了CPU)可选默认配置则动态占用，实时调整，避免服务器有别的任何资源已经超过限额了仍然再占用资源
为避免GitHub的CDN抽风加载不了新内容，所有新更新已使用Gitlab仓库
由于speedtest-go的release依赖于GitHub，所以请检查 www.githubstatus.com ,有问题时无法安装带宽占用
基础开发完毕，测试中，有问题请在issues中反馈 ​
选项1安装，选项2卸载，选项3更新安装引导脚本，选项4退出脚本
安装过程中无脑回车则全部可选的占用都占用，不需要什么占用输入n再回车
如果选择带宽占用，会询问使用speedtest-go占用还是使用wget占用，按照提示进行选择即可
有询问是否需要带宽占用的参数自定义，这时候默认选项就是n，回车就使用默认配置，输入y再回车则需要按照提示自定义参数
curl -L https://gitlab.com/spiritysdx/Oracle-server-keep-alive-script/-/raw/main/oalive.sh -o oalive.sh && chmod +x oalive.sh && bash oalive.sh
或
bash oalive.sh
或
bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/Oracle-server-keep-alive-script/-/raw/main/oalive.sh)
说明 ​
  • 提供两种CPU占用模式：DD模拟占用和科学计算模式，用户可以自由选择，占用范围设置在15%至25%之间，更推荐DD模拟占用
  • DD模拟占用在守护进程中设置了CPU占用的最高限制
  • 默认情况下，CPU占用设置为25%最高值，计算方法是核数乘以12%，如果计算结果低于25%，则设置为该值；如果计算结果高于25%，则按照计算结果的比例进行设置。
  • 内存占用设置为占用总内存的20%，占用时间为300秒，休息时间为300秒。
  • 每300秒检测一次内存占用情况，并根据需要动态调整占用大小。如果内存占用已经大于20%，则不增加占用。
  • 在占用过程中，使用守护进程和开机自启服务，以确保占用任务持续且有效。
  • 默认选项的带宽占用每45分钟下载一次大小在1G至10G之间的文件，只进行下载而不保存。在下载过程中会占用硬盘空间，但在下载完成后会自动释放。
  • 默认选项的带宽占用动态调整实际下载的带宽/速率，限制每次下载的最长时长为6分钟。在每次下载之前，会测试最大可用带宽，并根据实时结果将下载速率设置为30%的带宽。
  • 带宽占用测试使用了speedtest-cli和speedtest-go两种工具，以防其中之一不可用时使用第二种工具，用户可以自定义设置带宽占用，此时详见设置提示。
  • 提供一键卸载所有占用服务的选项，卸载将删除所有脚本、服务、任务、守护进程和开机自启设置。
  • 提供一键检查更新的功能，更新范围仅限于脚本更新。请在更新后重新设置占用服务
  • 对所有进程执行增加唯一性检测，避免重复运行，使用PID文件进行判断。
如若不希望一键的，希望自定义设置时间的，请查看README_CRON.md自行设置定时任务
',26),r=[l];function p(c,o,n,h,d,u){return a(),s("div",null,r)}const v=e(i,[["render",p]]);export{m as __pageData,v as default};
+import{_ as e,v as a,b as s,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case5.md","filePath":"case/case5.md","lastUpdated":1747730955000}'),i={name:"case/case5.md"},l=t('
仓库 ​
https://github.com/spiritLHLS/Oracle-server-keep-alive-script
Hits
Oracle-server-keep-alive-script ​
实际不止可以在甲骨文服务器上使用，也可以使用在任意ARM或X86_64架构的系统，用作资源占用
甲骨文服务器保活脚本 ​
适配系统：已在Ubuntu 20+，Debian 10+, Centos 7+, Oracle linux 8+，AlmaLinux 8.5+
上述系统验证无问题，别的主流系统应该也没有问题
可选占用：CPU，内存，带宽
安装完毕后如果有问题请卸载脚本反馈问题(重复卸载也没问题)
所有资源(除了CPU)可选默认配置则动态占用，实时调整，避免服务器有别的任何资源已经超过限额了仍然再占用资源
为避免GitHub的CDN抽风加载不了新内容，所有新更新已使用Gitlab仓库
由于speedtest-go的release依赖于GitHub，所以请检查 www.githubstatus.com ,有问题时无法安装带宽占用
基础开发完毕，测试中，有问题请在issues中反馈 ​
选项1安装，选项2卸载，选项3更新安装引导脚本，选项4退出脚本
安装过程中无脑回车则全部可选的占用都占用，不需要什么占用输入n再回车
如果选择带宽占用，会询问使用speedtest-go占用还是使用wget占用，按照提示进行选择即可
有询问是否需要带宽占用的参数自定义，这时候默认选项就是n，回车就使用默认配置，输入y再回车则需要按照提示自定义参数
curl -L https://gitlab.com/spiritysdx/Oracle-server-keep-alive-script/-/raw/main/oalive.sh -o oalive.sh && chmod +x oalive.sh && bash oalive.sh
或
bash oalive.sh
或
bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/Oracle-server-keep-alive-script/-/raw/main/oalive.sh)
说明 ​
  • 提供两种CPU占用模式：DD模拟占用和科学计算模式，用户可以自由选择，占用范围设置在15%至25%之间，更推荐DD模拟占用
  • DD模拟占用在守护进程中设置了CPU占用的最高限制
  • 默认情况下，CPU占用设置为25%最高值，计算方法是核数乘以12%，如果计算结果低于25%，则设置为该值；如果计算结果高于25%，则按照计算结果的比例进行设置。
  • 内存占用设置为占用总内存的20%，占用时间为300秒，休息时间为300秒。
  • 每300秒检测一次内存占用情况，并根据需要动态调整占用大小。如果内存占用已经大于20%，则不增加占用。
  • 在占用过程中，使用守护进程和开机自启服务，以确保占用任务持续且有效。
  • 默认选项的带宽占用每45分钟下载一次大小在1G至10G之间的文件，只进行下载而不保存。在下载过程中会占用硬盘空间，但在下载完成后会自动释放。
  • 默认选项的带宽占用动态调整实际下载的带宽/速率，限制每次下载的最长时长为6分钟。在每次下载之前，会测试最大可用带宽，并根据实时结果将下载速率设置为30%的带宽。
  • 带宽占用测试使用了speedtest-cli和speedtest-go两种工具，以防其中之一不可用时使用第二种工具，用户可以自定义设置带宽占用，此时详见设置提示。
  • 提供一键卸载所有占用服务的选项，卸载将删除所有脚本、服务、任务、守护进程和开机自启设置。
  • 提供一键检查更新的功能，更新范围仅限于脚本更新。请在更新后重新设置占用服务
  • 对所有进程执行增加唯一性检测，避免重复运行，使用PID文件进行判断。
如若不希望一键的，希望自定义设置时间的，请查看README_CRON.md自行设置定时任务
',26),r=[l];function p(c,o,n,h,d,u){return a(),s("div",null,r)}const v=e(i,[["render",p]]);export{m as __pageData,v as default};
diff --git a/assets/case_case6.md.dbb1e397.js b/assets/case_case6.md.f3e2edf5.js
similarity index 98%
rename from assets/case_case6.md.dbb1e397.js
rename to assets/case_case6.md.f3e2edf5.js
index 26f7e67860..707554668b 100644
--- a/assets/case_case6.md.dbb1e397.js
+++ b/assets/case_case6.md.f3e2edf5.js
@@ -1 +1 @@
-import{_ as s,v as a,b as p,R as o}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case6.md","filePath":"case/case6.md","lastUpdated":1747726389000}'),n={name:"case/case6.md"},l=o('
仓库 ​
https://github.com/spiritLHLS/addswap
addswap ​
为openvz、kvm虚拟化的linux服务器增加swap分区(虚拟内存)
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
已增加openvz架构重启swap自动添加的
openvz这个添加=掩耳盗铃，实际受到虚拟化限制应该是无法添加的，只能由虚拟化的宿主机控制，同理LXC虚拟化的也只能由宿主机控制，都无法自主添加虚拟内存SWAP
因此，该项目不再更新，除非另有需求
单位换算：输入 1024 产生 1G SWAP内存
致谢 ​
kvm分区原版脚本源自 https://www.moerats.com/
bash
curl -L https://www.moerats.com/usr/shell/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
openVZ分区原版脚本源自
http://linux-problem-solver.blogspot.com/2013/08/create-fake-swap-in-openvz-vps-if-you-get-swapon-failed-operation-not-permitted-error.html
感谢 @fscarmen 提供优化建议
',18),e=[l];function t(r,c,C,d,i,h){return a(),p("div",null,e)}const D=s(n,[["render",t]]);export{A as __pageData,D as default};
+import{_ as s,v as a,b as p,R as o}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case6.md","filePath":"case/case6.md","lastUpdated":1747730955000}'),n={name:"case/case6.md"},l=o('
仓库 ​
https://github.com/spiritLHLS/addswap
addswap ​
为openvz、kvm虚拟化的linux服务器增加swap分区(虚拟内存)
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
已增加openvz架构重启swap自动添加的
openvz这个添加=掩耳盗铃，实际受到虚拟化限制应该是无法添加的，只能由虚拟化的宿主机控制，同理LXC虚拟化的也只能由宿主机控制，都无法自主添加虚拟内存SWAP
因此，该项目不再更新，除非另有需求
单位换算：输入 1024 产生 1G SWAP内存
致谢 ​
kvm分区原版脚本源自 https://www.moerats.com/
bash
curl -L https://www.moerats.com/usr/shell/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
openVZ分区原版脚本源自
http://linux-problem-solver.blogspot.com/2013/08/create-fake-swap-in-openvz-vps-if-you-get-swapon-failed-operation-not-permitted-error.html
感谢 @fscarmen 提供优化建议
',18),e=[l];function t(r,c,C,d,i,h){return a(),p("div",null,e)}const D=s(n,[["render",t]]);export{A as __pageData,D as default};
diff --git a/assets/case_case6.md.dbb1e397.lean.js b/assets/case_case6.md.f3e2edf5.lean.js
similarity index 98%
rename from assets/case_case6.md.dbb1e397.lean.js
rename to assets/case_case6.md.f3e2edf5.lean.js
index 26f7e67860..707554668b 100644
--- a/assets/case_case6.md.dbb1e397.lean.js
+++ b/assets/case_case6.md.f3e2edf5.lean.js
@@ -1 +1 @@
-import{_ as s,v as a,b as p,R as o}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case6.md","filePath":"case/case6.md","lastUpdated":1747726389000}'),n={name:"case/case6.md"},l=o('
仓库 ​
https://github.com/spiritLHLS/addswap
addswap ​
为openvz、kvm虚拟化的linux服务器增加swap分区(虚拟内存)
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
已增加openvz架构重启swap自动添加的
openvz这个添加=掩耳盗铃，实际受到虚拟化限制应该是无法添加的，只能由虚拟化的宿主机控制，同理LXC虚拟化的也只能由宿主机控制，都无法自主添加虚拟内存SWAP
因此，该项目不再更新，除非另有需求
单位换算：输入 1024 产生 1G SWAP内存
致谢 ​
kvm分区原版脚本源自 https://www.moerats.com/
bash
curl -L https://www.moerats.com/usr/shell/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
openVZ分区原版脚本源自
http://linux-problem-solver.blogspot.com/2013/08/create-fake-swap-in-openvz-vps-if-you-get-swapon-failed-operation-not-permitted-error.html
感谢 @fscarmen 提供优化建议
',18),e=[l];function t(r,c,C,d,i,h){return a(),p("div",null,e)}const D=s(n,[["render",t]]);export{A as __pageData,D as default};
+import{_ as s,v as a,b as p,R as o}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case6.md","filePath":"case/case6.md","lastUpdated":1747730955000}'),n={name:"case/case6.md"},l=o('
仓库 ​
https://github.com/spiritLHLS/addswap
addswap ​
为openvz、kvm虚拟化的linux服务器增加swap分区(虚拟内存)
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
已增加openvz架构重启swap自动添加的
openvz这个添加=掩耳盗铃，实际受到虚拟化限制应该是无法添加的，只能由虚拟化的宿主机控制，同理LXC虚拟化的也只能由宿主机控制，都无法自主添加虚拟内存SWAP
因此，该项目不再更新，除非另有需求
单位换算：输入 1024 产生 1G SWAP内存
致谢 ​
kvm分区原版脚本源自 https://www.moerats.com/
bash
curl -L https://www.moerats.com/usr/shell/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
openVZ分区原版脚本源自
http://linux-problem-solver.blogspot.com/2013/08/create-fake-swap-in-openvz-vps-if-you-get-swapon-failed-operation-not-permitted-error.html
感谢 @fscarmen 提供优化建议
',18),e=[l];function t(r,c,C,d,i,h){return a(),p("div",null,e)}const D=s(n,[["render",t]]);export{A as __pageData,D as default};
diff --git a/assets/case_case7.md.fd93ad86.js b/assets/case_case7.md.1ef021a6.js
similarity index 98%
rename from assets/case_case7.md.fd93ad86.js
rename to assets/case_case7.md.1ef021a6.js
index 0acc299678..9247dc9321 100644
--- a/assets/case_case7.md.fd93ad86.js
+++ b/assets/case_case7.md.1ef021a6.js
@@ -1 +1 @@
-import{_ as a,v as s,b as p,R as l}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case7.md","filePath":"case/case7.md","lastUpdated":1747726389000}'),n={name:"case/case7.md"},o=l('
仓库 ​
https://github.com/spiritLHLS/addzram
addzram ​
为linux服务器启用zram(压缩内存)
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addzram/main/addzram.sh -o addzram.sh && chmod +x addzram.sh && bash addzram.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addzram/main/addzram.sh -o addzram.sh && chmod +x addzram.sh && bash addzram.sh
类同前面的addswap项目
同样是给机器优化内存占用的东西，只不过zram是压缩内存占用，swap是附加虚拟内存增加内存空间，二者都会占用CPU资源，zram在CPU性能冗余的机器上使用更优
(理论上zram会比swap的性能占用低，但未实际测试过)
单位换算：输入 1024 产生 1G 的 zram 设备压缩内存，zram 设备大小不能大于实际内存大小
致谢 ​
感谢 @Ella-Alinda 提供优化建议
',14),e=[o];function t(r,c,d,C,i,h){return s(),p("div",null,e)}const A=a(n,[["render",t]]);export{y as __pageData,A as default};
+import{_ as a,v as s,b as p,R as l}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case7.md","filePath":"case/case7.md","lastUpdated":1747730955000}'),n={name:"case/case7.md"},o=l('
仓库 ​
https://github.com/spiritLHLS/addzram
addzram ​
为linux服务器启用zram(压缩内存)
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addzram/main/addzram.sh -o addzram.sh && chmod +x addzram.sh && bash addzram.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addzram/main/addzram.sh -o addzram.sh && chmod +x addzram.sh && bash addzram.sh
类同前面的addswap项目
同样是给机器优化内存占用的东西，只不过zram是压缩内存占用，swap是附加虚拟内存增加内存空间，二者都会占用CPU资源，zram在CPU性能冗余的机器上使用更优
(理论上zram会比swap的性能占用低，但未实际测试过)
单位换算：输入 1024 产生 1G 的 zram 设备压缩内存，zram 设备大小不能大于实际内存大小
致谢 ​
感谢 @Ella-Alinda 提供优化建议
',14),e=[o];function t(r,c,d,C,i,h){return s(),p("div",null,e)}const A=a(n,[["render",t]]);export{y as __pageData,A as default};
diff --git a/assets/case_case7.md.fd93ad86.lean.js b/assets/case_case7.md.1ef021a6.lean.js
similarity index 98%
rename from assets/case_case7.md.fd93ad86.lean.js
rename to assets/case_case7.md.1ef021a6.lean.js
index 0acc299678..9247dc9321 100644
--- a/assets/case_case7.md.fd93ad86.lean.js
+++ b/assets/case_case7.md.1ef021a6.lean.js
@@ -1 +1 @@
-import{_ as a,v as s,b as p,R as l}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case7.md","filePath":"case/case7.md","lastUpdated":1747726389000}'),n={name:"case/case7.md"},o=l('
仓库 ​
https://github.com/spiritLHLS/addzram
addzram ​
为linux服务器启用zram(压缩内存)
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addzram/main/addzram.sh -o addzram.sh && chmod +x addzram.sh && bash addzram.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addzram/main/addzram.sh -o addzram.sh && chmod +x addzram.sh && bash addzram.sh
类同前面的addswap项目
同样是给机器优化内存占用的东西，只不过zram是压缩内存占用，swap是附加虚拟内存增加内存空间，二者都会占用CPU资源，zram在CPU性能冗余的机器上使用更优
(理论上zram会比swap的性能占用低，但未实际测试过)
单位换算：输入 1024 产生 1G 的 zram 设备压缩内存，zram 设备大小不能大于实际内存大小
致谢 ​
感谢 @Ella-Alinda 提供优化建议
',14),e=[o];function t(r,c,d,C,i,h){return s(),p("div",null,e)}const A=a(n,[["render",t]]);export{y as __pageData,A as default};
+import{_ as a,v as s,b as p,R as l}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case7.md","filePath":"case/case7.md","lastUpdated":1747730955000}'),n={name:"case/case7.md"},o=l('
仓库 ​
https://github.com/spiritLHLS/addzram
addzram ​
为linux服务器启用zram(压缩内存)
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addzram/main/addzram.sh -o addzram.sh && chmod +x addzram.sh && bash addzram.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addzram/main/addzram.sh -o addzram.sh && chmod +x addzram.sh && bash addzram.sh
类同前面的addswap项目
同样是给机器优化内存占用的东西，只不过zram是压缩内存占用，swap是附加虚拟内存增加内存空间，二者都会占用CPU资源，zram在CPU性能冗余的机器上使用更优
(理论上zram会比swap的性能占用低，但未实际测试过)
单位换算：输入 1024 产生 1G 的 zram 设备压缩内存，zram 设备大小不能大于实际内存大小
致谢 ​
感谢 @Ella-Alinda 提供优化建议
',14),e=[o];function t(r,c,d,C,i,h){return s(),p("div",null,e)}const A=a(n,[["render",t]]);export{y as __pageData,A as default};
diff --git a/assets/case_index.md.9ebc1ebb.js b/assets/case_index.md.56532888.js
similarity index 92%
rename from assets/case_index.md.9ebc1ebb.js
rename to assets/case_index.md.56532888.js
index c64e1c36bf..3ab8c954f2 100644
--- a/assets/case_index.md.9ebc1ebb.js
+++ b/assets/case_index.md.56532888.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"其他实用项目","titleTemplate":"与Linux相关的其他实用项目","description":"","frontmatter":{"layout":"home","title":"其他实用项目","titleTemplate":"与Linux相关的其他实用项目","hero":{"name":"其他实用项目","text":"与Linux相关的其他实用项目","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"查看项目 →","link":"/case/case1"}]},"features":[{"title":"实用性","details":"仁者见仁智者见智。"}]},"headers":[],"relativePath":"case/index.md","filePath":"case/index.md","lastUpdated":1747726389000}'),s={name:"case/index.md"};function i(n,r,o,c,d,l){return t(),a("div")}const h=e(s,[["render",i]]);export{m as __pageData,h as default};
+import{_ as e,v as t,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"其他实用项目","titleTemplate":"与Linux相关的其他实用项目","description":"","frontmatter":{"layout":"home","title":"其他实用项目","titleTemplate":"与Linux相关的其他实用项目","hero":{"name":"其他实用项目","text":"与Linux相关的其他实用项目","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"查看项目 →","link":"/case/case1"}]},"features":[{"title":"实用性","details":"仁者见仁智者见智。"}]},"headers":[],"relativePath":"case/index.md","filePath":"case/index.md","lastUpdated":1747730955000}'),s={name:"case/index.md"};function i(n,r,o,c,d,l){return t(),a("div")}const h=e(s,[["render",i]]);export{m as __pageData,h as default};
diff --git a/assets/case_index.md.9ebc1ebb.lean.js b/assets/case_index.md.56532888.lean.js
similarity index 92%
rename from assets/case_index.md.9ebc1ebb.lean.js
rename to assets/case_index.md.56532888.lean.js
index c64e1c36bf..3ab8c954f2 100644
--- a/assets/case_index.md.9ebc1ebb.lean.js
+++ b/assets/case_index.md.56532888.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"其他实用项目","titleTemplate":"与Linux相关的其他实用项目","description":"","frontmatter":{"layout":"home","title":"其他实用项目","titleTemplate":"与Linux相关的其他实用项目","hero":{"name":"其他实用项目","text":"与Linux相关的其他实用项目","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"查看项目 →","link":"/case/case1"}]},"features":[{"title":"实用性","details":"仁者见仁智者见智。"}]},"headers":[],"relativePath":"case/index.md","filePath":"case/index.md","lastUpdated":1747726389000}'),s={name:"case/index.md"};function i(n,r,o,c,d,l){return t(),a("div")}const h=e(s,[["render",i]]);export{m as __pageData,h as default};
+import{_ as e,v as t,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"其他实用项目","titleTemplate":"与Linux相关的其他实用项目","description":"","frontmatter":{"layout":"home","title":"其他实用项目","titleTemplate":"与Linux相关的其他实用项目","hero":{"name":"其他实用项目","text":"与Linux相关的其他实用项目","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"查看项目 →","link":"/case/case1"}]},"features":[{"title":"实用性","details":"仁者见仁智者见智。"}]},"headers":[],"relativePath":"case/index.md","filePath":"case/index.md","lastUpdated":1747730955000}'),s={name:"case/index.md"};function i(n,r,o,c,d,l){return t(),a("div")}const h=e(s,[["render",i]]);export{m as __pageData,h as default};
diff --git a/assets/developer_index.md.bcfb38d4.js b/assets/developer_index.md.50574134.js
similarity index 93%
rename from assets/developer_index.md.bcfb38d4.js
rename to assets/developer_index.md.50574134.js
index b041ca83f3..d4827d6814 100644
--- a/assets/developer_index.md.bcfb38d4.js
+++ b/assets/developer_index.md.50574134.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a}from"./chunks/framework.70afa331.js";const c=JSON.parse('{"title":"开发手册","titleTemplate":"欢迎使用一键虚拟化项目开发手册，欢迎你提出高质量的Pull Request，帮助一键虚拟化项目变得更好！","description":"","frontmatter":{"layout":"home","title":"开发手册","titleTemplate":"欢迎使用一键虚拟化项目开发手册，欢迎你提出高质量的Pull Request，帮助一键虚拟化项目变得更好！","hero":{"name":"开发手册","text":"开发手册","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"开始使用 →","link":"/developer/l10n"}]}},"headers":[],"relativePath":"developer/index.md","filePath":"developer/index.md","lastUpdated":1747726389000}'),s={name:"developer/index.md"};function n(r,i,l,o,p,d){return t(),a("div")}const h=e(s,[["render",n]]);export{c as __pageData,h as default};
+import{_ as e,v as t,b as a}from"./chunks/framework.70afa331.js";const c=JSON.parse('{"title":"开发手册","titleTemplate":"欢迎使用一键虚拟化项目开发手册，欢迎你提出高质量的Pull Request，帮助一键虚拟化项目变得更好！","description":"","frontmatter":{"layout":"home","title":"开发手册","titleTemplate":"欢迎使用一键虚拟化项目开发手册，欢迎你提出高质量的Pull Request，帮助一键虚拟化项目变得更好！","hero":{"name":"开发手册","text":"开发手册","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"开始使用 →","link":"/developer/l10n"}]}},"headers":[],"relativePath":"developer/index.md","filePath":"developer/index.md","lastUpdated":1747730955000}'),s={name:"developer/index.md"};function n(r,i,l,o,p,d){return t(),a("div")}const h=e(s,[["render",n]]);export{c as __pageData,h as default};
diff --git a/assets/developer_index.md.bcfb38d4.lean.js b/assets/developer_index.md.50574134.lean.js
similarity index 93%
rename from assets/developer_index.md.bcfb38d4.lean.js
rename to assets/developer_index.md.50574134.lean.js
index b041ca83f3..d4827d6814 100644
--- a/assets/developer_index.md.bcfb38d4.lean.js
+++ b/assets/developer_index.md.50574134.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a}from"./chunks/framework.70afa331.js";const c=JSON.parse('{"title":"开发手册","titleTemplate":"欢迎使用一键虚拟化项目开发手册，欢迎你提出高质量的Pull Request，帮助一键虚拟化项目变得更好！","description":"","frontmatter":{"layout":"home","title":"开发手册","titleTemplate":"欢迎使用一键虚拟化项目开发手册，欢迎你提出高质量的Pull Request，帮助一键虚拟化项目变得更好！","hero":{"name":"开发手册","text":"开发手册","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"开始使用 →","link":"/developer/l10n"}]}},"headers":[],"relativePath":"developer/index.md","filePath":"developer/index.md","lastUpdated":1747726389000}'),s={name:"developer/index.md"};function n(r,i,l,o,p,d){return t(),a("div")}const h=e(s,[["render",n]]);export{c as __pageData,h as default};
+import{_ as e,v as t,b as a}from"./chunks/framework.70afa331.js";const c=JSON.parse('{"title":"开发手册","titleTemplate":"欢迎使用一键虚拟化项目开发手册，欢迎你提出高质量的Pull Request，帮助一键虚拟化项目变得更好！","description":"","frontmatter":{"layout":"home","title":"开发手册","titleTemplate":"欢迎使用一键虚拟化项目开发手册，欢迎你提出高质量的Pull Request，帮助一键虚拟化项目变得更好！","hero":{"name":"开发手册","text":"开发手册","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"开始使用 →","link":"/developer/l10n"}]}},"headers":[],"relativePath":"developer/index.md","filePath":"developer/index.md","lastUpdated":1747730955000}'),s={name:"developer/index.md"};function n(r,i,l,o,p,d){return t(),a("div")}const h=e(s,[["render",n]]);export{c as __pageData,h as default};
diff --git a/assets/developer_l10n.md.668cddf4.js b/assets/developer_l10n.md.43daef7f.js
similarity index 90%
rename from assets/developer_l10n.md.668cddf4.js
rename to assets/developer_l10n.md.43daef7f.js
index 06adad9628..0b5db4db2c 100644
--- a/assets/developer_l10n.md.668cddf4.js
+++ b/assets/developer_l10n.md.43daef7f.js
@@ -1 +1 @@
-import{_ as e,v as o,b as t,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"developer/l10n.md","filePath":"developer/l10n.md","lastUpdated":1747726389000}'),l={name:"developer/l10n.md"},r=a('
你可以在开发新功能时遵循以下步骤来支持本地化
介绍 ​
  1. 你可以直接使用 /resource/l10n/zh-CN.toml 中已有的文本配置来替换新功能中的文本
  2. 如果新功能中有新增文本，请参考 zh-CN.toml 的配置文本，将新文本拉取到 zh-CN.toml 等其他语言的配置文件中，并添加翻译
新本地化文本的添加 ​
  1. 在 /resource/l10n/ 中添加新的语言文本配置
  2. 在新的语言文本配置中拉取其他语言已有的文本配置
  3. 为新的语言文本配置添加翻译
',5),s=[r];function d(i,n,c,h,p,_){return o(),t("div",null,s)}const f=e(l,[["render",d]]);export{u as __pageData,f as default};
+import{_ as e,v as o,b as t,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"developer/l10n.md","filePath":"developer/l10n.md","lastUpdated":1747730955000}'),l={name:"developer/l10n.md"},r=a('
你可以在开发新功能时遵循以下步骤来支持本地化
介绍 ​
  1. 你可以直接使用 /resource/l10n/zh-CN.toml 中已有的文本配置来替换新功能中的文本
  2. 如果新功能中有新增文本，请参考 zh-CN.toml 的配置文本，将新文本拉取到 zh-CN.toml 等其他语言的配置文件中，并添加翻译
新本地化文本的添加 ​
  1. 在 /resource/l10n/ 中添加新的语言文本配置
  2. 在新的语言文本配置中拉取其他语言已有的文本配置
  3. 为新的语言文本配置添加翻译
',5),s=[r];function d(i,n,c,h,p,_){return o(),t("div",null,s)}const f=e(l,[["render",d]]);export{u as __pageData,f as default};
diff --git a/assets/developer_l10n.md.668cddf4.lean.js b/assets/developer_l10n.md.43daef7f.lean.js
similarity index 90%
rename from assets/developer_l10n.md.668cddf4.lean.js
rename to assets/developer_l10n.md.43daef7f.lean.js
index 06adad9628..0b5db4db2c 100644
--- a/assets/developer_l10n.md.668cddf4.lean.js
+++ b/assets/developer_l10n.md.43daef7f.lean.js
@@ -1 +1 @@
-import{_ as e,v as o,b as t,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"developer/l10n.md","filePath":"developer/l10n.md","lastUpdated":1747726389000}'),l={name:"developer/l10n.md"},r=a('
你可以在开发新功能时遵循以下步骤来支持本地化
介绍 ​
  1. 你可以直接使用 /resource/l10n/zh-CN.toml 中已有的文本配置来替换新功能中的文本
  2. 如果新功能中有新增文本，请参考 zh-CN.toml 的配置文本，将新文本拉取到 zh-CN.toml 等其他语言的配置文件中，并添加翻译
新本地化文本的添加 ​
  1. 在 /resource/l10n/ 中添加新的语言文本配置
  2. 在新的语言文本配置中拉取其他语言已有的文本配置
  3. 为新的语言文本配置添加翻译
',5),s=[r];function d(i,n,c,h,p,_){return o(),t("div",null,s)}const f=e(l,[["render",d]]);export{u as __pageData,f as default};
+import{_ as e,v as o,b as t,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"developer/l10n.md","filePath":"developer/l10n.md","lastUpdated":1747730955000}'),l={name:"developer/l10n.md"},r=a('
你可以在开发新功能时遵循以下步骤来支持本地化
介绍 ​
  1. 你可以直接使用 /resource/l10n/zh-CN.toml 中已有的文本配置来替换新功能中的文本
  2. 如果新功能中有新增文本，请参考 zh-CN.toml 的配置文本，将新文本拉取到 zh-CN.toml 等其他语言的配置文件中，并添加翻译
新本地化文本的添加 ​
  1. 在 /resource/l10n/ 中添加新的语言文本配置
  2. 在新的语言文本配置中拉取其他语言已有的文本配置
  3. 为新的语言文本配置添加翻译
',5),s=[r];function d(i,n,c,h,p,_){return o(),t("div",null,s)}const f=e(l,[["render",d]]);export{u as __pageData,f as default};
diff --git a/assets/en_developer_index.md.2781d9ef.js b/assets/en_developer_index.md.36a7747c.js
similarity index 92%
rename from assets/en_developer_index.md.2781d9ef.js
rename to assets/en_developer_index.md.36a7747c.js
index 07507db9b8..c723d41e44 100644
--- a/assets/en_developer_index.md.2781d9ef.js
+++ b/assets/en_developer_index.md.36a7747c.js
@@ -1 +1 @@
-import{_ as e,v as t,b as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"Development Manual","titleTemplate":"Welcome to the oneclickvirt Development Manual.","description":"","frontmatter":{"layout":"home","title":"Development Manual","titleTemplate":"Welcome to the oneclickvirt Development Manual.","hero":{"name":"Development Manual","text":"Welcome to the oneclickvirt Development Manual.","image":"https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"Start Now →","link":"/en_US/developer/l10n"}]}},"headers":[],"relativePath":"en/developer/index.md","filePath":"en/developer/index.md","lastUpdated":1747726389000}'),a={name:"en/developer/index.md"};function o(l,i,r,p,m,s){return t(),n("div")}const v=e(a,[["render",o]]);export{d as __pageData,v as default};
+import{_ as e,v as t,b as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"Development Manual","titleTemplate":"Welcome to the oneclickvirt Development Manual.","description":"","frontmatter":{"layout":"home","title":"Development Manual","titleTemplate":"Welcome to the oneclickvirt Development Manual.","hero":{"name":"Development Manual","text":"Welcome to the oneclickvirt Development Manual.","image":"https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"Start Now →","link":"/en_US/developer/l10n"}]}},"headers":[],"relativePath":"en/developer/index.md","filePath":"en/developer/index.md","lastUpdated":1747730955000}'),a={name:"en/developer/index.md"};function o(l,i,r,p,m,s){return t(),n("div")}const v=e(a,[["render",o]]);export{d as __pageData,v as default};
diff --git a/assets/en_developer_index.md.2781d9ef.lean.js b/assets/en_developer_index.md.36a7747c.lean.js
similarity index 92%
rename from assets/en_developer_index.md.2781d9ef.lean.js
rename to assets/en_developer_index.md.36a7747c.lean.js
index 07507db9b8..c723d41e44 100644
--- a/assets/en_developer_index.md.2781d9ef.lean.js
+++ b/assets/en_developer_index.md.36a7747c.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"Development Manual","titleTemplate":"Welcome to the oneclickvirt Development Manual.","description":"","frontmatter":{"layout":"home","title":"Development Manual","titleTemplate":"Welcome to the oneclickvirt Development Manual.","hero":{"name":"Development Manual","text":"Welcome to the oneclickvirt Development Manual.","image":"https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"Start Now →","link":"/en_US/developer/l10n"}]}},"headers":[],"relativePath":"en/developer/index.md","filePath":"en/developer/index.md","lastUpdated":1747726389000}'),a={name:"en/developer/index.md"};function o(l,i,r,p,m,s){return t(),n("div")}const v=e(a,[["render",o]]);export{d as __pageData,v as default};
+import{_ as e,v as t,b as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"Development Manual","titleTemplate":"Welcome to the oneclickvirt Development Manual.","description":"","frontmatter":{"layout":"home","title":"Development Manual","titleTemplate":"Welcome to the oneclickvirt Development Manual.","hero":{"name":"Development Manual","text":"Welcome to the oneclickvirt Development Manual.","image":"https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"Start Now →","link":"/en_US/developer/l10n"}]}},"headers":[],"relativePath":"en/developer/index.md","filePath":"en/developer/index.md","lastUpdated":1747730955000}'),a={name:"en/developer/index.md"};function o(l,i,r,p,m,s){return t(),n("div")}const v=e(a,[["render",o]]);export{d as __pageData,v as default};
diff --git a/assets/en_developer_l10n.md.cd095d45.js b/assets/en_developer_l10n.md.4dc4f4b3.js
similarity index 95%
rename from assets/en_developer_l10n.md.cd095d45.js
rename to assets/en_developer_l10n.md.4dc4f4b3.js
index ed742c8e4d..9e32ff2fd9 100644
--- a/assets/en_developer_l10n.md.cd095d45.js
+++ b/assets/en_developer_l10n.md.4dc4f4b3.js
@@ -1 +1 @@
-import{_ as e,v as t,b as n,R as o}from"./chunks/framework.70afa331.js";const p=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/developer/l10n.md","filePath":"en/developer/l10n.md","lastUpdated":1747726389000}'),a={name:"en/developer/l10n.md"},i=o('
You can follow these steps to support localization when developing new features
Introduction ​
  1. You can directly use the text configuration already available in /resource/l10n/en-US.toml to replace the text in the new feature.
  2. If there is new text in the new feature, please refer to the configuration text in en-US.toml, pull the new text into the configuration files of other languages such as en-US.toml, and add translations.
Adding a new localized text file ​
  1. Add a new language text configuration in /resource/l10n/.
  2. Pull existing text configurations from other languages in the new language text configuration.
  3. Add translations for the new language text configuration.
',5),l=[i];function r(d,s,c,u,f,h){return t(),n("div",null,l)}const x=e(a,[["render",r]]);export{p as __pageData,x as default};
+import{_ as e,v as t,b as n,R as o}from"./chunks/framework.70afa331.js";const p=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/developer/l10n.md","filePath":"en/developer/l10n.md","lastUpdated":1747730955000}'),a={name:"en/developer/l10n.md"},i=o('
You can follow these steps to support localization when developing new features
Introduction ​
  1. You can directly use the text configuration already available in /resource/l10n/en-US.toml to replace the text in the new feature.
  2. If there is new text in the new feature, please refer to the configuration text in en-US.toml, pull the new text into the configuration files of other languages such as en-US.toml, and add translations.
Adding a new localized text file ​
  1. Add a new language text configuration in /resource/l10n/.
  2. Pull existing text configurations from other languages in the new language text configuration.
  3. Add translations for the new language text configuration.
',5),l=[i];function r(d,s,c,u,f,h){return t(),n("div",null,l)}const x=e(a,[["render",r]]);export{p as __pageData,x as default};
diff --git a/assets/en_developer_l10n.md.cd095d45.lean.js b/assets/en_developer_l10n.md.4dc4f4b3.lean.js
similarity index 95%
rename from assets/en_developer_l10n.md.cd095d45.lean.js
rename to assets/en_developer_l10n.md.4dc4f4b3.lean.js
index ed742c8e4d..9e32ff2fd9 100644
--- a/assets/en_developer_l10n.md.cd095d45.lean.js
+++ b/assets/en_developer_l10n.md.4dc4f4b3.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as n,R as o}from"./chunks/framework.70afa331.js";const p=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/developer/l10n.md","filePath":"en/developer/l10n.md","lastUpdated":1747726389000}'),a={name:"en/developer/l10n.md"},i=o('
You can follow these steps to support localization when developing new features
Introduction ​
  1. You can directly use the text configuration already available in /resource/l10n/en-US.toml to replace the text in the new feature.
  2. If there is new text in the new feature, please refer to the configuration text in en-US.toml, pull the new text into the configuration files of other languages such as en-US.toml, and add translations.
Adding a new localized text file ​
  1. Add a new language text configuration in /resource/l10n/.
  2. Pull existing text configurations from other languages in the new language text configuration.
  3. Add translations for the new language text configuration.
',5),l=[i];function r(d,s,c,u,f,h){return t(),n("div",null,l)}const x=e(a,[["render",r]]);export{p as __pageData,x as default};
+import{_ as e,v as t,b as n,R as o}from"./chunks/framework.70afa331.js";const p=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/developer/l10n.md","filePath":"en/developer/l10n.md","lastUpdated":1747730955000}'),a={name:"en/developer/l10n.md"},i=o('
You can follow these steps to support localization when developing new features
Introduction ​
  1. You can directly use the text configuration already available in /resource/l10n/en-US.toml to replace the text in the new feature.
  2. If there is new text in the new feature, please refer to the configuration text in en-US.toml, pull the new text into the configuration files of other languages such as en-US.toml, and add translations.
Adding a new localized text file ​
  1. Add a new language text configuration in /resource/l10n/.
  2. Pull existing text configurations from other languages in the new language text configuration.
  3. Add translations for the new language text configuration.
',5),l=[i];function r(d,s,c,u,f,h){return t(),n("div",null,l)}const x=e(a,[["render",r]]);export{p as __pageData,x as default};
diff --git a/assets/en_guide_block_block_docker.md.cbf92a99.js b/assets/en_guide_block_block_docker.md.b4fe6add.js
similarity index 91%
rename from assets/en_guide_block_block_docker.md.cbf92a99.js
rename to assets/en_guide_block_block_docker.md.b4fe6add.js
index 000617739b..bc1e714711 100644
--- a/assets/en_guide_block_block_docker.md.cbf92a99.js
+++ b/assets/en_guide_block_block_docker.md.b4fe6add.js
@@ -1 +1 @@
-import{_ as t,v as o,b as d,F as e,L as a}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"To be developed, stay tuned","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_docker.md","filePath":"en/guide/block/block_docker.md","lastUpdated":1747726389000}'),s={name:"en/guide/block/block_docker.md"},n=e("h1",{id:"to-be-developed-stay-tuned",tabindex:"-1"},[a("To be developed, stay tuned "),e("a",{class:"header-anchor",href:"#to-be-developed-stay-tuned","aria-label":'Permalink to "To be developed, stay tuned"'},"​")],-1),c=[n];function r(l,i,_,p,b,u){return o(),d("div",null,c)}const f=t(s,[["render",r]]);export{h as __pageData,f as default};
+import{_ as t,v as o,b as d,F as e,L as a}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"To be developed, stay tuned","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_docker.md","filePath":"en/guide/block/block_docker.md","lastUpdated":1747730955000}'),s={name:"en/guide/block/block_docker.md"},n=e("h1",{id:"to-be-developed-stay-tuned",tabindex:"-1"},[a("To be developed, stay tuned "),e("a",{class:"header-anchor",href:"#to-be-developed-stay-tuned","aria-label":'Permalink to "To be developed, stay tuned"'},"​")],-1),c=[n];function r(l,i,_,p,b,u){return o(),d("div",null,c)}const f=t(s,[["render",r]]);export{h as __pageData,f as default};
diff --git a/assets/en_guide_block_block_docker.md.cbf92a99.lean.js b/assets/en_guide_block_block_docker.md.b4fe6add.lean.js
similarity index 91%
rename from assets/en_guide_block_block_docker.md.cbf92a99.lean.js
rename to assets/en_guide_block_block_docker.md.b4fe6add.lean.js
index 000617739b..bc1e714711 100644
--- a/assets/en_guide_block_block_docker.md.cbf92a99.lean.js
+++ b/assets/en_guide_block_block_docker.md.b4fe6add.lean.js
@@ -1 +1 @@
-import{_ as t,v as o,b as d,F as e,L as a}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"To be developed, stay tuned","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_docker.md","filePath":"en/guide/block/block_docker.md","lastUpdated":1747726389000}'),s={name:"en/guide/block/block_docker.md"},n=e("h1",{id:"to-be-developed-stay-tuned",tabindex:"-1"},[a("To be developed, stay tuned "),e("a",{class:"header-anchor",href:"#to-be-developed-stay-tuned","aria-label":'Permalink to "To be developed, stay tuned"'},"​")],-1),c=[n];function r(l,i,_,p,b,u){return o(),d("div",null,c)}const f=t(s,[["render",r]]);export{h as __pageData,f as default};
+import{_ as t,v as o,b as d,F as e,L as a}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"To be developed, stay tuned","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_docker.md","filePath":"en/guide/block/block_docker.md","lastUpdated":1747730955000}'),s={name:"en/guide/block/block_docker.md"},n=e("h1",{id:"to-be-developed-stay-tuned",tabindex:"-1"},[a("To be developed, stay tuned "),e("a",{class:"header-anchor",href:"#to-be-developed-stay-tuned","aria-label":'Permalink to "To be developed, stay tuned"'},"​")],-1),c=[n];function r(l,i,_,p,b,u){return o(),d("div",null,c)}const f=t(s,[["render",r]]);export{h as __pageData,f as default};
diff --git a/assets/en_guide_block_block_incus.md.970a86f8.js b/assets/en_guide_block_block_incus.md.6f7902ba.js
similarity index 97%
rename from assets/en_guide_block_block_incus.md.970a86f8.js
rename to assets/en_guide_block_block_incus.md.6f7902ba.js
index 2eb430fa98..07781ccb56 100644
--- a/assets/en_guide_block_block_incus.md.970a86f8.js
+++ b/assets/en_guide_block_block_incus.md.6f7902ba.js
@@ -1 +1 @@
-import{_ as s,v as n,b as o,R as a}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"Blocking Abusive Behavior via Shell Scripts","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_incus.md","filePath":"en/guide/block/block_incus.md","lastUpdated":1747726389000}'),e={name:"en/guide/block/block_incus.md"},t=a('
Blocking Abusive Behavior via Shell Scripts ​
Blocking Ingress/Egress Traffic on Easily Abused Ports and Filtering Out Port Scanning and Exploitation Toolkits ​
  • (Optional, this script is solely for preventing container abuse and is not mandatory to install.)
  • Precautionary Measures
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
Use the 'screen' command to configure monitoring and blocking of certain processes' commands: terminate containers immediately upon the appearance of specific processes. ​
  • To stop monitoring, you can use the 'screen' command to stop the window named 'lxc_monitor' and delete it.
  • (Optional, this script is only for preventing misuse of containers; it's fine not to install it.)
  • Shutdown afterwards.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
',9),l=[t];function i(r,c,p,d,m,u){return n(),o("div",null,l)}const y=s(e,[["render",i]]);export{C as __pageData,y as default};
+import{_ as s,v as n,b as o,R as a}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"Blocking Abusive Behavior via Shell Scripts","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_incus.md","filePath":"en/guide/block/block_incus.md","lastUpdated":1747730955000}'),e={name:"en/guide/block/block_incus.md"},t=a('
Blocking Abusive Behavior via Shell Scripts ​
Blocking Ingress/Egress Traffic on Easily Abused Ports and Filtering Out Port Scanning and Exploitation Toolkits ​
  • (Optional, this script is solely for preventing container abuse and is not mandatory to install.)
  • Precautionary Measures
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
Use the 'screen' command to configure monitoring and blocking of certain processes' commands: terminate containers immediately upon the appearance of specific processes. ​
  • To stop monitoring, you can use the 'screen' command to stop the window named 'lxc_monitor' and delete it.
  • (Optional, this script is only for preventing misuse of containers; it's fine not to install it.)
  • Shutdown afterwards.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
',9),l=[t];function i(r,c,p,d,m,u){return n(),o("div",null,l)}const y=s(e,[["render",i]]);export{C as __pageData,y as default};
diff --git a/assets/en_guide_block_block_incus.md.970a86f8.lean.js b/assets/en_guide_block_block_incus.md.6f7902ba.lean.js
similarity index 97%
rename from assets/en_guide_block_block_incus.md.970a86f8.lean.js
rename to assets/en_guide_block_block_incus.md.6f7902ba.lean.js
index 2eb430fa98..07781ccb56 100644
--- a/assets/en_guide_block_block_incus.md.970a86f8.lean.js
+++ b/assets/en_guide_block_block_incus.md.6f7902ba.lean.js
@@ -1 +1 @@
-import{_ as s,v as n,b as o,R as a}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"Blocking Abusive Behavior via Shell Scripts","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_incus.md","filePath":"en/guide/block/block_incus.md","lastUpdated":1747726389000}'),e={name:"en/guide/block/block_incus.md"},t=a('
Blocking Abusive Behavior via Shell Scripts ​
Blocking Ingress/Egress Traffic on Easily Abused Ports and Filtering Out Port Scanning and Exploitation Toolkits ​
  • (Optional, this script is solely for preventing container abuse and is not mandatory to install.)
  • Precautionary Measures
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
Use the 'screen' command to configure monitoring and blocking of certain processes' commands: terminate containers immediately upon the appearance of specific processes. ​
  • To stop monitoring, you can use the 'screen' command to stop the window named 'lxc_monitor' and delete it.
  • (Optional, this script is only for preventing misuse of containers; it's fine not to install it.)
  • Shutdown afterwards.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
',9),l=[t];function i(r,c,p,d,m,u){return n(),o("div",null,l)}const y=s(e,[["render",i]]);export{C as __pageData,y as default};
+import{_ as s,v as n,b as o,R as a}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"Blocking Abusive Behavior via Shell Scripts","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_incus.md","filePath":"en/guide/block/block_incus.md","lastUpdated":1747730955000}'),e={name:"en/guide/block/block_incus.md"},t=a('
Blocking Abusive Behavior via Shell Scripts ​
Blocking Ingress/Egress Traffic on Easily Abused Ports and Filtering Out Port Scanning and Exploitation Toolkits ​
  • (Optional, this script is solely for preventing container abuse and is not mandatory to install.)
  • Precautionary Measures
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
Use the 'screen' command to configure monitoring and blocking of certain processes' commands: terminate containers immediately upon the appearance of specific processes. ​
  • To stop monitoring, you can use the 'screen' command to stop the window named 'lxc_monitor' and delete it.
  • (Optional, this script is only for preventing misuse of containers; it's fine not to install it.)
  • Shutdown afterwards.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
',9),l=[t];function i(r,c,p,d,m,u){return n(),o("div",null,l)}const y=s(e,[["render",i]]);export{C as __pageData,y as default};
diff --git a/assets/en_guide_block_block_iptables.md.2f94165c.js b/assets/en_guide_block_block_iptables.md.1e8129d7.js
similarity index 99%
rename from assets/en_guide_block_block_iptables.md.2f94165c.js
rename to assets/en_guide_block_block_iptables.md.1e8129d7.js
index fc5018cc79..69ff9fee96 100644
--- a/assets/en_guide_block_block_iptables.md.2f94165c.js
+++ b/assets/en_guide_block_block_iptables.md.1e8129d7.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"Blocking abuse through iptables","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_iptables.md","filePath":"en/guide/block/block_iptables.md","lastUpdated":1747726389000}'),l={name:"en/guide/block/block_iptables.md"},o=e(`
Blocking abuse through iptables ​
Basic Usage of iptables ​
1. Start iptables ​
In most Linux distributions, the iptables service can be started using the following command:
bash
sudo systemctl start iptables
2. Set Rules ​
After starting iptables, you can set rules to block abusive traffic. For example, the following command will block traffic from a specific IPv4 address:
bash
sudo iptables -A INPUT -s xxx.xxx.xxx.xxx -j DROP
3. Query Rules ​
After setting the rules, you can use the following command to view the current iptables rules:
bash
sudo iptables -L
This will list all input, output, and forwarding rules.
4. Stop iptables ​
If you need to stop the iptables service, you can use the following command:
bash
sudo systemctl stop iptables
5. Save Rules ​
To ensure that the rules persist after a reboot, you can save the current rules:
bash
sudo iptables-save | sudo tee /etc/iptables/rules.v4
6. Restore Rules ​
When you need to restore the rules, you can use the following command:
bash
sudo iptables-restore < /etc/iptables/rules.v4
7. Other Common Commands ​
  • List Rules (Detailed Information):
    bash
    sudo iptables -L -v
  • Delete Specific Rule:
    bash
    sudo iptables -D INPUT -s 192.168.1.100 -j DROP
  • Flush All Rules:
    bash
    sudo iptables -F
Block abusive traffic on the host ​
  • prevention in advance
Blocking Mining Behavior ​
strings=(
+import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"Blocking abuse through iptables","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_iptables.md","filePath":"en/guide/block/block_iptables.md","lastUpdated":1747730955000}'),l={name:"en/guide/block/block_iptables.md"},o=e(`
Blocking abuse through iptables ​
Basic Usage of iptables ​
1. Start iptables ​
In most Linux distributions, the iptables service can be started using the following command:
bash
sudo systemctl start iptables
2. Set Rules ​
After starting iptables, you can set rules to block abusive traffic. For example, the following command will block traffic from a specific IPv4 address:
bash
sudo iptables -A INPUT -s xxx.xxx.xxx.xxx -j DROP
3. Query Rules ​
After setting the rules, you can use the following command to view the current iptables rules:
bash
sudo iptables -L
This will list all input, output, and forwarding rules.
4. Stop iptables ​
If you need to stop the iptables service, you can use the following command:
bash
sudo systemctl stop iptables
5. Save Rules ​
To ensure that the rules persist after a reboot, you can save the current rules:
bash
sudo iptables-save | sudo tee /etc/iptables/rules.v4
6. Restore Rules ​
When you need to restore the rules, you can use the following command:
bash
sudo iptables-restore < /etc/iptables/rules.v4
7. Other Common Commands ​
  • List Rules (Detailed Information):
    bash
    sudo iptables -L -v
  • Delete Specific Rule:
    bash
    sudo iptables -D INPUT -s 192.168.1.100 -j DROP
  • Flush All Rules:
    bash
    sudo iptables -F
Block abusive traffic on the host ​
  • prevention in advance
Blocking Mining Behavior ​
strings=(
     "ethermine.com"
     "antpool.one"
     "antpool.com"
diff --git a/assets/en_guide_block_block_iptables.md.2f94165c.lean.js b/assets/en_guide_block_block_iptables.md.1e8129d7.lean.js
similarity index 99%
rename from assets/en_guide_block_block_iptables.md.2f94165c.lean.js
rename to assets/en_guide_block_block_iptables.md.1e8129d7.lean.js
index fc5018cc79..69ff9fee96 100644
--- a/assets/en_guide_block_block_iptables.md.2f94165c.lean.js
+++ b/assets/en_guide_block_block_iptables.md.1e8129d7.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"Blocking abuse through iptables","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_iptables.md","filePath":"en/guide/block/block_iptables.md","lastUpdated":1747726389000}'),l={name:"en/guide/block/block_iptables.md"},o=e(`
Blocking abuse through iptables ​
Basic Usage of iptables ​
1. Start iptables ​
In most Linux distributions, the iptables service can be started using the following command:
bash
sudo systemctl start iptables
2. Set Rules ​
After starting iptables, you can set rules to block abusive traffic. For example, the following command will block traffic from a specific IPv4 address:
bash
sudo iptables -A INPUT -s xxx.xxx.xxx.xxx -j DROP
3. Query Rules ​
After setting the rules, you can use the following command to view the current iptables rules:
bash
sudo iptables -L
This will list all input, output, and forwarding rules.
4. Stop iptables ​
If you need to stop the iptables service, you can use the following command:
bash
sudo systemctl stop iptables
5. Save Rules ​
To ensure that the rules persist after a reboot, you can save the current rules:
bash
sudo iptables-save | sudo tee /etc/iptables/rules.v4
6. Restore Rules ​
When you need to restore the rules, you can use the following command:
bash
sudo iptables-restore < /etc/iptables/rules.v4
7. Other Common Commands ​
  • List Rules (Detailed Information):
    bash
    sudo iptables -L -v
  • Delete Specific Rule:
    bash
    sudo iptables -D INPUT -s 192.168.1.100 -j DROP
  • Flush All Rules:
    bash
    sudo iptables -F
Block abusive traffic on the host ​
  • prevention in advance
Blocking Mining Behavior ​
strings=(
+import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"Blocking abuse through iptables","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_iptables.md","filePath":"en/guide/block/block_iptables.md","lastUpdated":1747730955000}'),l={name:"en/guide/block/block_iptables.md"},o=e(`
Blocking abuse through iptables ​
Basic Usage of iptables ​
1. Start iptables ​
In most Linux distributions, the iptables service can be started using the following command:
bash
sudo systemctl start iptables
2. Set Rules ​
After starting iptables, you can set rules to block abusive traffic. For example, the following command will block traffic from a specific IPv4 address:
bash
sudo iptables -A INPUT -s xxx.xxx.xxx.xxx -j DROP
3. Query Rules ​
After setting the rules, you can use the following command to view the current iptables rules:
bash
sudo iptables -L
This will list all input, output, and forwarding rules.
4. Stop iptables ​
If you need to stop the iptables service, you can use the following command:
bash
sudo systemctl stop iptables
5. Save Rules ​
To ensure that the rules persist after a reboot, you can save the current rules:
bash
sudo iptables-save | sudo tee /etc/iptables/rules.v4
6. Restore Rules ​
When you need to restore the rules, you can use the following command:
bash
sudo iptables-restore < /etc/iptables/rules.v4
7. Other Common Commands ​
  • List Rules (Detailed Information):
    bash
    sudo iptables -L -v
  • Delete Specific Rule:
    bash
    sudo iptables -D INPUT -s 192.168.1.100 -j DROP
  • Flush All Rules:
    bash
    sudo iptables -F
Block abusive traffic on the host ​
  • prevention in advance
Blocking Mining Behavior ​
strings=(
     "ethermine.com"
     "antpool.one"
     "antpool.com"
diff --git a/assets/en_guide_block_block_lxd.md.be399aac.js b/assets/en_guide_block_block_lxd.md.0c221dad.js
similarity index 98%
rename from assets/en_guide_block_block_lxd.md.be399aac.js
rename to assets/en_guide_block_block_lxd.md.0c221dad.js
index eb84076f3c..9171e43efb 100644
--- a/assets/en_guide_block_block_lxd.md.be399aac.js
+++ b/assets/en_guide_block_block_lxd.md.0c221dad.js
@@ -1 +1 @@
-import{_ as s,v as o,b as n,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Blocking Abusive Behavior via Shell Scripts","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_lxd.md","filePath":"en/guide/block/block_lxd.md","lastUpdated":1747726389000}'),e={name:"en/guide/block/block_lxd.md"},l=a('
Blocking Abusive Behavior via Shell Scripts ​
Blocking Ingress/Egress Traffic on Easily Abused Ports and Filtering Out Port Scanning and Exploitation Toolkits ​
  • (Optional, this script is solely for preventing container abuse and is not mandatory to install.)
  • Precautionary Measures
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
Use the 'screen' command to configure monitoring and blocking of certain processes' commands: terminate containers immediately upon the appearance of specific processes. ​
  • To stop monitoring, you can use the 'screen' command to stop the window named 'lxc_monitor' and delete it.
  • (Optional, this script is only for preventing misuse of containers; it's fine not to install it.)
  • Shutdown afterwards.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
',9),t=[l];function i(r,p,c,d,m,h){return o(),n("div",null,t)}const y=s(e,[["render",i]]);export{u as __pageData,y as default};
+import{_ as s,v as o,b as n,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Blocking Abusive Behavior via Shell Scripts","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_lxd.md","filePath":"en/guide/block/block_lxd.md","lastUpdated":1747730955000}'),e={name:"en/guide/block/block_lxd.md"},l=a('
Blocking Abusive Behavior via Shell Scripts ​
Blocking Ingress/Egress Traffic on Easily Abused Ports and Filtering Out Port Scanning and Exploitation Toolkits ​
  • (Optional, this script is solely for preventing container abuse and is not mandatory to install.)
  • Precautionary Measures
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
Use the 'screen' command to configure monitoring and blocking of certain processes' commands: terminate containers immediately upon the appearance of specific processes. ​
  • To stop monitoring, you can use the 'screen' command to stop the window named 'lxc_monitor' and delete it.
  • (Optional, this script is only for preventing misuse of containers; it's fine not to install it.)
  • Shutdown afterwards.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
',9),t=[l];function i(r,p,c,d,m,h){return o(),n("div",null,t)}const y=s(e,[["render",i]]);export{u as __pageData,y as default};
diff --git a/assets/en_guide_block_block_lxd.md.be399aac.lean.js b/assets/en_guide_block_block_lxd.md.0c221dad.lean.js
similarity index 98%
rename from assets/en_guide_block_block_lxd.md.be399aac.lean.js
rename to assets/en_guide_block_block_lxd.md.0c221dad.lean.js
index eb84076f3c..9171e43efb 100644
--- a/assets/en_guide_block_block_lxd.md.be399aac.lean.js
+++ b/assets/en_guide_block_block_lxd.md.0c221dad.lean.js
@@ -1 +1 @@
-import{_ as s,v as o,b as n,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Blocking Abusive Behavior via Shell Scripts","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_lxd.md","filePath":"en/guide/block/block_lxd.md","lastUpdated":1747726389000}'),e={name:"en/guide/block/block_lxd.md"},l=a('
Blocking Abusive Behavior via Shell Scripts ​
Blocking Ingress/Egress Traffic on Easily Abused Ports and Filtering Out Port Scanning and Exploitation Toolkits ​
  • (Optional, this script is solely for preventing container abuse and is not mandatory to install.)
  • Precautionary Measures
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
Use the 'screen' command to configure monitoring and blocking of certain processes' commands: terminate containers immediately upon the appearance of specific processes. ​
  • To stop monitoring, you can use the 'screen' command to stop the window named 'lxc_monitor' and delete it.
  • (Optional, this script is only for preventing misuse of containers; it's fine not to install it.)
  • Shutdown afterwards.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
',9),t=[l];function i(r,p,c,d,m,h){return o(),n("div",null,t)}const y=s(e,[["render",i]]);export{u as __pageData,y as default};
+import{_ as s,v as o,b as n,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Blocking Abusive Behavior via Shell Scripts","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_lxd.md","filePath":"en/guide/block/block_lxd.md","lastUpdated":1747730955000}'),e={name:"en/guide/block/block_lxd.md"},l=a('
Blocking Abusive Behavior via Shell Scripts ​
Blocking Ingress/Egress Traffic on Easily Abused Ports and Filtering Out Port Scanning and Exploitation Toolkits ​
  • (Optional, this script is solely for preventing container abuse and is not mandatory to install.)
  • Precautionary Measures
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
Use the 'screen' command to configure monitoring and blocking of certain processes' commands: terminate containers immediately upon the appearance of specific processes. ​
  • To stop monitoring, you can use the 'screen' command to stop the window named 'lxc_monitor' and delete it.
  • (Optional, this script is only for preventing misuse of containers; it's fine not to install it.)
  • Shutdown afterwards.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
',9),t=[l];function i(r,p,c,d,m,h){return o(),n("div",null,t)}const y=s(e,[["render",i]]);export{u as __pageData,y as default};
diff --git a/assets/en_guide_block_block_pve.md.b7c2dece.js b/assets/en_guide_block_block_pve.md.0baa3bcd.js
similarity index 97%
rename from assets/en_guide_block_block_pve.md.b7c2dece.js
rename to assets/en_guide_block_block_pve.md.0baa3bcd.js
index 5a331d265c..56ad24d766 100644
--- a/assets/en_guide_block_block_pve.md.b7c2dece.js
+++ b/assets/en_guide_block_block_pve.md.0baa3bcd.js
@@ -1,3 +1,3 @@
-import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"Avoid theft by setting up a firewall to limit the IPs used by the VMs","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_pve.md","filePath":"en/guide/block/block_pve.md","lastUpdated":1747726389000}'),n={name:"en/guide/block/block_pve.md"},o=a(`
Avoid theft by setting up a firewall to limit the IPs used by the VMs ​
Create the following file under the PVE's host machine
shell
/etc/pve/firewall/<VMID>.fw
+import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"Avoid theft by setting up a firewall to limit the IPs used by the VMs","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_pve.md","filePath":"en/guide/block/block_pve.md","lastUpdated":1747730955000}'),n={name:"en/guide/block/block_pve.md"},o=a(`
Avoid theft by setting up a firewall to limit the IPs used by the VMs ​
Create the following file under the PVE's host machine
shell
/etc/pve/firewall/<VMID>.fw
 [IPSET ipfilter-<net0>]
 xxx.xxx.xxx.xxx
<VMID> is replaced with the VMID number of the virtual machine, <net0> is replaced with the corresponding alias in the network device (which generally doesn't need to be changed unless you're restricted to IPV6), and xxx.xxx.xxx.xxx is replaced with the public IP address, noting that this IP corresponds to the network device in front of it.
The idea here is that net0 can only use the IP xxx.xxx.xxx.xxx, if you use any other IP the data will be dropped, thus restricting the VM to only use this IP.
There can be more than one IP, once this rule is enabled the VM can't use any other IP, if you don't write an IPv6 address it means the VM can't use an IPv6 address.
TIP
This setting is only recommended when opening VMs with separate IPs that are not NAT full port mapped, otherwise it may cause strange issues resulting in the server being without a network.
This method is not suitable for use on PVEs that open any NAT VMs/containers.
`,8),i=[o];function l(r,p,h,c,d,u){return t(),s("div",null,i)}const g=e(n,[["render",l]]);export{b as __pageData,g as default};
diff --git a/assets/en_guide_block_block_pve.md.b7c2dece.lean.js b/assets/en_guide_block_block_pve.md.0baa3bcd.lean.js
similarity index 97%
rename from assets/en_guide_block_block_pve.md.b7c2dece.lean.js
rename to assets/en_guide_block_block_pve.md.0baa3bcd.lean.js
index 5a331d265c..56ad24d766 100644
--- a/assets/en_guide_block_block_pve.md.b7c2dece.lean.js
+++ b/assets/en_guide_block_block_pve.md.0baa3bcd.lean.js
@@ -1,3 +1,3 @@
-import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"Avoid theft by setting up a firewall to limit the IPs used by the VMs","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_pve.md","filePath":"en/guide/block/block_pve.md","lastUpdated":1747726389000}'),n={name:"en/guide/block/block_pve.md"},o=a(`
Avoid theft by setting up a firewall to limit the IPs used by the VMs ​
Create the following file under the PVE's host machine
shell
/etc/pve/firewall/<VMID>.fw
+import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"Avoid theft by setting up a firewall to limit the IPs used by the VMs","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/block/block_pve.md","filePath":"en/guide/block/block_pve.md","lastUpdated":1747730955000}'),n={name:"en/guide/block/block_pve.md"},o=a(`
Avoid theft by setting up a firewall to limit the IPs used by the VMs ​
Create the following file under the PVE's host machine
shell
/etc/pve/firewall/<VMID>.fw
 [IPSET ipfilter-<net0>]
 xxx.xxx.xxx.xxx
<VMID> is replaced with the VMID number of the virtual machine, <net0> is replaced with the corresponding alias in the network device (which generally doesn't need to be changed unless you're restricted to IPV6), and xxx.xxx.xxx.xxx is replaced with the public IP address, noting that this IP corresponds to the network device in front of it.
The idea here is that net0 can only use the IP xxx.xxx.xxx.xxx, if you use any other IP the data will be dropped, thus restricting the VM to only use this IP.
There can be more than one IP, once this rule is enabled the VM can't use any other IP, if you don't write an IPv6 address it means the VM can't use an IPv6 address.
TIP
This setting is only recommended when opening VMs with separate IPs that are not NAT full port mapped, otherwise it may cause strange issues resulting in the server being without a network.
This method is not suitable for use on PVEs that open any NAT VMs/containers.
`,8),i=[o];function l(r,p,h,c,d,u){return t(),s("div",null,i)}const g=e(n,[["render",l]]);export{b as __pageData,g as default};
diff --git a/assets/en_guide_dashboard.md.ee4b3fc1.js b/assets/en_guide_dashboard.md.a98739aa.js
similarity index 98%
rename from assets/en_guide_dashboard.md.ee4b3fc1.js
rename to assets/en_guide_dashboard.md.a98739aa.js
index 905833c7eb..011533ea61 100644
--- a/assets/en_guide_dashboard.md.ee4b3fc1.js
+++ b/assets/en_guide_dashboard.md.a98739aa.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a,R as r}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/dashboard.md","filePath":"en/guide/dashboard.md","lastUpdated":1747726389000}'),i={name:"en/guide/dashboard.md"},o=r('
Preparation Work ​
To virtualize a server, you will need:
  1. A server (VPS or Dedicated Server) that can connect to the public internet. It's preferable if this server can access GitHub's RAW pages perfectly, as some projects and components might not use CDN acceleration.
  2. A stable SSH connection from your local machine. If the connection isn't stable, you can use the screen command to create a window and execute commands within that window.
TIP
If you're unfamiliar with the screen command, please search for relevant tutorials to learn it, or you can use tmux as an alternative.
  1. Ensure that the server's system and hardware meet the requirements specified by the corresponding project. Refer to the project's documentation for detailed information.
This document will use a VPS as an example, and the VPS should be clean without any native environment issues. If necessary, reinstall the system to ensure the initial environment's cleanliness.
WARNING
The PVE project might cause problems on the host machine. If you're not familiar with debugging bugs and fixing system issues, it's not recommended to use PVE in a production environment. When using PVE-related scripts, make sure the host machine can be reinstalled at any time.
Project Repository ​
Welcome Star and Fork, all resources are open source, no non-open source parts, reproduced as well as the use of please write on the source of this site, thank you!
PVE ​
https://github.com/oneclickvirt/pve
Hits
incus ​
https://github.com/oneclickvirt/incus
Hits
Docker ​
https://github.com/oneclickvirt/docker
Hits
LXD ​
https://github.com/oneclickvirt/lxd
Hits
',21),s=[o];function n(l,c,h,p,d,u){return t(),a("div",null,s)}const b=e(i,[["render",n]]);export{f as __pageData,b as default};
+import{_ as e,v as t,b as a,R as r}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/dashboard.md","filePath":"en/guide/dashboard.md","lastUpdated":1747730955000}'),i={name:"en/guide/dashboard.md"},o=r('
Preparation Work ​
To virtualize a server, you will need:
  1. A server (VPS or Dedicated Server) that can connect to the public internet. It's preferable if this server can access GitHub's RAW pages perfectly, as some projects and components might not use CDN acceleration.
  2. A stable SSH connection from your local machine. If the connection isn't stable, you can use the screen command to create a window and execute commands within that window.
TIP
If you're unfamiliar with the screen command, please search for relevant tutorials to learn it, or you can use tmux as an alternative.
  1. Ensure that the server's system and hardware meet the requirements specified by the corresponding project. Refer to the project's documentation for detailed information.
This document will use a VPS as an example, and the VPS should be clean without any native environment issues. If necessary, reinstall the system to ensure the initial environment's cleanliness.
WARNING
The PVE project might cause problems on the host machine. If you're not familiar with debugging bugs and fixing system issues, it's not recommended to use PVE in a production environment. When using PVE-related scripts, make sure the host machine can be reinstalled at any time.
Project Repository ​
Welcome Star and Fork, all resources are open source, no non-open source parts, reproduced as well as the use of please write on the source of this site, thank you!
PVE ​
https://github.com/oneclickvirt/pve
Hits
incus ​
https://github.com/oneclickvirt/incus
Hits
Docker ​
https://github.com/oneclickvirt/docker
Hits
LXD ​
https://github.com/oneclickvirt/lxd
Hits
',21),s=[o];function n(l,c,h,p,d,u){return t(),a("div",null,s)}const b=e(i,[["render",n]]);export{f as __pageData,b as default};
diff --git a/assets/en_guide_dashboard.md.ee4b3fc1.lean.js b/assets/en_guide_dashboard.md.a98739aa.lean.js
similarity index 98%
rename from assets/en_guide_dashboard.md.ee4b3fc1.lean.js
rename to assets/en_guide_dashboard.md.a98739aa.lean.js
index 905833c7eb..011533ea61 100644
--- a/assets/en_guide_dashboard.md.ee4b3fc1.lean.js
+++ b/assets/en_guide_dashboard.md.a98739aa.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a,R as r}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/dashboard.md","filePath":"en/guide/dashboard.md","lastUpdated":1747726389000}'),i={name:"en/guide/dashboard.md"},o=r('
Preparation Work ​
To virtualize a server, you will need:
  1. A server (VPS or Dedicated Server) that can connect to the public internet. It's preferable if this server can access GitHub's RAW pages perfectly, as some projects and components might not use CDN acceleration.
  2. A stable SSH connection from your local machine. If the connection isn't stable, you can use the screen command to create a window and execute commands within that window.
TIP
If you're unfamiliar with the screen command, please search for relevant tutorials to learn it, or you can use tmux as an alternative.
  1. Ensure that the server's system and hardware meet the requirements specified by the corresponding project. Refer to the project's documentation for detailed information.
This document will use a VPS as an example, and the VPS should be clean without any native environment issues. If necessary, reinstall the system to ensure the initial environment's cleanliness.
WARNING
The PVE project might cause problems on the host machine. If you're not familiar with debugging bugs and fixing system issues, it's not recommended to use PVE in a production environment. When using PVE-related scripts, make sure the host machine can be reinstalled at any time.
Project Repository ​
Welcome Star and Fork, all resources are open source, no non-open source parts, reproduced as well as the use of please write on the source of this site, thank you!
PVE ​
https://github.com/oneclickvirt/pve
Hits
incus ​
https://github.com/oneclickvirt/incus
Hits
Docker ​
https://github.com/oneclickvirt/docker
Hits
LXD ​
https://github.com/oneclickvirt/lxd
Hits
',21),s=[o];function n(l,c,h,p,d,u){return t(),a("div",null,s)}const b=e(i,[["render",n]]);export{f as __pageData,b as default};
+import{_ as e,v as t,b as a,R as r}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/dashboard.md","filePath":"en/guide/dashboard.md","lastUpdated":1747730955000}'),i={name:"en/guide/dashboard.md"},o=r('
Preparation Work ​
To virtualize a server, you will need:
  1. A server (VPS or Dedicated Server) that can connect to the public internet. It's preferable if this server can access GitHub's RAW pages perfectly, as some projects and components might not use CDN acceleration.
  2. A stable SSH connection from your local machine. If the connection isn't stable, you can use the screen command to create a window and execute commands within that window.
TIP
If you're unfamiliar with the screen command, please search for relevant tutorials to learn it, or you can use tmux as an alternative.
  1. Ensure that the server's system and hardware meet the requirements specified by the corresponding project. Refer to the project's documentation for detailed information.
This document will use a VPS as an example, and the VPS should be clean without any native environment issues. If necessary, reinstall the system to ensure the initial environment's cleanliness.
WARNING
The PVE project might cause problems on the host machine. If you're not familiar with debugging bugs and fixing system issues, it's not recommended to use PVE in a production environment. When using PVE-related scripts, make sure the host machine can be reinstalled at any time.
Project Repository ​
Welcome Star and Fork, all resources are open source, no non-open source parts, reproduced as well as the use of please write on the source of this site, thank you!
PVE ​
https://github.com/oneclickvirt/pve
Hits
incus ​
https://github.com/oneclickvirt/incus
Hits
Docker ​
https://github.com/oneclickvirt/docker
Hits
LXD ​
https://github.com/oneclickvirt/lxd
Hits
',21),s=[o];function n(l,c,h,p,d,u){return t(),a("div",null,s)}const b=e(i,[["render",n]]);export{f as __pageData,b as default};
diff --git a/assets/en_guide_dashboardq.md.c810f576.js b/assets/en_guide_dashboardq.md.eeb9456d.js
similarity index 94%
rename from assets/en_guide_dashboardq.md.c810f576.js
rename to assets/en_guide_dashboardq.md.eeb9456d.js
index d2d9aabef6..d9936f4a3f 100644
--- a/assets/en_guide_dashboardq.md.c810f576.js
+++ b/assets/en_guide_dashboardq.md.eeb9456d.js
@@ -1 +1 @@
-import{_ as a,v as s,b as e,R as t}from"./chunks/framework.70afa331.js";const p="/assets/wechat.e3b2e06e.jpg",_=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/dashboardq.md","filePath":"en/guide/dashboardq.md","lastUpdated":1747726389000}'),o={name:"en/guide/dashboardq.md"},n=t('
Give me a cup of coffee.
https://ko-fi.com/spiritlhl
WeChat
WeChat
USDT-TRC20
bash
TNqjaPYAmDsm9pbpLY79pixE8z1ce3Zj1B
USDT-Polygon/Matic
bash
0xb81b44cb00f9e6e084f85e5da604ec479e7ffab6
',8),c=[n];function i(l,r,d,h,b,f){return s(),e("div",null,c)}const g=a(o,[["render",i]]);export{_ as __pageData,g as default};
+import{_ as a,v as s,b as e,R as t}from"./chunks/framework.70afa331.js";const p="/assets/wechat.e3b2e06e.jpg",_=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/dashboardq.md","filePath":"en/guide/dashboardq.md","lastUpdated":1747730955000}'),o={name:"en/guide/dashboardq.md"},n=t('
Give me a cup of coffee.
https://ko-fi.com/spiritlhl
WeChat
WeChat
USDT-TRC20
bash
TNqjaPYAmDsm9pbpLY79pixE8z1ce3Zj1B
USDT-Polygon/Matic
bash
0xb81b44cb00f9e6e084f85e5da604ec479e7ffab6
',8),c=[n];function i(l,r,d,h,b,f){return s(),e("div",null,c)}const g=a(o,[["render",i]]);export{_ as __pageData,g as default};
diff --git a/assets/en_guide_dashboardq.md.c810f576.lean.js b/assets/en_guide_dashboardq.md.eeb9456d.lean.js
similarity index 94%
rename from assets/en_guide_dashboardq.md.c810f576.lean.js
rename to assets/en_guide_dashboardq.md.eeb9456d.lean.js
index d2d9aabef6..d9936f4a3f 100644
--- a/assets/en_guide_dashboardq.md.c810f576.lean.js
+++ b/assets/en_guide_dashboardq.md.eeb9456d.lean.js
@@ -1 +1 @@
-import{_ as a,v as s,b as e,R as t}from"./chunks/framework.70afa331.js";const p="/assets/wechat.e3b2e06e.jpg",_=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/dashboardq.md","filePath":"en/guide/dashboardq.md","lastUpdated":1747726389000}'),o={name:"en/guide/dashboardq.md"},n=t('
Give me a cup of coffee.
https://ko-fi.com/spiritlhl
WeChat
WeChat
USDT-TRC20
bash
TNqjaPYAmDsm9pbpLY79pixE8z1ce3Zj1B
USDT-Polygon/Matic
bash
0xb81b44cb00f9e6e084f85e5da604ec479e7ffab6
',8),c=[n];function i(l,r,d,h,b,f){return s(),e("div",null,c)}const g=a(o,[["render",i]]);export{_ as __pageData,g as default};
+import{_ as a,v as s,b as e,R as t}from"./chunks/framework.70afa331.js";const p="/assets/wechat.e3b2e06e.jpg",_=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/dashboardq.md","filePath":"en/guide/dashboardq.md","lastUpdated":1747730955000}'),o={name:"en/guide/dashboardq.md"},n=t('
Give me a cup of coffee.
https://ko-fi.com/spiritlhl
WeChat
WeChat
USDT-TRC20
bash
TNqjaPYAmDsm9pbpLY79pixE8z1ce3Zj1B
USDT-Polygon/Matic
bash
0xb81b44cb00f9e6e084f85e5da604ec479e7ffab6
',8),c=[n];function i(l,r,d,h,b,f){return s(),e("div",null,c)}const g=a(o,[["render",i]]);export{_ as __pageData,g as default};
diff --git a/assets/en_guide_docker_docker_android.md.c3074ab7.js b/assets/en_guide_docker_docker_android.md.3fc2817d.js
similarity index 99%
rename from assets/en_guide_docker_docker_android.md.c3074ab7.js
rename to assets/en_guide_docker_docker_android.md.3fc2817d.js
index dac5920d23..198d41e36c 100644
--- a/assets/en_guide_docker_docker_android.md.c3074ab7.js
+++ b/assets/en_guide_docker_docker_android.md.3fc2817d.js
@@ -1,4 +1,4 @@
-import{_ as e,v as n,b as s,R as o}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Running Android Virtual Machine in Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_android.md","filePath":"en/guide/docker/docker_android.md","lastUpdated":1747726389000}'),a={name:"en/guide/docker/docker_android.md"},t=o(`
Running Android Virtual Machine in Docker ​
One-Click Deployment ​
  • Customizable Android version
  • Automatically creates a validated web website
  • Automatically installs Nginx and configures reverse proxy. Option to bind a domain is available. Default is port 80 if no domain binding is chosen.
  • No need to worry about host machine supporting nested virtualization
  • Supports x86_64 and ARM architectures
Host machine should have a minimum configuration of 1 core, 2GB RAM, and 15GB storage, else starting the setup might lead to host machine freezing.
Ubuntu is recommended for hosting, Debian may cause white screen on Android.
Newer Android versions occupy more resources. The above configuration requirements are for the minimum version of Android. (Personally tested with the tag "12.0.0-latest", higher versions resulted in a blank screen. Test which version works for you.)
If, after 5 minutes after opening, the login verification of the browser page still keeps failing, then please check the logs of the Android container, it is probable that the Android container has crashed, and it is recommended to replace the container with a lower version of the Android system for installation.
Setup:
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/create_android.sh -o create_android.sh && chmod +x create_android.sh && bash create_android.sh
After executing the command, follow the prompts to input the required information. Make sure to choose the version by entering the corresponding number index. Once the installation is complete, open YourMachineIPv4+80Port to log in.
If you need to check the generated Android information and web login details, execute cat /root/android_info to retrieve the information.
Default username: onea Default password: oneclick
For remote desktop, click on H264 Converter to initiate the redirection.
Please note that currently only one Android container can be generated. Do not generate duplicates. If you need to replace the version, please execute the subsequent commands after deletion.
Temporarily only support the opening has been used, can not restart the server, reboot may not be able to restart after the mapping success, self-test
Deletion:
  • Delete the container
  • Delete the corresponding container image
  • Delete the configuration file
shell
docker rm -f android
+import{_ as e,v as n,b as s,R as o}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Running Android Virtual Machine in Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_android.md","filePath":"en/guide/docker/docker_android.md","lastUpdated":1747730955000}'),a={name:"en/guide/docker/docker_android.md"},t=o(`
Running Android Virtual Machine in Docker ​
One-Click Deployment ​
  • Customizable Android version
  • Automatically creates a validated web website
  • Automatically installs Nginx and configures reverse proxy. Option to bind a domain is available. Default is port 80 if no domain binding is chosen.
  • No need to worry about host machine supporting nested virtualization
  • Supports x86_64 and ARM architectures
Host machine should have a minimum configuration of 1 core, 2GB RAM, and 15GB storage, else starting the setup might lead to host machine freezing.
Ubuntu is recommended for hosting, Debian may cause white screen on Android.
Newer Android versions occupy more resources. The above configuration requirements are for the minimum version of Android. (Personally tested with the tag "12.0.0-latest", higher versions resulted in a blank screen. Test which version works for you.)
If, after 5 minutes after opening, the login verification of the browser page still keeps failing, then please check the logs of the Android container, it is probable that the Android container has crashed, and it is recommended to replace the container with a lower version of the Android system for installation.
Setup:
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/create_android.sh -o create_android.sh && chmod +x create_android.sh && bash create_android.sh
After executing the command, follow the prompts to input the required information. Make sure to choose the version by entering the corresponding number index. Once the installation is complete, open YourMachineIPv4+80Port to log in.
If you need to check the generated Android information and web login details, execute cat /root/android_info to retrieve the information.
Default username: onea Default password: oneclick
For remote desktop, click on H264 Converter to initiate the redirection.
Please note that currently only one Android container can be generated. Do not generate duplicates. If you need to replace the version, please execute the subsequent commands after deletion.
Temporarily only support the opening has been used, can not restart the server, reboot may not be able to restart after the mapping success, self-test
Deletion:
  • Delete the container
  • Delete the corresponding container image
  • Delete the configuration file
shell
docker rm -f android
 docker rmi $(docker images | grep "redroid" | awk '{print $3}')
 rm -rf /etc/nginx/sites-enabled/reverse-proxy
 rm -rf /etc/nginx/sites-available/reverse-proxy
diff --git a/assets/en_guide_docker_docker_android.md.c3074ab7.lean.js b/assets/en_guide_docker_docker_android.md.3fc2817d.lean.js
similarity index 99%
rename from assets/en_guide_docker_docker_android.md.c3074ab7.lean.js
rename to assets/en_guide_docker_docker_android.md.3fc2817d.lean.js
index dac5920d23..198d41e36c 100644
--- a/assets/en_guide_docker_docker_android.md.c3074ab7.lean.js
+++ b/assets/en_guide_docker_docker_android.md.3fc2817d.lean.js
@@ -1,4 +1,4 @@
-import{_ as e,v as n,b as s,R as o}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Running Android Virtual Machine in Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_android.md","filePath":"en/guide/docker/docker_android.md","lastUpdated":1747726389000}'),a={name:"en/guide/docker/docker_android.md"},t=o(`
Running Android Virtual Machine in Docker ​
One-Click Deployment ​
  • Customizable Android version
  • Automatically creates a validated web website
  • Automatically installs Nginx and configures reverse proxy. Option to bind a domain is available. Default is port 80 if no domain binding is chosen.
  • No need to worry about host machine supporting nested virtualization
  • Supports x86_64 and ARM architectures
Host machine should have a minimum configuration of 1 core, 2GB RAM, and 15GB storage, else starting the setup might lead to host machine freezing.
Ubuntu is recommended for hosting, Debian may cause white screen on Android.
Newer Android versions occupy more resources. The above configuration requirements are for the minimum version of Android. (Personally tested with the tag "12.0.0-latest", higher versions resulted in a blank screen. Test which version works for you.)
If, after 5 minutes after opening, the login verification of the browser page still keeps failing, then please check the logs of the Android container, it is probable that the Android container has crashed, and it is recommended to replace the container with a lower version of the Android system for installation.
Setup:
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/create_android.sh -o create_android.sh && chmod +x create_android.sh && bash create_android.sh
After executing the command, follow the prompts to input the required information. Make sure to choose the version by entering the corresponding number index. Once the installation is complete, open YourMachineIPv4+80Port to log in.
If you need to check the generated Android information and web login details, execute cat /root/android_info to retrieve the information.
Default username: onea Default password: oneclick
For remote desktop, click on H264 Converter to initiate the redirection.
Please note that currently only one Android container can be generated. Do not generate duplicates. If you need to replace the version, please execute the subsequent commands after deletion.
Temporarily only support the opening has been used, can not restart the server, reboot may not be able to restart after the mapping success, self-test
Deletion:
  • Delete the container
  • Delete the corresponding container image
  • Delete the configuration file
shell
docker rm -f android
+import{_ as e,v as n,b as s,R as o}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Running Android Virtual Machine in Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_android.md","filePath":"en/guide/docker/docker_android.md","lastUpdated":1747730955000}'),a={name:"en/guide/docker/docker_android.md"},t=o(`
Running Android Virtual Machine in Docker ​
One-Click Deployment ​
  • Customizable Android version
  • Automatically creates a validated web website
  • Automatically installs Nginx and configures reverse proxy. Option to bind a domain is available. Default is port 80 if no domain binding is chosen.
  • No need to worry about host machine supporting nested virtualization
  • Supports x86_64 and ARM architectures
Host machine should have a minimum configuration of 1 core, 2GB RAM, and 15GB storage, else starting the setup might lead to host machine freezing.
Ubuntu is recommended for hosting, Debian may cause white screen on Android.
Newer Android versions occupy more resources. The above configuration requirements are for the minimum version of Android. (Personally tested with the tag "12.0.0-latest", higher versions resulted in a blank screen. Test which version works for you.)
If, after 5 minutes after opening, the login verification of the browser page still keeps failing, then please check the logs of the Android container, it is probable that the Android container has crashed, and it is recommended to replace the container with a lower version of the Android system for installation.
Setup:
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/create_android.sh -o create_android.sh && chmod +x create_android.sh && bash create_android.sh
After executing the command, follow the prompts to input the required information. Make sure to choose the version by entering the corresponding number index. Once the installation is complete, open YourMachineIPv4+80Port to log in.
If you need to check the generated Android information and web login details, execute cat /root/android_info to retrieve the information.
Default username: onea Default password: oneclick
For remote desktop, click on H264 Converter to initiate the redirection.
Please note that currently only one Android container can be generated. Do not generate duplicates. If you need to replace the version, please execute the subsequent commands after deletion.
Temporarily only support the opening has been used, can not restart the server, reboot may not be able to restart after the mapping success, self-test
Deletion:
  • Delete the container
  • Delete the corresponding container image
  • Delete the configuration file
shell
docker rm -f android
 docker rmi $(docker images | grep "redroid" | awk '{print $3}')
 rm -rf /etc/nginx/sites-enabled/reverse-proxy
 rm -rf /etc/nginx/sites-available/reverse-proxy
diff --git a/assets/en_guide_docker_docker_build.md.f3c9d6b5.js b/assets/en_guide_docker_docker_build.md.374f9f42.js
similarity index 99%
rename from assets/en_guide_docker_docker_build.md.f3c9d6b5.js
rename to assets/en_guide_docker_docker_build.md.374f9f42.js
index f18bc388fc..d2ff088026 100644
--- a/assets/en_guide_docker_docker_build.md.f3c9d6b5.js
+++ b/assets/en_guide_docker_docker_build.md.374f9f42.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"Introduction","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_build.md","filePath":"en/guide/docker/docker_build.md","lastUpdated":1747726389000}'),e={name:"en/guide/docker/docker_build.md"},l=o(`
Introduction ​
There are two methods of building
Setting Up Standalone ​
  • Generate only one docker
  • Can be configured to bind a separate IPV6 address, but requires a docker previously installed using the environment installation command of this set of scripts, and requires the host to be bound to at least the /112 IPV6 subnet
  • Support for x86_64 and ARM architecture servers
Download the Script ​
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
Example ​
Run
./onedocker.sh name cpu memory password sshport startport endport <independent_ipv6> <system>
Currently, the system only supports selecting:
  • alpine
  • debian
  • ubuntu
  • almalinux
with Debian being the default choice.
The following is the information for the created example container:
AttributeValue
Container Nametest
Username for SSH Loginroot
Password for SSH Login123456
Number of CPU Cores1
Memory Size512MB
SSH Port25000
Port Range for Internal and External Mapping34975 to 35000
Operating Systemdebian
Whether to bind a separate IPV6 addressN
shell
./onedocker.sh test 1 512 123456 25000 34975 35000 N debian
Deleting the test container
shell
docker rm -f test
+import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"Introduction","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_build.md","filePath":"en/guide/docker/docker_build.md","lastUpdated":1747730955000}'),e={name:"en/guide/docker/docker_build.md"},l=o(`
Introduction ​
There are two methods of building
Setting Up Standalone ​
  • Generate only one docker
  • Can be configured to bind a separate IPV6 address, but requires a docker previously installed using the environment installation command of this set of scripts, and requires the host to be bound to at least the /112 IPV6 subnet
  • Support for x86_64 and ARM architecture servers
Download the Script ​
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
Example ​
Run
./onedocker.sh name cpu memory password sshport startport endport <independent_ipv6> <system>
Currently, the system only supports selecting:
  • alpine
  • debian
  • ubuntu
  • almalinux
with Debian being the default choice.
The following is the information for the created example container:
AttributeValue
Container Nametest
Username for SSH Loginroot
Password for SSH Login123456
Number of CPU Cores1
Memory Size512MB
SSH Port25000
Port Range for Internal and External Mapping34975 to 35000
Operating Systemdebian
Whether to bind a separate IPV6 addressN
shell
./onedocker.sh test 1 512 123456 25000 34975 35000 N debian
Deleting the test container
shell
docker rm -f test
 rm -rf test
 ls
Accessing the test container
shell
docker exec -it test /bin/bash
To exit the container, simply execute exit.
Inquiry Information
shell
cat Container_Name(change me)
The output format is
Container_Name SSH_Port Root_Password Number_of_Cores Memory Start_of_Public_Port End_of_Public_Port
The docker's ipv6 address can only be looked up within the container itself, it doesn't exist in the docker's configuration
Batch Deployment ​
  • Run inheritance configuration generation multiple times in bulk.
  • When generating multiple instances, it is recommended to execute within a screen session to avoid SSH connection interruptions.
  • Support for x86_64 and ARM architecture servers
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/create_docker.sh -o create_docker.sh && chmod +x create_docker.sh && bash create_docker.sh
Querying information on batch openings ​
shell
cat dclog
The output format is
Container_Name SSH_Port Root_Password Number_of_Cores Memory Start_of_Public_Port End_of_Public_Port
One line corresponds to information about a container, the docker's ipv6 address can only be looked up within the container itself, it doesn't exist in the docker's configuration.
Uninstall all Docker containers and images ​
The following command offload ignores ndpresponder to prevent IPV6 configuration failure
shell
docker ps -aq --format '{{.Names}}' | grep -E '^ndpresponder' | xargs -r docker rm -f
 docker images -aq --format '{{.Repository}}:{{.Tag}}' | grep -E '^ndpresponder' | xargs -r docker rmi
diff --git a/assets/en_guide_docker_docker_build.md.f3c9d6b5.lean.js b/assets/en_guide_docker_docker_build.md.374f9f42.lean.js
similarity index 99%
rename from assets/en_guide_docker_docker_build.md.f3c9d6b5.lean.js
rename to assets/en_guide_docker_docker_build.md.374f9f42.lean.js
index f18bc388fc..d2ff088026 100644
--- a/assets/en_guide_docker_docker_build.md.f3c9d6b5.lean.js
+++ b/assets/en_guide_docker_docker_build.md.374f9f42.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"Introduction","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_build.md","filePath":"en/guide/docker/docker_build.md","lastUpdated":1747726389000}'),e={name:"en/guide/docker/docker_build.md"},l=o(`
Introduction ​
There are two methods of building
Setting Up Standalone ​
  • Generate only one docker
  • Can be configured to bind a separate IPV6 address, but requires a docker previously installed using the environment installation command of this set of scripts, and requires the host to be bound to at least the /112 IPV6 subnet
  • Support for x86_64 and ARM architecture servers
Download the Script ​
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
Example ​
Run
./onedocker.sh name cpu memory password sshport startport endport <independent_ipv6> <system>
Currently, the system only supports selecting:
  • alpine
  • debian
  • ubuntu
  • almalinux
with Debian being the default choice.
The following is the information for the created example container:
AttributeValue
Container Nametest
Username for SSH Loginroot
Password for SSH Login123456
Number of CPU Cores1
Memory Size512MB
SSH Port25000
Port Range for Internal and External Mapping34975 to 35000
Operating Systemdebian
Whether to bind a separate IPV6 addressN
shell
./onedocker.sh test 1 512 123456 25000 34975 35000 N debian
Deleting the test container
shell
docker rm -f test
+import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"Introduction","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_build.md","filePath":"en/guide/docker/docker_build.md","lastUpdated":1747730955000}'),e={name:"en/guide/docker/docker_build.md"},l=o(`
Introduction ​
There are two methods of building
Setting Up Standalone ​
  • Generate only one docker
  • Can be configured to bind a separate IPV6 address, but requires a docker previously installed using the environment installation command of this set of scripts, and requires the host to be bound to at least the /112 IPV6 subnet
  • Support for x86_64 and ARM architecture servers
Download the Script ​
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
Example ​
Run
./onedocker.sh name cpu memory password sshport startport endport <independent_ipv6> <system>
Currently, the system only supports selecting:
  • alpine
  • debian
  • ubuntu
  • almalinux
with Debian being the default choice.
The following is the information for the created example container:
AttributeValue
Container Nametest
Username for SSH Loginroot
Password for SSH Login123456
Number of CPU Cores1
Memory Size512MB
SSH Port25000
Port Range for Internal and External Mapping34975 to 35000
Operating Systemdebian
Whether to bind a separate IPV6 addressN
shell
./onedocker.sh test 1 512 123456 25000 34975 35000 N debian
Deleting the test container
shell
docker rm -f test
 rm -rf test
 ls
Accessing the test container
shell
docker exec -it test /bin/bash
To exit the container, simply execute exit.
Inquiry Information
shell
cat Container_Name(change me)
The output format is
Container_Name SSH_Port Root_Password Number_of_Cores Memory Start_of_Public_Port End_of_Public_Port
The docker's ipv6 address can only be looked up within the container itself, it doesn't exist in the docker's configuration
Batch Deployment ​
  • Run inheritance configuration generation multiple times in bulk.
  • When generating multiple instances, it is recommended to execute within a screen session to avoid SSH connection interruptions.
  • Support for x86_64 and ARM architecture servers
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/create_docker.sh -o create_docker.sh && chmod +x create_docker.sh && bash create_docker.sh
Querying information on batch openings ​
shell
cat dclog
The output format is
Container_Name SSH_Port Root_Password Number_of_Cores Memory Start_of_Public_Port End_of_Public_Port
One line corresponds to information about a container, the docker's ipv6 address can only be looked up within the container itself, it doesn't exist in the docker's configuration.
Uninstall all Docker containers and images ​
The following command offload ignores ndpresponder to prevent IPV6 configuration failure
shell
docker ps -aq --format '{{.Names}}' | grep -E '^ndpresponder' | xargs -r docker rm -f
 docker images -aq --format '{{.Repository}}:{{.Tag}}' | grep -E '^ndpresponder' | xargs -r docker rmi
diff --git a/assets/en_guide_docker_docker_custom.md.7f4ad96a.js b/assets/en_guide_docker_docker_custom.md.670a640f.js
similarity index 99%
rename from assets/en_guide_docker_docker_custom.md.7f4ad96a.js
rename to assets/en_guide_docker_docker_custom.md.670a640f.js
index f30f1f6df1..502e53387f 100644
--- a/assets/en_guide_docker_docker_custom.md.7f4ad96a.js
+++ b/assets/en_guide_docker_docker_custom.md.670a640f.js
@@ -1,4 +1,4 @@
-import{_ as s,v as o,b as e,R as a}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Script for One-Click Installation of Certain Containers using Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_custom.md","filePath":"en/guide/docker/docker_custom.md","lastUpdated":1747726389000}'),n={name:"en/guide/docker/docker_custom.md"},l=a(`
Script for One-Click Installation of Certain Containers using Docker ​
Each container has specific configuration requirements; please refer to them individually.
If the configured memory is not enough, then it's okay to make up for it with the virtual memory here.
Note that the following scripts must be pre-installed using the environment installation scripts in this set of tutorials before using them
One-Click Setup of Firefox Browser Container ​
  • Crash recovery on startup has been configured.
  • Chinese fonts have been integrated into the container.
  • Built-in web validation with the option to set a custom password.
  • Maximum memory usage for the container is customizable.
  • Choice to enable VNC port, disabled by default.
  • No need to consider support for nested virtualization or server architecture.
  • Audio mapping is not supported; sound transmission is unavailable on both the web and VNC.
The host machine should have at least 1 core, 1GB RAM, and 5GB disk space. The created container will occupy a minimum of 1GB disk space.
Setup:
After setup, the default password is oneclick.
The default web port is 3003. Once the setup is complete, simply open HOST_IPV4:PORT in your browser.
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onefirefox.sh -o onefirefox.sh && chmod +x onefirefox.sh && bash onefirefox.sh
Deletion
Modify the following port number 3003 to your actual port number, and then execute the command to delete the container, configuration file, and corresponding image
shell
PORT="3003"
+import{_ as s,v as o,b as e,R as a}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Script for One-Click Installation of Certain Containers using Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_custom.md","filePath":"en/guide/docker/docker_custom.md","lastUpdated":1747730955000}'),n={name:"en/guide/docker/docker_custom.md"},l=a(`
Script for One-Click Installation of Certain Containers using Docker ​
Each container has specific configuration requirements; please refer to them individually.
If the configured memory is not enough, then it's okay to make up for it with the virtual memory here.
Note that the following scripts must be pre-installed using the environment installation scripts in this set of tutorials before using them
One-Click Setup of Firefox Browser Container ​
  • Crash recovery on startup has been configured.
  • Chinese fonts have been integrated into the container.
  • Built-in web validation with the option to set a custom password.
  • Maximum memory usage for the container is customizable.
  • Choice to enable VNC port, disabled by default.
  • No need to consider support for nested virtualization or server architecture.
  • Audio mapping is not supported; sound transmission is unavailable on both the web and VNC.
The host machine should have at least 1 core, 1GB RAM, and 5GB disk space. The created container will occupy a minimum of 1GB disk space.
Setup:
After setup, the default password is oneclick.
The default web port is 3003. Once the setup is complete, simply open HOST_IPV4:PORT in your browser.
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onefirefox.sh -o onefirefox.sh && chmod +x onefirefox.sh && bash onefirefox.sh
Deletion
Modify the following port number 3003 to your actual port number, and then execute the command to delete the container, configuration file, and corresponding image
shell
PORT="3003"
 docker stop firefox_\${PORT}
 docker rm -f firefox_\${PORT}
 rm -rf /usr/local/bin/firefox_\${PORT}
diff --git a/assets/en_guide_docker_docker_custom.md.7f4ad96a.lean.js b/assets/en_guide_docker_docker_custom.md.670a640f.lean.js
similarity index 99%
rename from assets/en_guide_docker_docker_custom.md.7f4ad96a.lean.js
rename to assets/en_guide_docker_docker_custom.md.670a640f.lean.js
index f30f1f6df1..502e53387f 100644
--- a/assets/en_guide_docker_docker_custom.md.7f4ad96a.lean.js
+++ b/assets/en_guide_docker_docker_custom.md.670a640f.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as o,b as e,R as a}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Script for One-Click Installation of Certain Containers using Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_custom.md","filePath":"en/guide/docker/docker_custom.md","lastUpdated":1747726389000}'),n={name:"en/guide/docker/docker_custom.md"},l=a(`
Script for One-Click Installation of Certain Containers using Docker ​
Each container has specific configuration requirements; please refer to them individually.
If the configured memory is not enough, then it's okay to make up for it with the virtual memory here.
Note that the following scripts must be pre-installed using the environment installation scripts in this set of tutorials before using them
One-Click Setup of Firefox Browser Container ​
  • Crash recovery on startup has been configured.
  • Chinese fonts have been integrated into the container.
  • Built-in web validation with the option to set a custom password.
  • Maximum memory usage for the container is customizable.
  • Choice to enable VNC port, disabled by default.
  • No need to consider support for nested virtualization or server architecture.
  • Audio mapping is not supported; sound transmission is unavailable on both the web and VNC.
The host machine should have at least 1 core, 1GB RAM, and 5GB disk space. The created container will occupy a minimum of 1GB disk space.
Setup:
After setup, the default password is oneclick.
The default web port is 3003. Once the setup is complete, simply open HOST_IPV4:PORT in your browser.
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onefirefox.sh -o onefirefox.sh && chmod +x onefirefox.sh && bash onefirefox.sh
Deletion
Modify the following port number 3003 to your actual port number, and then execute the command to delete the container, configuration file, and corresponding image
shell
PORT="3003"
+import{_ as s,v as o,b as e,R as a}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Script for One-Click Installation of Certain Containers using Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_custom.md","filePath":"en/guide/docker/docker_custom.md","lastUpdated":1747730955000}'),n={name:"en/guide/docker/docker_custom.md"},l=a(`
Script for One-Click Installation of Certain Containers using Docker ​
Each container has specific configuration requirements; please refer to them individually.
If the configured memory is not enough, then it's okay to make up for it with the virtual memory here.
Note that the following scripts must be pre-installed using the environment installation scripts in this set of tutorials before using them
One-Click Setup of Firefox Browser Container ​
  • Crash recovery on startup has been configured.
  • Chinese fonts have been integrated into the container.
  • Built-in web validation with the option to set a custom password.
  • Maximum memory usage for the container is customizable.
  • Choice to enable VNC port, disabled by default.
  • No need to consider support for nested virtualization or server architecture.
  • Audio mapping is not supported; sound transmission is unavailable on both the web and VNC.
The host machine should have at least 1 core, 1GB RAM, and 5GB disk space. The created container will occupy a minimum of 1GB disk space.
Setup:
After setup, the default password is oneclick.
The default web port is 3003. Once the setup is complete, simply open HOST_IPV4:PORT in your browser.
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onefirefox.sh -o onefirefox.sh && chmod +x onefirefox.sh && bash onefirefox.sh
Deletion
Modify the following port number 3003 to your actual port number, and then execute the command to delete the container, configuration file, and corresponding image
shell
PORT="3003"
 docker stop firefox_\${PORT}
 docker rm -f firefox_\${PORT}
 rm -rf /usr/local/bin/firefox_\${PORT}
diff --git a/assets/en_guide_docker_docker_install.md.ecacf3a2.js b/assets/en_guide_docker_docker_install.md.6de25cff.js
similarity index 98%
rename from assets/en_guide_docker_docker_install.md.ecacf3a2.js
rename to assets/en_guide_docker_docker_install.md.6de25cff.js
index e88870ec6d..89729da132 100644
--- a/assets/en_guide_docker_docker_install.md.ecacf3a2.js
+++ b/assets/en_guide_docker_docker_install.md.6de25cff.js
@@ -1 +1 @@
-import{_ as s,v as a,b as e,R as o}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_install.md","filePath":"en/guide/docker/docker_install.md","lastUpdated":1747726389000}'),n={name:"en/guide/docker/docker_install.md"},t=o('
Preface ​
Support for running Docker virtualization on various systems, including Linux, Android, and Windows.
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the LXD module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
Setting Up Virtual Memory ​
TIP
Allocate some swap space to prevent your machine from crashing.
Unit conversion: Inputting 1024 results in 1G of SWAP - virtual memory. Virtual memory occupies disk space and is automatically utilized when the physical memory is insufficient. However, this leads to high IO usage and CPU performance overhead.
It is recommended to allocate virtual memory twice the size of your physical memory.
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
Environment Setup ​
  • Detect the system environment and install the corresponding components
  • Install docker and docker-compose.
  • Download some configuration scripts required by default
  • Detect if there is an IPV6 address, check if it is greater than or equal to /112, and if so, configure the docker's ipv6 network.
  • If all the above conditions are met, create ndpresponder docker and radvd so that IPV6 allocation supports ndp broadcasting and auto-allocation.
  • Support for x86_64 and ARM architecture servers
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
OR
bash dockerinstall.sh
TIP
The environment installation process may require you to reboot the server and then execute the script again, see the instructions after the script is run for more details
',16),l=[t];function p(r,c,i,d,h,u){return a(),e("div",null,l)}const y=s(n,[["render",p]]);export{C as __pageData,y as default};
+import{_ as s,v as a,b as e,R as o}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_install.md","filePath":"en/guide/docker/docker_install.md","lastUpdated":1747730955000}'),n={name:"en/guide/docker/docker_install.md"},t=o('
Preface ​
Support for running Docker virtualization on various systems, including Linux, Android, and Windows.
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the LXD module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
Setting Up Virtual Memory ​
TIP
Allocate some swap space to prevent your machine from crashing.
Unit conversion: Inputting 1024 results in 1G of SWAP - virtual memory. Virtual memory occupies disk space and is automatically utilized when the physical memory is insufficient. However, this leads to high IO usage and CPU performance overhead.
It is recommended to allocate virtual memory twice the size of your physical memory.
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
Environment Setup ​
  • Detect the system environment and install the corresponding components
  • Install docker and docker-compose.
  • Download some configuration scripts required by default
  • Detect if there is an IPV6 address, check if it is greater than or equal to /112, and if so, configure the docker's ipv6 network.
  • If all the above conditions are met, create ndpresponder docker and radvd so that IPV6 allocation supports ndp broadcasting and auto-allocation.
  • Support for x86_64 and ARM architecture servers
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
OR
bash dockerinstall.sh
TIP
The environment installation process may require you to reboot the server and then execute the script again, see the instructions after the script is run for more details
',16),l=[t];function p(r,c,i,d,h,u){return a(),e("div",null,l)}const y=s(n,[["render",p]]);export{C as __pageData,y as default};
diff --git a/assets/en_guide_docker_docker_install.md.ecacf3a2.lean.js b/assets/en_guide_docker_docker_install.md.6de25cff.lean.js
similarity index 98%
rename from assets/en_guide_docker_docker_install.md.ecacf3a2.lean.js
rename to assets/en_guide_docker_docker_install.md.6de25cff.lean.js
index e88870ec6d..89729da132 100644
--- a/assets/en_guide_docker_docker_install.md.ecacf3a2.lean.js
+++ b/assets/en_guide_docker_docker_install.md.6de25cff.lean.js
@@ -1 +1 @@
-import{_ as s,v as a,b as e,R as o}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_install.md","filePath":"en/guide/docker/docker_install.md","lastUpdated":1747726389000}'),n={name:"en/guide/docker/docker_install.md"},t=o('
Preface ​
Support for running Docker virtualization on various systems, including Linux, Android, and Windows.
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the LXD module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
Setting Up Virtual Memory ​
TIP
Allocate some swap space to prevent your machine from crashing.
Unit conversion: Inputting 1024 results in 1G of SWAP - virtual memory. Virtual memory occupies disk space and is automatically utilized when the physical memory is insufficient. However, this leads to high IO usage and CPU performance overhead.
It is recommended to allocate virtual memory twice the size of your physical memory.
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
Environment Setup ​
  • Detect the system environment and install the corresponding components
  • Install docker and docker-compose.
  • Download some configuration scripts required by default
  • Detect if there is an IPV6 address, check if it is greater than or equal to /112, and if so, configure the docker's ipv6 network.
  • If all the above conditions are met, create ndpresponder docker and radvd so that IPV6 allocation supports ndp broadcasting and auto-allocation.
  • Support for x86_64 and ARM architecture servers
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
OR
bash dockerinstall.sh
TIP
The environment installation process may require you to reboot the server and then execute the script again, see the instructions after the script is run for more details
',16),l=[t];function p(r,c,i,d,h,u){return a(),e("div",null,l)}const y=s(n,[["render",p]]);export{C as __pageData,y as default};
+import{_ as s,v as a,b as e,R as o}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_install.md","filePath":"en/guide/docker/docker_install.md","lastUpdated":1747730955000}'),n={name:"en/guide/docker/docker_install.md"},t=o('
Preface ​
Support for running Docker virtualization on various systems, including Linux, Android, and Windows.
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the LXD module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
Setting Up Virtual Memory ​
TIP
Allocate some swap space to prevent your machine from crashing.
Unit conversion: Inputting 1024 results in 1G of SWAP - virtual memory. Virtual memory occupies disk space and is automatically utilized when the physical memory is insufficient. However, this leads to high IO usage and CPU performance overhead.
It is recommended to allocate virtual memory twice the size of your physical memory.
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
Environment Setup ​
  • Detect the system environment and install the corresponding components
  • Install docker and docker-compose.
  • Download some configuration scripts required by default
  • Detect if there is an IPV6 address, check if it is greater than or equal to /112, and if so, configure the docker's ipv6 network.
  • If all the above conditions are met, create ndpresponder docker and radvd so that IPV6 allocation supports ndp broadcasting and auto-allocation.
  • Support for x86_64 and ARM architecture servers
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
OR
bash dockerinstall.sh
TIP
The environment installation process may require you to reboot the server and then execute the script again, see the instructions after the script is run for more details
',16),l=[t];function p(r,c,i,d,h,u){return a(),e("div",null,l)}const y=s(n,[["render",p]]);export{C as __pageData,y as default};
diff --git a/assets/en_guide_docker_docker_macos.md.fd3f0bcb.js b/assets/en_guide_docker_docker_macos.md.19741399.js
similarity index 95%
rename from assets/en_guide_docker_docker_macos.md.fd3f0bcb.js
rename to assets/en_guide_docker_docker_macos.md.19741399.js
index 82349b5923..fb43171e98 100644
--- a/assets/en_guide_docker_docker_macos.md.fd3f0bcb.js
+++ b/assets/en_guide_docker_docker_macos.md.19741399.js
@@ -1 +1 @@
-import{_ as e,v as a,b as r,R as o}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"Running macOS Virtual Machines in Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_macos.md","filePath":"en/guide/docker/docker_macos.md","lastUpdated":1747726389000}'),c={name:"en/guide/docker/docker_macos.md"},n=o('
Running macOS Virtual Machines in Docker ​
Using Dockur ​
Original Project:
https://github.com/dockur/macos
Using Docker-OSX ​
Original Project:
https://github.com/sickcodes/Docker-OSX
',7),i=[n];function t(s,d,u,h,k,l){return a(),r("div",null,i)}const p=e(c,[["render",t]]);export{g as __pageData,p as default};
+import{_ as e,v as a,b as r,R as o}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"Running macOS Virtual Machines in Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_macos.md","filePath":"en/guide/docker/docker_macos.md","lastUpdated":1747730955000}'),c={name:"en/guide/docker/docker_macos.md"},n=o('
Running macOS Virtual Machines in Docker ​
Using Dockur ​
Original Project:
https://github.com/dockur/macos
Using Docker-OSX ​
Original Project:
https://github.com/sickcodes/Docker-OSX
',7),i=[n];function t(s,d,u,h,k,l){return a(),r("div",null,i)}const p=e(c,[["render",t]]);export{g as __pageData,p as default};
diff --git a/assets/en_guide_docker_docker_macos.md.fd3f0bcb.lean.js b/assets/en_guide_docker_docker_macos.md.19741399.lean.js
similarity index 95%
rename from assets/en_guide_docker_docker_macos.md.fd3f0bcb.lean.js
rename to assets/en_guide_docker_docker_macos.md.19741399.lean.js
index 82349b5923..fb43171e98 100644
--- a/assets/en_guide_docker_docker_macos.md.fd3f0bcb.lean.js
+++ b/assets/en_guide_docker_docker_macos.md.19741399.lean.js
@@ -1 +1 @@
-import{_ as e,v as a,b as r,R as o}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"Running macOS Virtual Machines in Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_macos.md","filePath":"en/guide/docker/docker_macos.md","lastUpdated":1747726389000}'),c={name:"en/guide/docker/docker_macos.md"},n=o('
Running macOS Virtual Machines in Docker ​
Using Dockur ​
Original Project:
https://github.com/dockur/macos
Using Docker-OSX ​
Original Project:
https://github.com/sickcodes/Docker-OSX
',7),i=[n];function t(s,d,u,h,k,l){return a(),r("div",null,i)}const p=e(c,[["render",t]]);export{g as __pageData,p as default};
+import{_ as e,v as a,b as r,R as o}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"Running macOS Virtual Machines in Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_macos.md","filePath":"en/guide/docker/docker_macos.md","lastUpdated":1747730955000}'),c={name:"en/guide/docker/docker_macos.md"},n=o('
Running macOS Virtual Machines in Docker ​
Using Dockur ​
Original Project:
https://github.com/dockur/macos
Using Docker-OSX ​
Original Project:
https://github.com/sickcodes/Docker-OSX
',7),i=[n];function t(s,d,u,h,k,l){return a(),r("div",null,i)}const p=e(c,[["render",t]]);export{g as __pageData,p as default};
diff --git a/assets/en_guide_docker_docker_precheck.md.91792c33.js b/assets/en_guide_docker_docker_precheck.md.08aa05c6.js
similarity index 98%
rename from assets/en_guide_docker_docker_precheck.md.91792c33.js
rename to assets/en_guide_docker_docker_precheck.md.08aa05c6.js
index 7f2e2a3d22..03ece9ff04 100644
--- a/assets/en_guide_docker_docker_precheck.md.91792c33.js
+++ b/assets/en_guide_docker_docker_precheck.md.08aa05c6.js
@@ -1 +1 @@
-import{_ as e,v as t,b as o,R as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Introduction","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/docker/docker_precheck.md","filePath":"en/guide/docker/docker_precheck.md","lastUpdated":1747726389000}'),n={name:"en/guide/docker/docker_precheck.md"},s=a('
Introduction ​
The following is an introduction to the non-customized sections. Please ensure that you don't confuse them with the customized parts.
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the incus module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
WARNING
If the host has an IPV6 network, the installation will change the network structure of the host, please make sure that the host can reset the system at any time and that there is no important data on the host before running.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/docker
Project Features ​
Bulk or individual NAT server provisioning via docker
Default use of debian system optional alpine system, each container comes with 1 external ssh port, 25 internal and external network ports, you can choose whether to bind IPV6 address
The default creation of unprivileged containers, and does not mount and host docker daemon communication, so ** host created docker virtualization NAT servers can not be nested within the virtualization docker **
By default, lxcfs is installed and enabled, so that when querying resources within a container, CPU and memory use the configured view instead of the host's view.
Since most cloud servers have ext4 filesystems, even xfs filesystems do not enable the pquota option, so sharing the host's hard disk by default does not limit the disk size of each container.
Configuration requirements ​
The system can be installed docker can be used, the network can connect to the Github raw interface can be used, hardware configuration as long as not pull across the line, free hard disk has 3G on it!
(If you need to bind an IPV6 address, then please make sure to use the installation script of this set of scripts for docker installation, you need it to automatically preset some of the settings)
If the hardware resources are just a little bit better, need to limit more things and need to limit the size of the hard disk, you can use the incus partition of the script batch open LXC virtualization containers
If the hardware is very good and you have a lot of resources, you can use the PVE partition script to batch open KVM virtualized VMs.
',16),r=[s];function i(c,d,h,u,l,p){return t(),o("div",null,r)}const k=e(n,[["render",i]]);export{m as __pageData,k as default};
+import{_ as e,v as t,b as o,R as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Introduction","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/docker/docker_precheck.md","filePath":"en/guide/docker/docker_precheck.md","lastUpdated":1747730955000}'),n={name:"en/guide/docker/docker_precheck.md"},s=a('
Introduction ​
The following is an introduction to the non-customized sections. Please ensure that you don't confuse them with the customized parts.
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the incus module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
WARNING
If the host has an IPV6 network, the installation will change the network structure of the host, please make sure that the host can reset the system at any time and that there is no important data on the host before running.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/docker
Project Features ​
Bulk or individual NAT server provisioning via docker
Default use of debian system optional alpine system, each container comes with 1 external ssh port, 25 internal and external network ports, you can choose whether to bind IPV6 address
The default creation of unprivileged containers, and does not mount and host docker daemon communication, so ** host created docker virtualization NAT servers can not be nested within the virtualization docker **
By default, lxcfs is installed and enabled, so that when querying resources within a container, CPU and memory use the configured view instead of the host's view.
Since most cloud servers have ext4 filesystems, even xfs filesystems do not enable the pquota option, so sharing the host's hard disk by default does not limit the disk size of each container.
Configuration requirements ​
The system can be installed docker can be used, the network can connect to the Github raw interface can be used, hardware configuration as long as not pull across the line, free hard disk has 3G on it!
(If you need to bind an IPV6 address, then please make sure to use the installation script of this set of scripts for docker installation, you need it to automatically preset some of the settings)
If the hardware resources are just a little bit better, need to limit more things and need to limit the size of the hard disk, you can use the incus partition of the script batch open LXC virtualization containers
If the hardware is very good and you have a lot of resources, you can use the PVE partition script to batch open KVM virtualized VMs.
',16),r=[s];function i(c,d,h,u,l,p){return t(),o("div",null,r)}const k=e(n,[["render",i]]);export{m as __pageData,k as default};
diff --git a/assets/en_guide_docker_docker_precheck.md.91792c33.lean.js b/assets/en_guide_docker_docker_precheck.md.08aa05c6.lean.js
similarity index 98%
rename from assets/en_guide_docker_docker_precheck.md.91792c33.lean.js
rename to assets/en_guide_docker_docker_precheck.md.08aa05c6.lean.js
index 7f2e2a3d22..03ece9ff04 100644
--- a/assets/en_guide_docker_docker_precheck.md.91792c33.lean.js
+++ b/assets/en_guide_docker_docker_precheck.md.08aa05c6.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as o,R as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Introduction","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/docker/docker_precheck.md","filePath":"en/guide/docker/docker_precheck.md","lastUpdated":1747726389000}'),n={name:"en/guide/docker/docker_precheck.md"},s=a('
Introduction ​
The following is an introduction to the non-customized sections. Please ensure that you don't confuse them with the customized parts.
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the incus module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
WARNING
If the host has an IPV6 network, the installation will change the network structure of the host, please make sure that the host can reset the system at any time and that there is no important data on the host before running.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/docker
Project Features ​
Bulk or individual NAT server provisioning via docker
Default use of debian system optional alpine system, each container comes with 1 external ssh port, 25 internal and external network ports, you can choose whether to bind IPV6 address
The default creation of unprivileged containers, and does not mount and host docker daemon communication, so ** host created docker virtualization NAT servers can not be nested within the virtualization docker **
By default, lxcfs is installed and enabled, so that when querying resources within a container, CPU and memory use the configured view instead of the host's view.
Since most cloud servers have ext4 filesystems, even xfs filesystems do not enable the pquota option, so sharing the host's hard disk by default does not limit the disk size of each container.
Configuration requirements ​
The system can be installed docker can be used, the network can connect to the Github raw interface can be used, hardware configuration as long as not pull across the line, free hard disk has 3G on it!
(If you need to bind an IPV6 address, then please make sure to use the installation script of this set of scripts for docker installation, you need it to automatically preset some of the settings)
If the hardware resources are just a little bit better, need to limit more things and need to limit the size of the hard disk, you can use the incus partition of the script batch open LXC virtualization containers
If the hardware is very good and you have a lot of resources, you can use the PVE partition script to batch open KVM virtualized VMs.
',16),r=[s];function i(c,d,h,u,l,p){return t(),o("div",null,r)}const k=e(n,[["render",i]]);export{m as __pageData,k as default};
+import{_ as e,v as t,b as o,R as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Introduction","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/docker/docker_precheck.md","filePath":"en/guide/docker/docker_precheck.md","lastUpdated":1747730955000}'),n={name:"en/guide/docker/docker_precheck.md"},s=a('
Introduction ​
The following is an introduction to the non-customized sections. Please ensure that you don't confuse them with the customized parts.
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the incus module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
WARNING
If the host has an IPV6 network, the installation will change the network structure of the host, please make sure that the host can reset the system at any time and that there is no important data on the host before running.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/docker
Project Features ​
Bulk or individual NAT server provisioning via docker
Default use of debian system optional alpine system, each container comes with 1 external ssh port, 25 internal and external network ports, you can choose whether to bind IPV6 address
The default creation of unprivileged containers, and does not mount and host docker daemon communication, so ** host created docker virtualization NAT servers can not be nested within the virtualization docker **
By default, lxcfs is installed and enabled, so that when querying resources within a container, CPU and memory use the configured view instead of the host's view.
Since most cloud servers have ext4 filesystems, even xfs filesystems do not enable the pquota option, so sharing the host's hard disk by default does not limit the disk size of each container.
Configuration requirements ​
The system can be installed docker can be used, the network can connect to the Github raw interface can be used, hardware configuration as long as not pull across the line, free hard disk has 3G on it!
(If you need to bind an IPV6 address, then please make sure to use the installation script of this set of scripts for docker installation, you need it to automatically preset some of the settings)
If the hardware resources are just a little bit better, need to limit more things and need to limit the size of the hard disk, you can use the incus partition of the script batch open LXC virtualization containers
If the hardware is very good and you have a lot of resources, you can use the PVE partition script to batch open KVM virtualized VMs.
',16),r=[s];function i(c,d,h,u,l,p){return t(),o("div",null,r)}const k=e(n,[["render",i]]);export{m as __pageData,k as default};
diff --git a/assets/en_guide_docker_docker_qa.md.ac754529.js b/assets/en_guide_docker_docker_qa.md.54c54320.js
similarity index 98%
rename from assets/en_guide_docker_docker_qa.md.ac754529.js
rename to assets/en_guide_docker_docker_qa.md.54c54320.js
index baa3d0e313..f08b34f5a2 100644
--- a/assets/en_guide_docker_docker_qa.md.ac754529.js
+++ b/assets/en_guide_docker_docker_qa.md.54c54320.js
@@ -1 +1 @@
-import{_ as e,v as a,b as s,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"Solve the puzzle","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_qa.md","filePath":"en/guide/docker/docker_qa.md","lastUpdated":1747726389000}'),o={name:"en/guide/docker/docker_qa.md"},l=n('
Solve the puzzle ​
Common Docker Commands ​
Check real-time resource usage of a specific container
docker stats <container_name>
Enter a specific container
docker exec -it <container_name> /bin/bash
Clean Docker cache, remove unused resources including images, containers, networks, etc.
docker system prune -a
Uninstall all Docker images and containers
docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)
View logs of a specific container
docker logs <container_name_or_ID>
View overall disk usage of Docker
docker system df
List all containers
docker ps -a
List all images
docker images
Remove a specific container
docker rm -f <container_name_or_ID>
Remove a specific image
docker rmi <image_name_or_ID>
',22),t=[l];function c(p,i,r,d,m,g){return a(),s("div",null,t)}const C=e(o,[["render",c]]);export{h as __pageData,C as default};
+import{_ as e,v as a,b as s,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"Solve the puzzle","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_qa.md","filePath":"en/guide/docker/docker_qa.md","lastUpdated":1747730955000}'),o={name:"en/guide/docker/docker_qa.md"},l=n('
Solve the puzzle ​
Common Docker Commands ​
Check real-time resource usage of a specific container
docker stats <container_name>
Enter a specific container
docker exec -it <container_name> /bin/bash
Clean Docker cache, remove unused resources including images, containers, networks, etc.
docker system prune -a
Uninstall all Docker images and containers
docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)
View logs of a specific container
docker logs <container_name_or_ID>
View overall disk usage of Docker
docker system df
List all containers
docker ps -a
List all images
docker images
Remove a specific container
docker rm -f <container_name_or_ID>
Remove a specific image
docker rmi <image_name_or_ID>
',22),t=[l];function c(p,i,r,d,m,g){return a(),s("div",null,t)}const C=e(o,[["render",c]]);export{h as __pageData,C as default};
diff --git a/assets/en_guide_docker_docker_qa.md.ac754529.lean.js b/assets/en_guide_docker_docker_qa.md.54c54320.lean.js
similarity index 98%
rename from assets/en_guide_docker_docker_qa.md.ac754529.lean.js
rename to assets/en_guide_docker_docker_qa.md.54c54320.lean.js
index baa3d0e313..f08b34f5a2 100644
--- a/assets/en_guide_docker_docker_qa.md.ac754529.lean.js
+++ b/assets/en_guide_docker_docker_qa.md.54c54320.lean.js
@@ -1 +1 @@
-import{_ as e,v as a,b as s,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"Solve the puzzle","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_qa.md","filePath":"en/guide/docker/docker_qa.md","lastUpdated":1747726389000}'),o={name:"en/guide/docker/docker_qa.md"},l=n('
Solve the puzzle ​
Common Docker Commands ​
Check real-time resource usage of a specific container
docker stats <container_name>
Enter a specific container
docker exec -it <container_name> /bin/bash
Clean Docker cache, remove unused resources including images, containers, networks, etc.
docker system prune -a
Uninstall all Docker images and containers
docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)
View logs of a specific container
docker logs <container_name_or_ID>
View overall disk usage of Docker
docker system df
List all containers
docker ps -a
List all images
docker images
Remove a specific container
docker rm -f <container_name_or_ID>
Remove a specific image
docker rmi <image_name_or_ID>
',22),t=[l];function c(p,i,r,d,m,g){return a(),s("div",null,t)}const C=e(o,[["render",c]]);export{h as __pageData,C as default};
+import{_ as e,v as a,b as s,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"Solve the puzzle","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_qa.md","filePath":"en/guide/docker/docker_qa.md","lastUpdated":1747730955000}'),o={name:"en/guide/docker/docker_qa.md"},l=n('
Solve the puzzle ​
Common Docker Commands ​
Check real-time resource usage of a specific container
docker stats <container_name>
Enter a specific container
docker exec -it <container_name> /bin/bash
Clean Docker cache, remove unused resources including images, containers, networks, etc.
docker system prune -a
Uninstall all Docker images and containers
docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)
View logs of a specific container
docker logs <container_name_or_ID>
View overall disk usage of Docker
docker system df
List all containers
docker ps -a
List all images
docker images
Remove a specific container
docker rm -f <container_name_or_ID>
Remove a specific image
docker rmi <image_name_or_ID>
',22),t=[l];function c(p,i,r,d,m,g){return a(),s("div",null,t)}const C=e(o,[["render",c]]);export{h as __pageData,C as default};
diff --git a/assets/en_guide_docker_docker_thanks.md.6a38453c.js b/assets/en_guide_docker_docker_thanks.md.e2ee842f.js
similarity index 98%
rename from assets/en_guide_docker_docker_thanks.md.6a38453c.js
rename to assets/en_guide_docker_docker_thanks.md.e2ee842f.js
index 036ec83f78..af56e91f52 100644
--- a/assets/en_guide_docker_docker_thanks.md.6a38453c.js
+++ b/assets/en_guide_docker_docker_thanks.md.e2ee842f.js
@@ -1 +1 @@
-import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/docker/docker_thanks.md","filePath":"en/guide/docker/docker_thanks.md","lastUpdated":1747726389000}'),o={name:"en/guide/docker/docker_thanks.md"},n=a('
Acknowledgements ​
https://hub.docker.com/_/debian
https://hub.docker.com/r/redroid/redroid
https://github.com/NetrisTV/ws-scrcpy
https://guacamole.apache.org/doc/gug/introduction.html
https://blog.imoeq.com/oracle-arm-run-android-by-docker
https://blog.imoeq.com/scrcpy-run-a-android-web-page
https://github.com/NetrisTV/ws-scrcpy
https://www.howtoforge.com/how-to-install-apache-guacamole-as-docker-container-on-ubuntu/
https://releases.hashicorp.com/vagrant/
https://github.com/hashicorp/vagrant/
https://app.vagrantup.com/peru
https://medium.com/axon-technologies/installing-a-windows-virtual-machine-in-a-linux-docker-container-c78e4c3f9ba1
https://forum.garudalinux.org/t/error-while-attempting-to-create-a-virtual-machine-with-virt-manager/18534/4
https://github.com/jlesage/docker-firefox
https://github.com/linuxserver/docker-webtop
https://github.com/yoursunny/ndpresponder
https://github.com/linuxserver/docker-chromium
https://github.com/SuperManito/LinuxMirrors
Thank @Ella-Alinda and @CoiaPrant for providing docker guidance.
',20),c=[n];function h(p,i,s,l,d,g){return e(),t("div",null,c)}const b=r(o,[["render",h]]);export{m as __pageData,b as default};
+import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/docker/docker_thanks.md","filePath":"en/guide/docker/docker_thanks.md","lastUpdated":1747730955000}'),o={name:"en/guide/docker/docker_thanks.md"},n=a('
Acknowledgements ​
https://hub.docker.com/_/debian
https://hub.docker.com/r/redroid/redroid
https://github.com/NetrisTV/ws-scrcpy
https://guacamole.apache.org/doc/gug/introduction.html
https://blog.imoeq.com/oracle-arm-run-android-by-docker
https://blog.imoeq.com/scrcpy-run-a-android-web-page
https://github.com/NetrisTV/ws-scrcpy
https://www.howtoforge.com/how-to-install-apache-guacamole-as-docker-container-on-ubuntu/
https://releases.hashicorp.com/vagrant/
https://github.com/hashicorp/vagrant/
https://app.vagrantup.com/peru
https://medium.com/axon-technologies/installing-a-windows-virtual-machine-in-a-linux-docker-container-c78e4c3f9ba1
https://forum.garudalinux.org/t/error-while-attempting-to-create-a-virtual-machine-with-virt-manager/18534/4
https://github.com/jlesage/docker-firefox
https://github.com/linuxserver/docker-webtop
https://github.com/yoursunny/ndpresponder
https://github.com/linuxserver/docker-chromium
https://github.com/SuperManito/LinuxMirrors
Thank @Ella-Alinda and @CoiaPrant for providing docker guidance.
',20),c=[n];function h(p,i,s,l,d,g){return e(),t("div",null,c)}const b=r(o,[["render",h]]);export{m as __pageData,b as default};
diff --git a/assets/en_guide_docker_docker_thanks.md.6a38453c.lean.js b/assets/en_guide_docker_docker_thanks.md.e2ee842f.lean.js
similarity index 98%
rename from assets/en_guide_docker_docker_thanks.md.6a38453c.lean.js
rename to assets/en_guide_docker_docker_thanks.md.e2ee842f.lean.js
index 036ec83f78..af56e91f52 100644
--- a/assets/en_guide_docker_docker_thanks.md.6a38453c.lean.js
+++ b/assets/en_guide_docker_docker_thanks.md.e2ee842f.lean.js
@@ -1 +1 @@
-import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/docker/docker_thanks.md","filePath":"en/guide/docker/docker_thanks.md","lastUpdated":1747726389000}'),o={name:"en/guide/docker/docker_thanks.md"},n=a('
Acknowledgements ​
https://hub.docker.com/_/debian
https://hub.docker.com/r/redroid/redroid
https://github.com/NetrisTV/ws-scrcpy
https://guacamole.apache.org/doc/gug/introduction.html
https://blog.imoeq.com/oracle-arm-run-android-by-docker
https://blog.imoeq.com/scrcpy-run-a-android-web-page
https://github.com/NetrisTV/ws-scrcpy
https://www.howtoforge.com/how-to-install-apache-guacamole-as-docker-container-on-ubuntu/
https://releases.hashicorp.com/vagrant/
https://github.com/hashicorp/vagrant/
https://app.vagrantup.com/peru
https://medium.com/axon-technologies/installing-a-windows-virtual-machine-in-a-linux-docker-container-c78e4c3f9ba1
https://forum.garudalinux.org/t/error-while-attempting-to-create-a-virtual-machine-with-virt-manager/18534/4
https://github.com/jlesage/docker-firefox
https://github.com/linuxserver/docker-webtop
https://github.com/yoursunny/ndpresponder
https://github.com/linuxserver/docker-chromium
https://github.com/SuperManito/LinuxMirrors
Thank @Ella-Alinda and @CoiaPrant for providing docker guidance.
',20),c=[n];function h(p,i,s,l,d,g){return e(),t("div",null,c)}const b=r(o,[["render",h]]);export{m as __pageData,b as default};
+import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/docker/docker_thanks.md","filePath":"en/guide/docker/docker_thanks.md","lastUpdated":1747730955000}'),o={name:"en/guide/docker/docker_thanks.md"},n=a('
Acknowledgements ​
https://hub.docker.com/_/debian
https://hub.docker.com/r/redroid/redroid
https://github.com/NetrisTV/ws-scrcpy
https://guacamole.apache.org/doc/gug/introduction.html
https://blog.imoeq.com/oracle-arm-run-android-by-docker
https://blog.imoeq.com/scrcpy-run-a-android-web-page
https://github.com/NetrisTV/ws-scrcpy
https://www.howtoforge.com/how-to-install-apache-guacamole-as-docker-container-on-ubuntu/
https://releases.hashicorp.com/vagrant/
https://github.com/hashicorp/vagrant/
https://app.vagrantup.com/peru
https://medium.com/axon-technologies/installing-a-windows-virtual-machine-in-a-linux-docker-container-c78e4c3f9ba1
https://forum.garudalinux.org/t/error-while-attempting-to-create-a-virtual-machine-with-virt-manager/18534/4
https://github.com/jlesage/docker-firefox
https://github.com/linuxserver/docker-webtop
https://github.com/yoursunny/ndpresponder
https://github.com/linuxserver/docker-chromium
https://github.com/SuperManito/LinuxMirrors
Thank @Ella-Alinda and @CoiaPrant for providing docker guidance.
',20),c=[n];function h(p,i,s,l,d,g){return e(),t("div",null,c)}const b=r(o,[["render",h]]);export{m as __pageData,b as default};
diff --git a/assets/en_guide_docker_docker_windows.md.a1539013.js b/assets/en_guide_docker_docker_windows.md.82ebd842.js
similarity index 99%
rename from assets/en_guide_docker_docker_windows.md.a1539013.js
rename to assets/en_guide_docker_docker_windows.md.82ebd842.js
index 449e37cf02..b9944edfc1 100644
--- a/assets/en_guide_docker_docker_windows.md.a1539013.js
+++ b/assets/en_guide_docker_docker_windows.md.82ebd842.js
@@ -1,4 +1,4 @@
-import{_ as s,v as e,b as a,R as n}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Running Windows Virtual Machine in Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_windows.md","filePath":"en/guide/docker/docker_windows.md","lastUpdated":1747726389000}'),o={name:"en/guide/docker/docker_windows.md"},t=n(`
Running Windows Virtual Machine in Docker ​
One-Click Deployment (Using Vagrant) ​
  • Shares all resources of the host machine; based on Docker, so it only occupies the size of the system, suitable for multiple instances.
  • Shares IP; Docker's NAT mapping is employed. You can choose whether to map to the external network or just the internal network.
  • The configured Windows system is set to use a maximum of 1 core, 2GB RAM, and 50GB hard disk by default. Actual usage may vary based on usage patterns.
  • No need for iptables for NAT mapping; port mappings are automatically deleted when containers are removed, making maintenance easier.
  • Ensure that the host machine supports nested virtualization, and currently, only X86_64 architecture systems are supported. I haven't compiled corresponding images for ARM devices at the moment.
The host machine needs to support nested virtualization and currently only supports systems based on the X86_64 architecture; I don't have an ARM machine on hand to compile the corresponding image at the moment.
Command:
shell
egrep -c '(vmx|svm)' /proc/cpuinfo
The result should be greater than or equal to 1 and cannot be 0.
Next, you need to configure Docker to start using the v1 version of cgroup.
shell
sed -i 's/GRUB_CMDLINE_LINUX="\\(.*\\)"/GRUB_CMDLINE_LINUX="\\1 systemd.unified_cgroup_hierarchy=0"/' /etc/default/grub
+import{_ as s,v as e,b as a,R as n}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Running Windows Virtual Machine in Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_windows.md","filePath":"en/guide/docker/docker_windows.md","lastUpdated":1747730955000}'),o={name:"en/guide/docker/docker_windows.md"},t=n(`
Running Windows Virtual Machine in Docker ​
One-Click Deployment (Using Vagrant) ​
  • Shares all resources of the host machine; based on Docker, so it only occupies the size of the system, suitable for multiple instances.
  • Shares IP; Docker's NAT mapping is employed. You can choose whether to map to the external network or just the internal network.
  • The configured Windows system is set to use a maximum of 1 core, 2GB RAM, and 50GB hard disk by default. Actual usage may vary based on usage patterns.
  • No need for iptables for NAT mapping; port mappings are automatically deleted when containers are removed, making maintenance easier.
  • Ensure that the host machine supports nested virtualization, and currently, only X86_64 architecture systems are supported. I haven't compiled corresponding images for ARM devices at the moment.
The host machine needs to support nested virtualization and currently only supports systems based on the X86_64 architecture; I don't have an ARM machine on hand to compile the corresponding image at the moment.
Command:
shell
egrep -c '(vmx|svm)' /proc/cpuinfo
The result should be greater than or equal to 1 and cannot be 0.
Next, you need to configure Docker to start using the v1 version of cgroup.
shell
sed -i 's/GRUB_CMDLINE_LINUX="\\(.*\\)"/GRUB_CMDLINE_LINUX="\\1 systemd.unified_cgroup_hierarchy=0"/' /etc/default/grub
 update-grub
 ls
If there are no errors during execution, run the reboot command to restart the system and apply the settings.
Supported Images
We are using custom-built images: https://hub.docker.com/r/spiritlhl/wds
Image NameImage Size
1020GB
202217.5GB
201917GB
The size of the created container will be slightly larger than the image size, but not by much.
Download Script
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onewindows.sh -o onewindows.sh && chmod +x onewindows.sh
Usage Instructions
Make sure to execute the following commands in a 'screen' session before proceeding, to avoid potential disconnection or freezing of the SSH connection.
./onewindows.sh <container_name> <system_version> <RDP_port> <external_mapping>
  • Replace <container_name> with the name.
  • Replace <system_version> with the desired Windows system version.
  • Replace <RDP_port> with the port number for RDP access.
  • If you want to enable external mapping, replace <external_mapping> with 'Y'. If not, leave it blank or use 'N'.
Before initiating the setup, ensure that the host machine has a disk size at least twice the size of the image, plus an additional 10GB, as Docker needs to pull the image locally before creating the container.
During the creation process, the peak disk usage will be host_system_size + image_size + container_size.
For example, to set up a container with the name test, the container with the lowest occupancy Windows 2019 system, map the extranet RDP port 13389 and set it to extranet mapping (mapping to your server's extranet IPV4 address)
shell
./onewindows.sh test 2019 13389 Y
After it, the default usernames are Administrator and vagrant, with the default password being vagrant.
If you choose to open a mapped extranet port, be sure to log in and change the password of the corresponding account (both accounts may have, try it yourself), otherwise it may be abused by someone blasting
Deletion
To delete the corresponding image and container, first use the command docker ps -a and docker images to find the ID of the image named spiritlhl/wds. Then, use the following commands accordingly:
docker rm -f container_ID
 docker rmi image_ID
After deletion, you can create containers of different versions of Windows.
Other similar projects
https://github.com/dockur/windows - Similar project that support more systems, but have more resource requirements
https://github.com/dockur/windows-arm/ - It's great that he has ARM servers for mirror compilation, my project doesn't have
Note that both of the above projects require a host with at least 4 cores of CPU, at least 4G of RAM, and at least 64G of hard disk, which is greater than the mirroring requirements of my project. (The advantage of his project is that you can customize many configuration items, see his corresponding project description for details.)
Manual Provisioning (via the Dockur Project) ​
This project supports VM creation using QEMU even on host systems that do not support nested virtualization.
Original Project Repositories ​
⚠️ Notes:
  • The original project provides only the launcher, not a Windows image.
  • The first container startup may take up to 4 hours on domestic (China) networks, due to image download and installation.
  • The host system should meet the following minimum hardware requirements (can be adjusted via script modifications):
    • CPU: At least 4 cores
    • RAM: At least 4 GB
    • Disk: At least 64 GB
For customization such as reducing resource usage or changing launch parameters, refer to:
For x86_64 Architecture Users ​
A pre-modified single-file launcher is available to simplify building a Windows image. This version writes system files and images directly into Docker’s writable layer—no external image mounting required.
Download link: https://github.com/oneclickvirt/docker/releases/download/amd64_builder/builder.tar
Import Docker image:
bash
docker load -i builder.tar
Launching the Container with a Custom Windows ISO ​
Download a Windows ISO image from: https://down.idc.wiki/ISOS/Windows/
Sample command to start the container:
bash
docker run -it -d \\
diff --git a/assets/en_guide_docker_docker_windows.md.a1539013.lean.js b/assets/en_guide_docker_docker_windows.md.82ebd842.lean.js
similarity index 99%
rename from assets/en_guide_docker_docker_windows.md.a1539013.lean.js
rename to assets/en_guide_docker_docker_windows.md.82ebd842.lean.js
index 449e37cf02..b9944edfc1 100644
--- a/assets/en_guide_docker_docker_windows.md.a1539013.lean.js
+++ b/assets/en_guide_docker_docker_windows.md.82ebd842.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as e,b as a,R as n}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Running Windows Virtual Machine in Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_windows.md","filePath":"en/guide/docker/docker_windows.md","lastUpdated":1747726389000}'),o={name:"en/guide/docker/docker_windows.md"},t=n(`
Running Windows Virtual Machine in Docker ​
One-Click Deployment (Using Vagrant) ​
  • Shares all resources of the host machine; based on Docker, so it only occupies the size of the system, suitable for multiple instances.
  • Shares IP; Docker's NAT mapping is employed. You can choose whether to map to the external network or just the internal network.
  • The configured Windows system is set to use a maximum of 1 core, 2GB RAM, and 50GB hard disk by default. Actual usage may vary based on usage patterns.
  • No need for iptables for NAT mapping; port mappings are automatically deleted when containers are removed, making maintenance easier.
  • Ensure that the host machine supports nested virtualization, and currently, only X86_64 architecture systems are supported. I haven't compiled corresponding images for ARM devices at the moment.
The host machine needs to support nested virtualization and currently only supports systems based on the X86_64 architecture; I don't have an ARM machine on hand to compile the corresponding image at the moment.
Command:
shell
egrep -c '(vmx|svm)' /proc/cpuinfo
The result should be greater than or equal to 1 and cannot be 0.
Next, you need to configure Docker to start using the v1 version of cgroup.
shell
sed -i 's/GRUB_CMDLINE_LINUX="\\(.*\\)"/GRUB_CMDLINE_LINUX="\\1 systemd.unified_cgroup_hierarchy=0"/' /etc/default/grub
+import{_ as s,v as e,b as a,R as n}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Running Windows Virtual Machine in Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_windows.md","filePath":"en/guide/docker/docker_windows.md","lastUpdated":1747730955000}'),o={name:"en/guide/docker/docker_windows.md"},t=n(`
Running Windows Virtual Machine in Docker ​
One-Click Deployment (Using Vagrant) ​
  • Shares all resources of the host machine; based on Docker, so it only occupies the size of the system, suitable for multiple instances.
  • Shares IP; Docker's NAT mapping is employed. You can choose whether to map to the external network or just the internal network.
  • The configured Windows system is set to use a maximum of 1 core, 2GB RAM, and 50GB hard disk by default. Actual usage may vary based on usage patterns.
  • No need for iptables for NAT mapping; port mappings are automatically deleted when containers are removed, making maintenance easier.
  • Ensure that the host machine supports nested virtualization, and currently, only X86_64 architecture systems are supported. I haven't compiled corresponding images for ARM devices at the moment.
The host machine needs to support nested virtualization and currently only supports systems based on the X86_64 architecture; I don't have an ARM machine on hand to compile the corresponding image at the moment.
Command:
shell
egrep -c '(vmx|svm)' /proc/cpuinfo
The result should be greater than or equal to 1 and cannot be 0.
Next, you need to configure Docker to start using the v1 version of cgroup.
shell
sed -i 's/GRUB_CMDLINE_LINUX="\\(.*\\)"/GRUB_CMDLINE_LINUX="\\1 systemd.unified_cgroup_hierarchy=0"/' /etc/default/grub
 update-grub
 ls
If there are no errors during execution, run the reboot command to restart the system and apply the settings.
Supported Images
We are using custom-built images: https://hub.docker.com/r/spiritlhl/wds
Image NameImage Size
1020GB
202217.5GB
201917GB
The size of the created container will be slightly larger than the image size, but not by much.
Download Script
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onewindows.sh -o onewindows.sh && chmod +x onewindows.sh
Usage Instructions
Make sure to execute the following commands in a 'screen' session before proceeding, to avoid potential disconnection or freezing of the SSH connection.
./onewindows.sh <container_name> <system_version> <RDP_port> <external_mapping>
  • Replace <container_name> with the name.
  • Replace <system_version> with the desired Windows system version.
  • Replace <RDP_port> with the port number for RDP access.
  • If you want to enable external mapping, replace <external_mapping> with 'Y'. If not, leave it blank or use 'N'.
Before initiating the setup, ensure that the host machine has a disk size at least twice the size of the image, plus an additional 10GB, as Docker needs to pull the image locally before creating the container.
During the creation process, the peak disk usage will be host_system_size + image_size + container_size.
For example, to set up a container with the name test, the container with the lowest occupancy Windows 2019 system, map the extranet RDP port 13389 and set it to extranet mapping (mapping to your server's extranet IPV4 address)
shell
./onewindows.sh test 2019 13389 Y
After it, the default usernames are Administrator and vagrant, with the default password being vagrant.
If you choose to open a mapped extranet port, be sure to log in and change the password of the corresponding account (both accounts may have, try it yourself), otherwise it may be abused by someone blasting
Deletion
To delete the corresponding image and container, first use the command docker ps -a and docker images to find the ID of the image named spiritlhl/wds. Then, use the following commands accordingly:
docker rm -f container_ID
 docker rmi image_ID
After deletion, you can create containers of different versions of Windows.
Other similar projects
https://github.com/dockur/windows - Similar project that support more systems, but have more resource requirements
https://github.com/dockur/windows-arm/ - It's great that he has ARM servers for mirror compilation, my project doesn't have
Note that both of the above projects require a host with at least 4 cores of CPU, at least 4G of RAM, and at least 64G of hard disk, which is greater than the mirroring requirements of my project. (The advantage of his project is that you can customize many configuration items, see his corresponding project description for details.)
Manual Provisioning (via the Dockur Project) ​
This project supports VM creation using QEMU even on host systems that do not support nested virtualization.
Original Project Repositories ​
⚠️ Notes:
  • The original project provides only the launcher, not a Windows image.
  • The first container startup may take up to 4 hours on domestic (China) networks, due to image download and installation.
  • The host system should meet the following minimum hardware requirements (can be adjusted via script modifications):
    • CPU: At least 4 cores
    • RAM: At least 4 GB
    • Disk: At least 64 GB
For customization such as reducing resource usage or changing launch parameters, refer to:
For x86_64 Architecture Users ​
A pre-modified single-file launcher is available to simplify building a Windows image. This version writes system files and images directly into Docker’s writable layer—no external image mounting required.
Download link: https://github.com/oneclickvirt/docker/releases/download/amd64_builder/builder.tar
Import Docker image:
bash
docker load -i builder.tar
Launching the Container with a Custom Windows ISO ​
Download a Windows ISO image from: https://down.idc.wiki/ISOS/Windows/
Sample command to start the container:
bash
docker run -it -d \\
diff --git a/assets/en_guide_incus_incus_custom.md.4c2b9e58.js b/assets/en_guide_incus_incus_custom.md.70184a5b.js
similarity index 99%
rename from assets/en_guide_incus_incus_custom.md.4c2b9e58.js
rename to assets/en_guide_incus_incus_custom.md.70184a5b.js
index 9045362656..4bc11a6c89 100644
--- a/assets/en_guide_incus_incus_custom.md.4c2b9e58.js
+++ b/assets/en_guide_incus_incus_custom.md.70184a5b.js
@@ -1,4 +1,4 @@
-import{_ as e,v as s,b as t,R as a}from"./chunks/framework.70afa331.js";const n="/assets/lxd1.78537e30.png",o="/assets/lxd2.da10b5ec.png",l="/assets/lxd3.917f56de.png",p="/assets/lxd4.83a1a121.png",i="/assets/lxd5.4ebc1444.png",r="/assets/lxd6.572825bf.png",c="/assets/lxd7.b73982c7.png",d="/assets/lxd8.9fcc21e5.png",h="/assets/lxd9.00250a32.png",u="/assets/lxd10.a25a745c.png",y="/assets/lxd11.b83f953c.png",m="/assets/lxd12.0da335dd.png",C="/assets/lxd13.308fe0de.png",g="/assets/lxd14.8dbfdcd6.png",f="/assets/lxd15.70114933.png",b="/assets/lxd16.a595fa36.png",A="/assets/lxd17.d7ea65d8.png",v="/assets/lxd18.d6225daa.png",D="/assets/lxd19.69674669.png",k="/assets/lxd20.179fc6e1.png",w="/assets/lxd21.48123d6a.png",F="/assets/lxd22.4386597e.png",P="/assets/lxd23.c26427e3.png",W=JSON.parse('{"title":"Custom","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_custom.md","filePath":"en/guide/incus/incus_custom.md","lastUpdated":1747726389000}'),_={name:"en/guide/incus/incus_custom.md"},I=a(`
Custom ​
Attach free IPV6 address segments to host machines ​
Some machines don't have an IPV6 /64 subnet on the machine itself, here is a method given to attach an IPV6 subnet for free.
Here is a solution using the 6in4 method for a host machine that doesn't have an IPV6 address on its own.
TIP
The operations on this page must be performed on the original system, and ensure that no other scripts from this project are installed(Except for PVE, which needs to be installed first), as this may lead to environment conflicts.
Here are the platforms that are currently running in 2023 that offer IPV6 subnets for free.
Supported PlatformsCorresponding Required Installation PackagesProtocolsNumber of Channels/Subnets
tunnelbroker.netifupdown OR ifupdown2v4tunnel OR sit3✖/64 OR 5✖/64
tunnelbroker.chifupdown OR ifupdown2v4tunnel OR sit3✖/64
ip4market.ruifupdown OR ifupdown2v4tunnel OR sit1✖/64
netassist.uaifupdown OR ifupdown2v4tunnel OR sit1✖/64
https://github.com/oneclickvirt/6in4ifupdown2sit、gre、ipipcustom
The free platform only solves the problem that IPV6 is not available, it does not provide premium IPV6 bandwidth.
If you need high quality bandwidth, please build your own tunnel. When both ifupdown and ifupdown2 are available, try ifupdown first to see if it can be installed successfully, otherwise install ifupdown2.
After the installation is complete, select which package is installed behind to convert the format.
Initial environment modifications ​
Execute
touch /etc/cloud/cloud-init.disabled
Turn off the automated overwrite of cloud-init first, and then to see what the local machine is using to manage the network, run
systemctl is-active systemd-networkd
and
systemctl is-active networking
See which case this falls into, if it's the former active and the latter inactive, you need to reinstall/DD a system that isn't configured this way, or switch the local machine to use ifupdown/ifupdown2 to manage network execution
# Judge for yourself whether you need to disable the original network management or not
+import{_ as e,v as s,b as t,R as a}from"./chunks/framework.70afa331.js";const n="/assets/lxd1.78537e30.png",o="/assets/lxd2.da10b5ec.png",l="/assets/lxd3.917f56de.png",p="/assets/lxd4.83a1a121.png",i="/assets/lxd5.4ebc1444.png",r="/assets/lxd6.572825bf.png",c="/assets/lxd7.b73982c7.png",d="/assets/lxd8.9fcc21e5.png",h="/assets/lxd9.00250a32.png",u="/assets/lxd10.a25a745c.png",y="/assets/lxd11.b83f953c.png",m="/assets/lxd12.0da335dd.png",C="/assets/lxd13.308fe0de.png",g="/assets/lxd14.8dbfdcd6.png",f="/assets/lxd15.70114933.png",b="/assets/lxd16.a595fa36.png",A="/assets/lxd17.d7ea65d8.png",v="/assets/lxd18.d6225daa.png",D="/assets/lxd19.69674669.png",k="/assets/lxd20.179fc6e1.png",w="/assets/lxd21.48123d6a.png",F="/assets/lxd22.4386597e.png",P="/assets/lxd23.c26427e3.png",W=JSON.parse('{"title":"Custom","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_custom.md","filePath":"en/guide/incus/incus_custom.md","lastUpdated":1747730955000}'),_={name:"en/guide/incus/incus_custom.md"},I=a(`
Custom ​
Attach free IPV6 address segments to host machines ​
Some machines don't have an IPV6 /64 subnet on the machine itself, here is a method given to attach an IPV6 subnet for free.
Here is a solution using the 6in4 method for a host machine that doesn't have an IPV6 address on its own.
TIP
The operations on this page must be performed on the original system, and ensure that no other scripts from this project are installed(Except for PVE, which needs to be installed first), as this may lead to environment conflicts.
Here are the platforms that are currently running in 2023 that offer IPV6 subnets for free.
Supported PlatformsCorresponding Required Installation PackagesProtocolsNumber of Channels/Subnets
tunnelbroker.netifupdown OR ifupdown2v4tunnel OR sit3✖/64 OR 5✖/64
tunnelbroker.chifupdown OR ifupdown2v4tunnel OR sit3✖/64
ip4market.ruifupdown OR ifupdown2v4tunnel OR sit1✖/64
netassist.uaifupdown OR ifupdown2v4tunnel OR sit1✖/64
https://github.com/oneclickvirt/6in4ifupdown2sit、gre、ipipcustom
The free platform only solves the problem that IPV6 is not available, it does not provide premium IPV6 bandwidth.
If you need high quality bandwidth, please build your own tunnel. When both ifupdown and ifupdown2 are available, try ifupdown first to see if it can be installed successfully, otherwise install ifupdown2.
After the installation is complete, select which package is installed behind to convert the format.
Initial environment modifications ​
Execute
touch /etc/cloud/cloud-init.disabled
Turn off the automated overwrite of cloud-init first, and then to see what the local machine is using to manage the network, run
systemctl is-active systemd-networkd
and
systemctl is-active networking
See which case this falls into, if it's the former active and the latter inactive, you need to reinstall/DD a system that isn't configured this way, or switch the local machine to use ifupdown/ifupdown2 to manage network execution
# Judge for yourself whether you need to disable the original network management or not
 # systemctl stop systemd-networkd
 # systemctl disable systemd-networkd
 # systemctl stop systemd-networkd.socket
diff --git a/assets/en_guide_incus_incus_custom.md.4c2b9e58.lean.js b/assets/en_guide_incus_incus_custom.md.70184a5b.lean.js
similarity index 99%
rename from assets/en_guide_incus_incus_custom.md.4c2b9e58.lean.js
rename to assets/en_guide_incus_incus_custom.md.70184a5b.lean.js
index 9045362656..4bc11a6c89 100644
--- a/assets/en_guide_incus_incus_custom.md.4c2b9e58.lean.js
+++ b/assets/en_guide_incus_incus_custom.md.70184a5b.lean.js
@@ -1,4 +1,4 @@
-import{_ as e,v as s,b as t,R as a}from"./chunks/framework.70afa331.js";const n="/assets/lxd1.78537e30.png",o="/assets/lxd2.da10b5ec.png",l="/assets/lxd3.917f56de.png",p="/assets/lxd4.83a1a121.png",i="/assets/lxd5.4ebc1444.png",r="/assets/lxd6.572825bf.png",c="/assets/lxd7.b73982c7.png",d="/assets/lxd8.9fcc21e5.png",h="/assets/lxd9.00250a32.png",u="/assets/lxd10.a25a745c.png",y="/assets/lxd11.b83f953c.png",m="/assets/lxd12.0da335dd.png",C="/assets/lxd13.308fe0de.png",g="/assets/lxd14.8dbfdcd6.png",f="/assets/lxd15.70114933.png",b="/assets/lxd16.a595fa36.png",A="/assets/lxd17.d7ea65d8.png",v="/assets/lxd18.d6225daa.png",D="/assets/lxd19.69674669.png",k="/assets/lxd20.179fc6e1.png",w="/assets/lxd21.48123d6a.png",F="/assets/lxd22.4386597e.png",P="/assets/lxd23.c26427e3.png",W=JSON.parse('{"title":"Custom","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_custom.md","filePath":"en/guide/incus/incus_custom.md","lastUpdated":1747726389000}'),_={name:"en/guide/incus/incus_custom.md"},I=a(`
Custom ​
Attach free IPV6 address segments to host machines ​
Some machines don't have an IPV6 /64 subnet on the machine itself, here is a method given to attach an IPV6 subnet for free.
Here is a solution using the 6in4 method for a host machine that doesn't have an IPV6 address on its own.
TIP
The operations on this page must be performed on the original system, and ensure that no other scripts from this project are installed(Except for PVE, which needs to be installed first), as this may lead to environment conflicts.
Here are the platforms that are currently running in 2023 that offer IPV6 subnets for free.
Supported PlatformsCorresponding Required Installation PackagesProtocolsNumber of Channels/Subnets
tunnelbroker.netifupdown OR ifupdown2v4tunnel OR sit3✖/64 OR 5✖/64
tunnelbroker.chifupdown OR ifupdown2v4tunnel OR sit3✖/64
ip4market.ruifupdown OR ifupdown2v4tunnel OR sit1✖/64
netassist.uaifupdown OR ifupdown2v4tunnel OR sit1✖/64
https://github.com/oneclickvirt/6in4ifupdown2sit、gre、ipipcustom
The free platform only solves the problem that IPV6 is not available, it does not provide premium IPV6 bandwidth.
If you need high quality bandwidth, please build your own tunnel. When both ifupdown and ifupdown2 are available, try ifupdown first to see if it can be installed successfully, otherwise install ifupdown2.
After the installation is complete, select which package is installed behind to convert the format.
Initial environment modifications ​
Execute
touch /etc/cloud/cloud-init.disabled
Turn off the automated overwrite of cloud-init first, and then to see what the local machine is using to manage the network, run
systemctl is-active systemd-networkd
and
systemctl is-active networking
See which case this falls into, if it's the former active and the latter inactive, you need to reinstall/DD a system that isn't configured this way, or switch the local machine to use ifupdown/ifupdown2 to manage network execution
# Judge for yourself whether you need to disable the original network management or not
+import{_ as e,v as s,b as t,R as a}from"./chunks/framework.70afa331.js";const n="/assets/lxd1.78537e30.png",o="/assets/lxd2.da10b5ec.png",l="/assets/lxd3.917f56de.png",p="/assets/lxd4.83a1a121.png",i="/assets/lxd5.4ebc1444.png",r="/assets/lxd6.572825bf.png",c="/assets/lxd7.b73982c7.png",d="/assets/lxd8.9fcc21e5.png",h="/assets/lxd9.00250a32.png",u="/assets/lxd10.a25a745c.png",y="/assets/lxd11.b83f953c.png",m="/assets/lxd12.0da335dd.png",C="/assets/lxd13.308fe0de.png",g="/assets/lxd14.8dbfdcd6.png",f="/assets/lxd15.70114933.png",b="/assets/lxd16.a595fa36.png",A="/assets/lxd17.d7ea65d8.png",v="/assets/lxd18.d6225daa.png",D="/assets/lxd19.69674669.png",k="/assets/lxd20.179fc6e1.png",w="/assets/lxd21.48123d6a.png",F="/assets/lxd22.4386597e.png",P="/assets/lxd23.c26427e3.png",W=JSON.parse('{"title":"Custom","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_custom.md","filePath":"en/guide/incus/incus_custom.md","lastUpdated":1747730955000}'),_={name:"en/guide/incus/incus_custom.md"},I=a(`
Custom ​
Attach free IPV6 address segments to host machines ​
Some machines don't have an IPV6 /64 subnet on the machine itself, here is a method given to attach an IPV6 subnet for free.
Here is a solution using the 6in4 method for a host machine that doesn't have an IPV6 address on its own.
TIP
The operations on this page must be performed on the original system, and ensure that no other scripts from this project are installed(Except for PVE, which needs to be installed first), as this may lead to environment conflicts.
Here are the platforms that are currently running in 2023 that offer IPV6 subnets for free.
Supported PlatformsCorresponding Required Installation PackagesProtocolsNumber of Channels/Subnets
tunnelbroker.netifupdown OR ifupdown2v4tunnel OR sit3✖/64 OR 5✖/64
tunnelbroker.chifupdown OR ifupdown2v4tunnel OR sit3✖/64
ip4market.ruifupdown OR ifupdown2v4tunnel OR sit1✖/64
netassist.uaifupdown OR ifupdown2v4tunnel OR sit1✖/64
https://github.com/oneclickvirt/6in4ifupdown2sit、gre、ipipcustom
The free platform only solves the problem that IPV6 is not available, it does not provide premium IPV6 bandwidth.
If you need high quality bandwidth, please build your own tunnel. When both ifupdown and ifupdown2 are available, try ifupdown first to see if it can be installed successfully, otherwise install ifupdown2.
After the installation is complete, select which package is installed behind to convert the format.
Initial environment modifications ​
Execute
touch /etc/cloud/cloud-init.disabled
Turn off the automated overwrite of cloud-init first, and then to see what the local machine is using to manage the network, run
systemctl is-active systemd-networkd
and
systemctl is-active networking
See which case this falls into, if it's the former active and the latter inactive, you need to reinstall/DD a system that isn't configured this way, or switch the local machine to use ifupdown/ifupdown2 to manage network execution
# Judge for yourself whether you need to disable the original network management or not
 # systemctl stop systemd-networkd
 # systemctl disable systemd-networkd
 # systemctl stop systemd-networkd.socket
diff --git a/assets/en_guide_incus_incus_extra_config.md.b24e5ad8.js b/assets/en_guide_incus_incus_extra_config.md.5f26742c.js
similarity index 99%
rename from assets/en_guide_incus_incus_extra_config.md.b24e5ad8.js
rename to assets/en_guide_incus_incus_extra_config.md.5f26742c.js
index 65f90f74fe..21216f87be 100644
--- a/assets/en_guide_incus_incus_extra_config.md.b24e5ad8.js
+++ b/assets/en_guide_incus_incus_extra_config.md.5f26742c.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"Custom Configuration","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_extra_config.md","filePath":"en/guide/incus/incus_extra_config.md","lastUpdated":1747726389000}'),e={name:"en/guide/incus/incus_extra_config.md"},l=o(`
Custom Configuration ​
TIP
The following configurations may increase the load on the server. Only install them if necessary.
Automatic IPV6 Address Configuration ​
  • (Optional, not required if not using)
  • This script is only suitable for servers that have an IPV6 subnet with a prefix, and the server has bound the first IP of the subnet as its IPV6 address or IPV6 gateway.
  • Automatically configures IPV6 addresses for incus containers created with incus.
  • Integrated into buildone.sh and can be controlled by variables without needing to be downloaded beforehand. You don't need to manually use this script; when using buildone.sh, configure with variable Y to enable it.
Download Script
Command:
bash
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
Automatically configure IPV6 mapped addresses for containers
bash
bash build_ipv6_network.sh Container_Name(change_me)
A message is printed when the mapping is complete (Default mapping without iptables)
Example (automatically configure the test container with an IPV6 address, a test_v6 file is written when the configuration is complete)
bash
bash build_ipv6_network.sh test
PS: Add ipv6 processing can choose whether to use ip6tables for mapping, the default is not to use ip6tables for mapping but to add new network devices for mapping.
Use ip6tables for mapping
bash
bash build_ipv6_network.sh Container_name Y
If ip6tables is used for mapping, remove all IPV6 mapped rules available:
bash
ip6tables -t nat -F PREROUTING
+import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"Custom Configuration","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_extra_config.md","filePath":"en/guide/incus/incus_extra_config.md","lastUpdated":1747730955000}'),e={name:"en/guide/incus/incus_extra_config.md"},l=o(`
Custom Configuration ​
TIP
The following configurations may increase the load on the server. Only install them if necessary.
Automatic IPV6 Address Configuration ​
  • (Optional, not required if not using)
  • This script is only suitable for servers that have an IPV6 subnet with a prefix, and the server has bound the first IP of the subnet as its IPV6 address or IPV6 gateway.
  • Automatically configures IPV6 addresses for incus containers created with incus.
  • Integrated into buildone.sh and can be controlled by variables without needing to be downloaded beforehand. You don't need to manually use this script; when using buildone.sh, configure with variable Y to enable it.
Download Script
Command:
bash
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
Automatically configure IPV6 mapped addresses for containers
bash
bash build_ipv6_network.sh Container_Name(change_me)
A message is printed when the mapping is complete (Default mapping without iptables)
Example (automatically configure the test container with an IPV6 address, a test_v6 file is written when the configuration is complete)
bash
bash build_ipv6_network.sh test
PS: Add ipv6 processing can choose whether to use ip6tables for mapping, the default is not to use ip6tables for mapping but to add new network devices for mapping.
Use ip6tables for mapping
bash
bash build_ipv6_network.sh Container_name Y
If ip6tables is used for mapping, remove all IPV6 mapped rules available:
bash
ip6tables -t nat -F PREROUTING
 ip6tables-legacy -t nat -F PREROUTING
 ip6tables-save > /etc/iptables/rules.v6
 netfilter-persistent save
diff --git a/assets/en_guide_incus_incus_extra_config.md.b24e5ad8.lean.js b/assets/en_guide_incus_incus_extra_config.md.5f26742c.lean.js
similarity index 99%
rename from assets/en_guide_incus_incus_extra_config.md.b24e5ad8.lean.js
rename to assets/en_guide_incus_incus_extra_config.md.5f26742c.lean.js
index 65f90f74fe..21216f87be 100644
--- a/assets/en_guide_incus_incus_extra_config.md.b24e5ad8.lean.js
+++ b/assets/en_guide_incus_incus_extra_config.md.5f26742c.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"Custom Configuration","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_extra_config.md","filePath":"en/guide/incus/incus_extra_config.md","lastUpdated":1747726389000}'),e={name:"en/guide/incus/incus_extra_config.md"},l=o(`
Custom Configuration ​
TIP
The following configurations may increase the load on the server. Only install them if necessary.
Automatic IPV6 Address Configuration ​
  • (Optional, not required if not using)
  • This script is only suitable for servers that have an IPV6 subnet with a prefix, and the server has bound the first IP of the subnet as its IPV6 address or IPV6 gateway.
  • Automatically configures IPV6 addresses for incus containers created with incus.
  • Integrated into buildone.sh and can be controlled by variables without needing to be downloaded beforehand. You don't need to manually use this script; when using buildone.sh, configure with variable Y to enable it.
Download Script
Command:
bash
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
Automatically configure IPV6 mapped addresses for containers
bash
bash build_ipv6_network.sh Container_Name(change_me)
A message is printed when the mapping is complete (Default mapping without iptables)
Example (automatically configure the test container with an IPV6 address, a test_v6 file is written when the configuration is complete)
bash
bash build_ipv6_network.sh test
PS: Add ipv6 processing can choose whether to use ip6tables for mapping, the default is not to use ip6tables for mapping but to add new network devices for mapping.
Use ip6tables for mapping
bash
bash build_ipv6_network.sh Container_name Y
If ip6tables is used for mapping, remove all IPV6 mapped rules available:
bash
ip6tables -t nat -F PREROUTING
+import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"Custom Configuration","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_extra_config.md","filePath":"en/guide/incus/incus_extra_config.md","lastUpdated":1747730955000}'),e={name:"en/guide/incus/incus_extra_config.md"},l=o(`
Custom Configuration ​
TIP
The following configurations may increase the load on the server. Only install them if necessary.
Automatic IPV6 Address Configuration ​
  • (Optional, not required if not using)
  • This script is only suitable for servers that have an IPV6 subnet with a prefix, and the server has bound the first IP of the subnet as its IPV6 address or IPV6 gateway.
  • Automatically configures IPV6 addresses for incus containers created with incus.
  • Integrated into buildone.sh and can be controlled by variables without needing to be downloaded beforehand. You don't need to manually use this script; when using buildone.sh, configure with variable Y to enable it.
Download Script
Command:
bash
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
Automatically configure IPV6 mapped addresses for containers
bash
bash build_ipv6_network.sh Container_Name(change_me)
A message is printed when the mapping is complete (Default mapping without iptables)
Example (automatically configure the test container with an IPV6 address, a test_v6 file is written when the configuration is complete)
bash
bash build_ipv6_network.sh test
PS: Add ipv6 processing can choose whether to use ip6tables for mapping, the default is not to use ip6tables for mapping but to add new network devices for mapping.
Use ip6tables for mapping
bash
bash build_ipv6_network.sh Container_name Y
If ip6tables is used for mapping, remove all IPV6 mapped rules available:
bash
ip6tables -t nat -F PREROUTING
 ip6tables-legacy -t nat -F PREROUTING
 ip6tables-save > /etc/iptables/rules.v6
 netfilter-persistent save
diff --git a/assets/en_guide_incus_incus_install.md.3dbc0035.js b/assets/en_guide_incus_incus_install.md.f80502c3.js
similarity index 99%
rename from assets/en_guide_incus_incus_install.md.3dbc0035.js
rename to assets/en_guide_incus_incus_install.md.f80502c3.js
index b964e8dd95..4033817518 100644
--- a/assets/en_guide_incus_incus_install.md.3dbc0035.js
+++ b/assets/en_guide_incus_incus_install.md.f80502c3.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"incus Installation Guide","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_install.md","filePath":"en/guide/incus/incus_install.md","lastUpdated":1747726389000}'),l={name:"en/guide/incus/incus_install.md"},t=e(`
incus Installation Guide ​
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the incus module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
One-Click Installation ​
WARNING
If this is a new server, make sure that both update and curl are working properly before executing this script.
  • Prerequisites: Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • The virtual memory here is talking about the size of the SWAP to be opened, and the storage pool is the sum of the sizes of the disks occupied by all your servers to be opened
  • The server needs to be restarted after the environment installation process to load some default configurations
  • By default, lxd's lxcfs-related configuration is enabled, so that in-container querying of container information changes to information about the container itself rather than the host
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/incus_install.sh -o incus_install.sh && chmod +x incus_install.sh && bash incus_install.sh
OR
shell
bash incus_install.sh
Example of initialization configuration:
If there is 18GB of unused disk space on the system disk, after deducting the space already occupied, and you want to allocate 2GB of virtual memory (2048MB of SWAP) and a 15GB storage pool, then following the prompts in the command line, enter 2048 and 15.
TIP
The execution process may require a manual reboot to load the storage type into the kernel, the installation is completed at the end of the execution will automatically reboot the server, the first time after the complete installation of the reboot will take about 400 ~ 500 seconds, please be patient
WARNING
If you need to open more than 200 Incus containers on a single server, then it is not recommended to use this project, there may be problems with lxcfs access drift, which generates IO occupancy that cannot be released. (This is a native LXC problem that can't be fixed.)
Manual Installation (optional) ​
Not recommended, just for some odd environments where one-click scripts won't run.
Disable Firewall ​
bash
apt update
+import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"incus Installation Guide","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_install.md","filePath":"en/guide/incus/incus_install.md","lastUpdated":1747730955000}'),l={name:"en/guide/incus/incus_install.md"},t=e(`
incus Installation Guide ​
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the incus module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
One-Click Installation ​
WARNING
If this is a new server, make sure that both update and curl are working properly before executing this script.
  • Prerequisites: Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • The virtual memory here is talking about the size of the SWAP to be opened, and the storage pool is the sum of the sizes of the disks occupied by all your servers to be opened
  • The server needs to be restarted after the environment installation process to load some default configurations
  • By default, lxd's lxcfs-related configuration is enabled, so that in-container querying of container information changes to information about the container itself rather than the host
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/incus_install.sh -o incus_install.sh && chmod +x incus_install.sh && bash incus_install.sh
OR
shell
bash incus_install.sh
Example of initialization configuration:
If there is 18GB of unused disk space on the system disk, after deducting the space already occupied, and you want to allocate 2GB of virtual memory (2048MB of SWAP) and a 15GB storage pool, then following the prompts in the command line, enter 2048 and 15.
TIP
The execution process may require a manual reboot to load the storage type into the kernel, the installation is completed at the end of the execution will automatically reboot the server, the first time after the complete installation of the reboot will take about 400 ~ 500 seconds, please be patient
WARNING
If you need to open more than 200 Incus containers on a single server, then it is not recommended to use this project, there may be problems with lxcfs access drift, which generates IO occupancy that cannot be released. (This is a native LXC problem that can't be fixed.)
Manual Installation (optional) ​
Not recommended, just for some odd environments where one-click scripts won't run.
Disable Firewall ​
bash
apt update
 apt install curl wget sudo dos2unix ufw jq -y
 ufw disable
Enabling Virtual Memory SWAP ​
The amount of memory depends on how many instances you want to run. If you want to run 8 instances and calculate, you'll need 2GB of memory. If your actual physical memory is 512MB, you'll need an additional 1.5GB. To be cautious, allocate 2GB of virtual memory.
Execute the following commands: Enter '1', then enter '2048'. This signifies allocating 2GB of virtual memory.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
Installing incus ​
Actually, the virtual memory allocated for swap should be twice the size of the actual memory. So, it's reasonable to allocate 1GB if the actual memory is 500MB. The scenario I described above is an excessive allocation.
sudo -i
 mkdir -p /etc/apt/keyrings/
diff --git a/assets/en_guide_incus_incus_install.md.3dbc0035.lean.js b/assets/en_guide_incus_incus_install.md.f80502c3.lean.js
similarity index 99%
rename from assets/en_guide_incus_incus_install.md.3dbc0035.lean.js
rename to assets/en_guide_incus_incus_install.md.f80502c3.lean.js
index b964e8dd95..4033817518 100644
--- a/assets/en_guide_incus_incus_install.md.3dbc0035.lean.js
+++ b/assets/en_guide_incus_incus_install.md.f80502c3.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"incus Installation Guide","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_install.md","filePath":"en/guide/incus/incus_install.md","lastUpdated":1747726389000}'),l={name:"en/guide/incus/incus_install.md"},t=e(`
incus Installation Guide ​
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the incus module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
One-Click Installation ​
WARNING
If this is a new server, make sure that both update and curl are working properly before executing this script.
  • Prerequisites: Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • The virtual memory here is talking about the size of the SWAP to be opened, and the storage pool is the sum of the sizes of the disks occupied by all your servers to be opened
  • The server needs to be restarted after the environment installation process to load some default configurations
  • By default, lxd's lxcfs-related configuration is enabled, so that in-container querying of container information changes to information about the container itself rather than the host
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/incus_install.sh -o incus_install.sh && chmod +x incus_install.sh && bash incus_install.sh
OR
shell
bash incus_install.sh
Example of initialization configuration:
If there is 18GB of unused disk space on the system disk, after deducting the space already occupied, and you want to allocate 2GB of virtual memory (2048MB of SWAP) and a 15GB storage pool, then following the prompts in the command line, enter 2048 and 15.
TIP
The execution process may require a manual reboot to load the storage type into the kernel, the installation is completed at the end of the execution will automatically reboot the server, the first time after the complete installation of the reboot will take about 400 ~ 500 seconds, please be patient
WARNING
If you need to open more than 200 Incus containers on a single server, then it is not recommended to use this project, there may be problems with lxcfs access drift, which generates IO occupancy that cannot be released. (This is a native LXC problem that can't be fixed.)
Manual Installation (optional) ​
Not recommended, just for some odd environments where one-click scripts won't run.
Disable Firewall ​
bash
apt update
+import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"incus Installation Guide","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_install.md","filePath":"en/guide/incus/incus_install.md","lastUpdated":1747730955000}'),l={name:"en/guide/incus/incus_install.md"},t=e(`
incus Installation Guide ​
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the incus module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
One-Click Installation ​
WARNING
If this is a new server, make sure that both update and curl are working properly before executing this script.
  • Prerequisites: Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • The virtual memory here is talking about the size of the SWAP to be opened, and the storage pool is the sum of the sizes of the disks occupied by all your servers to be opened
  • The server needs to be restarted after the environment installation process to load some default configurations
  • By default, lxd's lxcfs-related configuration is enabled, so that in-container querying of container information changes to information about the container itself rather than the host
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/incus_install.sh -o incus_install.sh && chmod +x incus_install.sh && bash incus_install.sh
OR
shell
bash incus_install.sh
Example of initialization configuration:
If there is 18GB of unused disk space on the system disk, after deducting the space already occupied, and you want to allocate 2GB of virtual memory (2048MB of SWAP) and a 15GB storage pool, then following the prompts in the command line, enter 2048 and 15.
TIP
The execution process may require a manual reboot to load the storage type into the kernel, the installation is completed at the end of the execution will automatically reboot the server, the first time after the complete installation of the reboot will take about 400 ~ 500 seconds, please be patient
WARNING
If you need to open more than 200 Incus containers on a single server, then it is not recommended to use this project, there may be problems with lxcfs access drift, which generates IO occupancy that cannot be released. (This is a native LXC problem that can't be fixed.)
Manual Installation (optional) ​
Not recommended, just for some odd environments where one-click scripts won't run.
Disable Firewall ​
bash
apt update
 apt install curl wget sudo dos2unix ufw jq -y
 ufw disable
Enabling Virtual Memory SWAP ​
The amount of memory depends on how many instances you want to run. If you want to run 8 instances and calculate, you'll need 2GB of memory. If your actual physical memory is 512MB, you'll need an additional 1.5GB. To be cautious, allocate 2GB of virtual memory.
Execute the following commands: Enter '1', then enter '2048'. This signifies allocating 2GB of virtual memory.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
Installing incus ​
Actually, the virtual memory allocated for swap should be twice the size of the actual memory. So, it's reasonable to allocate 1GB if the actual memory is 500MB. The scenario I described above is an excessive allocation.
sudo -i
 mkdir -p /etc/apt/keyrings/
diff --git a/assets/en_guide_incus_incus_lxc.md.c6d15d7c.js b/assets/en_guide_incus_incus_lxc.md.99febac7.js
similarity index 99%
rename from assets/en_guide_incus_incus_lxc.md.c6d15d7c.js
rename to assets/en_guide_incus_incus_lxc.md.99febac7.js
index ab999f57d0..92fbf86ea3 100644
--- a/assets/en_guide_incus_incus_lxc.md.c6d15d7c.js
+++ b/assets/en_guide_incus_incus_lxc.md.99febac7.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Running LXC Container in Incus","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_lxc.md","filePath":"en/guide/incus/incus_lxc.md","lastUpdated":1747726389000}'),o={name:"en/guide/incus/incus_lxc.md"},l=e(`
Running LXC Container in Incus ​
Images available for creating LXC Containers ​
A portion of the available system parameters are shown here for your reference:
  • debian10, debian11, debian12
  • ubuntu18, ubuntu20, ubuntu22
  • centos8, centos9 (actually opened out of the Stream version)
  • alpine3.15, alpine3.16, alpine3.17, alpine3.18
  • openwrt21，openwrt22，fedora37，fedora38，fedora39
  • rockylinux8，rockylinux9，oralce8，oracle9
  • oralce7，centos7 (CGroupV1 needs to be enabled in GRUB or it won't start.)
  • kali，archlinux
  • Note that the combination of lowercase letters + numbers or only lowercase letters, try it yourself, if the search is not the system will automatically exit the script
  • The version number can be with English decimal point, in order to adapt to the alpine version number has been supported.
  • If you can't open it, it may be that the hard disk is not big enough or it doesn't fit the host, try it by yourself.
  • The images currently in use are triple filtered and prioritized: self-hosted、official-hosted、opsmaru
  • A complete list of supported systems for self-compiling images: x86_64_fixed_images.txt and arm64_fixed_images.txt
TIP
The version number has ended the long-term maintenance of the general no longer have an official mirror, temporarily did not find the archive address of the historical mirror, if you find welcome to leave a message I will add support!
Generate only one NAT server ​
  • Generate only one NAT server, with customizable restrictions on all content.
Download script ​
Downloading the boot script is NOT REQUIRED, if you have used the command to install incus with one click, the corresponding boot script will be downloaded automatically, so you don't need to download the script again.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
Usage ​
. /buildone.sh name Cpu_num Memory_size Hard_disk_size SSH_port Extranet_start_port Extranet_stop_port Download_speed Upload_speed Whether_IPV6_is_enabled(Y or N) System(leave blank for debian11)
Memory size is calculated in MB, hard disk size is calculated in GB, download speed upload speed is calculated in Mbit, whether to enable IPV6 does not have to fill in Y or N, no this parameter can also be left blank default does not enable IPV6
If external start port\`\` and external stop port are both set to 0, then we don't do interval port mapping, only the basic SSH port is mapped, note that \`\`\`can't be null, and it needs to be set to 0 if it's not to be mapped.
Support custom server system, do not fill in the leave blank default use debian11, pay attention to the incoming parameters for the system name + version number
Example ​
Here is the information about the example chick that is being raised:
AttributeValue
server's Nametest
Username for SSH Loginroot
Password for SSH LoginRandomly generated
Number of CPU Cores1
Memory Size256MB
Disk Size2G
Range of Internal and External Port Mapping20002 to 20025
Upload Bandwidth500Mbit
Download Bandwidth500Mbit
Automatically Set External IPv6 AddressNo
Operating SystemDebian 11
./buildone.sh test 1 256 2 20001 20002 20025 500 500 N debian11
If you need to see the information, run
shell
cat ct_name_change_me
For example, the information for the query example is
shell
cat test
If you have already generated chicks through the above methods and still need to batch generate chicks, you can use a customized batch generation version of the script, but note that you should first delete the test chicks before batch generating chicks
Delete Test Chick ​
shell
incus stop test
+import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Running LXC Container in Incus","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_lxc.md","filePath":"en/guide/incus/incus_lxc.md","lastUpdated":1747730955000}'),o={name:"en/guide/incus/incus_lxc.md"},l=e(`
Running LXC Container in Incus ​
Images available for creating LXC Containers ​
A portion of the available system parameters are shown here for your reference:
  • debian10, debian11, debian12
  • ubuntu18, ubuntu20, ubuntu22
  • centos8, centos9 (actually opened out of the Stream version)
  • alpine3.15, alpine3.16, alpine3.17, alpine3.18
  • openwrt21，openwrt22，fedora37，fedora38，fedora39
  • rockylinux8，rockylinux9，oralce8，oracle9
  • oralce7，centos7 (CGroupV1 needs to be enabled in GRUB or it won't start.)
  • kali，archlinux
  • Note that the combination of lowercase letters + numbers or only lowercase letters, try it yourself, if the search is not the system will automatically exit the script
  • The version number can be with English decimal point, in order to adapt to the alpine version number has been supported.
  • If you can't open it, it may be that the hard disk is not big enough or it doesn't fit the host, try it by yourself.
  • The images currently in use are triple filtered and prioritized: self-hosted、official-hosted、opsmaru
  • A complete list of supported systems for self-compiling images: x86_64_fixed_images.txt and arm64_fixed_images.txt
TIP
The version number has ended the long-term maintenance of the general no longer have an official mirror, temporarily did not find the archive address of the historical mirror, if you find welcome to leave a message I will add support!
Generate only one NAT server ​
  • Generate only one NAT server, with customizable restrictions on all content.
Download script ​
Downloading the boot script is NOT REQUIRED, if you have used the command to install incus with one click, the corresponding boot script will be downloaded automatically, so you don't need to download the script again.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
Usage ​
. /buildone.sh name Cpu_num Memory_size Hard_disk_size SSH_port Extranet_start_port Extranet_stop_port Download_speed Upload_speed Whether_IPV6_is_enabled(Y or N) System(leave blank for debian11)
Memory size is calculated in MB, hard disk size is calculated in GB, download speed upload speed is calculated in Mbit, whether to enable IPV6 does not have to fill in Y or N, no this parameter can also be left blank default does not enable IPV6
If external start port\`\` and external stop port are both set to 0, then we don't do interval port mapping, only the basic SSH port is mapped, note that \`\`\`can't be null, and it needs to be set to 0 if it's not to be mapped.
Support custom server system, do not fill in the leave blank default use debian11, pay attention to the incoming parameters for the system name + version number
Example ​
Here is the information about the example chick that is being raised:
AttributeValue
server's Nametest
Username for SSH Loginroot
Password for SSH LoginRandomly generated
Number of CPU Cores1
Memory Size256MB
Disk Size2G
Range of Internal and External Port Mapping20002 to 20025
Upload Bandwidth500Mbit
Download Bandwidth500Mbit
Automatically Set External IPv6 AddressNo
Operating SystemDebian 11
./buildone.sh test 1 256 2 20001 20002 20025 500 500 N debian11
If you need to see the information, run
shell
cat ct_name_change_me
For example, the information for the query example is
shell
cat test
If you have already generated chicks through the above methods and still need to batch generate chicks, you can use a customized batch generation version of the script, but note that you should first delete the test chicks before batch generating chicks
Delete Test Chick ​
shell
incus stop test
 incus delete test
 rm -rf test
 rm -rf test_v6
diff --git a/assets/en_guide_incus_incus_lxc.md.c6d15d7c.lean.js b/assets/en_guide_incus_incus_lxc.md.99febac7.lean.js
similarity index 99%
rename from assets/en_guide_incus_incus_lxc.md.c6d15d7c.lean.js
rename to assets/en_guide_incus_incus_lxc.md.99febac7.lean.js
index ab999f57d0..92fbf86ea3 100644
--- a/assets/en_guide_incus_incus_lxc.md.c6d15d7c.lean.js
+++ b/assets/en_guide_incus_incus_lxc.md.99febac7.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Running LXC Container in Incus","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_lxc.md","filePath":"en/guide/incus/incus_lxc.md","lastUpdated":1747726389000}'),o={name:"en/guide/incus/incus_lxc.md"},l=e(`
Running LXC Container in Incus ​
Images available for creating LXC Containers ​
A portion of the available system parameters are shown here for your reference:
  • debian10, debian11, debian12
  • ubuntu18, ubuntu20, ubuntu22
  • centos8, centos9 (actually opened out of the Stream version)
  • alpine3.15, alpine3.16, alpine3.17, alpine3.18
  • openwrt21，openwrt22，fedora37，fedora38，fedora39
  • rockylinux8，rockylinux9，oralce8，oracle9
  • oralce7，centos7 (CGroupV1 needs to be enabled in GRUB or it won't start.)
  • kali，archlinux
  • Note that the combination of lowercase letters + numbers or only lowercase letters, try it yourself, if the search is not the system will automatically exit the script
  • The version number can be with English decimal point, in order to adapt to the alpine version number has been supported.
  • If you can't open it, it may be that the hard disk is not big enough or it doesn't fit the host, try it by yourself.
  • The images currently in use are triple filtered and prioritized: self-hosted、official-hosted、opsmaru
  • A complete list of supported systems for self-compiling images: x86_64_fixed_images.txt and arm64_fixed_images.txt
TIP
The version number has ended the long-term maintenance of the general no longer have an official mirror, temporarily did not find the archive address of the historical mirror, if you find welcome to leave a message I will add support!
Generate only one NAT server ​
  • Generate only one NAT server, with customizable restrictions on all content.
Download script ​
Downloading the boot script is NOT REQUIRED, if you have used the command to install incus with one click, the corresponding boot script will be downloaded automatically, so you don't need to download the script again.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
Usage ​
. /buildone.sh name Cpu_num Memory_size Hard_disk_size SSH_port Extranet_start_port Extranet_stop_port Download_speed Upload_speed Whether_IPV6_is_enabled(Y or N) System(leave blank for debian11)
Memory size is calculated in MB, hard disk size is calculated in GB, download speed upload speed is calculated in Mbit, whether to enable IPV6 does not have to fill in Y or N, no this parameter can also be left blank default does not enable IPV6
If external start port\`\` and external stop port are both set to 0, then we don't do interval port mapping, only the basic SSH port is mapped, note that \`\`\`can't be null, and it needs to be set to 0 if it's not to be mapped.
Support custom server system, do not fill in the leave blank default use debian11, pay attention to the incoming parameters for the system name + version number
Example ​
Here is the information about the example chick that is being raised:
AttributeValue
server's Nametest
Username for SSH Loginroot
Password for SSH LoginRandomly generated
Number of CPU Cores1
Memory Size256MB
Disk Size2G
Range of Internal and External Port Mapping20002 to 20025
Upload Bandwidth500Mbit
Download Bandwidth500Mbit
Automatically Set External IPv6 AddressNo
Operating SystemDebian 11
./buildone.sh test 1 256 2 20001 20002 20025 500 500 N debian11
If you need to see the information, run
shell
cat ct_name_change_me
For example, the information for the query example is
shell
cat test
If you have already generated chicks through the above methods and still need to batch generate chicks, you can use a customized batch generation version of the script, but note that you should first delete the test chicks before batch generating chicks
Delete Test Chick ​
shell
incus stop test
+import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Running LXC Container in Incus","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_lxc.md","filePath":"en/guide/incus/incus_lxc.md","lastUpdated":1747730955000}'),o={name:"en/guide/incus/incus_lxc.md"},l=e(`
Running LXC Container in Incus ​
Images available for creating LXC Containers ​
A portion of the available system parameters are shown here for your reference:
  • debian10, debian11, debian12
  • ubuntu18, ubuntu20, ubuntu22
  • centos8, centos9 (actually opened out of the Stream version)
  • alpine3.15, alpine3.16, alpine3.17, alpine3.18
  • openwrt21，openwrt22，fedora37，fedora38，fedora39
  • rockylinux8，rockylinux9，oralce8，oracle9
  • oralce7，centos7 (CGroupV1 needs to be enabled in GRUB or it won't start.)
  • kali，archlinux
  • Note that the combination of lowercase letters + numbers or only lowercase letters, try it yourself, if the search is not the system will automatically exit the script
  • The version number can be with English decimal point, in order to adapt to the alpine version number has been supported.
  • If you can't open it, it may be that the hard disk is not big enough or it doesn't fit the host, try it by yourself.
  • The images currently in use are triple filtered and prioritized: self-hosted、official-hosted、opsmaru
  • A complete list of supported systems for self-compiling images: x86_64_fixed_images.txt and arm64_fixed_images.txt
TIP
The version number has ended the long-term maintenance of the general no longer have an official mirror, temporarily did not find the archive address of the historical mirror, if you find welcome to leave a message I will add support!
Generate only one NAT server ​
  • Generate only one NAT server, with customizable restrictions on all content.
Download script ​
Downloading the boot script is NOT REQUIRED, if you have used the command to install incus with one click, the corresponding boot script will be downloaded automatically, so you don't need to download the script again.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
Usage ​
. /buildone.sh name Cpu_num Memory_size Hard_disk_size SSH_port Extranet_start_port Extranet_stop_port Download_speed Upload_speed Whether_IPV6_is_enabled(Y or N) System(leave blank for debian11)
Memory size is calculated in MB, hard disk size is calculated in GB, download speed upload speed is calculated in Mbit, whether to enable IPV6 does not have to fill in Y or N, no this parameter can also be left blank default does not enable IPV6
If external start port\`\` and external stop port are both set to 0, then we don't do interval port mapping, only the basic SSH port is mapped, note that \`\`\`can't be null, and it needs to be set to 0 if it's not to be mapped.
Support custom server system, do not fill in the leave blank default use debian11, pay attention to the incoming parameters for the system name + version number
Example ​
Here is the information about the example chick that is being raised:
AttributeValue
server's Nametest
Username for SSH Loginroot
Password for SSH LoginRandomly generated
Number of CPU Cores1
Memory Size256MB
Disk Size2G
Range of Internal and External Port Mapping20002 to 20025
Upload Bandwidth500Mbit
Download Bandwidth500Mbit
Automatically Set External IPv6 AddressNo
Operating SystemDebian 11
./buildone.sh test 1 256 2 20001 20002 20025 500 500 N debian11
If you need to see the information, run
shell
cat ct_name_change_me
For example, the information for the query example is
shell
cat test
If you have already generated chicks through the above methods and still need to batch generate chicks, you can use a customized batch generation version of the script, but note that you should first delete the test chicks before batch generating chicks
Delete Test Chick ​
shell
incus stop test
 incus delete test
 rm -rf test
 rm -rf test_v6
diff --git a/assets/en_guide_incus_incus_precheck.md.6c589e43.js b/assets/en_guide_incus_incus_precheck.md.2a9177ef.js
similarity index 98%
rename from assets/en_guide_incus_incus_precheck.md.6c589e43.js
rename to assets/en_guide_incus_incus_precheck.md.2a9177ef.js
index c02d27a588..5736f31b8f 100644
--- a/assets/en_guide_incus_incus_precheck.md.6c589e43.js
+++ b/assets/en_guide_incus_incus_precheck.md.2a9177ef.js
@@ -1 +1 @@
-import{_ as e,v as t,b as n,R as o}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_precheck.md","filePath":"en/guide/incus/incus_precheck.md","lastUpdated":1747726389000}'),a={name:"en/guide/incus/incus_precheck.md"},r=o('
Preface ​
The following is the introduction of the non-customized part, the customized part has its own corresponding introduction, do not get confused!
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the incus module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/incus
Requirements ​
Hardware requirements.
  • System: Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • Virtualization: KVM, VMWARE recommended.
  • Memory: At least 512MB of RAM
  • Hard disk: hard disk (system disk) at least 10G
  • Network: Independent IPV4 address, IPV6 is optional, bandwidth can download scripts on the line, the network can connect to the Github raw page on the line
PS: If the hardware is very good and has a lot of resources, you can use PVE to batch open KVM virtualized VMs Jump
PS: If the hardware resources are even worse, virtualization is not supported, you can use the docker version, the adaption surface is wider Jump
Project Features ​
  • This set of script development using Ubuntu24 and Debian12, other long-term maintenance version should also be no problem, automatically switch to another storage type if btrfs not supported
  • Set up both TCP and UDP forwarding, in addition to SSH ports, other mapping intranet and extranet ports are the same.
  • Support for docker nested virtualization of open incus containers has been set up, and the default normal version and pure probe version use the debian11 system.
  • lxcfs has been set to be enabled by default, so that querying resources within a container uses the configured view rather than the host's view
  • Have blocked the container may be used to abuse the toolkit and IPV4 network TCP/UDP protocol ports ( 3389 8888 54321 65432 ), to prevent the container is used for scanning and blasting, and can be external process checking for problems automatically shut down
  • Has supported one-click configuration of IPV6 addresses for incus containers (provided that the mother hen has an IPV6 subnet, no IPV6 address is not configured), automatically adapted to the size of the subnet
  • Ensure that the disk you want to open is the default system disk (sda or sda1) and not the mounted disk (sdb and so on), if you are not sure, use fdisk -l and df to check.
  • See Other notes for details on mounting other disks.
  • One-click scripts support custom restrictions on all content, the normal version supports multiple runs of the batch generation does not overwrite the previously generated configuration
Detecting the environment ​
Use the subsequent script must execute this command to detect the hen whether it meets the requirements
Command:
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)
',15),s=[r];function i(c,d,h,l,u,p){return t(),n("div",null,s)}const b=e(a,[["render",i]]);export{f as __pageData,b as default};
+import{_ as e,v as t,b as n,R as o}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_precheck.md","filePath":"en/guide/incus/incus_precheck.md","lastUpdated":1747730955000}'),a={name:"en/guide/incus/incus_precheck.md"},r=o('
Preface ​
The following is the introduction of the non-customized part, the customized part has its own corresponding introduction, do not get confused!
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the incus module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/incus
Requirements ​
Hardware requirements.
  • System: Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • Virtualization: KVM, VMWARE recommended.
  • Memory: At least 512MB of RAM
  • Hard disk: hard disk (system disk) at least 10G
  • Network: Independent IPV4 address, IPV6 is optional, bandwidth can download scripts on the line, the network can connect to the Github raw page on the line
PS: If the hardware is very good and has a lot of resources, you can use PVE to batch open KVM virtualized VMs Jump
PS: If the hardware resources are even worse, virtualization is not supported, you can use the docker version, the adaption surface is wider Jump
Project Features ​
  • This set of script development using Ubuntu24 and Debian12, other long-term maintenance version should also be no problem, automatically switch to another storage type if btrfs not supported
  • Set up both TCP and UDP forwarding, in addition to SSH ports, other mapping intranet and extranet ports are the same.
  • Support for docker nested virtualization of open incus containers has been set up, and the default normal version and pure probe version use the debian11 system.
  • lxcfs has been set to be enabled by default, so that querying resources within a container uses the configured view rather than the host's view
  • Have blocked the container may be used to abuse the toolkit and IPV4 network TCP/UDP protocol ports ( 3389 8888 54321 65432 ), to prevent the container is used for scanning and blasting, and can be external process checking for problems automatically shut down
  • Has supported one-click configuration of IPV6 addresses for incus containers (provided that the mother hen has an IPV6 subnet, no IPV6 address is not configured), automatically adapted to the size of the subnet
  • Ensure that the disk you want to open is the default system disk (sda or sda1) and not the mounted disk (sdb and so on), if you are not sure, use fdisk -l and df to check.
  • See Other notes for details on mounting other disks.
  • One-click scripts support custom restrictions on all content, the normal version supports multiple runs of the batch generation does not overwrite the previously generated configuration
Detecting the environment ​
Use the subsequent script must execute this command to detect the hen whether it meets the requirements
Command:
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)
',15),s=[r];function i(c,d,h,l,u,p){return t(),n("div",null,s)}const b=e(a,[["render",i]]);export{f as __pageData,b as default};
diff --git a/assets/en_guide_incus_incus_precheck.md.6c589e43.lean.js b/assets/en_guide_incus_incus_precheck.md.2a9177ef.lean.js
similarity index 98%
rename from assets/en_guide_incus_incus_precheck.md.6c589e43.lean.js
rename to assets/en_guide_incus_incus_precheck.md.2a9177ef.lean.js
index c02d27a588..5736f31b8f 100644
--- a/assets/en_guide_incus_incus_precheck.md.6c589e43.lean.js
+++ b/assets/en_guide_incus_incus_precheck.md.2a9177ef.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as n,R as o}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_precheck.md","filePath":"en/guide/incus/incus_precheck.md","lastUpdated":1747726389000}'),a={name:"en/guide/incus/incus_precheck.md"},r=o('
Preface ​
The following is the introduction of the non-customized part, the customized part has its own corresponding introduction, do not get confused!
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the incus module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/incus
Requirements ​
Hardware requirements.
  • System: Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • Virtualization: KVM, VMWARE recommended.
  • Memory: At least 512MB of RAM
  • Hard disk: hard disk (system disk) at least 10G
  • Network: Independent IPV4 address, IPV6 is optional, bandwidth can download scripts on the line, the network can connect to the Github raw page on the line
PS: If the hardware is very good and has a lot of resources, you can use PVE to batch open KVM virtualized VMs Jump
PS: If the hardware resources are even worse, virtualization is not supported, you can use the docker version, the adaption surface is wider Jump
Project Features ​
  • This set of script development using Ubuntu24 and Debian12, other long-term maintenance version should also be no problem, automatically switch to another storage type if btrfs not supported
  • Set up both TCP and UDP forwarding, in addition to SSH ports, other mapping intranet and extranet ports are the same.
  • Support for docker nested virtualization of open incus containers has been set up, and the default normal version and pure probe version use the debian11 system.
  • lxcfs has been set to be enabled by default, so that querying resources within a container uses the configured view rather than the host's view
  • Have blocked the container may be used to abuse the toolkit and IPV4 network TCP/UDP protocol ports ( 3389 8888 54321 65432 ), to prevent the container is used for scanning and blasting, and can be external process checking for problems automatically shut down
  • Has supported one-click configuration of IPV6 addresses for incus containers (provided that the mother hen has an IPV6 subnet, no IPV6 address is not configured), automatically adapted to the size of the subnet
  • Ensure that the disk you want to open is the default system disk (sda or sda1) and not the mounted disk (sdb and so on), if you are not sure, use fdisk -l and df to check.
  • See Other notes for details on mounting other disks.
  • One-click scripts support custom restrictions on all content, the normal version supports multiple runs of the batch generation does not overwrite the previously generated configuration
Detecting the environment ​
Use the subsequent script must execute this command to detect the hen whether it meets the requirements
Command:
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)
',15),s=[r];function i(c,d,h,l,u,p){return t(),n("div",null,s)}const b=e(a,[["render",i]]);export{f as __pageData,b as default};
+import{_ as e,v as t,b as n,R as o}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_precheck.md","filePath":"en/guide/incus/incus_precheck.md","lastUpdated":1747730955000}'),a={name:"en/guide/incus/incus_precheck.md"},r=o('
Preface ​
The following is the introduction of the non-customized part, the customized part has its own corresponding introduction, do not get confused!
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the incus module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/incus
Requirements ​
Hardware requirements.
  • System: Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • Virtualization: KVM, VMWARE recommended.
  • Memory: At least 512MB of RAM
  • Hard disk: hard disk (system disk) at least 10G
  • Network: Independent IPV4 address, IPV6 is optional, bandwidth can download scripts on the line, the network can connect to the Github raw page on the line
PS: If the hardware is very good and has a lot of resources, you can use PVE to batch open KVM virtualized VMs Jump
PS: If the hardware resources are even worse, virtualization is not supported, you can use the docker version, the adaption surface is wider Jump
Project Features ​
  • This set of script development using Ubuntu24 and Debian12, other long-term maintenance version should also be no problem, automatically switch to another storage type if btrfs not supported
  • Set up both TCP and UDP forwarding, in addition to SSH ports, other mapping intranet and extranet ports are the same.
  • Support for docker nested virtualization of open incus containers has been set up, and the default normal version and pure probe version use the debian11 system.
  • lxcfs has been set to be enabled by default, so that querying resources within a container uses the configured view rather than the host's view
  • Have blocked the container may be used to abuse the toolkit and IPV4 network TCP/UDP protocol ports ( 3389 8888 54321 65432 ), to prevent the container is used for scanning and blasting, and can be external process checking for problems automatically shut down
  • Has supported one-click configuration of IPV6 addresses for incus containers (provided that the mother hen has an IPV6 subnet, no IPV6 address is not configured), automatically adapted to the size of the subnet
  • Ensure that the disk you want to open is the default system disk (sda or sda1) and not the mounted disk (sdb and so on), if you are not sure, use fdisk -l and df to check.
  • See Other notes for details on mounting other disks.
  • One-click scripts support custom restrictions on all content, the normal version supports multiple runs of the batch generation does not overwrite the previously generated configuration
Detecting the environment ​
Use the subsequent script must execute this command to detect the hen whether it meets the requirements
Command:
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)
',15),s=[r];function i(c,d,h,l,u,p){return t(),n("div",null,s)}const b=e(a,[["render",i]]);export{f as __pageData,b as default};
diff --git a/assets/en_guide_incus_incus_qa.md.79b297e9.js b/assets/en_guide_incus_incus_qa.md.1773ea44.js
similarity index 97%
rename from assets/en_guide_incus_incus_qa.md.79b297e9.js
rename to assets/en_guide_incus_incus_qa.md.1773ea44.js
index cade2b9da9..163b81b9e2 100644
--- a/assets/en_guide_incus_incus_qa.md.79b297e9.js
+++ b/assets/en_guide_incus_incus_qa.md.1773ea44.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a,R as s}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_qa.md","filePath":"en/guide/incus/incus_qa.md","lastUpdated":1747726389000}'),o={name:"en/guide/incus/incus_qa.md"},n=s('
Solve the puzzle ​
What to do if you open centos7 and find that CGroupV1 is not supported? ​
Enable CGroup V1: To enable CGroup V1 on an Ubuntu system, you need to edit the kernel boot parameters.
Please note that before changing kernel boot parameters, make sure to backup important data and settings to prevent unexpected problems.
Edit the ```/etc/default/grubfile and addsystemd.unified_cgroup_hierarchy=0to the end of the parameters inGRUB_CMDLINE_LINUX_DEFAULT``, just like:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"
Save the file and run the following command to update the GRUB boot.
bash
sudo update-grub
Reboot the system for the changes to take effect
If the above changes still do not support the opening of centos7, try using a different host system.
Currently verified VPS vendors that can open containers with separate IPV6 addresses. ​
kuroit Phoenix, USA regular
datalix German AMD Promotions
',13),r=[n];function p(i,d,l,c,h,u){return t(),a("div",null,r)}const _=e(o,[["render",p]]);export{m as __pageData,_ as default};
+import{_ as e,v as t,b as a,R as s}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_qa.md","filePath":"en/guide/incus/incus_qa.md","lastUpdated":1747730955000}'),o={name:"en/guide/incus/incus_qa.md"},n=s('
Solve the puzzle ​
What to do if you open centos7 and find that CGroupV1 is not supported? ​
Enable CGroup V1: To enable CGroup V1 on an Ubuntu system, you need to edit the kernel boot parameters.
Please note that before changing kernel boot parameters, make sure to backup important data and settings to prevent unexpected problems.
Edit the ```/etc/default/grubfile and addsystemd.unified_cgroup_hierarchy=0to the end of the parameters inGRUB_CMDLINE_LINUX_DEFAULT``, just like:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"
Save the file and run the following command to update the GRUB boot.
bash
sudo update-grub
Reboot the system for the changes to take effect
If the above changes still do not support the opening of centos7, try using a different host system.
Currently verified VPS vendors that can open containers with separate IPV6 addresses. ​
kuroit Phoenix, USA regular
datalix German AMD Promotions
',13),r=[n];function p(i,d,l,c,h,u){return t(),a("div",null,r)}const _=e(o,[["render",p]]);export{m as __pageData,_ as default};
diff --git a/assets/en_guide_incus_incus_qa.md.79b297e9.lean.js b/assets/en_guide_incus_incus_qa.md.1773ea44.lean.js
similarity index 97%
rename from assets/en_guide_incus_incus_qa.md.79b297e9.lean.js
rename to assets/en_guide_incus_incus_qa.md.1773ea44.lean.js
index cade2b9da9..163b81b9e2 100644
--- a/assets/en_guide_incus_incus_qa.md.79b297e9.lean.js
+++ b/assets/en_guide_incus_incus_qa.md.1773ea44.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a,R as s}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_qa.md","filePath":"en/guide/incus/incus_qa.md","lastUpdated":1747726389000}'),o={name:"en/guide/incus/incus_qa.md"},n=s('
Solve the puzzle ​
What to do if you open centos7 and find that CGroupV1 is not supported? ​
Enable CGroup V1: To enable CGroup V1 on an Ubuntu system, you need to edit the kernel boot parameters.
Please note that before changing kernel boot parameters, make sure to backup important data and settings to prevent unexpected problems.
Edit the ```/etc/default/grubfile and addsystemd.unified_cgroup_hierarchy=0to the end of the parameters inGRUB_CMDLINE_LINUX_DEFAULT``, just like:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"
Save the file and run the following command to update the GRUB boot.
bash
sudo update-grub
Reboot the system for the changes to take effect
If the above changes still do not support the opening of centos7, try using a different host system.
Currently verified VPS vendors that can open containers with separate IPV6 addresses. ​
kuroit Phoenix, USA regular
datalix German AMD Promotions
',13),r=[n];function p(i,d,l,c,h,u){return t(),a("div",null,r)}const _=e(o,[["render",p]]);export{m as __pageData,_ as default};
+import{_ as e,v as t,b as a,R as s}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_qa.md","filePath":"en/guide/incus/incus_qa.md","lastUpdated":1747730955000}'),o={name:"en/guide/incus/incus_qa.md"},n=s('
Solve the puzzle ​
What to do if you open centos7 and find that CGroupV1 is not supported? ​
Enable CGroup V1: To enable CGroup V1 on an Ubuntu system, you need to edit the kernel boot parameters.
Please note that before changing kernel boot parameters, make sure to backup important data and settings to prevent unexpected problems.
Edit the ```/etc/default/grubfile and addsystemd.unified_cgroup_hierarchy=0to the end of the parameters inGRUB_CMDLINE_LINUX_DEFAULT``, just like:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"
Save the file and run the following command to update the GRUB boot.
bash
sudo update-grub
Reboot the system for the changes to take effect
If the above changes still do not support the opening of centos7, try using a different host system.
Currently verified VPS vendors that can open containers with separate IPV6 addresses. ​
kuroit Phoenix, USA regular
datalix German AMD Promotions
',13),r=[n];function p(i,d,l,c,h,u){return t(),a("div",null,r)}const _=e(o,[["render",p]]);export{m as __pageData,_ as default};
diff --git a/assets/en_guide_incus_incus_thanks.md.f575d7ec.js b/assets/en_guide_incus_incus_thanks.md.9f2285ce.js
similarity index 97%
rename from assets/en_guide_incus_incus_thanks.md.f575d7ec.js
rename to assets/en_guide_incus_incus_thanks.md.9f2285ce.js
index 9e24e6615b..c0ac48916e 100644
--- a/assets/en_guide_incus_incus_thanks.md.f575d7ec.js
+++ b/assets/en_guide_incus_incus_thanks.md.9f2285ce.js
@@ -1 +1 @@
-import{_ as t,v as e,b as r,R as n}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/incus/incus_thanks.md","filePath":"en/guide/incus/incus_thanks.md","lastUpdated":1747726389000}'),s={name:"en/guide/incus/incus_thanks.md"},a=n('
Acknowledgements ​
https://github.com/lxc/lxd
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
https://github.com/SuperManito/LinuxMirrors
https://github.com/zabbly/incus
',10),o=[a];function i(c,p,h,l,u,d){return e(),r("div",null,o)}const b=t(s,[["render",i]]);export{f as __pageData,b as default};
+import{_ as t,v as e,b as r,R as n}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/incus/incus_thanks.md","filePath":"en/guide/incus/incus_thanks.md","lastUpdated":1747730955000}'),s={name:"en/guide/incus/incus_thanks.md"},a=n('
Acknowledgements ​
https://github.com/lxc/lxd
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
https://github.com/SuperManito/LinuxMirrors
https://github.com/zabbly/incus
',10),o=[a];function i(c,p,h,l,u,d){return e(),r("div",null,o)}const b=t(s,[["render",i]]);export{f as __pageData,b as default};
diff --git a/assets/en_guide_incus_incus_thanks.md.f575d7ec.lean.js b/assets/en_guide_incus_incus_thanks.md.9f2285ce.lean.js
similarity index 97%
rename from assets/en_guide_incus_incus_thanks.md.f575d7ec.lean.js
rename to assets/en_guide_incus_incus_thanks.md.9f2285ce.lean.js
index 9e24e6615b..c0ac48916e 100644
--- a/assets/en_guide_incus_incus_thanks.md.f575d7ec.lean.js
+++ b/assets/en_guide_incus_incus_thanks.md.9f2285ce.lean.js
@@ -1 +1 @@
-import{_ as t,v as e,b as r,R as n}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/incus/incus_thanks.md","filePath":"en/guide/incus/incus_thanks.md","lastUpdated":1747726389000}'),s={name:"en/guide/incus/incus_thanks.md"},a=n('
Acknowledgements ​
https://github.com/lxc/lxd
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
https://github.com/SuperManito/LinuxMirrors
https://github.com/zabbly/incus
',10),o=[a];function i(c,p,h,l,u,d){return e(),r("div",null,o)}const b=t(s,[["render",i]]);export{f as __pageData,b as default};
+import{_ as t,v as e,b as r,R as n}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/incus/incus_thanks.md","filePath":"en/guide/incus/incus_thanks.md","lastUpdated":1747730955000}'),s={name:"en/guide/incus/incus_thanks.md"},a=n('
Acknowledgements ​
https://github.com/lxc/lxd
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
https://github.com/SuperManito/LinuxMirrors
https://github.com/zabbly/incus
',10),o=[a];function i(c,p,h,l,u,d){return e(),r("div",null,o)}const b=t(s,[["render",i]]);export{f as __pageData,b as default};
diff --git a/assets/en_guide_incus_incus_windows.md.bb2cdc9d.js b/assets/en_guide_incus_incus_windows.md.c1838523.js
similarity index 99%
rename from assets/en_guide_incus_incus_windows.md.bb2cdc9d.js
rename to assets/en_guide_incus_incus_windows.md.c1838523.js
index c8dfcca6cf..55f477a1b3 100644
--- a/assets/en_guide_incus_incus_windows.md.bb2cdc9d.js
+++ b/assets/en_guide_incus_incus_windows.md.c1838523.js
@@ -1,4 +1,4 @@
-import{_ as s,v as n,b as a,R as l}from"./chunks/framework.70afa331.js";const o="/assets/win1.7d3fc058.png",F=JSON.parse('{"title":"Running Windows Virtual Machines in Incus","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/incus/incus_windows.md","filePath":"en/guide/incus/incus_windows.md","lastUpdated":1747726389000}'),p={name:"en/guide/incus/incus_windows.md"},e=l(`
Running Windows Virtual Machines in Incus ​
Verify the Incus Driver ​
Ensure that incus info output contains driver: qemu, otherwise you cannot create VMs:
shell
incus info | grep -i driver:
+import{_ as s,v as n,b as a,R as l}from"./chunks/framework.70afa331.js";const o="/assets/win1.7d3fc058.png",F=JSON.parse('{"title":"Running Windows Virtual Machines in Incus","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/incus/incus_windows.md","filePath":"en/guide/incus/incus_windows.md","lastUpdated":1747730955000}'),p={name:"en/guide/incus/incus_windows.md"},e=l(`
Running Windows Virtual Machines in Incus ​
Verify the Incus Driver ​
Ensure that incus info output contains driver: qemu, otherwise you cannot create VMs:
shell
incus info | grep -i driver:
 # Correct example:
 # driver: qemu
If it shows driver: lxc, adjust the setting in /etc/incus/daemon.conf to driver = qemu and restart the Incus service.
Prepare the Environment and Patch the Image ​
Execute the following commands in sequence in the /root directory:
shell
apt update
 apt install -y snapd libguestfs-tools wimtools rsync libhivex-bin libwin-hivex-perl genisoimage || apt install -y mkisofs
diff --git a/assets/en_guide_incus_incus_windows.md.bb2cdc9d.lean.js b/assets/en_guide_incus_incus_windows.md.c1838523.lean.js
similarity index 99%
rename from assets/en_guide_incus_incus_windows.md.bb2cdc9d.lean.js
rename to assets/en_guide_incus_incus_windows.md.c1838523.lean.js
index c8dfcca6cf..55f477a1b3 100644
--- a/assets/en_guide_incus_incus_windows.md.bb2cdc9d.lean.js
+++ b/assets/en_guide_incus_incus_windows.md.c1838523.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as n,b as a,R as l}from"./chunks/framework.70afa331.js";const o="/assets/win1.7d3fc058.png",F=JSON.parse('{"title":"Running Windows Virtual Machines in Incus","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/incus/incus_windows.md","filePath":"en/guide/incus/incus_windows.md","lastUpdated":1747726389000}'),p={name:"en/guide/incus/incus_windows.md"},e=l(`
Running Windows Virtual Machines in Incus ​
Verify the Incus Driver ​
Ensure that incus info output contains driver: qemu, otherwise you cannot create VMs:
shell
incus info | grep -i driver:
+import{_ as s,v as n,b as a,R as l}from"./chunks/framework.70afa331.js";const o="/assets/win1.7d3fc058.png",F=JSON.parse('{"title":"Running Windows Virtual Machines in Incus","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/incus/incus_windows.md","filePath":"en/guide/incus/incus_windows.md","lastUpdated":1747730955000}'),p={name:"en/guide/incus/incus_windows.md"},e=l(`
Running Windows Virtual Machines in Incus ​
Verify the Incus Driver ​
Ensure that incus info output contains driver: qemu, otherwise you cannot create VMs:
shell
incus info | grep -i driver:
 # Correct example:
 # driver: qemu
If it shows driver: lxc, adjust the setting in /etc/incus/daemon.conf to driver = qemu and restart the Incus service.
Prepare the Environment and Patch the Image ​
Execute the following commands in sequence in the /root directory:
shell
apt update
 apt install -y snapd libguestfs-tools wimtools rsync libhivex-bin libwin-hivex-perl genisoimage || apt install -y mkisofs
diff --git a/assets/en_guide_lxd_lxd_custom.md.afca2a12.js b/assets/en_guide_lxd_lxd_custom.md.e332d18b.js
similarity index 99%
rename from assets/en_guide_lxd_lxd_custom.md.afca2a12.js
rename to assets/en_guide_lxd_lxd_custom.md.e332d18b.js
index d41ff9a95a..294871e91e 100644
--- a/assets/en_guide_lxd_lxd_custom.md.afca2a12.js
+++ b/assets/en_guide_lxd_lxd_custom.md.e332d18b.js
@@ -1,4 +1,4 @@
-import{_ as e,v as s,b as t,R as a}from"./chunks/framework.70afa331.js";const n="/assets/lxd1.78537e30.png",o="/assets/lxd2.da10b5ec.png",l="/assets/lxd3.917f56de.png",p="/assets/lxd4.83a1a121.png",r="/assets/lxd5.4ebc1444.png",i="/assets/lxd6.572825bf.png",c="/assets/lxd7.b73982c7.png",d="/assets/lxd8.9fcc21e5.png",h="/assets/lxd9.00250a32.png",u="/assets/lxd10.a25a745c.png",y="/assets/lxd11.b83f953c.png",m="/assets/lxd12.0da335dd.png",C="/assets/lxd13.308fe0de.png",g="/assets/lxd14.8dbfdcd6.png",f="/assets/lxd15.70114933.png",b="/assets/lxd16.a595fa36.png",A="/assets/lxd17.d7ea65d8.png",v="/assets/lxd18.d6225daa.png",D="/assets/lxd19.69674669.png",k="/assets/lxd20.179fc6e1.png",w="/assets/lxd21.48123d6a.png",F="/assets/lxd22.4386597e.png",P="/assets/lxd23.c26427e3.png",W=JSON.parse('{"title":"Custom","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_custom.md","filePath":"en/guide/lxd/lxd_custom.md","lastUpdated":1747726389000}'),_={name:"en/guide/lxd/lxd_custom.md"},x=a(`
Custom ​
Attach free IPV6 address segments to host machines ​
Some machines don't have an IPV6 /64 subnet on the machine itself, here is a method given to attach an IPV6 subnet for free.
Here is a solution using the 6in4 method for a host machine that doesn't have an IPV6 address on its own.
TIP
The operations on this page must be performed on the original system, and ensure that no other scripts from this project are installed(Except for PVE, which needs to be installed first), as this may lead to environment conflicts.
Here are the platforms that are currently running in 2023 that offer IPV6 subnets for free.
Supported PlatformsCorresponding Required Installation PackagesProtocolsNumber of Channels/Subnets
tunnelbroker.netifupdown OR ifupdown2v4tunnel OR sit3✖/64 OR 5✖/64
tunnelbroker.chifupdown OR ifupdown2v4tunnel OR sit3✖/64
ip4market.ruifupdown OR ifupdown2v4tunnel OR sit1✖/64
netassist.uaifupdown OR ifupdown2v4tunnel OR sit1✖/64
https://github.com/oneclickvirt/6in4ifupdown2sit、gre、ipipcustom
The free platform only solves the problem that IPV6 is not available, it does not provide premium IPV6 bandwidth.
If you need high quality bandwidth, please build your own tunnel. When both ifupdown and ifupdown2 are available, try ifupdown first to see if it can be installed successfully, otherwise install ifupdown2.
After the installation is complete, select which package is installed behind to convert the format.
Initial environment modifications ​
Execute
touch /etc/cloud/cloud-init.disabled
Turn off the automated overwrite of cloud-init first, and then to see what the local machine is using to manage the network, run
systemctl is-active systemd-networkd
and
systemctl is-active networking
See which case this falls into, if it's the former active and the latter inactive, you need to reinstall/DD a system that isn't configured this way, or switch the local machine to use ifupdown/ifupdown2 to manage network execution
# Judge for yourself whether you need to disable the original network management or not
+import{_ as e,v as s,b as t,R as a}from"./chunks/framework.70afa331.js";const n="/assets/lxd1.78537e30.png",o="/assets/lxd2.da10b5ec.png",l="/assets/lxd3.917f56de.png",p="/assets/lxd4.83a1a121.png",r="/assets/lxd5.4ebc1444.png",i="/assets/lxd6.572825bf.png",c="/assets/lxd7.b73982c7.png",d="/assets/lxd8.9fcc21e5.png",h="/assets/lxd9.00250a32.png",u="/assets/lxd10.a25a745c.png",y="/assets/lxd11.b83f953c.png",m="/assets/lxd12.0da335dd.png",C="/assets/lxd13.308fe0de.png",g="/assets/lxd14.8dbfdcd6.png",f="/assets/lxd15.70114933.png",b="/assets/lxd16.a595fa36.png",A="/assets/lxd17.d7ea65d8.png",v="/assets/lxd18.d6225daa.png",D="/assets/lxd19.69674669.png",k="/assets/lxd20.179fc6e1.png",w="/assets/lxd21.48123d6a.png",F="/assets/lxd22.4386597e.png",P="/assets/lxd23.c26427e3.png",W=JSON.parse('{"title":"Custom","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_custom.md","filePath":"en/guide/lxd/lxd_custom.md","lastUpdated":1747730955000}'),_={name:"en/guide/lxd/lxd_custom.md"},x=a(`
Custom ​
Attach free IPV6 address segments to host machines ​
Some machines don't have an IPV6 /64 subnet on the machine itself, here is a method given to attach an IPV6 subnet for free.
Here is a solution using the 6in4 method for a host machine that doesn't have an IPV6 address on its own.
TIP
The operations on this page must be performed on the original system, and ensure that no other scripts from this project are installed(Except for PVE, which needs to be installed first), as this may lead to environment conflicts.
Here are the platforms that are currently running in 2023 that offer IPV6 subnets for free.
Supported PlatformsCorresponding Required Installation PackagesProtocolsNumber of Channels/Subnets
tunnelbroker.netifupdown OR ifupdown2v4tunnel OR sit3✖/64 OR 5✖/64
tunnelbroker.chifupdown OR ifupdown2v4tunnel OR sit3✖/64
ip4market.ruifupdown OR ifupdown2v4tunnel OR sit1✖/64
netassist.uaifupdown OR ifupdown2v4tunnel OR sit1✖/64
https://github.com/oneclickvirt/6in4ifupdown2sit、gre、ipipcustom
The free platform only solves the problem that IPV6 is not available, it does not provide premium IPV6 bandwidth.
If you need high quality bandwidth, please build your own tunnel. When both ifupdown and ifupdown2 are available, try ifupdown first to see if it can be installed successfully, otherwise install ifupdown2.
After the installation is complete, select which package is installed behind to convert the format.
Initial environment modifications ​
Execute
touch /etc/cloud/cloud-init.disabled
Turn off the automated overwrite of cloud-init first, and then to see what the local machine is using to manage the network, run
systemctl is-active systemd-networkd
and
systemctl is-active networking
See which case this falls into, if it's the former active and the latter inactive, you need to reinstall/DD a system that isn't configured this way, or switch the local machine to use ifupdown/ifupdown2 to manage network execution
# Judge for yourself whether you need to disable the original network management or not
 # systemctl stop systemd-networkd
 # systemctl disable systemd-networkd
 # systemctl stop systemd-networkd.socket
diff --git a/assets/en_guide_lxd_lxd_custom.md.afca2a12.lean.js b/assets/en_guide_lxd_lxd_custom.md.e332d18b.lean.js
similarity index 99%
rename from assets/en_guide_lxd_lxd_custom.md.afca2a12.lean.js
rename to assets/en_guide_lxd_lxd_custom.md.e332d18b.lean.js
index d41ff9a95a..294871e91e 100644
--- a/assets/en_guide_lxd_lxd_custom.md.afca2a12.lean.js
+++ b/assets/en_guide_lxd_lxd_custom.md.e332d18b.lean.js
@@ -1,4 +1,4 @@
-import{_ as e,v as s,b as t,R as a}from"./chunks/framework.70afa331.js";const n="/assets/lxd1.78537e30.png",o="/assets/lxd2.da10b5ec.png",l="/assets/lxd3.917f56de.png",p="/assets/lxd4.83a1a121.png",r="/assets/lxd5.4ebc1444.png",i="/assets/lxd6.572825bf.png",c="/assets/lxd7.b73982c7.png",d="/assets/lxd8.9fcc21e5.png",h="/assets/lxd9.00250a32.png",u="/assets/lxd10.a25a745c.png",y="/assets/lxd11.b83f953c.png",m="/assets/lxd12.0da335dd.png",C="/assets/lxd13.308fe0de.png",g="/assets/lxd14.8dbfdcd6.png",f="/assets/lxd15.70114933.png",b="/assets/lxd16.a595fa36.png",A="/assets/lxd17.d7ea65d8.png",v="/assets/lxd18.d6225daa.png",D="/assets/lxd19.69674669.png",k="/assets/lxd20.179fc6e1.png",w="/assets/lxd21.48123d6a.png",F="/assets/lxd22.4386597e.png",P="/assets/lxd23.c26427e3.png",W=JSON.parse('{"title":"Custom","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_custom.md","filePath":"en/guide/lxd/lxd_custom.md","lastUpdated":1747726389000}'),_={name:"en/guide/lxd/lxd_custom.md"},x=a(`
Custom ​
Attach free IPV6 address segments to host machines ​
Some machines don't have an IPV6 /64 subnet on the machine itself, here is a method given to attach an IPV6 subnet for free.
Here is a solution using the 6in4 method for a host machine that doesn't have an IPV6 address on its own.
TIP
The operations on this page must be performed on the original system, and ensure that no other scripts from this project are installed(Except for PVE, which needs to be installed first), as this may lead to environment conflicts.
Here are the platforms that are currently running in 2023 that offer IPV6 subnets for free.
Supported PlatformsCorresponding Required Installation PackagesProtocolsNumber of Channels/Subnets
tunnelbroker.netifupdown OR ifupdown2v4tunnel OR sit3✖/64 OR 5✖/64
tunnelbroker.chifupdown OR ifupdown2v4tunnel OR sit3✖/64
ip4market.ruifupdown OR ifupdown2v4tunnel OR sit1✖/64
netassist.uaifupdown OR ifupdown2v4tunnel OR sit1✖/64
https://github.com/oneclickvirt/6in4ifupdown2sit、gre、ipipcustom
The free platform only solves the problem that IPV6 is not available, it does not provide premium IPV6 bandwidth.
If you need high quality bandwidth, please build your own tunnel. When both ifupdown and ifupdown2 are available, try ifupdown first to see if it can be installed successfully, otherwise install ifupdown2.
After the installation is complete, select which package is installed behind to convert the format.
Initial environment modifications ​
Execute
touch /etc/cloud/cloud-init.disabled
Turn off the automated overwrite of cloud-init first, and then to see what the local machine is using to manage the network, run
systemctl is-active systemd-networkd
and
systemctl is-active networking
See which case this falls into, if it's the former active and the latter inactive, you need to reinstall/DD a system that isn't configured this way, or switch the local machine to use ifupdown/ifupdown2 to manage network execution
# Judge for yourself whether you need to disable the original network management or not
+import{_ as e,v as s,b as t,R as a}from"./chunks/framework.70afa331.js";const n="/assets/lxd1.78537e30.png",o="/assets/lxd2.da10b5ec.png",l="/assets/lxd3.917f56de.png",p="/assets/lxd4.83a1a121.png",r="/assets/lxd5.4ebc1444.png",i="/assets/lxd6.572825bf.png",c="/assets/lxd7.b73982c7.png",d="/assets/lxd8.9fcc21e5.png",h="/assets/lxd9.00250a32.png",u="/assets/lxd10.a25a745c.png",y="/assets/lxd11.b83f953c.png",m="/assets/lxd12.0da335dd.png",C="/assets/lxd13.308fe0de.png",g="/assets/lxd14.8dbfdcd6.png",f="/assets/lxd15.70114933.png",b="/assets/lxd16.a595fa36.png",A="/assets/lxd17.d7ea65d8.png",v="/assets/lxd18.d6225daa.png",D="/assets/lxd19.69674669.png",k="/assets/lxd20.179fc6e1.png",w="/assets/lxd21.48123d6a.png",F="/assets/lxd22.4386597e.png",P="/assets/lxd23.c26427e3.png",W=JSON.parse('{"title":"Custom","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_custom.md","filePath":"en/guide/lxd/lxd_custom.md","lastUpdated":1747730955000}'),_={name:"en/guide/lxd/lxd_custom.md"},x=a(`
Custom ​
Attach free IPV6 address segments to host machines ​
Some machines don't have an IPV6 /64 subnet on the machine itself, here is a method given to attach an IPV6 subnet for free.
Here is a solution using the 6in4 method for a host machine that doesn't have an IPV6 address on its own.
TIP
The operations on this page must be performed on the original system, and ensure that no other scripts from this project are installed(Except for PVE, which needs to be installed first), as this may lead to environment conflicts.
Here are the platforms that are currently running in 2023 that offer IPV6 subnets for free.
Supported PlatformsCorresponding Required Installation PackagesProtocolsNumber of Channels/Subnets
tunnelbroker.netifupdown OR ifupdown2v4tunnel OR sit3✖/64 OR 5✖/64
tunnelbroker.chifupdown OR ifupdown2v4tunnel OR sit3✖/64
ip4market.ruifupdown OR ifupdown2v4tunnel OR sit1✖/64
netassist.uaifupdown OR ifupdown2v4tunnel OR sit1✖/64
https://github.com/oneclickvirt/6in4ifupdown2sit、gre、ipipcustom
The free platform only solves the problem that IPV6 is not available, it does not provide premium IPV6 bandwidth.
If you need high quality bandwidth, please build your own tunnel. When both ifupdown and ifupdown2 are available, try ifupdown first to see if it can be installed successfully, otherwise install ifupdown2.
After the installation is complete, select which package is installed behind to convert the format.
Initial environment modifications ​
Execute
touch /etc/cloud/cloud-init.disabled
Turn off the automated overwrite of cloud-init first, and then to see what the local machine is using to manage the network, run
systemctl is-active systemd-networkd
and
systemctl is-active networking
See which case this falls into, if it's the former active and the latter inactive, you need to reinstall/DD a system that isn't configured this way, or switch the local machine to use ifupdown/ifupdown2 to manage network execution
# Judge for yourself whether you need to disable the original network management or not
 # systemctl stop systemd-networkd
 # systemctl disable systemd-networkd
 # systemctl stop systemd-networkd.socket
diff --git a/assets/en_guide_lxd_lxd_extra_config.md.ad5f5548.js b/assets/en_guide_lxd_lxd_extra_config.md.4fcf6710.js
similarity index 99%
rename from assets/en_guide_lxd_lxd_extra_config.md.ad5f5548.js
rename to assets/en_guide_lxd_lxd_extra_config.md.4fcf6710.js
index 61a39e1234..56e1184986 100644
--- a/assets/en_guide_lxd_lxd_extra_config.md.ad5f5548.js
+++ b/assets/en_guide_lxd_lxd_extra_config.md.4fcf6710.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"Custom Configuration","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_extra_config.md","filePath":"en/guide/lxd/lxd_extra_config.md","lastUpdated":1747726389000}'),l={name:"en/guide/lxd/lxd_extra_config.md"},e=o(`
Custom Configuration ​
TIP
The following configurations may increase the load on the server. Only install them if necessary.
Automatic IPV6 Address Configuration ​
  • (Optional, not required if not using)
  • This script is only suitable for servers that have an IPV6 subnet with a prefix, and the server has bound the first IP of the subnet as its IPV6 address or IPV6 gateway.
  • Automatically configures IPV6 addresses for LXC containers created with LXD.
  • Integrated into buildone.sh and can be controlled by variables without needing to be downloaded beforehand. You don't need to manually use this script; when using buildone.sh, configure with variable Y to enable it.
Download Script
Command:
bash
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
Automatically configure IPV6 mapped addresses for containers
bash
bash build_ipv6_network.sh Container_Name(change_me)
A message is printed when the mapping is complete (Default mapping without iptables)
Example (automatically configure the test container with an IPV6 address, a test_v6 file is written when the configuration is complete)
bash
bash build_ipv6_network.sh test
PS: Add ipv6 processing can choose whether to use ip6tables for mapping, the default is not to use ip6tables for mapping but to add new network devices for mapping.
Use ip6tables for mapping
bash
bash build_ipv6_network.sh Container_name Y
If ip6tables is used for mapping, remove all IPV6 mapped rules available:
bash
ip6tables -t nat -F PREROUTING
+import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"Custom Configuration","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_extra_config.md","filePath":"en/guide/lxd/lxd_extra_config.md","lastUpdated":1747730955000}'),l={name:"en/guide/lxd/lxd_extra_config.md"},e=o(`
Custom Configuration ​
TIP
The following configurations may increase the load on the server. Only install them if necessary.
Automatic IPV6 Address Configuration ​
  • (Optional, not required if not using)
  • This script is only suitable for servers that have an IPV6 subnet with a prefix, and the server has bound the first IP of the subnet as its IPV6 address or IPV6 gateway.
  • Automatically configures IPV6 addresses for LXC containers created with LXD.
  • Integrated into buildone.sh and can be controlled by variables without needing to be downloaded beforehand. You don't need to manually use this script; when using buildone.sh, configure with variable Y to enable it.
Download Script
Command:
bash
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
Automatically configure IPV6 mapped addresses for containers
bash
bash build_ipv6_network.sh Container_Name(change_me)
A message is printed when the mapping is complete (Default mapping without iptables)
Example (automatically configure the test container with an IPV6 address, a test_v6 file is written when the configuration is complete)
bash
bash build_ipv6_network.sh test
PS: Add ipv6 processing can choose whether to use ip6tables for mapping, the default is not to use ip6tables for mapping but to add new network devices for mapping.
Use ip6tables for mapping
bash
bash build_ipv6_network.sh Container_name Y
If ip6tables is used for mapping, remove all IPV6 mapped rules available:
bash
ip6tables -t nat -F PREROUTING
 ip6tables-legacy -t nat -F PREROUTING
 ip6tables-save > /etc/iptables/rules.v6
 netfilter-persistent save
diff --git a/assets/en_guide_lxd_lxd_extra_config.md.ad5f5548.lean.js b/assets/en_guide_lxd_lxd_extra_config.md.4fcf6710.lean.js
similarity index 99%
rename from assets/en_guide_lxd_lxd_extra_config.md.ad5f5548.lean.js
rename to assets/en_guide_lxd_lxd_extra_config.md.4fcf6710.lean.js
index 61a39e1234..56e1184986 100644
--- a/assets/en_guide_lxd_lxd_extra_config.md.ad5f5548.lean.js
+++ b/assets/en_guide_lxd_lxd_extra_config.md.4fcf6710.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"Custom Configuration","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_extra_config.md","filePath":"en/guide/lxd/lxd_extra_config.md","lastUpdated":1747726389000}'),l={name:"en/guide/lxd/lxd_extra_config.md"},e=o(`
Custom Configuration ​
TIP
The following configurations may increase the load on the server. Only install them if necessary.
Automatic IPV6 Address Configuration ​
  • (Optional, not required if not using)
  • This script is only suitable for servers that have an IPV6 subnet with a prefix, and the server has bound the first IP of the subnet as its IPV6 address or IPV6 gateway.
  • Automatically configures IPV6 addresses for LXC containers created with LXD.
  • Integrated into buildone.sh and can be controlled by variables without needing to be downloaded beforehand. You don't need to manually use this script; when using buildone.sh, configure with variable Y to enable it.
Download Script
Command:
bash
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
Automatically configure IPV6 mapped addresses for containers
bash
bash build_ipv6_network.sh Container_Name(change_me)
A message is printed when the mapping is complete (Default mapping without iptables)
Example (automatically configure the test container with an IPV6 address, a test_v6 file is written when the configuration is complete)
bash
bash build_ipv6_network.sh test
PS: Add ipv6 processing can choose whether to use ip6tables for mapping, the default is not to use ip6tables for mapping but to add new network devices for mapping.
Use ip6tables for mapping
bash
bash build_ipv6_network.sh Container_name Y
If ip6tables is used for mapping, remove all IPV6 mapped rules available:
bash
ip6tables -t nat -F PREROUTING
+import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"Custom Configuration","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_extra_config.md","filePath":"en/guide/lxd/lxd_extra_config.md","lastUpdated":1747730955000}'),l={name:"en/guide/lxd/lxd_extra_config.md"},e=o(`
Custom Configuration ​
TIP
The following configurations may increase the load on the server. Only install them if necessary.
Automatic IPV6 Address Configuration ​
  • (Optional, not required if not using)
  • This script is only suitable for servers that have an IPV6 subnet with a prefix, and the server has bound the first IP of the subnet as its IPV6 address or IPV6 gateway.
  • Automatically configures IPV6 addresses for LXC containers created with LXD.
  • Integrated into buildone.sh and can be controlled by variables without needing to be downloaded beforehand. You don't need to manually use this script; when using buildone.sh, configure with variable Y to enable it.
Download Script
Command:
bash
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
Automatically configure IPV6 mapped addresses for containers
bash
bash build_ipv6_network.sh Container_Name(change_me)
A message is printed when the mapping is complete (Default mapping without iptables)
Example (automatically configure the test container with an IPV6 address, a test_v6 file is written when the configuration is complete)
bash
bash build_ipv6_network.sh test
PS: Add ipv6 processing can choose whether to use ip6tables for mapping, the default is not to use ip6tables for mapping but to add new network devices for mapping.
Use ip6tables for mapping
bash
bash build_ipv6_network.sh Container_name Y
If ip6tables is used for mapping, remove all IPV6 mapped rules available:
bash
ip6tables -t nat -F PREROUTING
 ip6tables-legacy -t nat -F PREROUTING
 ip6tables-save > /etc/iptables/rules.v6
 netfilter-persistent save
diff --git a/assets/en_guide_lxd_lxd_install.md.219e45e1.js b/assets/en_guide_lxd_lxd_install.md.2b676884.js
similarity index 99%
rename from assets/en_guide_lxd_lxd_install.md.219e45e1.js
rename to assets/en_guide_lxd_lxd_install.md.2b676884.js
index 990b9c9417..65c0b50dfd 100644
--- a/assets/en_guide_lxd_lxd_install.md.219e45e1.js
+++ b/assets/en_guide_lxd_lxd_install.md.2b676884.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const o="/assets/lxdd1.433ff357.png",t="/assets/lxdd2.6a93138a.png",l="/assets/lxdd3.f56cf598.png",p="/assets/lxdd4.28d80b71.png",i="/assets/lxdd0.b1d6b8bc.png",f=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_install.md","filePath":"en/guide/lxd/lxd_install.md","lastUpdated":1747726389000}'),c={name:"en/guide/lxd/lxd_install.md"},r=n('
LXD Installation Guide ​
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the LXD module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
One-Click Installation ​
WARNING
If this is a new server, make sure that both apt update and apt install curl are working properly before executing this script. It is recommended to pre-install btrfs-progs to speed up the subsequent installation process, after installation it is recommended to reboot the system to load the settings, if it is not pre-installed it is no problem, just follow the prompts to execute the script.
TIP
It's recommended to wait for at least 5 minutes after the system boots up before executing the following commands. This is to avoid the script being executed by the default system settings, which could cause issues with apt sources.
  • Prerequisites: Ubuntu 18+ (recommended), Debian 8+ (x86_64 architecture only)
  • The virtual memory here is talking about the size of the SWAP to be opened, and the storage pool is the sum of the sizes of the disks occupied by all your servers to be opened
  • The server needs to be restarted after the environment installation process to load some default configurations
  • By default, lxd's lxcfs-related configuration is enabled, so that in-container querying of container information changes to information about the container itself rather than the host
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
Example of initialization configuration:
If there is 18GB of unused disk space on the system disk, after deducting the space already occupied, and you want to allocate 2GB of virtual memory (2048MB of SWAP) and a 15GB storage pool, then following the prompts in the command line, enter 2048 and 15.
WARNING
If you need to open more than 200 LXD containers on a single server, then it is not recommended to use this project, there may be problems with lxcfs access drift, which generates IO occupancy that cannot be released. (This is a native LXC problem that can't be fixed.)
Installation of WEB Control Panel ​
Customization There are tutorials on how to enable the official panel, but here do not choose to use the official panel, because the official panel in order to security, at the expense of a lot of user experience, this piece of using the
https://github.com/turtle0x1/LxdMosaic
third-party panels
shell
sudo snap install lxdmosaic
Do a straightforward one-click install, then open the current host's https://<public IP address>/ and force access to it to get to the setup page
lxd
lxd
lxd
This piece can be changed if you need to set up the site name
lxd
Better than nothing can only mean that there is no RBAC access control for sub-user segregation
Manual installation (optional) ​
Not recommended, just for some odd environments where one-click scripts won't run.
Disable Firewall ​
bash
apt update
+import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const o="/assets/lxdd1.433ff357.png",t="/assets/lxdd2.6a93138a.png",l="/assets/lxdd3.f56cf598.png",p="/assets/lxdd4.28d80b71.png",i="/assets/lxdd0.b1d6b8bc.png",f=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_install.md","filePath":"en/guide/lxd/lxd_install.md","lastUpdated":1747730955000}'),c={name:"en/guide/lxd/lxd_install.md"},r=n('
LXD Installation Guide ​
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the LXD module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
One-Click Installation ​
WARNING
If this is a new server, make sure that both apt update and apt install curl are working properly before executing this script. It is recommended to pre-install btrfs-progs to speed up the subsequent installation process, after installation it is recommended to reboot the system to load the settings, if it is not pre-installed it is no problem, just follow the prompts to execute the script.
TIP
It's recommended to wait for at least 5 minutes after the system boots up before executing the following commands. This is to avoid the script being executed by the default system settings, which could cause issues with apt sources.
  • Prerequisites: Ubuntu 18+ (recommended), Debian 8+ (x86_64 architecture only)
  • The virtual memory here is talking about the size of the SWAP to be opened, and the storage pool is the sum of the sizes of the disks occupied by all your servers to be opened
  • The server needs to be restarted after the environment installation process to load some default configurations
  • By default, lxd's lxcfs-related configuration is enabled, so that in-container querying of container information changes to information about the container itself rather than the host
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
Example of initialization configuration:
If there is 18GB of unused disk space on the system disk, after deducting the space already occupied, and you want to allocate 2GB of virtual memory (2048MB of SWAP) and a 15GB storage pool, then following the prompts in the command line, enter 2048 and 15.
WARNING
If you need to open more than 200 LXD containers on a single server, then it is not recommended to use this project, there may be problems with lxcfs access drift, which generates IO occupancy that cannot be released. (This is a native LXC problem that can't be fixed.)
Installation of WEB Control Panel ​
Customization There are tutorials on how to enable the official panel, but here do not choose to use the official panel, because the official panel in order to security, at the expense of a lot of user experience, this piece of using the
https://github.com/turtle0x1/LxdMosaic
third-party panels
shell
sudo snap install lxdmosaic
Do a straightforward one-click install, then open the current host's https://<public IP address>/ and force access to it to get to the setup page
lxd
lxd
lxd
This piece can be changed if you need to set up the site name
lxd
Better than nothing can only mean that there is no RBAC access control for sub-user segregation
Manual installation (optional) ​
Not recommended, just for some odd environments where one-click scripts won't run.
Disable Firewall ​
bash
apt update
 apt install curl wget sudo dos2unix ufw jq -y
 ufw disable
Enabling Virtual Memory SWAP ​
The amount of memory depends on how many instances you want to run. If you want to run 8 instances and calculate, you'll need 2GB of memory. If your actual physical memory is 512MB, you'll need an additional 1.5GB. To be cautious, allocate 2GB of virtual memory.
Execute the following commands: Enter '1', then enter '2048'. This signifies allocating 2GB of virtual memory.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
Installing LXD ​
Actually, the virtual memory allocated for swap should be twice the size of the actual memory. So, it's reasonable to allocate 1GB if the actual memory is 500MB. The scenario I described above is an excessive allocation.
apt install snapd -y
 snap install lxd
diff --git a/assets/en_guide_lxd_lxd_install.md.219e45e1.lean.js b/assets/en_guide_lxd_lxd_install.md.2b676884.lean.js
similarity index 99%
rename from assets/en_guide_lxd_lxd_install.md.219e45e1.lean.js
rename to assets/en_guide_lxd_lxd_install.md.2b676884.lean.js
index 990b9c9417..65c0b50dfd 100644
--- a/assets/en_guide_lxd_lxd_install.md.219e45e1.lean.js
+++ b/assets/en_guide_lxd_lxd_install.md.2b676884.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const o="/assets/lxdd1.433ff357.png",t="/assets/lxdd2.6a93138a.png",l="/assets/lxdd3.f56cf598.png",p="/assets/lxdd4.28d80b71.png",i="/assets/lxdd0.b1d6b8bc.png",f=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_install.md","filePath":"en/guide/lxd/lxd_install.md","lastUpdated":1747726389000}'),c={name:"en/guide/lxd/lxd_install.md"},r=n('
LXD Installation Guide ​
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the LXD module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
One-Click Installation ​
WARNING
If this is a new server, make sure that both apt update and apt install curl are working properly before executing this script. It is recommended to pre-install btrfs-progs to speed up the subsequent installation process, after installation it is recommended to reboot the system to load the settings, if it is not pre-installed it is no problem, just follow the prompts to execute the script.
TIP
It's recommended to wait for at least 5 minutes after the system boots up before executing the following commands. This is to avoid the script being executed by the default system settings, which could cause issues with apt sources.
  • Prerequisites: Ubuntu 18+ (recommended), Debian 8+ (x86_64 architecture only)
  • The virtual memory here is talking about the size of the SWAP to be opened, and the storage pool is the sum of the sizes of the disks occupied by all your servers to be opened
  • The server needs to be restarted after the environment installation process to load some default configurations
  • By default, lxd's lxcfs-related configuration is enabled, so that in-container querying of container information changes to information about the container itself rather than the host
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
Example of initialization configuration:
If there is 18GB of unused disk space on the system disk, after deducting the space already occupied, and you want to allocate 2GB of virtual memory (2048MB of SWAP) and a 15GB storage pool, then following the prompts in the command line, enter 2048 and 15.
WARNING
If you need to open more than 200 LXD containers on a single server, then it is not recommended to use this project, there may be problems with lxcfs access drift, which generates IO occupancy that cannot be released. (This is a native LXC problem that can't be fixed.)
Installation of WEB Control Panel ​
Customization There are tutorials on how to enable the official panel, but here do not choose to use the official panel, because the official panel in order to security, at the expense of a lot of user experience, this piece of using the
https://github.com/turtle0x1/LxdMosaic
third-party panels
shell
sudo snap install lxdmosaic
Do a straightforward one-click install, then open the current host's https://<public IP address>/ and force access to it to get to the setup page
lxd
lxd
lxd
This piece can be changed if you need to set up the site name
lxd
Better than nothing can only mean that there is no RBAC access control for sub-user segregation
Manual installation (optional) ​
Not recommended, just for some odd environments where one-click scripts won't run.
Disable Firewall ​
bash
apt update
+import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const o="/assets/lxdd1.433ff357.png",t="/assets/lxdd2.6a93138a.png",l="/assets/lxdd3.f56cf598.png",p="/assets/lxdd4.28d80b71.png",i="/assets/lxdd0.b1d6b8bc.png",f=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_install.md","filePath":"en/guide/lxd/lxd_install.md","lastUpdated":1747730955000}'),c={name:"en/guide/lxd/lxd_install.md"},r=n('
LXD Installation Guide ​
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the LXD module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
One-Click Installation ​
WARNING
If this is a new server, make sure that both apt update and apt install curl are working properly before executing this script. It is recommended to pre-install btrfs-progs to speed up the subsequent installation process, after installation it is recommended to reboot the system to load the settings, if it is not pre-installed it is no problem, just follow the prompts to execute the script.
TIP
It's recommended to wait for at least 5 minutes after the system boots up before executing the following commands. This is to avoid the script being executed by the default system settings, which could cause issues with apt sources.
  • Prerequisites: Ubuntu 18+ (recommended), Debian 8+ (x86_64 architecture only)
  • The virtual memory here is talking about the size of the SWAP to be opened, and the storage pool is the sum of the sizes of the disks occupied by all your servers to be opened
  • The server needs to be restarted after the environment installation process to load some default configurations
  • By default, lxd's lxcfs-related configuration is enabled, so that in-container querying of container information changes to information about the container itself rather than the host
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
Example of initialization configuration:
If there is 18GB of unused disk space on the system disk, after deducting the space already occupied, and you want to allocate 2GB of virtual memory (2048MB of SWAP) and a 15GB storage pool, then following the prompts in the command line, enter 2048 and 15.
WARNING
If you need to open more than 200 LXD containers on a single server, then it is not recommended to use this project, there may be problems with lxcfs access drift, which generates IO occupancy that cannot be released. (This is a native LXC problem that can't be fixed.)
Installation of WEB Control Panel ​
Customization There are tutorials on how to enable the official panel, but here do not choose to use the official panel, because the official panel in order to security, at the expense of a lot of user experience, this piece of using the
https://github.com/turtle0x1/LxdMosaic
third-party panels
shell
sudo snap install lxdmosaic
Do a straightforward one-click install, then open the current host's https://<public IP address>/ and force access to it to get to the setup page
lxd
lxd
lxd
This piece can be changed if you need to set up the site name
lxd
Better than nothing can only mean that there is no RBAC access control for sub-user segregation
Manual installation (optional) ​
Not recommended, just for some odd environments where one-click scripts won't run.
Disable Firewall ​
bash
apt update
 apt install curl wget sudo dos2unix ufw jq -y
 ufw disable
Enabling Virtual Memory SWAP ​
The amount of memory depends on how many instances you want to run. If you want to run 8 instances and calculate, you'll need 2GB of memory. If your actual physical memory is 512MB, you'll need an additional 1.5GB. To be cautious, allocate 2GB of virtual memory.
Execute the following commands: Enter '1', then enter '2048'. This signifies allocating 2GB of virtual memory.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
Installing LXD ​
Actually, the virtual memory allocated for swap should be twice the size of the actual memory. So, it's reasonable to allocate 1GB if the actual memory is 500MB. The scenario I described above is an excessive allocation.
apt install snapd -y
 snap install lxd
diff --git a/assets/en_guide_lxd_lxd_lxc.md.25c28cca.js b/assets/en_guide_lxd_lxd_lxc.md.851bcb26.js
similarity index 99%
rename from assets/en_guide_lxd_lxd_lxc.md.25c28cca.js
rename to assets/en_guide_lxd_lxd_lxc.md.851bcb26.js
index 0d48b70648..c4dff0deac 100644
--- a/assets/en_guide_lxd_lxd_lxc.md.25c28cca.js
+++ b/assets/en_guide_lxd_lxd_lxc.md.851bcb26.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"LXC virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_lxc.md","filePath":"en/guide/lxd/lxd_lxc.md","lastUpdated":1747726389000}'),o={name:"en/guide/lxd/lxd_lxc.md"},l=e(`
LXC virtualization ​
Generate only one NAT server ​
  • Generate only one NAT server, with customizable restrictions on all content.
Downloading the boot script is NOT REQUIRED, if you have used the command to install LXD with one click, the corresponding boot script will be downloaded automatically, so you don't need to download the script again.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
Usage ​
. /buildone.sh name Cpu_num Memory_size Hard_disk_size SSH_port Extranet_start_port Extranet_stop_port Download_speed Upload_speed Whether_IPV6_is_enabled(Y or N) System(leave blank for debian12)
Memory size is calculated in MB, hard disk size is calculated in GB, download speed upload speed is calculated in Mbit, whether to enable IPV6 does not have to fill in Y or N, no this parameter can also be left blank default does not enable IPV6
If external start port\`\` and external stop port are both set to 0, then we don't do interval port mapping, only the basic SSH port is mapped, note that \`\`\`can't be null, and it needs to be set to 0 if it's not to be mapped.
Support for customizing the system of the server, do not fill out the default use of debian12 when left blank, note that the incoming parameters for the system name + version number, such as:
  • debian12, debian13
  • ubuntu22, ubuntu24
  • centos8，centos9
  • alpine3.16, alpine3.17, alpine3.18，alpine3.19
  • Note that the combination of lowercase letters + numbers or only lowercase letters, try it yourself, if the search is not the system will automatically exit the script
  • The version number can be with English decimal point, in order to adapt to the alpine version number has been supported.
  • If you can't open it, it may be that the hard disk is not big enough or it doesn't fit the host, try it by yourself.
  • The images currently in use are triple filtered and prioritized: self-hosted、official-hosted、opsmaru
  • A complete list of supported systems for self-compiling images: x86_64_fixed_images.txt and arm64_fixed_images.txt
Example ​
Here is the information about the example chick that is being raised:
AttributeValue
server's Nametest
Username for SSH Loginroot
Password for SSH LoginRandomly generated
Number of CPU Cores1
Memory Size256MB
Disk Size2G
Range of Internal and External Port Mapping20002 to 20025
Upload Bandwidth500Mbit
Download Bandwidth500Mbit
Automatically Set External IPv6 AddressNo
Operating SystemDebian 12
./buildone.sh test 1 256 2 20001 20002 20025 500 500 N debian12
If you need to see the information, run
shell
cat ct_name_change_me
For example, the information for the query example is
shell
cat test
If you have already generated chicks through the above methods and still need to batch generate chicks, you can use a customized batch generation version of the script, but note that you should first delete the test chicks before batch generating chicks
Delete Test Chick ​
shell
lxc stop test
+import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"LXC virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_lxc.md","filePath":"en/guide/lxd/lxd_lxc.md","lastUpdated":1747730955000}'),o={name:"en/guide/lxd/lxd_lxc.md"},l=e(`
LXC virtualization ​
Generate only one NAT server ​
  • Generate only one NAT server, with customizable restrictions on all content.
Downloading the boot script is NOT REQUIRED, if you have used the command to install LXD with one click, the corresponding boot script will be downloaded automatically, so you don't need to download the script again.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
Usage ​
. /buildone.sh name Cpu_num Memory_size Hard_disk_size SSH_port Extranet_start_port Extranet_stop_port Download_speed Upload_speed Whether_IPV6_is_enabled(Y or N) System(leave blank for debian12)
Memory size is calculated in MB, hard disk size is calculated in GB, download speed upload speed is calculated in Mbit, whether to enable IPV6 does not have to fill in Y or N, no this parameter can also be left blank default does not enable IPV6
If external start port\`\` and external stop port are both set to 0, then we don't do interval port mapping, only the basic SSH port is mapped, note that \`\`\`can't be null, and it needs to be set to 0 if it's not to be mapped.
Support for customizing the system of the server, do not fill out the default use of debian12 when left blank, note that the incoming parameters for the system name + version number, such as:
  • debian12, debian13
  • ubuntu22, ubuntu24
  • centos8，centos9
  • alpine3.16, alpine3.17, alpine3.18，alpine3.19
  • Note that the combination of lowercase letters + numbers or only lowercase letters, try it yourself, if the search is not the system will automatically exit the script
  • The version number can be with English decimal point, in order to adapt to the alpine version number has been supported.
  • If you can't open it, it may be that the hard disk is not big enough or it doesn't fit the host, try it by yourself.
  • The images currently in use are triple filtered and prioritized: self-hosted、official-hosted、opsmaru
  • A complete list of supported systems for self-compiling images: x86_64_fixed_images.txt and arm64_fixed_images.txt
Example ​
Here is the information about the example chick that is being raised:
AttributeValue
server's Nametest
Username for SSH Loginroot
Password for SSH LoginRandomly generated
Number of CPU Cores1
Memory Size256MB
Disk Size2G
Range of Internal and External Port Mapping20002 to 20025
Upload Bandwidth500Mbit
Download Bandwidth500Mbit
Automatically Set External IPv6 AddressNo
Operating SystemDebian 12
./buildone.sh test 1 256 2 20001 20002 20025 500 500 N debian12
If you need to see the information, run
shell
cat ct_name_change_me
For example, the information for the query example is
shell
cat test
If you have already generated chicks through the above methods and still need to batch generate chicks, you can use a customized batch generation version of the script, but note that you should first delete the test chicks before batch generating chicks
Delete Test Chick ​
shell
lxc stop test
 lxc delete test
 rm -rf test
 rm -rf test_v6
diff --git a/assets/en_guide_lxd_lxd_lxc.md.25c28cca.lean.js b/assets/en_guide_lxd_lxd_lxc.md.851bcb26.lean.js
similarity index 99%
rename from assets/en_guide_lxd_lxd_lxc.md.25c28cca.lean.js
rename to assets/en_guide_lxd_lxd_lxc.md.851bcb26.lean.js
index 0d48b70648..c4dff0deac 100644
--- a/assets/en_guide_lxd_lxd_lxc.md.25c28cca.lean.js
+++ b/assets/en_guide_lxd_lxd_lxc.md.851bcb26.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"LXC virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_lxc.md","filePath":"en/guide/lxd/lxd_lxc.md","lastUpdated":1747726389000}'),o={name:"en/guide/lxd/lxd_lxc.md"},l=e(`
LXC virtualization ​
Generate only one NAT server ​
  • Generate only one NAT server, with customizable restrictions on all content.
Downloading the boot script is NOT REQUIRED, if you have used the command to install LXD with one click, the corresponding boot script will be downloaded automatically, so you don't need to download the script again.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
Usage ​
. /buildone.sh name Cpu_num Memory_size Hard_disk_size SSH_port Extranet_start_port Extranet_stop_port Download_speed Upload_speed Whether_IPV6_is_enabled(Y or N) System(leave blank for debian12)
Memory size is calculated in MB, hard disk size is calculated in GB, download speed upload speed is calculated in Mbit, whether to enable IPV6 does not have to fill in Y or N, no this parameter can also be left blank default does not enable IPV6
If external start port\`\` and external stop port are both set to 0, then we don't do interval port mapping, only the basic SSH port is mapped, note that \`\`\`can't be null, and it needs to be set to 0 if it's not to be mapped.
Support for customizing the system of the server, do not fill out the default use of debian12 when left blank, note that the incoming parameters for the system name + version number, such as:
  • debian12, debian13
  • ubuntu22, ubuntu24
  • centos8，centos9
  • alpine3.16, alpine3.17, alpine3.18，alpine3.19
  • Note that the combination of lowercase letters + numbers or only lowercase letters, try it yourself, if the search is not the system will automatically exit the script
  • The version number can be with English decimal point, in order to adapt to the alpine version number has been supported.
  • If you can't open it, it may be that the hard disk is not big enough or it doesn't fit the host, try it by yourself.
  • The images currently in use are triple filtered and prioritized: self-hosted、official-hosted、opsmaru
  • A complete list of supported systems for self-compiling images: x86_64_fixed_images.txt and arm64_fixed_images.txt
Example ​
Here is the information about the example chick that is being raised:
AttributeValue
server's Nametest
Username for SSH Loginroot
Password for SSH LoginRandomly generated
Number of CPU Cores1
Memory Size256MB
Disk Size2G
Range of Internal and External Port Mapping20002 to 20025
Upload Bandwidth500Mbit
Download Bandwidth500Mbit
Automatically Set External IPv6 AddressNo
Operating SystemDebian 12
./buildone.sh test 1 256 2 20001 20002 20025 500 500 N debian12
If you need to see the information, run
shell
cat ct_name_change_me
For example, the information for the query example is
shell
cat test
If you have already generated chicks through the above methods and still need to batch generate chicks, you can use a customized batch generation version of the script, but note that you should first delete the test chicks before batch generating chicks
Delete Test Chick ​
shell
lxc stop test
+import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"LXC virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_lxc.md","filePath":"en/guide/lxd/lxd_lxc.md","lastUpdated":1747730955000}'),o={name:"en/guide/lxd/lxd_lxc.md"},l=e(`
LXC virtualization ​
Generate only one NAT server ​
  • Generate only one NAT server, with customizable restrictions on all content.
Downloading the boot script is NOT REQUIRED, if you have used the command to install LXD with one click, the corresponding boot script will be downloaded automatically, so you don't need to download the script again.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
Usage ​
. /buildone.sh name Cpu_num Memory_size Hard_disk_size SSH_port Extranet_start_port Extranet_stop_port Download_speed Upload_speed Whether_IPV6_is_enabled(Y or N) System(leave blank for debian12)
Memory size is calculated in MB, hard disk size is calculated in GB, download speed upload speed is calculated in Mbit, whether to enable IPV6 does not have to fill in Y or N, no this parameter can also be left blank default does not enable IPV6
If external start port\`\` and external stop port are both set to 0, then we don't do interval port mapping, only the basic SSH port is mapped, note that \`\`\`can't be null, and it needs to be set to 0 if it's not to be mapped.
Support for customizing the system of the server, do not fill out the default use of debian12 when left blank, note that the incoming parameters for the system name + version number, such as:
  • debian12, debian13
  • ubuntu22, ubuntu24
  • centos8，centos9
  • alpine3.16, alpine3.17, alpine3.18，alpine3.19
  • Note that the combination of lowercase letters + numbers or only lowercase letters, try it yourself, if the search is not the system will automatically exit the script
  • The version number can be with English decimal point, in order to adapt to the alpine version number has been supported.
  • If you can't open it, it may be that the hard disk is not big enough or it doesn't fit the host, try it by yourself.
  • The images currently in use are triple filtered and prioritized: self-hosted、official-hosted、opsmaru
  • A complete list of supported systems for self-compiling images: x86_64_fixed_images.txt and arm64_fixed_images.txt
Example ​
Here is the information about the example chick that is being raised:
AttributeValue
server's Nametest
Username for SSH Loginroot
Password for SSH LoginRandomly generated
Number of CPU Cores1
Memory Size256MB
Disk Size2G
Range of Internal and External Port Mapping20002 to 20025
Upload Bandwidth500Mbit
Download Bandwidth500Mbit
Automatically Set External IPv6 AddressNo
Operating SystemDebian 12
./buildone.sh test 1 256 2 20001 20002 20025 500 500 N debian12
If you need to see the information, run
shell
cat ct_name_change_me
For example, the information for the query example is
shell
cat test
If you have already generated chicks through the above methods and still need to batch generate chicks, you can use a customized batch generation version of the script, but note that you should first delete the test chicks before batch generating chicks
Delete Test Chick ​
shell
lxc stop test
 lxc delete test
 rm -rf test
 rm -rf test_v6
diff --git a/assets/en_guide_lxd_lxd_precheck.md.20cf4fb8.js b/assets/en_guide_lxd_lxd_precheck.md.fadb2185.js
similarity index 98%
rename from assets/en_guide_lxd_lxd_precheck.md.20cf4fb8.js
rename to assets/en_guide_lxd_lxd_precheck.md.fadb2185.js
index c2d73f37be..a6e813ac4c 100644
--- a/assets/en_guide_lxd_lxd_precheck.md.20cf4fb8.js
+++ b/assets/en_guide_lxd_lxd_precheck.md.fadb2185.js
@@ -1 +1 @@
-import{_ as e,v as t,b as o,R as n}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_precheck.md","filePath":"en/guide/lxd/lxd_precheck.md","lastUpdated":1747726389000}'),a={name:"en/guide/lxd/lxd_precheck.md"},r=n('
Preface ​
The following is the introduction of the non-customized part, the customized part has its own corresponding introduction, do not get confused!
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the LXD module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/lxd
Requirements ​
Hardware requirements.
  • System: Debian 8+, Ubuntu 18+ (20.04 recommended).
  • Virtualization: KVM, VMWARE recommended.
  • Memory: At least 512MB of RAM
  • Hard disk: hard disk (system disk) at least 10G
  • Network: Independent IPV4 address, IPV6 is optional, bandwidth can download scripts on the line, the network can connect to the Github raw page on the line
PS: If the hardware is very good and has a lot of resources, you can use PVE to batch open KVM virtualized VMs Jump
PS: If the hardware resources are even worse, virtualization is not supported, you can use the docker version, the adaption surface is wider Jump
Project Features ​
  • This set of script development using Ubuntu20, Ubuntu other long-term maintenance version should also be no problem, automatically switch to another storage type if btrfs not supported
  • Set up both TCP and UDP forwarding, in addition to SSH ports, other mapping intranet and extranet ports are the same.
  • Support for docker nested virtualization of open LXC containers has been set up, and the default normal version and pure probe version use the debian11 system.
  • lxcfs has been set to be enabled by default, so that querying resources within a container uses the configured view rather than the host's view
  • Have blocked the container may be used to abuse the toolkit and IPV4 network TCP/UDP protocol ports ( 3389 8888 54321 65432 ), to prevent the container is used for scanning and blasting, and can be external process checking for problems automatically shut down
  • Has supported one-click configuration of IPV6 addresses for LXC containers (provided that the mother hen has an IPV6 subnet, no IPV6 address is not configured), automatically adapted to the size of the subnet
  • Ensure that the disk you want to open is the default system disk (sda or sda1) and not the mounted disk (sdb and so on), if you are not sure, use fdisk -l and df to check.
  • See Other notes for details on mounting other disks.
  • One-click scripts support custom restrictions on all content, the normal version supports multiple runs of the batch generation does not overwrite the previously generated configuration
Detecting the environment ​
Use the subsequent script must execute this command to detect the hen whether it meets the requirements
Command:
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)
',15),s=[r];function i(d,c,l,h,p,u){return t(),o("div",null,s)}const b=e(a,[["render",i]]);export{f as __pageData,b as default};
+import{_ as e,v as t,b as o,R as n}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_precheck.md","filePath":"en/guide/lxd/lxd_precheck.md","lastUpdated":1747730955000}'),a={name:"en/guide/lxd/lxd_precheck.md"},r=n('
Preface ​
The following is the introduction of the non-customized part, the customized part has its own corresponding introduction, do not get confused!
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the LXD module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/lxd
Requirements ​
Hardware requirements.
  • System: Debian 8+, Ubuntu 18+ (20.04 recommended).
  • Virtualization: KVM, VMWARE recommended.
  • Memory: At least 512MB of RAM
  • Hard disk: hard disk (system disk) at least 10G
  • Network: Independent IPV4 address, IPV6 is optional, bandwidth can download scripts on the line, the network can connect to the Github raw page on the line
PS: If the hardware is very good and has a lot of resources, you can use PVE to batch open KVM virtualized VMs Jump
PS: If the hardware resources are even worse, virtualization is not supported, you can use the docker version, the adaption surface is wider Jump
Project Features ​
  • This set of script development using Ubuntu20, Ubuntu other long-term maintenance version should also be no problem, automatically switch to another storage type if btrfs not supported
  • Set up both TCP and UDP forwarding, in addition to SSH ports, other mapping intranet and extranet ports are the same.
  • Support for docker nested virtualization of open LXC containers has been set up, and the default normal version and pure probe version use the debian11 system.
  • lxcfs has been set to be enabled by default, so that querying resources within a container uses the configured view rather than the host's view
  • Have blocked the container may be used to abuse the toolkit and IPV4 network TCP/UDP protocol ports ( 3389 8888 54321 65432 ), to prevent the container is used for scanning and blasting, and can be external process checking for problems automatically shut down
  • Has supported one-click configuration of IPV6 addresses for LXC containers (provided that the mother hen has an IPV6 subnet, no IPV6 address is not configured), automatically adapted to the size of the subnet
  • Ensure that the disk you want to open is the default system disk (sda or sda1) and not the mounted disk (sdb and so on), if you are not sure, use fdisk -l and df to check.
  • See Other notes for details on mounting other disks.
  • One-click scripts support custom restrictions on all content, the normal version supports multiple runs of the batch generation does not overwrite the previously generated configuration
Detecting the environment ​
Use the subsequent script must execute this command to detect the hen whether it meets the requirements
Command:
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)
',15),s=[r];function i(d,c,l,h,p,u){return t(),o("div",null,s)}const b=e(a,[["render",i]]);export{f as __pageData,b as default};
diff --git a/assets/en_guide_lxd_lxd_precheck.md.20cf4fb8.lean.js b/assets/en_guide_lxd_lxd_precheck.md.fadb2185.lean.js
similarity index 98%
rename from assets/en_guide_lxd_lxd_precheck.md.20cf4fb8.lean.js
rename to assets/en_guide_lxd_lxd_precheck.md.fadb2185.lean.js
index c2d73f37be..a6e813ac4c 100644
--- a/assets/en_guide_lxd_lxd_precheck.md.20cf4fb8.lean.js
+++ b/assets/en_guide_lxd_lxd_precheck.md.fadb2185.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as o,R as n}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_precheck.md","filePath":"en/guide/lxd/lxd_precheck.md","lastUpdated":1747726389000}'),a={name:"en/guide/lxd/lxd_precheck.md"},r=n('
Preface ​
The following is the introduction of the non-customized part, the customized part has its own corresponding introduction, do not get confused!
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the LXD module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/lxd
Requirements ​
Hardware requirements.
  • System: Debian 8+, Ubuntu 18+ (20.04 recommended).
  • Virtualization: KVM, VMWARE recommended.
  • Memory: At least 512MB of RAM
  • Hard disk: hard disk (system disk) at least 10G
  • Network: Independent IPV4 address, IPV6 is optional, bandwidth can download scripts on the line, the network can connect to the Github raw page on the line
PS: If the hardware is very good and has a lot of resources, you can use PVE to batch open KVM virtualized VMs Jump
PS: If the hardware resources are even worse, virtualization is not supported, you can use the docker version, the adaption surface is wider Jump
Project Features ​
  • This set of script development using Ubuntu20, Ubuntu other long-term maintenance version should also be no problem, automatically switch to another storage type if btrfs not supported
  • Set up both TCP and UDP forwarding, in addition to SSH ports, other mapping intranet and extranet ports are the same.
  • Support for docker nested virtualization of open LXC containers has been set up, and the default normal version and pure probe version use the debian11 system.
  • lxcfs has been set to be enabled by default, so that querying resources within a container uses the configured view rather than the host's view
  • Have blocked the container may be used to abuse the toolkit and IPV4 network TCP/UDP protocol ports ( 3389 8888 54321 65432 ), to prevent the container is used for scanning and blasting, and can be external process checking for problems automatically shut down
  • Has supported one-click configuration of IPV6 addresses for LXC containers (provided that the mother hen has an IPV6 subnet, no IPV6 address is not configured), automatically adapted to the size of the subnet
  • Ensure that the disk you want to open is the default system disk (sda or sda1) and not the mounted disk (sdb and so on), if you are not sure, use fdisk -l and df to check.
  • See Other notes for details on mounting other disks.
  • One-click scripts support custom restrictions on all content, the normal version supports multiple runs of the batch generation does not overwrite the previously generated configuration
Detecting the environment ​
Use the subsequent script must execute this command to detect the hen whether it meets the requirements
Command:
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)
',15),s=[r];function i(d,c,l,h,p,u){return t(),o("div",null,s)}const b=e(a,[["render",i]]);export{f as __pageData,b as default};
+import{_ as e,v as t,b as o,R as n}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_precheck.md","filePath":"en/guide/lxd/lxd_precheck.md","lastUpdated":1747730955000}'),a={name:"en/guide/lxd/lxd_precheck.md"},r=n('
Preface ​
The following is the introduction of the non-customized part, the customized part has its own corresponding introduction, do not get confused!
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the LXD module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/lxd
Requirements ​
Hardware requirements.
  • System: Debian 8+, Ubuntu 18+ (20.04 recommended).
  • Virtualization: KVM, VMWARE recommended.
  • Memory: At least 512MB of RAM
  • Hard disk: hard disk (system disk) at least 10G
  • Network: Independent IPV4 address, IPV6 is optional, bandwidth can download scripts on the line, the network can connect to the Github raw page on the line
PS: If the hardware is very good and has a lot of resources, you can use PVE to batch open KVM virtualized VMs Jump
PS: If the hardware resources are even worse, virtualization is not supported, you can use the docker version, the adaption surface is wider Jump
Project Features ​
  • This set of script development using Ubuntu20, Ubuntu other long-term maintenance version should also be no problem, automatically switch to another storage type if btrfs not supported
  • Set up both TCP and UDP forwarding, in addition to SSH ports, other mapping intranet and extranet ports are the same.
  • Support for docker nested virtualization of open LXC containers has been set up, and the default normal version and pure probe version use the debian11 system.
  • lxcfs has been set to be enabled by default, so that querying resources within a container uses the configured view rather than the host's view
  • Have blocked the container may be used to abuse the toolkit and IPV4 network TCP/UDP protocol ports ( 3389 8888 54321 65432 ), to prevent the container is used for scanning and blasting, and can be external process checking for problems automatically shut down
  • Has supported one-click configuration of IPV6 addresses for LXC containers (provided that the mother hen has an IPV6 subnet, no IPV6 address is not configured), automatically adapted to the size of the subnet
  • Ensure that the disk you want to open is the default system disk (sda or sda1) and not the mounted disk (sdb and so on), if you are not sure, use fdisk -l and df to check.
  • See Other notes for details on mounting other disks.
  • One-click scripts support custom restrictions on all content, the normal version supports multiple runs of the batch generation does not overwrite the previously generated configuration
Detecting the environment ​
Use the subsequent script must execute this command to detect the hen whether it meets the requirements
Command:
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)
',15),s=[r];function i(d,c,l,h,p,u){return t(),o("div",null,s)}const b=e(a,[["render",i]]);export{f as __pageData,b as default};
diff --git a/assets/en_guide_lxd_lxd_qa.md.63c8964a.js b/assets/en_guide_lxd_lxd_qa.md.6a1d11ff.js
similarity index 98%
rename from assets/en_guide_lxd_lxd_qa.md.63c8964a.js
rename to assets/en_guide_lxd_lxd_qa.md.6a1d11ff.js
index d49d7f5643..c839bd5776 100644
--- a/assets/en_guide_lxd_lxd_qa.md.63c8964a.js
+++ b/assets/en_guide_lxd_lxd_qa.md.6a1d11ff.js
@@ -1 +1 @@
-import{_ as e,v as a,b as t,R as s}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_qa.md","filePath":"en/guide/lxd/lxd_qa.md","lastUpdated":1747726389000}'),n={name:"en/guide/lxd/lxd_qa.md"},o=s('
Solve the puzzle ​
What if the lxc command says it can't be found after LXD is installed? ​
! lxc -h >/dev/null 2>&1 && echo 'alias lxc="/snap/bin/lxc"' >> /root/.bashrc && source /root/.bashrc\nexport PATH=$PATH:/snap/bin
After executing this command try
lxc -h
to see if the lxc command is fixed.
What to do if you open centos7 and find that CGroupV1 is not supported? ​
Enable CGroup V1: To enable CGroup V1 on an Ubuntu system, you need to edit the kernel boot parameters.
Please note that before changing kernel boot parameters, make sure to backup important data and settings to prevent unexpected problems.
Edit the ```/etc/default/grubfile and addsystemd.unified_cgroup_hierarchy=0to the end of the parameters inGRUB_CMDLINE_LINUX_DEFAULT``, just like:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"
Save the file and run the following command to update the GRUB boot.
bash
sudo update-grub
Reboot the system for the changes to take effect
If the above changes still do not support the opening of centos7, try using a different host system.
Currently verified VPS vendors that can open containers with separate IPV6 addresses. ​
kuroit Phoenix, USA regular
datalix German AMD Promotions
',18),r=[o];function p(i,l,d,c,h,u){return a(),t("div",null,r)}const b=e(n,[["render",p]]);export{m as __pageData,b as default};
+import{_ as e,v as a,b as t,R as s}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_qa.md","filePath":"en/guide/lxd/lxd_qa.md","lastUpdated":1747730955000}'),n={name:"en/guide/lxd/lxd_qa.md"},o=s('
Solve the puzzle ​
What if the lxc command says it can't be found after LXD is installed? ​
! lxc -h >/dev/null 2>&1 && echo 'alias lxc="/snap/bin/lxc"' >> /root/.bashrc && source /root/.bashrc\nexport PATH=$PATH:/snap/bin
After executing this command try
lxc -h
to see if the lxc command is fixed.
What to do if you open centos7 and find that CGroupV1 is not supported? ​
Enable CGroup V1: To enable CGroup V1 on an Ubuntu system, you need to edit the kernel boot parameters.
Please note that before changing kernel boot parameters, make sure to backup important data and settings to prevent unexpected problems.
Edit the ```/etc/default/grubfile and addsystemd.unified_cgroup_hierarchy=0to the end of the parameters inGRUB_CMDLINE_LINUX_DEFAULT``, just like:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"
Save the file and run the following command to update the GRUB boot.
bash
sudo update-grub
Reboot the system for the changes to take effect
If the above changes still do not support the opening of centos7, try using a different host system.
Currently verified VPS vendors that can open containers with separate IPV6 addresses. ​
kuroit Phoenix, USA regular
datalix German AMD Promotions
',18),r=[o];function p(i,l,d,c,h,u){return a(),t("div",null,r)}const b=e(n,[["render",p]]);export{m as __pageData,b as default};
diff --git a/assets/en_guide_lxd_lxd_qa.md.63c8964a.lean.js b/assets/en_guide_lxd_lxd_qa.md.6a1d11ff.lean.js
similarity index 98%
rename from assets/en_guide_lxd_lxd_qa.md.63c8964a.lean.js
rename to assets/en_guide_lxd_lxd_qa.md.6a1d11ff.lean.js
index d49d7f5643..c839bd5776 100644
--- a/assets/en_guide_lxd_lxd_qa.md.63c8964a.lean.js
+++ b/assets/en_guide_lxd_lxd_qa.md.6a1d11ff.lean.js
@@ -1 +1 @@
-import{_ as e,v as a,b as t,R as s}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_qa.md","filePath":"en/guide/lxd/lxd_qa.md","lastUpdated":1747726389000}'),n={name:"en/guide/lxd/lxd_qa.md"},o=s('
Solve the puzzle ​
What if the lxc command says it can't be found after LXD is installed? ​
! lxc -h >/dev/null 2>&1 && echo 'alias lxc="/snap/bin/lxc"' >> /root/.bashrc && source /root/.bashrc\nexport PATH=$PATH:/snap/bin
After executing this command try
lxc -h
to see if the lxc command is fixed.
What to do if you open centos7 and find that CGroupV1 is not supported? ​
Enable CGroup V1: To enable CGroup V1 on an Ubuntu system, you need to edit the kernel boot parameters.
Please note that before changing kernel boot parameters, make sure to backup important data and settings to prevent unexpected problems.
Edit the ```/etc/default/grubfile and addsystemd.unified_cgroup_hierarchy=0to the end of the parameters inGRUB_CMDLINE_LINUX_DEFAULT``, just like:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"
Save the file and run the following command to update the GRUB boot.
bash
sudo update-grub
Reboot the system for the changes to take effect
If the above changes still do not support the opening of centos7, try using a different host system.
Currently verified VPS vendors that can open containers with separate IPV6 addresses. ​
kuroit Phoenix, USA regular
datalix German AMD Promotions
',18),r=[o];function p(i,l,d,c,h,u){return a(),t("div",null,r)}const b=e(n,[["render",p]]);export{m as __pageData,b as default};
+import{_ as e,v as a,b as t,R as s}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_qa.md","filePath":"en/guide/lxd/lxd_qa.md","lastUpdated":1747730955000}'),n={name:"en/guide/lxd/lxd_qa.md"},o=s('
Solve the puzzle ​
What if the lxc command says it can't be found after LXD is installed? ​
! lxc -h >/dev/null 2>&1 && echo 'alias lxc="/snap/bin/lxc"' >> /root/.bashrc && source /root/.bashrc\nexport PATH=$PATH:/snap/bin
After executing this command try
lxc -h
to see if the lxc command is fixed.
What to do if you open centos7 and find that CGroupV1 is not supported? ​
Enable CGroup V1: To enable CGroup V1 on an Ubuntu system, you need to edit the kernel boot parameters.
Please note that before changing kernel boot parameters, make sure to backup important data and settings to prevent unexpected problems.
Edit the ```/etc/default/grubfile and addsystemd.unified_cgroup_hierarchy=0to the end of the parameters inGRUB_CMDLINE_LINUX_DEFAULT``, just like:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"
Save the file and run the following command to update the GRUB boot.
bash
sudo update-grub
Reboot the system for the changes to take effect
If the above changes still do not support the opening of centos7, try using a different host system.
Currently verified VPS vendors that can open containers with separate IPV6 addresses. ​
kuroit Phoenix, USA regular
datalix German AMD Promotions
',18),r=[o];function p(i,l,d,c,h,u){return a(),t("div",null,r)}const b=e(n,[["render",p]]);export{m as __pageData,b as default};
diff --git a/assets/en_guide_lxd_lxd_thanks.md.a98bd8f1.js b/assets/en_guide_lxd_lxd_thanks.md.af91b5a4.js
similarity index 94%
rename from assets/en_guide_lxd_lxd_thanks.md.a98bd8f1.js
rename to assets/en_guide_lxd_lxd_thanks.md.af91b5a4.js
index aa6035a65b..b7fc6fb0b0 100644
--- a/assets/en_guide_lxd_lxd_thanks.md.a98bd8f1.js
+++ b/assets/en_guide_lxd_lxd_thanks.md.af91b5a4.js
@@ -1 +1 @@
-import{_ as e,v as t,b as r,R as a}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/lxd/lxd_thanks.md","filePath":"en/guide/lxd/lxd_thanks.md","lastUpdated":1747726389000}'),n={name:"en/guide/lxd/lxd_thanks.md"},s=a('
Acknowledgements ​
https://github.com/lxc/lxd
https://lxdware.com/
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
https://github.com/SuperManito/LinuxMirrors
https://images.opsmaru.dev/
Thank @Ella-Alinda @fscarmen for providing guidance.
',12),o=[s];function i(l,p,c,d,h,u){return t(),r("div",null,o)}const x=e(n,[["render",i]]);export{f as __pageData,x as default};
+import{_ as e,v as t,b as r,R as a}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/lxd/lxd_thanks.md","filePath":"en/guide/lxd/lxd_thanks.md","lastUpdated":1747730955000}'),n={name:"en/guide/lxd/lxd_thanks.md"},s=a('
Acknowledgements ​
https://github.com/lxc/lxd
https://lxdware.com/
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
https://github.com/SuperManito/LinuxMirrors
https://images.opsmaru.dev/
Thank @Ella-Alinda @fscarmen for providing guidance.
',12),o=[s];function i(l,p,c,d,h,u){return t(),r("div",null,o)}const x=e(n,[["render",i]]);export{f as __pageData,x as default};
diff --git a/assets/en_guide_lxd_lxd_thanks.md.a98bd8f1.lean.js b/assets/en_guide_lxd_lxd_thanks.md.af91b5a4.lean.js
similarity index 94%
rename from assets/en_guide_lxd_lxd_thanks.md.a98bd8f1.lean.js
rename to assets/en_guide_lxd_lxd_thanks.md.af91b5a4.lean.js
index aa6035a65b..b7fc6fb0b0 100644
--- a/assets/en_guide_lxd_lxd_thanks.md.a98bd8f1.lean.js
+++ b/assets/en_guide_lxd_lxd_thanks.md.af91b5a4.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as r,R as a}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/lxd/lxd_thanks.md","filePath":"en/guide/lxd/lxd_thanks.md","lastUpdated":1747726389000}'),n={name:"en/guide/lxd/lxd_thanks.md"},s=a('
Acknowledgements ​
https://github.com/lxc/lxd
https://lxdware.com/
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
https://github.com/SuperManito/LinuxMirrors
https://images.opsmaru.dev/
Thank @Ella-Alinda @fscarmen for providing guidance.
',12),o=[s];function i(l,p,c,d,h,u){return t(),r("div",null,o)}const x=e(n,[["render",i]]);export{f as __pageData,x as default};
+import{_ as e,v as t,b as r,R as a}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/lxd/lxd_thanks.md","filePath":"en/guide/lxd/lxd_thanks.md","lastUpdated":1747730955000}'),n={name:"en/guide/lxd/lxd_thanks.md"},s=a('
Acknowledgements ​
https://github.com/lxc/lxd
https://lxdware.com/
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
https://github.com/SuperManito/LinuxMirrors
https://images.opsmaru.dev/
Thank @Ella-Alinda @fscarmen for providing guidance.
',12),o=[s];function i(l,p,c,d,h,u){return t(),r("div",null,o)}const x=e(n,[["render",i]]);export{f as __pageData,x as default};
diff --git a/assets/en_guide_pve_images_readme.md.13a6dece.js b/assets/en_guide_pve_images_readme.md.a40c9248.js
similarity index 86%
rename from assets/en_guide_pve_images_readme.md.13a6dece.js
rename to assets/en_guide_pve_images_readme.md.a40c9248.js
index 059298348d..c96953c108 100644
--- a/assets/en_guide_pve_images_readme.md.13a6dece.js
+++ b/assets/en_guide_pve_images_readme.md.a40c9248.js
@@ -1 +1 @@
-import{_ as e,v as a,b as t,F as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/pve/images/readme.md","filePath":"en/guide/pve/images/readme.md","lastUpdated":1747726389000}'),d={name:"en/guide/pve/images/readme.md"},r=s("p",null,"暂存图片",-1),n=[r];function i(o,m,p,_,c,l){return a(),t("div",null,n)}const g=e(d,[["render",i]]);export{f as __pageData,g as default};
+import{_ as e,v as a,b as t,F as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/pve/images/readme.md","filePath":"en/guide/pve/images/readme.md","lastUpdated":1747730955000}'),d={name:"en/guide/pve/images/readme.md"},r=s("p",null,"暂存图片",-1),n=[r];function i(o,m,p,_,c,l){return a(),t("div",null,n)}const g=e(d,[["render",i]]);export{f as __pageData,g as default};
diff --git a/assets/en_guide_pve_images_readme.md.13a6dece.lean.js b/assets/en_guide_pve_images_readme.md.a40c9248.lean.js
similarity index 86%
rename from assets/en_guide_pve_images_readme.md.13a6dece.lean.js
rename to assets/en_guide_pve_images_readme.md.a40c9248.lean.js
index 059298348d..c96953c108 100644
--- a/assets/en_guide_pve_images_readme.md.13a6dece.lean.js
+++ b/assets/en_guide_pve_images_readme.md.a40c9248.lean.js
@@ -1 +1 @@
-import{_ as e,v as a,b as t,F as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/pve/images/readme.md","filePath":"en/guide/pve/images/readme.md","lastUpdated":1747726389000}'),d={name:"en/guide/pve/images/readme.md"},r=s("p",null,"暂存图片",-1),n=[r];function i(o,m,p,_,c,l){return a(),t("div",null,n)}const g=e(d,[["render",i]]);export{f as __pageData,g as default};
+import{_ as e,v as a,b as t,F as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/pve/images/readme.md","filePath":"en/guide/pve/images/readme.md","lastUpdated":1747730955000}'),d={name:"en/guide/pve/images/readme.md"},r=s("p",null,"暂存图片",-1),n=[r];function i(o,m,p,_,c,l){return a(),t("div",null,n)}const g=e(d,[["render",i]]);export{f as __pageData,g as default};
diff --git a/assets/en_guide_pve_pve_android.md.05709719.js b/assets/en_guide_pve_pve_android.md.a3006536.js
similarity index 99%
rename from assets/en_guide_pve_pve_android.md.05709719.js
rename to assets/en_guide_pve_pve_android.md.a3006536.js
index cc53b719c8..52104d2961 100644
--- a/assets/en_guide_pve_pve_android.md.05709719.js
+++ b/assets/en_guide_pve_pve_android.md.a3006536.js
@@ -1 +1 @@
-import{_ as e,v as t,b as o,R as s}from"./chunks/framework.70afa331.js";const a="/assets/a1.662d9415.png",n="/assets/a2.1d7d86db.png",i="/assets/a3.178777a1.png",r="/assets/a4.65c15963.png",p="/assets/a5.01b8514f.png",c="/assets/a6.67efded0.png",d="/assets/a7.b8de9a6c.png",l="/assets/a8.69056d9a.png",h="/assets/a9.d4cc5fc0.png",m="/assets/a10.36860678.png",g="/assets/a11.bbc20080.png",u="/assets/a12.da46fe54.png",f="/assets/a13.b49276aa.png",b="/assets/a14.908480a6.png",_="/assets/a15.9533f30d.png",y="/assets/a16.2257f2d8.png",k="/assets/a17.b57c7755.png",w="/assets/a18.c3a22602.png",v="/assets/a19.1eefd81d.png",x="/assets/a20.24042237.png",I="/assets/a21.2bb37c9a.png",C="/assets/a22.44ab6d75.png",A="/assets/a23.191de0ca.png",S="/assets/a24.d2a9c729.png",q="/assets/a25.3e24d99b.png",P="/assets/a26.2fce6332.png",O="/assets/ar.0d8bb8f3.png",T="/assets/a27.dd61884c.png",V="/assets/a31.6d3a9d85.png",z="/assets/a32.d9973307.png",E="/assets/a33.8b54ce3f.png",M="/assets/a34.07f5cc75.png",U="/assets/a35.78be61d4.png",G="/assets/a36.a36765c2.png",D="/assets/a37.e6740eaa.png",F="/assets/a38.999b4ffb.png",B="/assets/a39.9dac95e1.png",K="/assets/a40.7f5ad4ea.png",R="/assets/a41.bbc5e317.png",N="/assets/a42.de7d1da7.png",Y="/assets/a43.e713599d.png",W="/assets/a44.5c4e5e0a.png",L="/assets/a45.2c32612e.png",H="/assets/b1.c1fdb506.png",j="/assets/b2.519a9bf0.png",Q="/assets/b3.42fd37a2.png",$="/assets/b4.b6d283a7.png",J="/assets/b5.4cd5361f.png",X="/assets/b6.36f0470d.png",Z="/assets/b7.9714bb16.png",ee="/assets/b8.2eb373bf.png",te="/assets/b9.3f01ffdc.png",oe="/assets/b10.52a93636.png",se="/assets/b11.2e525d8d.png",ae="/assets/b12.54c3189d.png",ne="/assets/b13.3b3ae784.png",ie="/assets/b14.662b1a1b.png",re="/assets/b15.0c5536d8.png",pe="/assets/b16.0fbcfcb1.png",ce="/assets/b17.4e7429fe.png",de="/assets/b18.8211f293.png",le="/assets/b19.2128d0fa.png",he="/assets/b20.8a62698b.png",me="/assets/b21.dfe1e8f0.png",ge="/assets/b22.13e3438c.png",ue="/assets/b23.e293a560.png",fe="/assets/b24.23cbc29a.png",be="/assets/b25.f2c2ebd7.png",_e="/assets/b26.b7136167.png",ye="/assets/b27.cc8f8644.png",ke="/assets/b28.2bf4d8b9.png",we="/assets/b29.8d301c10.png",ve="/assets/b30.a50bc8f3.png",xe="/assets/b31.4881ca1d.png",Ie="/assets/b32.b857654b.png",Ce="/assets/b33.1125a81c.png",Ae="/assets/b34.2101ce9a.png",Se="/assets/b35.83c5a766.png",qe="/assets/b36.ea1f048c.png",Pe="/assets/b37.b60405a9.png",Oe="/assets/br.bb3418b4.png",Te="/assets/b38.4d73fbe3.png",Ve="/assets/b39.c59ccabe.png",ze="/assets/b40.c1d0ee00.png",Ee="/assets/b41.0c6d7432.png",Me="/assets/b42.66cc353b.png",Ue="/assets/b43.a775b641.png",Ge="/assets/b44.2d540844.png",De="/assets/b45.fe0240c6.png",Fe="/assets/b46.f6b9da14.png",Je=JSON.parse('{"title":"Android Virtual Machine","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_android.md","filePath":"en/guide/pve/pve_android.md","lastUpdated":1747726389000}'),Be={name:"en/guide/pve/pve_android.md"},Ke=s('
Android Virtual Machine ​
Android System Image Download ​
Download links for Android system version 9 and earlier:
International
https://www.fosshub.com/Android-x86.html
https://sourceforge.net/projects/android-x86/files/
Domestic (China)
https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/
Download links for Android system version 10 and later:
https://blissos.org/index.html#download
Virtual Machine Setup ​
Setting up an Android Virtual Machine with version 9 and earlier images ​
This guide demonstrates using:
https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/71931/android-x86_64-9.0-rc2.iso
as an example
1
Template Configuration ​
Create a virtual machine with VMID 100 and select the corresponding storage disk
2
Select the Android image, then choose Linux for Type and choose an option with version 2.6 for Version
3
Select Vmware compatible for Graphic card, other options are default as shown
4
Choose SATA for disk format, allocate at least 30GB of disk space (size can be chosen based on your needs)
5
CPU count should be at least 2 cores
If your host machine supports nested virtualization, choose host for CPU type (verified to work)
If your host machine doesn't support nested virtualization, choose qemu64 for CPU type, and after creating the template, go to Options and uncheck KVM hardware virtualization before starting the virtual machine (no guarantee that system initialization will work properly)
6
Memory should be at least 4GB, enter at least 4096
7
Select vmbr1 for the network bridge, choose VirtIO (paravirtualized) for Model, and uncheck Firewall
8
After clicking the continue button, the template is successfully created. You need to manually start it and enter the VNC interface
9
System Installation ​
After entering the boot menu, select the option starting with Installation
10
Then you need to create disk partitions. If you can't select it, press the keyboard button 'c' to select it
11
Choose not to use GPT format
12
When the empty disk is displayed, select New
13
Select partition type Primary
14
Then you'll be prompted to specify the size of the space. Just press Enter to use all available space
15
Then select Flags, move to Bootable, press Enter until Boot appears under Flags
16
Then move to Write and press Enter to write changes
17
You'll be asked to confirm whether to continue. Type yes and press Enter to continue
18
After a progress bar completes, you'll return to the initial menu. Select Quit to exit the menu, everything is now ready
19
Then you'll return to the UI interface. Use the previously initialized disk and select the OK button
20
Use the arrow keys to select ext4 file system type, then select the OK button
21
Confirm formatting by selecting the Yes button
22
Confirm GRUB boot installation by selecting the OK button
23
Confirm the file system is readable and writable by selecting the OK button
24
After a progress bar runs for some time, it will show that installation was successful. Select Reboot and the OK button
25
After a while, you'll enter the Android logo screen
26
Removing the Image ​
Then there will be a black screen. If it's still black after 3-5 minutes, execute qm stop 100 on the host machine, then start removing the image file.
Remove the installed ISO file by manually clicking on the corresponding CD in the Hardware section of the ProxmoxVE web interface and selecting Remove
ar
Then execute qm start 100 on the host machine again, and you should enter the Android system initialization interface
System Initialization ​
In the initialization interface, select the language and click the confirm button
27
It will try to connect to WiFi. Since our PVE installation uses a completely static network configuration, just skip this and set it up later
31
Click the next button to confirm the time settings
32
Click to cancel screen protection, confirm to skip again
33
After a period of black screen, the main screen application selection will appear. If this interface doesn't appear after waiting 3-5 minutes, restart the virtual machine as before, and it should display after entering VNC
Select Quickstep
34
Network Settings ​
After entering the desktop, you need to set up the network. Click the settings icon in the upper left corner
35
A dropdown appears, click and hold to pull down
36
Click the gear button
37
Enter Network & Internet settings
38
Double-click WIFI with the left mouse button
39
Modify the detected VirtWIFI. Right-click to bring up the selection box, then click Modify network
40
Advanced options appear, click to open hidden options
41
Configure the network settings as shown
IP address 172.16.1.xxx (replace xxx with your desired IP, I used 100 because my vmid is 100 for convenience)
Subnet mask 24
Default gateway 172.16.1.1
DNS 8.8.8.8 or 144.144.144.144
Then click the save button
42
At this point, the settings may still not be applied. Turn off WiFi and then turn it back on, it should then show as connected
43
Then exit to the main interface, click on Google Chrome, and try to open a webpage
44
You can see that opening this guide's URL works without problems, proving that the network is connected
45
Setting up an Android Virtual Machine with version 10 and later images ​
This guide demonstrates using:
https://psychz.dl.sourceforge.net/project/blissos-x86/Official/BlissOS15/Gapps/Generic/Bliss-v15.9.2-x86_64-OFFICIAL-gapps-20241012.iso?viasf=1
as an example
1
Template Configuration ​
The host machine needs to execute the following command to install graphics environment dependencies
shell
apt install libgl1 libegl1 -y
Then start creating the virtual machine by clicking the Create VM button in the upper right corner. Fill in VMID, Name, Resource Pool
2
Select the Android image, then choose Linux for Type and an option with version 2.6 for Version
3
If the host machine has a GPU, select VirGL GPU for Graphic card.
If the host machine doesn't have a GPU, select VirtIO or Vmware compatible for Graphic card.
Select q35 for Machine, select OVMF (UEFI) for BIOS, and select local for EFI Storage.
4
Choose SATA for disk format. How much disk space to allocate is up to you, but at least 30GB is recommended
5
CPU count should be at least 2 cores
If your host machine supports nested virtualization, choose host for CPU type (verified to work)
If your host machine doesn't support nested virtualization, choose qemu64 for CPU type, and after creating the template, go to Options and uncheck KVM hardware virtualization before starting the virtual machine (no guarantee that system initialization will work properly)
6
Memory should be at least 4GB, enter at least 4096
7
Select vmbr1 for the network bridge, choose VirtIO (paravirtualized) for Model, and uncheck Firewall
8
After clicking the continue button, the template is successfully created. You need to manually start it and enter the VNC interface.
System Installation ​
After entering the boot menu, select the option ending with Installation
9
Then you need to create disk partitions. If you can't select it, press the keyboard button 'c' to select it.
10
Choose not to use GPT format, continue using cfdisk format.
11
When the format selection box appears, select gpt.
12
When the empty disk is displayed, select New.
13
Because you need to create an EFI partition, you need to change the size rather than using the default. Change the number to 1 to allocate 1GB of disk space, then press Enter.
14
Then you'll return to the menu bar. Use the arrow keys to select Type, then press Enter to choose the format type for the partition
15
Use the arrow keys to select the first option EFI System, then press Enter
16
Now you're back at the menu bar. In the upper half of the page, you can see the specific partition size and format
17
Then press the down arrow key to select the next empty partition line
18
Select New from the menu bar, then press Enter
19
Here you need to fill in the partition size. Match it with the empty partition size shown in the upper right corner, then press Enter.
20
Return to the menu bar, select Write, press Enter to write the partition.
21
You'll be prompted to enter yes to confirm. Enter it and press Enter.
22
After a progress bar runs, you should return to the menu bar. Select Quit to exit the menu, everything is now ready
23
Then you'll return to the UI interface. Use the previously initialized 1GB disk and select the OK button
24
Use the arrow keys to select fat32 file system type, then select the OK button
25
Confirm not to modify the name by selecting the OK button
26
Confirm formatting by selecting the Yes button
27
Then you'll return to the initial UI bar. Select the second partition that is not 1GB in size and select the OK button
28
Use the arrow keys to select ext4 file system type, then select the OK button
29
Confirm not to modify the name by selecting the OK button
30
Confirm formatting by selecting the Yes button
31
Choose not to use extra space for updates by selecting the No button
32
Confirm GRUB2 EFI BootLoader by selecting the OK button
33
After a progress bar runs for some time, it will show that installation was successful. Select Reboot and the OK button.
34
System Initialization ​
After a while, you'll enter the logo screen.
35
After some more time, you should enter the initial Android interface. You'll see a popup and the time. Hold the left mouse button and swipe up
36
The main screen application selection will appear. Select Quickstep
If this interface doesn't appear after waiting 3-5 minutes, restart the virtual machine, and it should display after entering VNC
37
Removing the Image ​
After the Android interface appears, execute qm stop 100 on the host machine, then start removing the image file.
Remove the installed ISO file by manually clicking on the corresponding CD in the Hardware section of the ProxmoxVE web interface and selecting Remove
br
Then execute qm start 100 on the host machine again, and you should enter the system's initial interface.
Network Settings ​
After entering the desktop, you need to set up the network. Hold the left mouse button in the indicated position and swipe up
38
A bunch of applications will pop up. Find the one called Bliss Ethernet Manager and click to open it
39
Click to open IP Assignment, select Static type, click the OK button to confirm
40
Click to open IP Address, enter 172.16.1.xxx/24 (I used 100 for xxx because my virtual machine VMID is 100 for easy identification), click the OK button to confirm
41
Click to open Gateway Address, enter 172.16.1.1, click the OK button to confirm
42
Click to open DNS Address, enter 8.8.8.8, click the OK button to confirm
43
Then in the application interface, click Interface Up and Refresh, then press the exit key on the keyboard to exit the program
44
Open the browser in the main interface to verify that the network is working properly
45
You can see that opening this guide works without problems, the network is functioning
46
',227),Re=[Ke];function Ne(Ye,We,Le,He,je,Qe){return t(),o("div",null,Re)}const Xe=e(Be,[["render",Ne]]);export{Je as __pageData,Xe as default};
+import{_ as e,v as t,b as o,R as s}from"./chunks/framework.70afa331.js";const a="/assets/a1.662d9415.png",n="/assets/a2.1d7d86db.png",i="/assets/a3.178777a1.png",r="/assets/a4.65c15963.png",p="/assets/a5.01b8514f.png",c="/assets/a6.67efded0.png",d="/assets/a7.b8de9a6c.png",l="/assets/a8.69056d9a.png",h="/assets/a9.d4cc5fc0.png",m="/assets/a10.36860678.png",g="/assets/a11.bbc20080.png",u="/assets/a12.da46fe54.png",f="/assets/a13.b49276aa.png",b="/assets/a14.908480a6.png",_="/assets/a15.9533f30d.png",y="/assets/a16.2257f2d8.png",k="/assets/a17.b57c7755.png",w="/assets/a18.c3a22602.png",v="/assets/a19.1eefd81d.png",x="/assets/a20.24042237.png",I="/assets/a21.2bb37c9a.png",C="/assets/a22.44ab6d75.png",A="/assets/a23.191de0ca.png",S="/assets/a24.d2a9c729.png",q="/assets/a25.3e24d99b.png",P="/assets/a26.2fce6332.png",O="/assets/ar.0d8bb8f3.png",T="/assets/a27.dd61884c.png",V="/assets/a31.6d3a9d85.png",z="/assets/a32.d9973307.png",E="/assets/a33.8b54ce3f.png",M="/assets/a34.07f5cc75.png",U="/assets/a35.78be61d4.png",G="/assets/a36.a36765c2.png",D="/assets/a37.e6740eaa.png",F="/assets/a38.999b4ffb.png",B="/assets/a39.9dac95e1.png",K="/assets/a40.7f5ad4ea.png",R="/assets/a41.bbc5e317.png",N="/assets/a42.de7d1da7.png",Y="/assets/a43.e713599d.png",W="/assets/a44.5c4e5e0a.png",L="/assets/a45.2c32612e.png",H="/assets/b1.c1fdb506.png",j="/assets/b2.519a9bf0.png",Q="/assets/b3.42fd37a2.png",$="/assets/b4.b6d283a7.png",J="/assets/b5.4cd5361f.png",X="/assets/b6.36f0470d.png",Z="/assets/b7.9714bb16.png",ee="/assets/b8.2eb373bf.png",te="/assets/b9.3f01ffdc.png",oe="/assets/b10.52a93636.png",se="/assets/b11.2e525d8d.png",ae="/assets/b12.54c3189d.png",ne="/assets/b13.3b3ae784.png",ie="/assets/b14.662b1a1b.png",re="/assets/b15.0c5536d8.png",pe="/assets/b16.0fbcfcb1.png",ce="/assets/b17.4e7429fe.png",de="/assets/b18.8211f293.png",le="/assets/b19.2128d0fa.png",he="/assets/b20.8a62698b.png",me="/assets/b21.dfe1e8f0.png",ge="/assets/b22.13e3438c.png",ue="/assets/b23.e293a560.png",fe="/assets/b24.23cbc29a.png",be="/assets/b25.f2c2ebd7.png",_e="/assets/b26.b7136167.png",ye="/assets/b27.cc8f8644.png",ke="/assets/b28.2bf4d8b9.png",we="/assets/b29.8d301c10.png",ve="/assets/b30.a50bc8f3.png",xe="/assets/b31.4881ca1d.png",Ie="/assets/b32.b857654b.png",Ce="/assets/b33.1125a81c.png",Ae="/assets/b34.2101ce9a.png",Se="/assets/b35.83c5a766.png",qe="/assets/b36.ea1f048c.png",Pe="/assets/b37.b60405a9.png",Oe="/assets/br.bb3418b4.png",Te="/assets/b38.4d73fbe3.png",Ve="/assets/b39.c59ccabe.png",ze="/assets/b40.c1d0ee00.png",Ee="/assets/b41.0c6d7432.png",Me="/assets/b42.66cc353b.png",Ue="/assets/b43.a775b641.png",Ge="/assets/b44.2d540844.png",De="/assets/b45.fe0240c6.png",Fe="/assets/b46.f6b9da14.png",Je=JSON.parse('{"title":"Android Virtual Machine","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_android.md","filePath":"en/guide/pve/pve_android.md","lastUpdated":1747730955000}'),Be={name:"en/guide/pve/pve_android.md"},Ke=s('
Android Virtual Machine ​
Android System Image Download ​
Download links for Android system version 9 and earlier:
International
https://www.fosshub.com/Android-x86.html
https://sourceforge.net/projects/android-x86/files/
Domestic (China)
https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/
Download links for Android system version 10 and later:
https://blissos.org/index.html#download
Virtual Machine Setup ​
Setting up an Android Virtual Machine with version 9 and earlier images ​
This guide demonstrates using:
https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/71931/android-x86_64-9.0-rc2.iso
as an example
1
Template Configuration ​
Create a virtual machine with VMID 100 and select the corresponding storage disk
2
Select the Android image, then choose Linux for Type and choose an option with version 2.6 for Version
3
Select Vmware compatible for Graphic card, other options are default as shown
4
Choose SATA for disk format, allocate at least 30GB of disk space (size can be chosen based on your needs)
5
CPU count should be at least 2 cores
If your host machine supports nested virtualization, choose host for CPU type (verified to work)
If your host machine doesn't support nested virtualization, choose qemu64 for CPU type, and after creating the template, go to Options and uncheck KVM hardware virtualization before starting the virtual machine (no guarantee that system initialization will work properly)
6
Memory should be at least 4GB, enter at least 4096
7
Select vmbr1 for the network bridge, choose VirtIO (paravirtualized) for Model, and uncheck Firewall
8
After clicking the continue button, the template is successfully created. You need to manually start it and enter the VNC interface
9
System Installation ​
After entering the boot menu, select the option starting with Installation
10
Then you need to create disk partitions. If you can't select it, press the keyboard button 'c' to select it
11
Choose not to use GPT format
12
When the empty disk is displayed, select New
13
Select partition type Primary
14
Then you'll be prompted to specify the size of the space. Just press Enter to use all available space
15
Then select Flags, move to Bootable, press Enter until Boot appears under Flags
16
Then move to Write and press Enter to write changes
17
You'll be asked to confirm whether to continue. Type yes and press Enter to continue
18
After a progress bar completes, you'll return to the initial menu. Select Quit to exit the menu, everything is now ready
19
Then you'll return to the UI interface. Use the previously initialized disk and select the OK button
20
Use the arrow keys to select ext4 file system type, then select the OK button
21
Confirm formatting by selecting the Yes button
22
Confirm GRUB boot installation by selecting the OK button
23
Confirm the file system is readable and writable by selecting the OK button
24
After a progress bar runs for some time, it will show that installation was successful. Select Reboot and the OK button
25
After a while, you'll enter the Android logo screen
26
Removing the Image ​
Then there will be a black screen. If it's still black after 3-5 minutes, execute qm stop 100 on the host machine, then start removing the image file.
Remove the installed ISO file by manually clicking on the corresponding CD in the Hardware section of the ProxmoxVE web interface and selecting Remove
ar
Then execute qm start 100 on the host machine again, and you should enter the Android system initialization interface
System Initialization ​
In the initialization interface, select the language and click the confirm button
27
It will try to connect to WiFi. Since our PVE installation uses a completely static network configuration, just skip this and set it up later
31
Click the next button to confirm the time settings
32
Click to cancel screen protection, confirm to skip again
33
After a period of black screen, the main screen application selection will appear. If this interface doesn't appear after waiting 3-5 minutes, restart the virtual machine as before, and it should display after entering VNC
Select Quickstep
34
Network Settings ​
After entering the desktop, you need to set up the network. Click the settings icon in the upper left corner
35
A dropdown appears, click and hold to pull down
36
Click the gear button
37
Enter Network & Internet settings
38
Double-click WIFI with the left mouse button
39
Modify the detected VirtWIFI. Right-click to bring up the selection box, then click Modify network
40
Advanced options appear, click to open hidden options
41
Configure the network settings as shown
IP address 172.16.1.xxx (replace xxx with your desired IP, I used 100 because my vmid is 100 for convenience)
Subnet mask 24
Default gateway 172.16.1.1
DNS 8.8.8.8 or 144.144.144.144
Then click the save button
42
At this point, the settings may still not be applied. Turn off WiFi and then turn it back on, it should then show as connected
43
Then exit to the main interface, click on Google Chrome, and try to open a webpage
44
You can see that opening this guide's URL works without problems, proving that the network is connected
45
Setting up an Android Virtual Machine with version 10 and later images ​
This guide demonstrates using:
https://psychz.dl.sourceforge.net/project/blissos-x86/Official/BlissOS15/Gapps/Generic/Bliss-v15.9.2-x86_64-OFFICIAL-gapps-20241012.iso?viasf=1
as an example
1
Template Configuration ​
The host machine needs to execute the following command to install graphics environment dependencies
shell
apt install libgl1 libegl1 -y
Then start creating the virtual machine by clicking the Create VM button in the upper right corner. Fill in VMID, Name, Resource Pool
2
Select the Android image, then choose Linux for Type and an option with version 2.6 for Version
3
If the host machine has a GPU, select VirGL GPU for Graphic card.
If the host machine doesn't have a GPU, select VirtIO or Vmware compatible for Graphic card.
Select q35 for Machine, select OVMF (UEFI) for BIOS, and select local for EFI Storage.
4
Choose SATA for disk format. How much disk space to allocate is up to you, but at least 30GB is recommended
5
CPU count should be at least 2 cores
If your host machine supports nested virtualization, choose host for CPU type (verified to work)
If your host machine doesn't support nested virtualization, choose qemu64 for CPU type, and after creating the template, go to Options and uncheck KVM hardware virtualization before starting the virtual machine (no guarantee that system initialization will work properly)
6
Memory should be at least 4GB, enter at least 4096
7
Select vmbr1 for the network bridge, choose VirtIO (paravirtualized) for Model, and uncheck Firewall
8
After clicking the continue button, the template is successfully created. You need to manually start it and enter the VNC interface.
System Installation ​
After entering the boot menu, select the option ending with Installation
9
Then you need to create disk partitions. If you can't select it, press the keyboard button 'c' to select it.
10
Choose not to use GPT format, continue using cfdisk format.
11
When the format selection box appears, select gpt.
12
When the empty disk is displayed, select New.
13
Because you need to create an EFI partition, you need to change the size rather than using the default. Change the number to 1 to allocate 1GB of disk space, then press Enter.
14
Then you'll return to the menu bar. Use the arrow keys to select Type, then press Enter to choose the format type for the partition
15
Use the arrow keys to select the first option EFI System, then press Enter
16
Now you're back at the menu bar. In the upper half of the page, you can see the specific partition size and format
17
Then press the down arrow key to select the next empty partition line
18
Select New from the menu bar, then press Enter
19
Here you need to fill in the partition size. Match it with the empty partition size shown in the upper right corner, then press Enter.
20
Return to the menu bar, select Write, press Enter to write the partition.
21
You'll be prompted to enter yes to confirm. Enter it and press Enter.
22
After a progress bar runs, you should return to the menu bar. Select Quit to exit the menu, everything is now ready
23
Then you'll return to the UI interface. Use the previously initialized 1GB disk and select the OK button
24
Use the arrow keys to select fat32 file system type, then select the OK button
25
Confirm not to modify the name by selecting the OK button
26
Confirm formatting by selecting the Yes button
27
Then you'll return to the initial UI bar. Select the second partition that is not 1GB in size and select the OK button
28
Use the arrow keys to select ext4 file system type, then select the OK button
29
Confirm not to modify the name by selecting the OK button
30
Confirm formatting by selecting the Yes button
31
Choose not to use extra space for updates by selecting the No button
32
Confirm GRUB2 EFI BootLoader by selecting the OK button
33
After a progress bar runs for some time, it will show that installation was successful. Select Reboot and the OK button.
34
System Initialization ​
After a while, you'll enter the logo screen.
35
After some more time, you should enter the initial Android interface. You'll see a popup and the time. Hold the left mouse button and swipe up
36
The main screen application selection will appear. Select Quickstep
If this interface doesn't appear after waiting 3-5 minutes, restart the virtual machine, and it should display after entering VNC
37
Removing the Image ​
After the Android interface appears, execute qm stop 100 on the host machine, then start removing the image file.
Remove the installed ISO file by manually clicking on the corresponding CD in the Hardware section of the ProxmoxVE web interface and selecting Remove
br
Then execute qm start 100 on the host machine again, and you should enter the system's initial interface.
Network Settings ​
After entering the desktop, you need to set up the network. Hold the left mouse button in the indicated position and swipe up
38
A bunch of applications will pop up. Find the one called Bliss Ethernet Manager and click to open it
39
Click to open IP Assignment, select Static type, click the OK button to confirm
40
Click to open IP Address, enter 172.16.1.xxx/24 (I used 100 for xxx because my virtual machine VMID is 100 for easy identification), click the OK button to confirm
41
Click to open Gateway Address, enter 172.16.1.1, click the OK button to confirm
42
Click to open DNS Address, enter 8.8.8.8, click the OK button to confirm
43
Then in the application interface, click Interface Up and Refresh, then press the exit key on the keyboard to exit the program
44
Open the browser in the main interface to verify that the network is working properly
45
You can see that opening this guide works without problems, the network is functioning
46
',227),Re=[Ke];function Ne(Ye,We,Le,He,je,Qe){return t(),o("div",null,Re)}const Xe=e(Be,[["render",Ne]]);export{Je as __pageData,Xe as default};
diff --git a/assets/en_guide_pve_pve_android.md.05709719.lean.js b/assets/en_guide_pve_pve_android.md.a3006536.lean.js
similarity index 99%
rename from assets/en_guide_pve_pve_android.md.05709719.lean.js
rename to assets/en_guide_pve_pve_android.md.a3006536.lean.js
index cc53b719c8..52104d2961 100644
--- a/assets/en_guide_pve_pve_android.md.05709719.lean.js
+++ b/assets/en_guide_pve_pve_android.md.a3006536.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as o,R as s}from"./chunks/framework.70afa331.js";const a="/assets/a1.662d9415.png",n="/assets/a2.1d7d86db.png",i="/assets/a3.178777a1.png",r="/assets/a4.65c15963.png",p="/assets/a5.01b8514f.png",c="/assets/a6.67efded0.png",d="/assets/a7.b8de9a6c.png",l="/assets/a8.69056d9a.png",h="/assets/a9.d4cc5fc0.png",m="/assets/a10.36860678.png",g="/assets/a11.bbc20080.png",u="/assets/a12.da46fe54.png",f="/assets/a13.b49276aa.png",b="/assets/a14.908480a6.png",_="/assets/a15.9533f30d.png",y="/assets/a16.2257f2d8.png",k="/assets/a17.b57c7755.png",w="/assets/a18.c3a22602.png",v="/assets/a19.1eefd81d.png",x="/assets/a20.24042237.png",I="/assets/a21.2bb37c9a.png",C="/assets/a22.44ab6d75.png",A="/assets/a23.191de0ca.png",S="/assets/a24.d2a9c729.png",q="/assets/a25.3e24d99b.png",P="/assets/a26.2fce6332.png",O="/assets/ar.0d8bb8f3.png",T="/assets/a27.dd61884c.png",V="/assets/a31.6d3a9d85.png",z="/assets/a32.d9973307.png",E="/assets/a33.8b54ce3f.png",M="/assets/a34.07f5cc75.png",U="/assets/a35.78be61d4.png",G="/assets/a36.a36765c2.png",D="/assets/a37.e6740eaa.png",F="/assets/a38.999b4ffb.png",B="/assets/a39.9dac95e1.png",K="/assets/a40.7f5ad4ea.png",R="/assets/a41.bbc5e317.png",N="/assets/a42.de7d1da7.png",Y="/assets/a43.e713599d.png",W="/assets/a44.5c4e5e0a.png",L="/assets/a45.2c32612e.png",H="/assets/b1.c1fdb506.png",j="/assets/b2.519a9bf0.png",Q="/assets/b3.42fd37a2.png",$="/assets/b4.b6d283a7.png",J="/assets/b5.4cd5361f.png",X="/assets/b6.36f0470d.png",Z="/assets/b7.9714bb16.png",ee="/assets/b8.2eb373bf.png",te="/assets/b9.3f01ffdc.png",oe="/assets/b10.52a93636.png",se="/assets/b11.2e525d8d.png",ae="/assets/b12.54c3189d.png",ne="/assets/b13.3b3ae784.png",ie="/assets/b14.662b1a1b.png",re="/assets/b15.0c5536d8.png",pe="/assets/b16.0fbcfcb1.png",ce="/assets/b17.4e7429fe.png",de="/assets/b18.8211f293.png",le="/assets/b19.2128d0fa.png",he="/assets/b20.8a62698b.png",me="/assets/b21.dfe1e8f0.png",ge="/assets/b22.13e3438c.png",ue="/assets/b23.e293a560.png",fe="/assets/b24.23cbc29a.png",be="/assets/b25.f2c2ebd7.png",_e="/assets/b26.b7136167.png",ye="/assets/b27.cc8f8644.png",ke="/assets/b28.2bf4d8b9.png",we="/assets/b29.8d301c10.png",ve="/assets/b30.a50bc8f3.png",xe="/assets/b31.4881ca1d.png",Ie="/assets/b32.b857654b.png",Ce="/assets/b33.1125a81c.png",Ae="/assets/b34.2101ce9a.png",Se="/assets/b35.83c5a766.png",qe="/assets/b36.ea1f048c.png",Pe="/assets/b37.b60405a9.png",Oe="/assets/br.bb3418b4.png",Te="/assets/b38.4d73fbe3.png",Ve="/assets/b39.c59ccabe.png",ze="/assets/b40.c1d0ee00.png",Ee="/assets/b41.0c6d7432.png",Me="/assets/b42.66cc353b.png",Ue="/assets/b43.a775b641.png",Ge="/assets/b44.2d540844.png",De="/assets/b45.fe0240c6.png",Fe="/assets/b46.f6b9da14.png",Je=JSON.parse('{"title":"Android Virtual Machine","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_android.md","filePath":"en/guide/pve/pve_android.md","lastUpdated":1747726389000}'),Be={name:"en/guide/pve/pve_android.md"},Ke=s('
Android Virtual Machine ​
Android System Image Download ​
Download links for Android system version 9 and earlier:
International
https://www.fosshub.com/Android-x86.html
https://sourceforge.net/projects/android-x86/files/
Domestic (China)
https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/
Download links for Android system version 10 and later:
https://blissos.org/index.html#download
Virtual Machine Setup ​
Setting up an Android Virtual Machine with version 9 and earlier images ​
This guide demonstrates using:
https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/71931/android-x86_64-9.0-rc2.iso
as an example
1
Template Configuration ​
Create a virtual machine with VMID 100 and select the corresponding storage disk
2
Select the Android image, then choose Linux for Type and choose an option with version 2.6 for Version
3
Select Vmware compatible for Graphic card, other options are default as shown
4
Choose SATA for disk format, allocate at least 30GB of disk space (size can be chosen based on your needs)
5
CPU count should be at least 2 cores
If your host machine supports nested virtualization, choose host for CPU type (verified to work)
If your host machine doesn't support nested virtualization, choose qemu64 for CPU type, and after creating the template, go to Options and uncheck KVM hardware virtualization before starting the virtual machine (no guarantee that system initialization will work properly)
6
Memory should be at least 4GB, enter at least 4096
7
Select vmbr1 for the network bridge, choose VirtIO (paravirtualized) for Model, and uncheck Firewall
8
After clicking the continue button, the template is successfully created. You need to manually start it and enter the VNC interface
9
System Installation ​
After entering the boot menu, select the option starting with Installation
10
Then you need to create disk partitions. If you can't select it, press the keyboard button 'c' to select it
11
Choose not to use GPT format
12
When the empty disk is displayed, select New
13
Select partition type Primary
14
Then you'll be prompted to specify the size of the space. Just press Enter to use all available space
15
Then select Flags, move to Bootable, press Enter until Boot appears under Flags
16
Then move to Write and press Enter to write changes
17
You'll be asked to confirm whether to continue. Type yes and press Enter to continue
18
After a progress bar completes, you'll return to the initial menu. Select Quit to exit the menu, everything is now ready
19
Then you'll return to the UI interface. Use the previously initialized disk and select the OK button
20
Use the arrow keys to select ext4 file system type, then select the OK button
21
Confirm formatting by selecting the Yes button
22
Confirm GRUB boot installation by selecting the OK button
23
Confirm the file system is readable and writable by selecting the OK button
24
After a progress bar runs for some time, it will show that installation was successful. Select Reboot and the OK button
25
After a while, you'll enter the Android logo screen
26
Removing the Image ​
Then there will be a black screen. If it's still black after 3-5 minutes, execute qm stop 100 on the host machine, then start removing the image file.
Remove the installed ISO file by manually clicking on the corresponding CD in the Hardware section of the ProxmoxVE web interface and selecting Remove
ar
Then execute qm start 100 on the host machine again, and you should enter the Android system initialization interface
System Initialization ​
In the initialization interface, select the language and click the confirm button
27
It will try to connect to WiFi. Since our PVE installation uses a completely static network configuration, just skip this and set it up later
31
Click the next button to confirm the time settings
32
Click to cancel screen protection, confirm to skip again
33
After a period of black screen, the main screen application selection will appear. If this interface doesn't appear after waiting 3-5 minutes, restart the virtual machine as before, and it should display after entering VNC
Select Quickstep
34
Network Settings ​
After entering the desktop, you need to set up the network. Click the settings icon in the upper left corner
35
A dropdown appears, click and hold to pull down
36
Click the gear button
37
Enter Network & Internet settings
38
Double-click WIFI with the left mouse button
39
Modify the detected VirtWIFI. Right-click to bring up the selection box, then click Modify network
40
Advanced options appear, click to open hidden options
41
Configure the network settings as shown
IP address 172.16.1.xxx (replace xxx with your desired IP, I used 100 because my vmid is 100 for convenience)
Subnet mask 24
Default gateway 172.16.1.1
DNS 8.8.8.8 or 144.144.144.144
Then click the save button
42
At this point, the settings may still not be applied. Turn off WiFi and then turn it back on, it should then show as connected
43
Then exit to the main interface, click on Google Chrome, and try to open a webpage
44
You can see that opening this guide's URL works without problems, proving that the network is connected
45
Setting up an Android Virtual Machine with version 10 and later images ​
This guide demonstrates using:
https://psychz.dl.sourceforge.net/project/blissos-x86/Official/BlissOS15/Gapps/Generic/Bliss-v15.9.2-x86_64-OFFICIAL-gapps-20241012.iso?viasf=1
as an example
1
Template Configuration ​
The host machine needs to execute the following command to install graphics environment dependencies
shell
apt install libgl1 libegl1 -y
Then start creating the virtual machine by clicking the Create VM button in the upper right corner. Fill in VMID, Name, Resource Pool
2
Select the Android image, then choose Linux for Type and an option with version 2.6 for Version
3
If the host machine has a GPU, select VirGL GPU for Graphic card.
If the host machine doesn't have a GPU, select VirtIO or Vmware compatible for Graphic card.
Select q35 for Machine, select OVMF (UEFI) for BIOS, and select local for EFI Storage.
4
Choose SATA for disk format. How much disk space to allocate is up to you, but at least 30GB is recommended
5
CPU count should be at least 2 cores
If your host machine supports nested virtualization, choose host for CPU type (verified to work)
If your host machine doesn't support nested virtualization, choose qemu64 for CPU type, and after creating the template, go to Options and uncheck KVM hardware virtualization before starting the virtual machine (no guarantee that system initialization will work properly)
6
Memory should be at least 4GB, enter at least 4096
7
Select vmbr1 for the network bridge, choose VirtIO (paravirtualized) for Model, and uncheck Firewall
8
After clicking the continue button, the template is successfully created. You need to manually start it and enter the VNC interface.
System Installation ​
After entering the boot menu, select the option ending with Installation
9
Then you need to create disk partitions. If you can't select it, press the keyboard button 'c' to select it.
10
Choose not to use GPT format, continue using cfdisk format.
11
When the format selection box appears, select gpt.
12
When the empty disk is displayed, select New.
13
Because you need to create an EFI partition, you need to change the size rather than using the default. Change the number to 1 to allocate 1GB of disk space, then press Enter.
14
Then you'll return to the menu bar. Use the arrow keys to select Type, then press Enter to choose the format type for the partition
15
Use the arrow keys to select the first option EFI System, then press Enter
16
Now you're back at the menu bar. In the upper half of the page, you can see the specific partition size and format
17
Then press the down arrow key to select the next empty partition line
18
Select New from the menu bar, then press Enter
19
Here you need to fill in the partition size. Match it with the empty partition size shown in the upper right corner, then press Enter.
20
Return to the menu bar, select Write, press Enter to write the partition.
21
You'll be prompted to enter yes to confirm. Enter it and press Enter.
22
After a progress bar runs, you should return to the menu bar. Select Quit to exit the menu, everything is now ready
23
Then you'll return to the UI interface. Use the previously initialized 1GB disk and select the OK button
24
Use the arrow keys to select fat32 file system type, then select the OK button
25
Confirm not to modify the name by selecting the OK button
26
Confirm formatting by selecting the Yes button
27
Then you'll return to the initial UI bar. Select the second partition that is not 1GB in size and select the OK button
28
Use the arrow keys to select ext4 file system type, then select the OK button
29
Confirm not to modify the name by selecting the OK button
30
Confirm formatting by selecting the Yes button
31
Choose not to use extra space for updates by selecting the No button
32
Confirm GRUB2 EFI BootLoader by selecting the OK button
33
After a progress bar runs for some time, it will show that installation was successful. Select Reboot and the OK button.
34
System Initialization ​
After a while, you'll enter the logo screen.
35
After some more time, you should enter the initial Android interface. You'll see a popup and the time. Hold the left mouse button and swipe up
36
The main screen application selection will appear. Select Quickstep
If this interface doesn't appear after waiting 3-5 minutes, restart the virtual machine, and it should display after entering VNC
37
Removing the Image ​
After the Android interface appears, execute qm stop 100 on the host machine, then start removing the image file.
Remove the installed ISO file by manually clicking on the corresponding CD in the Hardware section of the ProxmoxVE web interface and selecting Remove
br
Then execute qm start 100 on the host machine again, and you should enter the system's initial interface.
Network Settings ​
After entering the desktop, you need to set up the network. Hold the left mouse button in the indicated position and swipe up
38
A bunch of applications will pop up. Find the one called Bliss Ethernet Manager and click to open it
39
Click to open IP Assignment, select Static type, click the OK button to confirm
40
Click to open IP Address, enter 172.16.1.xxx/24 (I used 100 for xxx because my virtual machine VMID is 100 for easy identification), click the OK button to confirm
41
Click to open Gateway Address, enter 172.16.1.1, click the OK button to confirm
42
Click to open DNS Address, enter 8.8.8.8, click the OK button to confirm
43
Then in the application interface, click Interface Up and Refresh, then press the exit key on the keyboard to exit the program
44
Open the browser in the main interface to verify that the network is working properly
45
You can see that opening this guide works without problems, the network is functioning
46
',227),Re=[Ke];function Ne(Ye,We,Le,He,je,Qe){return t(),o("div",null,Re)}const Xe=e(Be,[["render",Ne]]);export{Je as __pageData,Xe as default};
+import{_ as e,v as t,b as o,R as s}from"./chunks/framework.70afa331.js";const a="/assets/a1.662d9415.png",n="/assets/a2.1d7d86db.png",i="/assets/a3.178777a1.png",r="/assets/a4.65c15963.png",p="/assets/a5.01b8514f.png",c="/assets/a6.67efded0.png",d="/assets/a7.b8de9a6c.png",l="/assets/a8.69056d9a.png",h="/assets/a9.d4cc5fc0.png",m="/assets/a10.36860678.png",g="/assets/a11.bbc20080.png",u="/assets/a12.da46fe54.png",f="/assets/a13.b49276aa.png",b="/assets/a14.908480a6.png",_="/assets/a15.9533f30d.png",y="/assets/a16.2257f2d8.png",k="/assets/a17.b57c7755.png",w="/assets/a18.c3a22602.png",v="/assets/a19.1eefd81d.png",x="/assets/a20.24042237.png",I="/assets/a21.2bb37c9a.png",C="/assets/a22.44ab6d75.png",A="/assets/a23.191de0ca.png",S="/assets/a24.d2a9c729.png",q="/assets/a25.3e24d99b.png",P="/assets/a26.2fce6332.png",O="/assets/ar.0d8bb8f3.png",T="/assets/a27.dd61884c.png",V="/assets/a31.6d3a9d85.png",z="/assets/a32.d9973307.png",E="/assets/a33.8b54ce3f.png",M="/assets/a34.07f5cc75.png",U="/assets/a35.78be61d4.png",G="/assets/a36.a36765c2.png",D="/assets/a37.e6740eaa.png",F="/assets/a38.999b4ffb.png",B="/assets/a39.9dac95e1.png",K="/assets/a40.7f5ad4ea.png",R="/assets/a41.bbc5e317.png",N="/assets/a42.de7d1da7.png",Y="/assets/a43.e713599d.png",W="/assets/a44.5c4e5e0a.png",L="/assets/a45.2c32612e.png",H="/assets/b1.c1fdb506.png",j="/assets/b2.519a9bf0.png",Q="/assets/b3.42fd37a2.png",$="/assets/b4.b6d283a7.png",J="/assets/b5.4cd5361f.png",X="/assets/b6.36f0470d.png",Z="/assets/b7.9714bb16.png",ee="/assets/b8.2eb373bf.png",te="/assets/b9.3f01ffdc.png",oe="/assets/b10.52a93636.png",se="/assets/b11.2e525d8d.png",ae="/assets/b12.54c3189d.png",ne="/assets/b13.3b3ae784.png",ie="/assets/b14.662b1a1b.png",re="/assets/b15.0c5536d8.png",pe="/assets/b16.0fbcfcb1.png",ce="/assets/b17.4e7429fe.png",de="/assets/b18.8211f293.png",le="/assets/b19.2128d0fa.png",he="/assets/b20.8a62698b.png",me="/assets/b21.dfe1e8f0.png",ge="/assets/b22.13e3438c.png",ue="/assets/b23.e293a560.png",fe="/assets/b24.23cbc29a.png",be="/assets/b25.f2c2ebd7.png",_e="/assets/b26.b7136167.png",ye="/assets/b27.cc8f8644.png",ke="/assets/b28.2bf4d8b9.png",we="/assets/b29.8d301c10.png",ve="/assets/b30.a50bc8f3.png",xe="/assets/b31.4881ca1d.png",Ie="/assets/b32.b857654b.png",Ce="/assets/b33.1125a81c.png",Ae="/assets/b34.2101ce9a.png",Se="/assets/b35.83c5a766.png",qe="/assets/b36.ea1f048c.png",Pe="/assets/b37.b60405a9.png",Oe="/assets/br.bb3418b4.png",Te="/assets/b38.4d73fbe3.png",Ve="/assets/b39.c59ccabe.png",ze="/assets/b40.c1d0ee00.png",Ee="/assets/b41.0c6d7432.png",Me="/assets/b42.66cc353b.png",Ue="/assets/b43.a775b641.png",Ge="/assets/b44.2d540844.png",De="/assets/b45.fe0240c6.png",Fe="/assets/b46.f6b9da14.png",Je=JSON.parse('{"title":"Android Virtual Machine","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_android.md","filePath":"en/guide/pve/pve_android.md","lastUpdated":1747730955000}'),Be={name:"en/guide/pve/pve_android.md"},Ke=s('
Android Virtual Machine ​
Android System Image Download ​
Download links for Android system version 9 and earlier:
International
https://www.fosshub.com/Android-x86.html
https://sourceforge.net/projects/android-x86/files/
Domestic (China)
https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/
Download links for Android system version 10 and later:
https://blissos.org/index.html#download
Virtual Machine Setup ​
Setting up an Android Virtual Machine with version 9 and earlier images ​
This guide demonstrates using:
https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/71931/android-x86_64-9.0-rc2.iso
as an example
1
Template Configuration ​
Create a virtual machine with VMID 100 and select the corresponding storage disk
2
Select the Android image, then choose Linux for Type and choose an option with version 2.6 for Version
3
Select Vmware compatible for Graphic card, other options are default as shown
4
Choose SATA for disk format, allocate at least 30GB of disk space (size can be chosen based on your needs)
5
CPU count should be at least 2 cores
If your host machine supports nested virtualization, choose host for CPU type (verified to work)
If your host machine doesn't support nested virtualization, choose qemu64 for CPU type, and after creating the template, go to Options and uncheck KVM hardware virtualization before starting the virtual machine (no guarantee that system initialization will work properly)
6
Memory should be at least 4GB, enter at least 4096
7
Select vmbr1 for the network bridge, choose VirtIO (paravirtualized) for Model, and uncheck Firewall
8
After clicking the continue button, the template is successfully created. You need to manually start it and enter the VNC interface
9
System Installation ​
After entering the boot menu, select the option starting with Installation
10
Then you need to create disk partitions. If you can't select it, press the keyboard button 'c' to select it
11
Choose not to use GPT format
12
When the empty disk is displayed, select New
13
Select partition type Primary
14
Then you'll be prompted to specify the size of the space. Just press Enter to use all available space
15
Then select Flags, move to Bootable, press Enter until Boot appears under Flags
16
Then move to Write and press Enter to write changes
17
You'll be asked to confirm whether to continue. Type yes and press Enter to continue
18
After a progress bar completes, you'll return to the initial menu. Select Quit to exit the menu, everything is now ready
19
Then you'll return to the UI interface. Use the previously initialized disk and select the OK button
20
Use the arrow keys to select ext4 file system type, then select the OK button
21
Confirm formatting by selecting the Yes button
22
Confirm GRUB boot installation by selecting the OK button
23
Confirm the file system is readable and writable by selecting the OK button
24
After a progress bar runs for some time, it will show that installation was successful. Select Reboot and the OK button
25
After a while, you'll enter the Android logo screen
26
Removing the Image ​
Then there will be a black screen. If it's still black after 3-5 minutes, execute qm stop 100 on the host machine, then start removing the image file.
Remove the installed ISO file by manually clicking on the corresponding CD in the Hardware section of the ProxmoxVE web interface and selecting Remove
ar
Then execute qm start 100 on the host machine again, and you should enter the Android system initialization interface
System Initialization ​
In the initialization interface, select the language and click the confirm button
27
It will try to connect to WiFi. Since our PVE installation uses a completely static network configuration, just skip this and set it up later
31
Click the next button to confirm the time settings
32
Click to cancel screen protection, confirm to skip again
33
After a period of black screen, the main screen application selection will appear. If this interface doesn't appear after waiting 3-5 minutes, restart the virtual machine as before, and it should display after entering VNC
Select Quickstep
34
Network Settings ​
After entering the desktop, you need to set up the network. Click the settings icon in the upper left corner
35
A dropdown appears, click and hold to pull down
36
Click the gear button
37
Enter Network & Internet settings
38
Double-click WIFI with the left mouse button
39
Modify the detected VirtWIFI. Right-click to bring up the selection box, then click Modify network
40
Advanced options appear, click to open hidden options
41
Configure the network settings as shown
IP address 172.16.1.xxx (replace xxx with your desired IP, I used 100 because my vmid is 100 for convenience)
Subnet mask 24
Default gateway 172.16.1.1
DNS 8.8.8.8 or 144.144.144.144
Then click the save button
42
At this point, the settings may still not be applied. Turn off WiFi and then turn it back on, it should then show as connected
43
Then exit to the main interface, click on Google Chrome, and try to open a webpage
44
You can see that opening this guide's URL works without problems, proving that the network is connected
45
Setting up an Android Virtual Machine with version 10 and later images ​
This guide demonstrates using:
https://psychz.dl.sourceforge.net/project/blissos-x86/Official/BlissOS15/Gapps/Generic/Bliss-v15.9.2-x86_64-OFFICIAL-gapps-20241012.iso?viasf=1
as an example
1
Template Configuration ​
The host machine needs to execute the following command to install graphics environment dependencies
shell
apt install libgl1 libegl1 -y
Then start creating the virtual machine by clicking the Create VM button in the upper right corner. Fill in VMID, Name, Resource Pool
2
Select the Android image, then choose Linux for Type and an option with version 2.6 for Version
3
If the host machine has a GPU, select VirGL GPU for Graphic card.
If the host machine doesn't have a GPU, select VirtIO or Vmware compatible for Graphic card.
Select q35 for Machine, select OVMF (UEFI) for BIOS, and select local for EFI Storage.
4
Choose SATA for disk format. How much disk space to allocate is up to you, but at least 30GB is recommended
5
CPU count should be at least 2 cores
If your host machine supports nested virtualization, choose host for CPU type (verified to work)
If your host machine doesn't support nested virtualization, choose qemu64 for CPU type, and after creating the template, go to Options and uncheck KVM hardware virtualization before starting the virtual machine (no guarantee that system initialization will work properly)
6
Memory should be at least 4GB, enter at least 4096
7
Select vmbr1 for the network bridge, choose VirtIO (paravirtualized) for Model, and uncheck Firewall
8
After clicking the continue button, the template is successfully created. You need to manually start it and enter the VNC interface.
System Installation ​
After entering the boot menu, select the option ending with Installation
9
Then you need to create disk partitions. If you can't select it, press the keyboard button 'c' to select it.
10
Choose not to use GPT format, continue using cfdisk format.
11
When the format selection box appears, select gpt.
12
When the empty disk is displayed, select New.
13
Because you need to create an EFI partition, you need to change the size rather than using the default. Change the number to 1 to allocate 1GB of disk space, then press Enter.
14
Then you'll return to the menu bar. Use the arrow keys to select Type, then press Enter to choose the format type for the partition
15
Use the arrow keys to select the first option EFI System, then press Enter
16
Now you're back at the menu bar. In the upper half of the page, you can see the specific partition size and format
17
Then press the down arrow key to select the next empty partition line
18
Select New from the menu bar, then press Enter
19
Here you need to fill in the partition size. Match it with the empty partition size shown in the upper right corner, then press Enter.
20
Return to the menu bar, select Write, press Enter to write the partition.
21
You'll be prompted to enter yes to confirm. Enter it and press Enter.
22
After a progress bar runs, you should return to the menu bar. Select Quit to exit the menu, everything is now ready
23
Then you'll return to the UI interface. Use the previously initialized 1GB disk and select the OK button
24
Use the arrow keys to select fat32 file system type, then select the OK button
25
Confirm not to modify the name by selecting the OK button
26
Confirm formatting by selecting the Yes button
27
Then you'll return to the initial UI bar. Select the second partition that is not 1GB in size and select the OK button
28
Use the arrow keys to select ext4 file system type, then select the OK button
29
Confirm not to modify the name by selecting the OK button
30
Confirm formatting by selecting the Yes button
31
Choose not to use extra space for updates by selecting the No button
32
Confirm GRUB2 EFI BootLoader by selecting the OK button
33
After a progress bar runs for some time, it will show that installation was successful. Select Reboot and the OK button.
34
System Initialization ​
After a while, you'll enter the logo screen.
35
After some more time, you should enter the initial Android interface. You'll see a popup and the time. Hold the left mouse button and swipe up
36
The main screen application selection will appear. Select Quickstep
If this interface doesn't appear after waiting 3-5 minutes, restart the virtual machine, and it should display after entering VNC
37
Removing the Image ​
After the Android interface appears, execute qm stop 100 on the host machine, then start removing the image file.
Remove the installed ISO file by manually clicking on the corresponding CD in the Hardware section of the ProxmoxVE web interface and selecting Remove
br
Then execute qm start 100 on the host machine again, and you should enter the system's initial interface.
Network Settings ​
After entering the desktop, you need to set up the network. Hold the left mouse button in the indicated position and swipe up
38
A bunch of applications will pop up. Find the one called Bliss Ethernet Manager and click to open it
39
Click to open IP Assignment, select Static type, click the OK button to confirm
40
Click to open IP Address, enter 172.16.1.xxx/24 (I used 100 for xxx because my virtual machine VMID is 100 for easy identification), click the OK button to confirm
41
Click to open Gateway Address, enter 172.16.1.1, click the OK button to confirm
42
Click to open DNS Address, enter 8.8.8.8, click the OK button to confirm
43
Then in the application interface, click Interface Up and Refresh, then press the exit key on the keyboard to exit the program
44
Open the browser in the main interface to verify that the network is working properly
45
You can see that opening this guide works without problems, the network is functioning
46
',227),Re=[Ke];function Ne(Ye,We,Le,He,je,Qe){return t(),o("div",null,Re)}const Xe=e(Be,[["render",Ne]]);export{Je as __pageData,Xe as default};
diff --git a/assets/en_guide_pve_pve_custom.md.3d92b33c.js b/assets/en_guide_pve_pve_custom.md.1a51ac96.js
similarity index 99%
rename from assets/en_guide_pve_pve_custom.md.3d92b33c.js
rename to assets/en_guide_pve_pve_custom.md.1a51ac96.js
index 8fd606b1aa..8e2c5769de 100644
--- a/assets/en_guide_pve_pve_custom.md.3d92b33c.js
+++ b/assets/en_guide_pve_pve_custom.md.1a51ac96.js
@@ -1,4 +1,4 @@
-import{_ as s,v as e,b as a,R as o}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Customized partitions","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_custom.md","filePath":"en/guide/pve/pve_custom.md","lastUpdated":1747726389000}'),n={name:"en/guide/pve/pve_custom.md"},t=o(`
Customized partitions ​
Installing Proxmox VE 7 on a non-Debian system ​
Minimum local hardware requirements are the same as for the previous normal installation.
You need to install docker first.
curl -sSL https://get.docker.com/ | sh
+import{_ as s,v as e,b as a,R as o}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Customized partitions","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_custom.md","filePath":"en/guide/pve/pve_custom.md","lastUpdated":1747730955000}'),n={name:"en/guide/pve/pve_custom.md"},t=o(`
Customized partitions ​
Installing Proxmox VE 7 on a non-Debian system ​
Minimum local hardware requirements are the same as for the previous normal installation.
You need to install docker first.
curl -sSL https://get.docker.com/ | sh
 curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-linux-$(uname -m)" -o /usr/local/bin/docker-compose
 chmod +x /usr/local/bin/docker-compose
 docker-compose --version
Then use uname -m to query the architecture and use the command corresponding to the architecture
The opened PVE panel information is:
Login username and password are both root, after logging in be sure to use web SSH to change the password to avoid being blown up.
When using host SSH, be sure to log into the corresponding https://IPV4:8006 to use SSH on the web panel, do not use the host's port 22 to manipulate the PVE.
Because the SSH on the web panel is inside Docker, it does not support subsequent one-click configurations, so please configure your own gateway, etc. to use it.
X86 architecture
bash
docker run -idt --network host \\
diff --git a/assets/en_guide_pve_pve_custom.md.3d92b33c.lean.js b/assets/en_guide_pve_pve_custom.md.1a51ac96.lean.js
similarity index 99%
rename from assets/en_guide_pve_pve_custom.md.3d92b33c.lean.js
rename to assets/en_guide_pve_pve_custom.md.1a51ac96.lean.js
index 8fd606b1aa..8e2c5769de 100644
--- a/assets/en_guide_pve_pve_custom.md.3d92b33c.lean.js
+++ b/assets/en_guide_pve_pve_custom.md.1a51ac96.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as e,b as a,R as o}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Customized partitions","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_custom.md","filePath":"en/guide/pve/pve_custom.md","lastUpdated":1747726389000}'),n={name:"en/guide/pve/pve_custom.md"},t=o(`
Customized partitions ​
Installing Proxmox VE 7 on a non-Debian system ​
Minimum local hardware requirements are the same as for the previous normal installation.
You need to install docker first.
curl -sSL https://get.docker.com/ | sh
+import{_ as s,v as e,b as a,R as o}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Customized partitions","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_custom.md","filePath":"en/guide/pve/pve_custom.md","lastUpdated":1747730955000}'),n={name:"en/guide/pve/pve_custom.md"},t=o(`
Customized partitions ​
Installing Proxmox VE 7 on a non-Debian system ​
Minimum local hardware requirements are the same as for the previous normal installation.
You need to install docker first.
curl -sSL https://get.docker.com/ | sh
 curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-linux-$(uname -m)" -o /usr/local/bin/docker-compose
 chmod +x /usr/local/bin/docker-compose
 docker-compose --version
Then use uname -m to query the architecture and use the command corresponding to the architecture
The opened PVE panel information is:
Login username and password are both root, after logging in be sure to use web SSH to change the password to avoid being blown up.
When using host SSH, be sure to log into the corresponding https://IPV4:8006 to use SSH on the web panel, do not use the host's port 22 to manipulate the PVE.
Because the SSH on the web panel is inside Docker, it does not support subsequent one-click configurations, so please configure your own gateway, etc. to use it.
X86 architecture
bash
docker run -idt --network host \\
diff --git a/assets/en_guide_pve_pve_install.md.9a42f3ee.js b/assets/en_guide_pve_pve_install.md.ea124862.js
similarity index 99%
rename from assets/en_guide_pve_pve_install.md.9a42f3ee.js
rename to assets/en_guide_pve_pve_install.md.ea124862.js
index 594a1c6113..ea5f38193a 100644
--- a/assets/en_guide_pve_pve_install.md.9a42f3ee.js
+++ b/assets/en_guide_pve_pve_install.md.ea124862.js
@@ -1 +1 @@
-import{_ as e,v as t,b as o,R as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"PVE Body Installation","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_install.md","filePath":"en/guide/pve/pve_install.md","lastUpdated":1747726389000}'),a={name:"en/guide/pve/pve_install.md"},n=s('
PVE Body Installation ​
If you don't know how to choose an option during installation, just press enter.
TIP
For low-configuration hosts, it is recommended to check the contents of the Custom partition after all the content has been installed to perform memory tuning and reduce the memory footprint.
One-click PVE installation ​
TIP
Suggest debian12, the actual test part of the independent server debian11 system will appear a reboot network will be lost, debian12 does not have such a problem!
  • The installation is the latest PVE from the apt source at the moment.
  • For example, debian10 is pve6.4, debian11 is pve7.x, debian12 is pve8.x
  • Changes to the /etc/hosts file (to fix the wrong hostname setting for merchants and to add the required content for PVE)
  • /etc/cloud/cloud.cfg file modification (to avoid overwriting modified hostname etc.)
  • /etc/network/interfaces file modification (fix auto, dhcp type to static, add vmbr0 gateway)
  • Detect whether it is China IP, if it is China IP use Tsinghua mirror source, otherwise use the official source, and at the same time deal with the source of apt and the corresponding nameserver, to avoid disconnections
  • Create vmbr0 (independent IP gateway), the host allows addr and gateway for intranet IP or extranet IP, has been automatically recognized
  • vmbr0 creation support to open pure IPV4, pure IPV6, dual-stack virtual machine, automatic identification of IPV4 address and IPV6 address, automatic identification of the corresponding IP interval
  • Installation of the necessary toolkit for PVE to open a virtual machine
  • x86_64 replace enterprise subscriptions in apt sources with community sources, arm sources built using third-party patches for fixes
  • Print query Linux system kernel and PVE kernel installed or not
  • Setting up DNS detection 8.8.8.8.8 for boot add DNS systemd service
  • Download PVE and printout of login information after adding APT source link for PVE
All modified files have been set to read-only mode to avoid overwriting after reboot.
If you want to modify the file, please use chattr -i file path to cancel the read-only lock, and run chattr +i file path to lock the read-only lock when you finish modifying the file.
You will be prompted to reboot your system once during the execution process, After rebooting, be sure to wait at least 20 seconds to make sure the system does not reboot automatically again.
Because the original environment may be missing ifupdown or ifupdown2 environment, there is a self-installation daemon loaded for the installation, after the installation of the system will automatically reboot the system again, wait for 20 seconds without reboot to ensure that the installation has been run.
If the host itself exists SLAAC assigned IPV6 address, will be able to choose whether to use the largest IPV6 subnet range, the default carriage return does not use the largest IPV6 subnet range only use the local IPV6, if you subsequently need to attach a separate IPV6 address to the virtual machine/container, the option must be selected y.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh
or
shell
bash install_pve.sh
TIP
After successful installation, the web page may not be safe to open, click on Advanced or More Options and insist on accessing it!
The login information is your SSH account and password.
Pre-configure the environment ​
  • Creating a resource pool mypool
  • Remove the subscription popup
  • Attempt to enable hardware passthrough
  • Detect and auto-install AppArmor modules.
  • Before rebooting the system, it is recommended to hook up nezha probe to facilitate the use of the command line in the background without SSH, to avoid the possibility that SSH may lead to the loss of the root password after the reboot due to the merchant's strange presets.
  • Before executing reboot, you need to wait for the background task to finish executing, some host system apt command execution is very slow, you have to wait for a while to finish executing, of course, most of the machines are not so bad!
Command:
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)
Automatically configure the host's gateway ​
WARNING
Before using this command, please make sure that you have restarted the server and that PVE can use the WEB terminal normally before executing this command. Do not execute this command immediately after restarting the machine, wait for at least 1 minute after the WEB terminal is successfully started before executing this command. If the WEB side doesn't start, run systemctl status pveproxy to see if it starts, if it's stuck, run systemctl start pveproxy to start the WEB side.
TIP
This step is most likely to cause SSH disconnections, the reason is to modify the network without waiting for the PVE kernel to start, which will result in setting conflicts, so wait at least a few minutes until the kernel is started, that is, the WEB side is started successfully before execution.
TIP
If the host needs to attach an IPV6 tunnel (add an IPV6 subnet to a host that does not have an IPV6 address) before executing this command, please check the IPV6 free subnet attachment section to attach to the corresponding configuration file, but please ignore 'initial environment modifications' and attach directly, and then execute the following one-click gateway configuration commands after verifying that you have an IPV6 address.
  • If vmbr0 is not created, it is automatically created with the same logic as the main installation
  • Create vmbr1 (NAT gateway) to support IPV4 servers that open NAT for IPV6 networks with NAT.
  • Create vmbr2 (standalone IPV6 gateway), use ndppd to solve the problem of MAC verification of IPV6 addresses by the host, support the opening of servers with standalone IPV6 networks.
  • If you want to see the complete settings, you can execute cat /etc/network/interfaces to see, if you need to modify the gateway you need to modify the file, the web site can not be modified!
  • Load iptables and set back to source and allow NAT port forwarding.
In short, vmbr0 is responsible for v4 standalone IPs, and vmbr1 is responsible for complex v4/v6 NATs, vmbr2 is responsible for v6 standalone IPs.
Open independent IPV4 virtual machine using vmbr0, gateway with the host, IPV4/CIDR using the same network segment address and the same subnet mask, using the host's unbound IPV4 address for IPV4/CIDR, of course, if the subsequent use of this script does not need to pay attention to this point of the nuances of the thing
Use vmbr1 for IPV4 VM with NAT, 172.16.1.1 for gateway, 172.16.1.x/24 for IPV4/CIDR, where x can't be 1, but of course you don't need to pay attention to this minutia if you use this script later.
Command:
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)
TIP
This step may require you to reboot your system after a few minutes of successful execution, see the final execution of the script at the end of the tip. However, a reboot will ensure that some of the hidden settings are loaded successfully, so be sure to reboot the server once if you are in a position to do so.
',32),i=[n];function l(r,c,p,d,h,u){return t(),o("div",null,i)}const y=e(a,[["render",l]]);export{f as __pageData,y as default};
+import{_ as e,v as t,b as o,R as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"PVE Body Installation","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_install.md","filePath":"en/guide/pve/pve_install.md","lastUpdated":1747730955000}'),a={name:"en/guide/pve/pve_install.md"},n=s('
PVE Body Installation ​
If you don't know how to choose an option during installation, just press enter.
TIP
For low-configuration hosts, it is recommended to check the contents of the Custom partition after all the content has been installed to perform memory tuning and reduce the memory footprint.
One-click PVE installation ​
TIP
Suggest debian12, the actual test part of the independent server debian11 system will appear a reboot network will be lost, debian12 does not have such a problem!
  • The installation is the latest PVE from the apt source at the moment.
  • For example, debian10 is pve6.4, debian11 is pve7.x, debian12 is pve8.x
  • Changes to the /etc/hosts file (to fix the wrong hostname setting for merchants and to add the required content for PVE)
  • /etc/cloud/cloud.cfg file modification (to avoid overwriting modified hostname etc.)
  • /etc/network/interfaces file modification (fix auto, dhcp type to static, add vmbr0 gateway)
  • Detect whether it is China IP, if it is China IP use Tsinghua mirror source, otherwise use the official source, and at the same time deal with the source of apt and the corresponding nameserver, to avoid disconnections
  • Create vmbr0 (independent IP gateway), the host allows addr and gateway for intranet IP or extranet IP, has been automatically recognized
  • vmbr0 creation support to open pure IPV4, pure IPV6, dual-stack virtual machine, automatic identification of IPV4 address and IPV6 address, automatic identification of the corresponding IP interval
  • Installation of the necessary toolkit for PVE to open a virtual machine
  • x86_64 replace enterprise subscriptions in apt sources with community sources, arm sources built using third-party patches for fixes
  • Print query Linux system kernel and PVE kernel installed or not
  • Setting up DNS detection 8.8.8.8.8 for boot add DNS systemd service
  • Download PVE and printout of login information after adding APT source link for PVE
All modified files have been set to read-only mode to avoid overwriting after reboot.
If you want to modify the file, please use chattr -i file path to cancel the read-only lock, and run chattr +i file path to lock the read-only lock when you finish modifying the file.
You will be prompted to reboot your system once during the execution process, After rebooting, be sure to wait at least 20 seconds to make sure the system does not reboot automatically again.
Because the original environment may be missing ifupdown or ifupdown2 environment, there is a self-installation daemon loaded for the installation, after the installation of the system will automatically reboot the system again, wait for 20 seconds without reboot to ensure that the installation has been run.
If the host itself exists SLAAC assigned IPV6 address, will be able to choose whether to use the largest IPV6 subnet range, the default carriage return does not use the largest IPV6 subnet range only use the local IPV6, if you subsequently need to attach a separate IPV6 address to the virtual machine/container, the option must be selected y.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh
or
shell
bash install_pve.sh
TIP
After successful installation, the web page may not be safe to open, click on Advanced or More Options and insist on accessing it!
The login information is your SSH account and password.
Pre-configure the environment ​
  • Creating a resource pool mypool
  • Remove the subscription popup
  • Attempt to enable hardware passthrough
  • Detect and auto-install AppArmor modules.
  • Before rebooting the system, it is recommended to hook up nezha probe to facilitate the use of the command line in the background without SSH, to avoid the possibility that SSH may lead to the loss of the root password after the reboot due to the merchant's strange presets.
  • Before executing reboot, you need to wait for the background task to finish executing, some host system apt command execution is very slow, you have to wait for a while to finish executing, of course, most of the machines are not so bad!
Command:
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)
Automatically configure the host's gateway ​
WARNING
Before using this command, please make sure that you have restarted the server and that PVE can use the WEB terminal normally before executing this command. Do not execute this command immediately after restarting the machine, wait for at least 1 minute after the WEB terminal is successfully started before executing this command. If the WEB side doesn't start, run systemctl status pveproxy to see if it starts, if it's stuck, run systemctl start pveproxy to start the WEB side.
TIP
This step is most likely to cause SSH disconnections, the reason is to modify the network without waiting for the PVE kernel to start, which will result in setting conflicts, so wait at least a few minutes until the kernel is started, that is, the WEB side is started successfully before execution.
TIP
If the host needs to attach an IPV6 tunnel (add an IPV6 subnet to a host that does not have an IPV6 address) before executing this command, please check the IPV6 free subnet attachment section to attach to the corresponding configuration file, but please ignore 'initial environment modifications' and attach directly, and then execute the following one-click gateway configuration commands after verifying that you have an IPV6 address.
  • If vmbr0 is not created, it is automatically created with the same logic as the main installation
  • Create vmbr1 (NAT gateway) to support IPV4 servers that open NAT for IPV6 networks with NAT.
  • Create vmbr2 (standalone IPV6 gateway), use ndppd to solve the problem of MAC verification of IPV6 addresses by the host, support the opening of servers with standalone IPV6 networks.
  • If you want to see the complete settings, you can execute cat /etc/network/interfaces to see, if you need to modify the gateway you need to modify the file, the web site can not be modified!
  • Load iptables and set back to source and allow NAT port forwarding.
In short, vmbr0 is responsible for v4 standalone IPs, and vmbr1 is responsible for complex v4/v6 NATs, vmbr2 is responsible for v6 standalone IPs.
Open independent IPV4 virtual machine using vmbr0, gateway with the host, IPV4/CIDR using the same network segment address and the same subnet mask, using the host's unbound IPV4 address for IPV4/CIDR, of course, if the subsequent use of this script does not need to pay attention to this point of the nuances of the thing
Use vmbr1 for IPV4 VM with NAT, 172.16.1.1 for gateway, 172.16.1.x/24 for IPV4/CIDR, where x can't be 1, but of course you don't need to pay attention to this minutia if you use this script later.
Command:
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)
TIP
This step may require you to reboot your system after a few minutes of successful execution, see the final execution of the script at the end of the tip. However, a reboot will ensure that some of the hidden settings are loaded successfully, so be sure to reboot the server once if you are in a position to do so.
',32),i=[n];function l(r,c,p,d,h,u){return t(),o("div",null,i)}const y=e(a,[["render",l]]);export{f as __pageData,y as default};
diff --git a/assets/en_guide_pve_pve_install.md.9a42f3ee.lean.js b/assets/en_guide_pve_pve_install.md.ea124862.lean.js
similarity index 99%
rename from assets/en_guide_pve_pve_install.md.9a42f3ee.lean.js
rename to assets/en_guide_pve_pve_install.md.ea124862.lean.js
index 594a1c6113..ea5f38193a 100644
--- a/assets/en_guide_pve_pve_install.md.9a42f3ee.lean.js
+++ b/assets/en_guide_pve_pve_install.md.ea124862.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as o,R as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"PVE Body Installation","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_install.md","filePath":"en/guide/pve/pve_install.md","lastUpdated":1747726389000}'),a={name:"en/guide/pve/pve_install.md"},n=s('
PVE Body Installation ​
If you don't know how to choose an option during installation, just press enter.
TIP
For low-configuration hosts, it is recommended to check the contents of the Custom partition after all the content has been installed to perform memory tuning and reduce the memory footprint.
One-click PVE installation ​
TIP
Suggest debian12, the actual test part of the independent server debian11 system will appear a reboot network will be lost, debian12 does not have such a problem!
  • The installation is the latest PVE from the apt source at the moment.
  • For example, debian10 is pve6.4, debian11 is pve7.x, debian12 is pve8.x
  • Changes to the /etc/hosts file (to fix the wrong hostname setting for merchants and to add the required content for PVE)
  • /etc/cloud/cloud.cfg file modification (to avoid overwriting modified hostname etc.)
  • /etc/network/interfaces file modification (fix auto, dhcp type to static, add vmbr0 gateway)
  • Detect whether it is China IP, if it is China IP use Tsinghua mirror source, otherwise use the official source, and at the same time deal with the source of apt and the corresponding nameserver, to avoid disconnections
  • Create vmbr0 (independent IP gateway), the host allows addr and gateway for intranet IP or extranet IP, has been automatically recognized
  • vmbr0 creation support to open pure IPV4, pure IPV6, dual-stack virtual machine, automatic identification of IPV4 address and IPV6 address, automatic identification of the corresponding IP interval
  • Installation of the necessary toolkit for PVE to open a virtual machine
  • x86_64 replace enterprise subscriptions in apt sources with community sources, arm sources built using third-party patches for fixes
  • Print query Linux system kernel and PVE kernel installed or not
  • Setting up DNS detection 8.8.8.8.8 for boot add DNS systemd service
  • Download PVE and printout of login information after adding APT source link for PVE
All modified files have been set to read-only mode to avoid overwriting after reboot.
If you want to modify the file, please use chattr -i file path to cancel the read-only lock, and run chattr +i file path to lock the read-only lock when you finish modifying the file.
You will be prompted to reboot your system once during the execution process, After rebooting, be sure to wait at least 20 seconds to make sure the system does not reboot automatically again.
Because the original environment may be missing ifupdown or ifupdown2 environment, there is a self-installation daemon loaded for the installation, after the installation of the system will automatically reboot the system again, wait for 20 seconds without reboot to ensure that the installation has been run.
If the host itself exists SLAAC assigned IPV6 address, will be able to choose whether to use the largest IPV6 subnet range, the default carriage return does not use the largest IPV6 subnet range only use the local IPV6, if you subsequently need to attach a separate IPV6 address to the virtual machine/container, the option must be selected y.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh
or
shell
bash install_pve.sh
TIP
After successful installation, the web page may not be safe to open, click on Advanced or More Options and insist on accessing it!
The login information is your SSH account and password.
Pre-configure the environment ​
  • Creating a resource pool mypool
  • Remove the subscription popup
  • Attempt to enable hardware passthrough
  • Detect and auto-install AppArmor modules.
  • Before rebooting the system, it is recommended to hook up nezha probe to facilitate the use of the command line in the background without SSH, to avoid the possibility that SSH may lead to the loss of the root password after the reboot due to the merchant's strange presets.
  • Before executing reboot, you need to wait for the background task to finish executing, some host system apt command execution is very slow, you have to wait for a while to finish executing, of course, most of the machines are not so bad!
Command:
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)
Automatically configure the host's gateway ​
WARNING
Before using this command, please make sure that you have restarted the server and that PVE can use the WEB terminal normally before executing this command. Do not execute this command immediately after restarting the machine, wait for at least 1 minute after the WEB terminal is successfully started before executing this command. If the WEB side doesn't start, run systemctl status pveproxy to see if it starts, if it's stuck, run systemctl start pveproxy to start the WEB side.
TIP
This step is most likely to cause SSH disconnections, the reason is to modify the network without waiting for the PVE kernel to start, which will result in setting conflicts, so wait at least a few minutes until the kernel is started, that is, the WEB side is started successfully before execution.
TIP
If the host needs to attach an IPV6 tunnel (add an IPV6 subnet to a host that does not have an IPV6 address) before executing this command, please check the IPV6 free subnet attachment section to attach to the corresponding configuration file, but please ignore 'initial environment modifications' and attach directly, and then execute the following one-click gateway configuration commands after verifying that you have an IPV6 address.
  • If vmbr0 is not created, it is automatically created with the same logic as the main installation
  • Create vmbr1 (NAT gateway) to support IPV4 servers that open NAT for IPV6 networks with NAT.
  • Create vmbr2 (standalone IPV6 gateway), use ndppd to solve the problem of MAC verification of IPV6 addresses by the host, support the opening of servers with standalone IPV6 networks.
  • If you want to see the complete settings, you can execute cat /etc/network/interfaces to see, if you need to modify the gateway you need to modify the file, the web site can not be modified!
  • Load iptables and set back to source and allow NAT port forwarding.
In short, vmbr0 is responsible for v4 standalone IPs, and vmbr1 is responsible for complex v4/v6 NATs, vmbr2 is responsible for v6 standalone IPs.
Open independent IPV4 virtual machine using vmbr0, gateway with the host, IPV4/CIDR using the same network segment address and the same subnet mask, using the host's unbound IPV4 address for IPV4/CIDR, of course, if the subsequent use of this script does not need to pay attention to this point of the nuances of the thing
Use vmbr1 for IPV4 VM with NAT, 172.16.1.1 for gateway, 172.16.1.x/24 for IPV4/CIDR, where x can't be 1, but of course you don't need to pay attention to this minutia if you use this script later.
Command:
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)
TIP
This step may require you to reboot your system after a few minutes of successful execution, see the final execution of the script at the end of the tip. However, a reboot will ensure that some of the hidden settings are loaded successfully, so be sure to reboot the server once if you are in a position to do so.
',32),i=[n];function l(r,c,p,d,h,u){return t(),o("div",null,i)}const y=e(a,[["render",l]]);export{f as __pageData,y as default};
+import{_ as e,v as t,b as o,R as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"PVE Body Installation","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_install.md","filePath":"en/guide/pve/pve_install.md","lastUpdated":1747730955000}'),a={name:"en/guide/pve/pve_install.md"},n=s('
PVE Body Installation ​
If you don't know how to choose an option during installation, just press enter.
TIP
For low-configuration hosts, it is recommended to check the contents of the Custom partition after all the content has been installed to perform memory tuning and reduce the memory footprint.
One-click PVE installation ​
TIP
Suggest debian12, the actual test part of the independent server debian11 system will appear a reboot network will be lost, debian12 does not have such a problem!
  • The installation is the latest PVE from the apt source at the moment.
  • For example, debian10 is pve6.4, debian11 is pve7.x, debian12 is pve8.x
  • Changes to the /etc/hosts file (to fix the wrong hostname setting for merchants and to add the required content for PVE)
  • /etc/cloud/cloud.cfg file modification (to avoid overwriting modified hostname etc.)
  • /etc/network/interfaces file modification (fix auto, dhcp type to static, add vmbr0 gateway)
  • Detect whether it is China IP, if it is China IP use Tsinghua mirror source, otherwise use the official source, and at the same time deal with the source of apt and the corresponding nameserver, to avoid disconnections
  • Create vmbr0 (independent IP gateway), the host allows addr and gateway for intranet IP or extranet IP, has been automatically recognized
  • vmbr0 creation support to open pure IPV4, pure IPV6, dual-stack virtual machine, automatic identification of IPV4 address and IPV6 address, automatic identification of the corresponding IP interval
  • Installation of the necessary toolkit for PVE to open a virtual machine
  • x86_64 replace enterprise subscriptions in apt sources with community sources, arm sources built using third-party patches for fixes
  • Print query Linux system kernel and PVE kernel installed or not
  • Setting up DNS detection 8.8.8.8.8 for boot add DNS systemd service
  • Download PVE and printout of login information after adding APT source link for PVE
All modified files have been set to read-only mode to avoid overwriting after reboot.
If you want to modify the file, please use chattr -i file path to cancel the read-only lock, and run chattr +i file path to lock the read-only lock when you finish modifying the file.
You will be prompted to reboot your system once during the execution process, After rebooting, be sure to wait at least 20 seconds to make sure the system does not reboot automatically again.
Because the original environment may be missing ifupdown or ifupdown2 environment, there is a self-installation daemon loaded for the installation, after the installation of the system will automatically reboot the system again, wait for 20 seconds without reboot to ensure that the installation has been run.
If the host itself exists SLAAC assigned IPV6 address, will be able to choose whether to use the largest IPV6 subnet range, the default carriage return does not use the largest IPV6 subnet range only use the local IPV6, if you subsequently need to attach a separate IPV6 address to the virtual machine/container, the option must be selected y.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh
or
shell
bash install_pve.sh
TIP
After successful installation, the web page may not be safe to open, click on Advanced or More Options and insist on accessing it!
The login information is your SSH account and password.
Pre-configure the environment ​
  • Creating a resource pool mypool
  • Remove the subscription popup
  • Attempt to enable hardware passthrough
  • Detect and auto-install AppArmor modules.
  • Before rebooting the system, it is recommended to hook up nezha probe to facilitate the use of the command line in the background without SSH, to avoid the possibility that SSH may lead to the loss of the root password after the reboot due to the merchant's strange presets.
  • Before executing reboot, you need to wait for the background task to finish executing, some host system apt command execution is very slow, you have to wait for a while to finish executing, of course, most of the machines are not so bad!
Command:
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)
Automatically configure the host's gateway ​
WARNING
Before using this command, please make sure that you have restarted the server and that PVE can use the WEB terminal normally before executing this command. Do not execute this command immediately after restarting the machine, wait for at least 1 minute after the WEB terminal is successfully started before executing this command. If the WEB side doesn't start, run systemctl status pveproxy to see if it starts, if it's stuck, run systemctl start pveproxy to start the WEB side.
TIP
This step is most likely to cause SSH disconnections, the reason is to modify the network without waiting for the PVE kernel to start, which will result in setting conflicts, so wait at least a few minutes until the kernel is started, that is, the WEB side is started successfully before execution.
TIP
If the host needs to attach an IPV6 tunnel (add an IPV6 subnet to a host that does not have an IPV6 address) before executing this command, please check the IPV6 free subnet attachment section to attach to the corresponding configuration file, but please ignore 'initial environment modifications' and attach directly, and then execute the following one-click gateway configuration commands after verifying that you have an IPV6 address.
  • If vmbr0 is not created, it is automatically created with the same logic as the main installation
  • Create vmbr1 (NAT gateway) to support IPV4 servers that open NAT for IPV6 networks with NAT.
  • Create vmbr2 (standalone IPV6 gateway), use ndppd to solve the problem of MAC verification of IPV6 addresses by the host, support the opening of servers with standalone IPV6 networks.
  • If you want to see the complete settings, you can execute cat /etc/network/interfaces to see, if you need to modify the gateway you need to modify the file, the web site can not be modified!
  • Load iptables and set back to source and allow NAT port forwarding.
In short, vmbr0 is responsible for v4 standalone IPs, and vmbr1 is responsible for complex v4/v6 NATs, vmbr2 is responsible for v6 standalone IPs.
Open independent IPV4 virtual machine using vmbr0, gateway with the host, IPV4/CIDR using the same network segment address and the same subnet mask, using the host's unbound IPV4 address for IPV4/CIDR, of course, if the subsequent use of this script does not need to pay attention to this point of the nuances of the thing
Use vmbr1 for IPV4 VM with NAT, 172.16.1.1 for gateway, 172.16.1.x/24 for IPV4/CIDR, where x can't be 1, but of course you don't need to pay attention to this minutia if you use this script later.
Command:
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)
TIP
This step may require you to reboot your system after a few minutes of successful execution, see the final execution of the script at the end of the tip. However, a reboot will ensure that some of the hidden settings are loaded successfully, so be sure to reboot the server once if you are in a position to do so.
',32),i=[n];function l(r,c,p,d,h,u){return t(),o("div",null,i)}const y=e(a,[["render",l]]);export{f as __pageData,y as default};
diff --git a/assets/en_guide_pve_pve_kvm.md.83cab4e3.js b/assets/en_guide_pve_pve_kvm.md.d2947595.js
similarity index 99%
rename from assets/en_guide_pve_pve_kvm.md.83cab4e3.js
rename to assets/en_guide_pve_pve_kvm.md.d2947595.js
index 5c3a14052e..3c90b94d4c 100644
--- a/assets/en_guide_pve_pve_kvm.md.83cab4e3.js
+++ b/assets/en_guide_pve_pve_kvm.md.d2947595.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Linux Virtual Machine (KVM/TCG Virtualization)","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_kvm.md","filePath":"en/guide/pve/pve_kvm.md","lastUpdated":1747726389000}'),n={name:"en/guide/pve/pve_kvm.md"},o=t(`
Linux Virtual Machine (KVM/TCG Virtualization) ​
SSH Login Instructions ​
When open a virtual machine, the default generated username can be something other than root, in which case you need to run sudo -i to switch to root!
If the default username is not root, the default unset root password is password or oneclickvirt.
After logging into SSH and switching to root privileges, be sure to change the root password, which can be changed using the following command:
bash
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
Considerations for opening a virtual machine with an IPV6 address ​
Due to long-term inactivity IPV6 does not use may lead to NDP broadcast cache invalidation reset, generally idle for about 50 minutes will appear IPV6 unavailable, commonly known as "IPV6 cutoff", at this time it is necessary to set up a timer task.
shell
echo '*/1 * * * * curl -m 6 -s ipv6.ip.sb || curl -m 6 -s ipv6.ip.sb' | crontab -
Executing the above commands in the opened virtual machine ensures that the IPV6 network is always used and does not fail over.
Images available for creating virtual machines ​
  • Pre-installed with cloud-init enabled.
  • Enabled SSH login.
  • Pre-configured SSH to listen on ports 22 for both IPv4 and IPv6.
  • Enabled password authentication for login.
  • Enabled root login.
  • Partially pre-installed QEMU guest agent.
The list of currently available image names is as follows:
https://github.com/oneclickvirt/kvm_images/blob/main/list.text
and
https://github.com/oneclickvirt/pve_kvm_images
Daily patch images stored in the Release of this repository.
Virtual machines with standalone NAT configuration. ​
  • Automatically deploy NAT servers with the default Debian 10 image, chosen for its minimal footprint.
  • It's possible to customize the image used through the command, and pre-configured images are available. These images come with storage settings ranging from 2 to 10 GB of disk space. For regular use, at least 10 GB of disk space is recommended. You can increase the disk size if certain images fail to start.
  • The command allows for specifying the storage disk location. When not specified, it defaults to the local disk, which is the system disk. It can also be set to a mount disk as displayed in PVE.
  • Recommended custom memory size is 512 MB.
  • Automatic internal and external port mapping, including ports 22, 80, 443, and 25 other port numbers shared between internal and external networks.
  • After generation, there's a wait time for the virtual machine's internal cloud-init configuration to establish network and login information. This process takes approximately 5 minutes.
  • Pertinent virtual machine information will be stored in the NOTES section of the corresponding VM on the web interface, accessible for viewing through the web portal.
  • If the host machine has an IPV6 subnet, IPV6 networking will be automatically added. However, there won't be any public IPV6 addresses.
  • Optionally enable or disable standalone IPV6, requires the host to have at least one /64 subnet
Usage Instructions ​
System Support:
  • For x86_64 architecture systems listed in this link, simply use the filename without the .qcow2 extension when using.
  • For arm architecture systems listed at this link, use the system name and version number, such as ubuntu20 or ubuntu22.
TIP
Note that usernames consisting of only numbers may cause issues with cloud-init. It's preferable to use usernames that are entirely in English or start with an English character.
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
Meaning of each parameter
shell
# ./buildvm.sh VMID Username Password Number_of_CPU_Cores Memory Disk SSH_Port Port_80 Port_443 Public_Port_Start Public_Port_End System Storage_Disk Independent_IPV6_address(leave default N blank)
TIP
Note that the Password here should be a mix of English and numbers only, and start with English, so as to avoid failing to set the Password due to special characters being escaped during the setup process.
Test Example ​
shell
./buildvm.sh 111 root oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
After setup is completed, you can execute cat vm111 to view the information or check the NOTES section for the corresponding VM on the WEB interface.
Below is the information for the example VM that has been set up:
AttributeValue
VMID111
SSH Usernameroot
SSH Passwordoneclick123
Number of CPU Cores1
Memory Size512MB
Disk Size10G
SSH Port40001
Port 8040002
Port 44340003
Port Range for NAT50000 to 50025
Operating Systemdebian11
Host Storage Disklocal
IPV6 addressN
TIP
Note that only VMIDs from 100 to 256 can be used here, no other numbers can be used.
Deletion specific VM ​
  • Stop VM
  • Delete VM
  • Delete port mapping
  • Restart network
  • Delete log files
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
Meaning of each parameter
You can delete the VM with the corresponding VMID, as demonstrated here using the example 111 above
shell
./pve_delete.sh 111
The actual number of deletions is not fixed, a space separates each VMID, and more than one can be deleted at a time.
Batch Creation of Virtual Machines with NAT ​
WARNING
Before initial use, ensure that the current Proxmox Virtual Environment (PVE) is clean and the host machine has not undergone any port forwarding, as conflicting settings may result in bugs.
TIP
Before initiating the batch creation process, please use the 'screen' command to execute it in the background. This will help avoid interruptions due to the instability of SSH caused by extended batch creation times.
  • The batch creation process can be run multiple times to generate multiple virtual machines (VMs).
  • NAT servers are automatically created during the process. If left blank, the default Debian 11 image will be used. You can also customize the image name. Refer to the list of supported images in the previous section.
  • Automatic internal and external port mapping is performed, including ports 22, 80, 443, and other ports with identical internal and external numbers (25 ports in total).
  • After generation, a waiting period is required for the cloud-init configuration of the VM's network and login information to be set up. This process takes approximately 5 minutes. There is a 60-second interval between creating each VM to avoid potential performance issues.
  • The default network configuration for VMs created in batches includes port mappings for ports 22, 80, 443, and a range of 25 ports for internal and external communication.
  • You can customize the number of CPU cores, memory size, disk size, and which storage disk on the host machine to use for batch creation. Ensure you calculate available resources before proceeding.
  • Relevant information about the virtual machines will be stored in the 'NOTES' section of the corresponding VM on the web interface, where you can view them.
  • If the host machine comes with an IPv6 subnet, an IPv6 network will be automatically attached, although there will be no public IPv6 addresses available.
  • Optionally enable or disable standalone IPV6, requires the host to have at least one /64 subnet.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_vm.sh -o create_vm.sh && chmod +x create_vm.sh && bash create_vm.sh
After the setup is completed, you can execute cat vmlog to view the information, or check the NOTES in the corresponding VM on the web interface.
Delete All Virtual Machines ​
  • Delete all VMs
  • Delete all NAT port mappings
  • Restart the network
  • Delete log files
shell
for vmid in $(qm list | awk '{if(NR>1) print $1}'); do qm stop $vmid; qm destroy $vmid; rm -rf /var/lib/vz/images/$vmid*; done
+import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Linux Virtual Machine (KVM/TCG Virtualization)","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_kvm.md","filePath":"en/guide/pve/pve_kvm.md","lastUpdated":1747730955000}'),n={name:"en/guide/pve/pve_kvm.md"},o=t(`
Linux Virtual Machine (KVM/TCG Virtualization) ​
SSH Login Instructions ​
When open a virtual machine, the default generated username can be something other than root, in which case you need to run sudo -i to switch to root!
If the default username is not root, the default unset root password is password or oneclickvirt.
After logging into SSH and switching to root privileges, be sure to change the root password, which can be changed using the following command:
bash
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
Considerations for opening a virtual machine with an IPV6 address ​
Due to long-term inactivity IPV6 does not use may lead to NDP broadcast cache invalidation reset, generally idle for about 50 minutes will appear IPV6 unavailable, commonly known as "IPV6 cutoff", at this time it is necessary to set up a timer task.
shell
echo '*/1 * * * * curl -m 6 -s ipv6.ip.sb || curl -m 6 -s ipv6.ip.sb' | crontab -
Executing the above commands in the opened virtual machine ensures that the IPV6 network is always used and does not fail over.
Images available for creating virtual machines ​
  • Pre-installed with cloud-init enabled.
  • Enabled SSH login.
  • Pre-configured SSH to listen on ports 22 for both IPv4 and IPv6.
  • Enabled password authentication for login.
  • Enabled root login.
  • Partially pre-installed QEMU guest agent.
The list of currently available image names is as follows:
https://github.com/oneclickvirt/kvm_images/blob/main/list.text
and
https://github.com/oneclickvirt/pve_kvm_images
Daily patch images stored in the Release of this repository.
Virtual machines with standalone NAT configuration. ​
  • Automatically deploy NAT servers with the default Debian 10 image, chosen for its minimal footprint.
  • It's possible to customize the image used through the command, and pre-configured images are available. These images come with storage settings ranging from 2 to 10 GB of disk space. For regular use, at least 10 GB of disk space is recommended. You can increase the disk size if certain images fail to start.
  • The command allows for specifying the storage disk location. When not specified, it defaults to the local disk, which is the system disk. It can also be set to a mount disk as displayed in PVE.
  • Recommended custom memory size is 512 MB.
  • Automatic internal and external port mapping, including ports 22, 80, 443, and 25 other port numbers shared between internal and external networks.
  • After generation, there's a wait time for the virtual machine's internal cloud-init configuration to establish network and login information. This process takes approximately 5 minutes.
  • Pertinent virtual machine information will be stored in the NOTES section of the corresponding VM on the web interface, accessible for viewing through the web portal.
  • If the host machine has an IPV6 subnet, IPV6 networking will be automatically added. However, there won't be any public IPV6 addresses.
  • Optionally enable or disable standalone IPV6, requires the host to have at least one /64 subnet
Usage Instructions ​
System Support:
  • For x86_64 architecture systems listed in this link, simply use the filename without the .qcow2 extension when using.
  • For arm architecture systems listed at this link, use the system name and version number, such as ubuntu20 or ubuntu22.
TIP
Note that usernames consisting of only numbers may cause issues with cloud-init. It's preferable to use usernames that are entirely in English or start with an English character.
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
Meaning of each parameter
shell
# ./buildvm.sh VMID Username Password Number_of_CPU_Cores Memory Disk SSH_Port Port_80 Port_443 Public_Port_Start Public_Port_End System Storage_Disk Independent_IPV6_address(leave default N blank)
TIP
Note that the Password here should be a mix of English and numbers only, and start with English, so as to avoid failing to set the Password due to special characters being escaped during the setup process.
Test Example ​
shell
./buildvm.sh 111 root oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
After setup is completed, you can execute cat vm111 to view the information or check the NOTES section for the corresponding VM on the WEB interface.
Below is the information for the example VM that has been set up:
AttributeValue
VMID111
SSH Usernameroot
SSH Passwordoneclick123
Number of CPU Cores1
Memory Size512MB
Disk Size10G
SSH Port40001
Port 8040002
Port 44340003
Port Range for NAT50000 to 50025
Operating Systemdebian11
Host Storage Disklocal
IPV6 addressN
TIP
Note that only VMIDs from 100 to 256 can be used here, no other numbers can be used.
Deletion specific VM ​
  • Stop VM
  • Delete VM
  • Delete port mapping
  • Restart network
  • Delete log files
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
Meaning of each parameter
You can delete the VM with the corresponding VMID, as demonstrated here using the example 111 above
shell
./pve_delete.sh 111
The actual number of deletions is not fixed, a space separates each VMID, and more than one can be deleted at a time.
Batch Creation of Virtual Machines with NAT ​
WARNING
Before initial use, ensure that the current Proxmox Virtual Environment (PVE) is clean and the host machine has not undergone any port forwarding, as conflicting settings may result in bugs.
TIP
Before initiating the batch creation process, please use the 'screen' command to execute it in the background. This will help avoid interruptions due to the instability of SSH caused by extended batch creation times.
  • The batch creation process can be run multiple times to generate multiple virtual machines (VMs).
  • NAT servers are automatically created during the process. If left blank, the default Debian 11 image will be used. You can also customize the image name. Refer to the list of supported images in the previous section.
  • Automatic internal and external port mapping is performed, including ports 22, 80, 443, and other ports with identical internal and external numbers (25 ports in total).
  • After generation, a waiting period is required for the cloud-init configuration of the VM's network and login information to be set up. This process takes approximately 5 minutes. There is a 60-second interval between creating each VM to avoid potential performance issues.
  • The default network configuration for VMs created in batches includes port mappings for ports 22, 80, 443, and a range of 25 ports for internal and external communication.
  • You can customize the number of CPU cores, memory size, disk size, and which storage disk on the host machine to use for batch creation. Ensure you calculate available resources before proceeding.
  • Relevant information about the virtual machines will be stored in the 'NOTES' section of the corresponding VM on the web interface, where you can view them.
  • If the host machine comes with an IPv6 subnet, an IPv6 network will be automatically attached, although there will be no public IPv6 addresses available.
  • Optionally enable or disable standalone IPV6, requires the host to have at least one /64 subnet.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_vm.sh -o create_vm.sh && chmod +x create_vm.sh && bash create_vm.sh
After the setup is completed, you can execute cat vmlog to view the information, or check the NOTES in the corresponding VM on the web interface.
Delete All Virtual Machines ​
  • Delete all VMs
  • Delete all NAT port mappings
  • Restart the network
  • Delete log files
shell
for vmid in $(qm list | awk '{if(NR>1) print $1}'); do qm stop $vmid; qm destroy $vmid; rm -rf /var/lib/vz/images/$vmid*; done
 iptables -t nat -F
 iptables -t filter -F
 service networking restart
diff --git a/assets/en_guide_pve_pve_kvm.md.83cab4e3.lean.js b/assets/en_guide_pve_pve_kvm.md.d2947595.lean.js
similarity index 99%
rename from assets/en_guide_pve_pve_kvm.md.83cab4e3.lean.js
rename to assets/en_guide_pve_pve_kvm.md.d2947595.lean.js
index 5c3a14052e..3c90b94d4c 100644
--- a/assets/en_guide_pve_pve_kvm.md.83cab4e3.lean.js
+++ b/assets/en_guide_pve_pve_kvm.md.d2947595.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Linux Virtual Machine (KVM/TCG Virtualization)","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_kvm.md","filePath":"en/guide/pve/pve_kvm.md","lastUpdated":1747726389000}'),n={name:"en/guide/pve/pve_kvm.md"},o=t(`
Linux Virtual Machine (KVM/TCG Virtualization) ​
SSH Login Instructions ​
When open a virtual machine, the default generated username can be something other than root, in which case you need to run sudo -i to switch to root!
If the default username is not root, the default unset root password is password or oneclickvirt.
After logging into SSH and switching to root privileges, be sure to change the root password, which can be changed using the following command:
bash
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
Considerations for opening a virtual machine with an IPV6 address ​
Due to long-term inactivity IPV6 does not use may lead to NDP broadcast cache invalidation reset, generally idle for about 50 minutes will appear IPV6 unavailable, commonly known as "IPV6 cutoff", at this time it is necessary to set up a timer task.
shell
echo '*/1 * * * * curl -m 6 -s ipv6.ip.sb || curl -m 6 -s ipv6.ip.sb' | crontab -
Executing the above commands in the opened virtual machine ensures that the IPV6 network is always used and does not fail over.
Images available for creating virtual machines ​
  • Pre-installed with cloud-init enabled.
  • Enabled SSH login.
  • Pre-configured SSH to listen on ports 22 for both IPv4 and IPv6.
  • Enabled password authentication for login.
  • Enabled root login.
  • Partially pre-installed QEMU guest agent.
The list of currently available image names is as follows:
https://github.com/oneclickvirt/kvm_images/blob/main/list.text
and
https://github.com/oneclickvirt/pve_kvm_images
Daily patch images stored in the Release of this repository.
Virtual machines with standalone NAT configuration. ​
  • Automatically deploy NAT servers with the default Debian 10 image, chosen for its minimal footprint.
  • It's possible to customize the image used through the command, and pre-configured images are available. These images come with storage settings ranging from 2 to 10 GB of disk space. For regular use, at least 10 GB of disk space is recommended. You can increase the disk size if certain images fail to start.
  • The command allows for specifying the storage disk location. When not specified, it defaults to the local disk, which is the system disk. It can also be set to a mount disk as displayed in PVE.
  • Recommended custom memory size is 512 MB.
  • Automatic internal and external port mapping, including ports 22, 80, 443, and 25 other port numbers shared between internal and external networks.
  • After generation, there's a wait time for the virtual machine's internal cloud-init configuration to establish network and login information. This process takes approximately 5 minutes.
  • Pertinent virtual machine information will be stored in the NOTES section of the corresponding VM on the web interface, accessible for viewing through the web portal.
  • If the host machine has an IPV6 subnet, IPV6 networking will be automatically added. However, there won't be any public IPV6 addresses.
  • Optionally enable or disable standalone IPV6, requires the host to have at least one /64 subnet
Usage Instructions ​
System Support:
  • For x86_64 architecture systems listed in this link, simply use the filename without the .qcow2 extension when using.
  • For arm architecture systems listed at this link, use the system name and version number, such as ubuntu20 or ubuntu22.
TIP
Note that usernames consisting of only numbers may cause issues with cloud-init. It's preferable to use usernames that are entirely in English or start with an English character.
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
Meaning of each parameter
shell
# ./buildvm.sh VMID Username Password Number_of_CPU_Cores Memory Disk SSH_Port Port_80 Port_443 Public_Port_Start Public_Port_End System Storage_Disk Independent_IPV6_address(leave default N blank)
TIP
Note that the Password here should be a mix of English and numbers only, and start with English, so as to avoid failing to set the Password due to special characters being escaped during the setup process.
Test Example ​
shell
./buildvm.sh 111 root oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
After setup is completed, you can execute cat vm111 to view the information or check the NOTES section for the corresponding VM on the WEB interface.
Below is the information for the example VM that has been set up:
AttributeValue
VMID111
SSH Usernameroot
SSH Passwordoneclick123
Number of CPU Cores1
Memory Size512MB
Disk Size10G
SSH Port40001
Port 8040002
Port 44340003
Port Range for NAT50000 to 50025
Operating Systemdebian11
Host Storage Disklocal
IPV6 addressN
TIP
Note that only VMIDs from 100 to 256 can be used here, no other numbers can be used.
Deletion specific VM ​
  • Stop VM
  • Delete VM
  • Delete port mapping
  • Restart network
  • Delete log files
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
Meaning of each parameter
You can delete the VM with the corresponding VMID, as demonstrated here using the example 111 above
shell
./pve_delete.sh 111
The actual number of deletions is not fixed, a space separates each VMID, and more than one can be deleted at a time.
Batch Creation of Virtual Machines with NAT ​
WARNING
Before initial use, ensure that the current Proxmox Virtual Environment (PVE) is clean and the host machine has not undergone any port forwarding, as conflicting settings may result in bugs.
TIP
Before initiating the batch creation process, please use the 'screen' command to execute it in the background. This will help avoid interruptions due to the instability of SSH caused by extended batch creation times.
  • The batch creation process can be run multiple times to generate multiple virtual machines (VMs).
  • NAT servers are automatically created during the process. If left blank, the default Debian 11 image will be used. You can also customize the image name. Refer to the list of supported images in the previous section.
  • Automatic internal and external port mapping is performed, including ports 22, 80, 443, and other ports with identical internal and external numbers (25 ports in total).
  • After generation, a waiting period is required for the cloud-init configuration of the VM's network and login information to be set up. This process takes approximately 5 minutes. There is a 60-second interval between creating each VM to avoid potential performance issues.
  • The default network configuration for VMs created in batches includes port mappings for ports 22, 80, 443, and a range of 25 ports for internal and external communication.
  • You can customize the number of CPU cores, memory size, disk size, and which storage disk on the host machine to use for batch creation. Ensure you calculate available resources before proceeding.
  • Relevant information about the virtual machines will be stored in the 'NOTES' section of the corresponding VM on the web interface, where you can view them.
  • If the host machine comes with an IPv6 subnet, an IPv6 network will be automatically attached, although there will be no public IPv6 addresses available.
  • Optionally enable or disable standalone IPV6, requires the host to have at least one /64 subnet.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_vm.sh -o create_vm.sh && chmod +x create_vm.sh && bash create_vm.sh
After the setup is completed, you can execute cat vmlog to view the information, or check the NOTES in the corresponding VM on the web interface.
Delete All Virtual Machines ​
  • Delete all VMs
  • Delete all NAT port mappings
  • Restart the network
  • Delete log files
shell
for vmid in $(qm list | awk '{if(NR>1) print $1}'); do qm stop $vmid; qm destroy $vmid; rm -rf /var/lib/vz/images/$vmid*; done
+import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Linux Virtual Machine (KVM/TCG Virtualization)","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_kvm.md","filePath":"en/guide/pve/pve_kvm.md","lastUpdated":1747730955000}'),n={name:"en/guide/pve/pve_kvm.md"},o=t(`
Linux Virtual Machine (KVM/TCG Virtualization) ​
SSH Login Instructions ​
When open a virtual machine, the default generated username can be something other than root, in which case you need to run sudo -i to switch to root!
If the default username is not root, the default unset root password is password or oneclickvirt.
After logging into SSH and switching to root privileges, be sure to change the root password, which can be changed using the following command:
bash
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
Considerations for opening a virtual machine with an IPV6 address ​
Due to long-term inactivity IPV6 does not use may lead to NDP broadcast cache invalidation reset, generally idle for about 50 minutes will appear IPV6 unavailable, commonly known as "IPV6 cutoff", at this time it is necessary to set up a timer task.
shell
echo '*/1 * * * * curl -m 6 -s ipv6.ip.sb || curl -m 6 -s ipv6.ip.sb' | crontab -
Executing the above commands in the opened virtual machine ensures that the IPV6 network is always used and does not fail over.
Images available for creating virtual machines ​
  • Pre-installed with cloud-init enabled.
  • Enabled SSH login.
  • Pre-configured SSH to listen on ports 22 for both IPv4 and IPv6.
  • Enabled password authentication for login.
  • Enabled root login.
  • Partially pre-installed QEMU guest agent.
The list of currently available image names is as follows:
https://github.com/oneclickvirt/kvm_images/blob/main/list.text
and
https://github.com/oneclickvirt/pve_kvm_images
Daily patch images stored in the Release of this repository.
Virtual machines with standalone NAT configuration. ​
  • Automatically deploy NAT servers with the default Debian 10 image, chosen for its minimal footprint.
  • It's possible to customize the image used through the command, and pre-configured images are available. These images come with storage settings ranging from 2 to 10 GB of disk space. For regular use, at least 10 GB of disk space is recommended. You can increase the disk size if certain images fail to start.
  • The command allows for specifying the storage disk location. When not specified, it defaults to the local disk, which is the system disk. It can also be set to a mount disk as displayed in PVE.
  • Recommended custom memory size is 512 MB.
  • Automatic internal and external port mapping, including ports 22, 80, 443, and 25 other port numbers shared between internal and external networks.
  • After generation, there's a wait time for the virtual machine's internal cloud-init configuration to establish network and login information. This process takes approximately 5 minutes.
  • Pertinent virtual machine information will be stored in the NOTES section of the corresponding VM on the web interface, accessible for viewing through the web portal.
  • If the host machine has an IPV6 subnet, IPV6 networking will be automatically added. However, there won't be any public IPV6 addresses.
  • Optionally enable or disable standalone IPV6, requires the host to have at least one /64 subnet
Usage Instructions ​
System Support:
  • For x86_64 architecture systems listed in this link, simply use the filename without the .qcow2 extension when using.
  • For arm architecture systems listed at this link, use the system name and version number, such as ubuntu20 or ubuntu22.
TIP
Note that usernames consisting of only numbers may cause issues with cloud-init. It's preferable to use usernames that are entirely in English or start with an English character.
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
Meaning of each parameter
shell
# ./buildvm.sh VMID Username Password Number_of_CPU_Cores Memory Disk SSH_Port Port_80 Port_443 Public_Port_Start Public_Port_End System Storage_Disk Independent_IPV6_address(leave default N blank)
TIP
Note that the Password here should be a mix of English and numbers only, and start with English, so as to avoid failing to set the Password due to special characters being escaped during the setup process.
Test Example ​
shell
./buildvm.sh 111 root oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
After setup is completed, you can execute cat vm111 to view the information or check the NOTES section for the corresponding VM on the WEB interface.
Below is the information for the example VM that has been set up:
AttributeValue
VMID111
SSH Usernameroot
SSH Passwordoneclick123
Number of CPU Cores1
Memory Size512MB
Disk Size10G
SSH Port40001
Port 8040002
Port 44340003
Port Range for NAT50000 to 50025
Operating Systemdebian11
Host Storage Disklocal
IPV6 addressN
TIP
Note that only VMIDs from 100 to 256 can be used here, no other numbers can be used.
Deletion specific VM ​
  • Stop VM
  • Delete VM
  • Delete port mapping
  • Restart network
  • Delete log files
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
Meaning of each parameter
You can delete the VM with the corresponding VMID, as demonstrated here using the example 111 above
shell
./pve_delete.sh 111
The actual number of deletions is not fixed, a space separates each VMID, and more than one can be deleted at a time.
Batch Creation of Virtual Machines with NAT ​
WARNING
Before initial use, ensure that the current Proxmox Virtual Environment (PVE) is clean and the host machine has not undergone any port forwarding, as conflicting settings may result in bugs.
TIP
Before initiating the batch creation process, please use the 'screen' command to execute it in the background. This will help avoid interruptions due to the instability of SSH caused by extended batch creation times.
  • The batch creation process can be run multiple times to generate multiple virtual machines (VMs).
  • NAT servers are automatically created during the process. If left blank, the default Debian 11 image will be used. You can also customize the image name. Refer to the list of supported images in the previous section.
  • Automatic internal and external port mapping is performed, including ports 22, 80, 443, and other ports with identical internal and external numbers (25 ports in total).
  • After generation, a waiting period is required for the cloud-init configuration of the VM's network and login information to be set up. This process takes approximately 5 minutes. There is a 60-second interval between creating each VM to avoid potential performance issues.
  • The default network configuration for VMs created in batches includes port mappings for ports 22, 80, 443, and a range of 25 ports for internal and external communication.
  • You can customize the number of CPU cores, memory size, disk size, and which storage disk on the host machine to use for batch creation. Ensure you calculate available resources before proceeding.
  • Relevant information about the virtual machines will be stored in the 'NOTES' section of the corresponding VM on the web interface, where you can view them.
  • If the host machine comes with an IPv6 subnet, an IPv6 network will be automatically attached, although there will be no public IPv6 addresses available.
  • Optionally enable or disable standalone IPV6, requires the host to have at least one /64 subnet.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_vm.sh -o create_vm.sh && chmod +x create_vm.sh && bash create_vm.sh
After the setup is completed, you can execute cat vmlog to view the information, or check the NOTES in the corresponding VM on the web interface.
Delete All Virtual Machines ​
  • Delete all VMs
  • Delete all NAT port mappings
  • Restart the network
  • Delete log files
shell
for vmid in $(qm list | awk '{if(NR>1) print $1}'); do qm stop $vmid; qm destroy $vmid; rm -rf /var/lib/vz/images/$vmid*; done
 iptables -t nat -F
 iptables -t filter -F
 service networking restart
diff --git a/assets/en_guide_pve_pve_lxc.md.1cfce08a.js b/assets/en_guide_pve_pve_lxc.md.7e809382.js
similarity index 99%
rename from assets/en_guide_pve_pve_lxc.md.1cfce08a.js
rename to assets/en_guide_pve_pve_lxc.md.7e809382.js
index 67ef9ac5e4..3ca8830b05 100644
--- a/assets/en_guide_pve_pve_lxc.md.1cfce08a.js
+++ b/assets/en_guide_pve_pve_lxc.md.7e809382.js
@@ -1,4 +1,4 @@
-import{_ as s,v as e,b as a,R as t}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"LXC Virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_lxc.md","filePath":"en/guide/pve/pve_lxc.md","lastUpdated":1747726389000}'),n={name:"en/guide/pve/pve_lxc.md"},o=t(`
LXC Virtualization ​
WARNING
If you need to open more than 200 LXC containers on a single server, then it is not recommended to use this project, there may be problems with lxcfs access drift, which generates IO occupancy that cannot be released. (This is a native LXC problem that can't be fixed.)
Images available for creating LXC Containers ​
x86_64:
Auto-patching images: https://github.com/oneclickvirt/lxc_amd64_images/blob/main/fixed_images.txt
TIP
Automated daily pulls for compilation and patching
Self-patching images: https://github.com/oneclickvirt/pve_lxc_images/blob/main/fixed_images.txt
TIP
Some of these images are flawed and not guaranteed to be available for all PVEs, with names like ubuntu16.04, debian6, centos7, opensuse42.2, opensuse42.3 Don't use them unless necessary.
and
Run pveam available --section system to see the names and version numbers of the officially available systems.
Priority: Self-patching images (not supported by Proxmox-VE 5 and below) > Official default images (both supported) image
The version has been automatically recognized by a script to use the corresponding image.
arm:
https://github.com/oneclickvirt/lxc_arm_images/blob/main/fixed_images.txt
Supported systems can be viewed in the file above, which lists debian and ubuntu systems do not use the aliases in it, just use the numeric designators.
TIP
All system parameters are lowercase system names spliced with version numbers, e.g. debian11, ubuntu22, etc. (Self-patched images support some out-of-the-way systems, such as centos6, centos7, debian8, debian9, etc.)
The default CT username for all systems is root
TIP
Of course, sometimes there are special cases where the version may be current/base, in which case it is sufficient to use only the English system name, e.g. archlinux, gentoo, kali.
Creating Individual LXC Containers for Virtualization ​
WARNING
Before initial use, ensure that the current PVE (Proxmox Virtual Environment) is clean and the host machine has not undergone any port mapping, as conflicts in settings could lead to bugs.
TIP
Before creating containers, use the 'screen' command to run them in the background. This helps to avoid extended creation times that might lead to interruptions due to unstable SSH connections.
  • Automatically create NAT servers using the default Debian 11 image, or customize the system image as needed.
  • Automatically perform internal and external network port mapping, including ports 22, 80, 443, and 25 additional ports with identical numbers for both internal and external networks.
  • After generation, allow some time for the virtual machine to configure its internal network and login information. This process takes approximately 3 minutes.
  • The default network configuration includes port mappings for 22, 80, 443, and a range of 25 ports for both internal and external networks.
  • Customize the number of cores, memory size, disk size, and the storage disk on the host machine for allocation. Ensure that you calculate available resources before creating containers.
  • Optionally specify the storage disk location in the command. When not specified, it defaults to the local disk, which is the system disk. Alternatively, you can specify a mount disk as displayed in PVE.
  • The created containers are enabled with SSH by default, allowing root login. They are also configured to support nested virtualization for Docker.
  • Relevant container information will be stored in the respective container's notes, accessible through the web interface.
  • If the host machine has an IPV6 subnet, IPV6 networking will be automatically attached, but no public IPV6 addresses will be provided.
  • Optionally enable or disable standalone IPV6, requires the host to have at least one /64 subnet
Usage Instructions ​
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
Meaning of each parameter
shell
# ./buildct.sh CTID Password Number_of_CPU_Cores Memory Disk SSH_Port Port_80 Port_443 Start_Public_Port End_Public_Port System Storage_Disk Independent_IPV6_address(leave default N blank)
Test Example ​
shell
./buildct.sh 111 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
After setting up, you can execute cat ct111 to view the information, or check the NOTES section on the web interface.
Here is the information for the created example CT:
Please note that "CT" and other technical terms might have specific meanings in different contexts. If "CT" stands for something specific in your domain, you might want to provide additional context for accurate translation.
AttributeValue
CTID111
SSH Usernameroot
SSH Passwordoneclick123
Number of CPU Cores1
Memory Size512MB
Disk Size5G
SSH Port20001
Port 8020002
Port 44320003
Port Range for NAT30000 to 30025
Operating Systemdebian11
Host Storage Disklocal
IPV6 addressN
TIP
Note that only CTIDs from 100 to 256 can be used here, no other numbers can be used.
Deletion specific CT ​
  • Stop CT
  • Delete CT
  • Delete Port Mapping
  • Restart Network
  • Delete Log Files
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
Meaning of each parameter
You can delete the CT with the corresponding CTID, as demonstrated here using the example 111 above
shell
./pve_delete.sh 111
The actual number of deletions is not fixed, a space separates each CTID, and more than one can be deleted at a time.
Batch Creation of LXC Containers with NAT ​
WARNING
Make sure the current Proxmox Virtual Environment (PVE) is clean and the host machine has not undergone any port mapping before the first use, as conflicting settings may result in bugs.
TIP
Before initiating the creation process, it's recommended to use the 'screen' command to execute the batch creation. This will prevent interruptions due to potential instability in SSH during the extended creation time.
  • It is possible to run the batch container creation process multiple times. However, please be mindful of allocating enough memory to the host machine to prevent system crashes. For adding swap space, refer to this link.
  • There is a 60-second interval between creating each container to avoid sudden performance bottlenecks.
  • Customization options include selecting the number of CPU cores, memory size, disk size, and the storage drive on the host machine. Ensure that you have calculated available resources appropriately before initiating the process.
  • The created containers have SSH enabled by default, allowing root login. Additionally, they are configured to support nested virtualization for Docker usage.
  • Relevant information about the containers will be stored in the corresponding container's notes, which can be viewed on the web interface.
  • If the host machine has an IPv6 subnet, it will be automatically assigned to the containers. However, public IPv6 addresses will not be provided.
  • Optionally enable or disable standalone IPV6, requires the host to have at least one /64 subnet.
Usage Instructions ​
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_ct.sh -o create_ct.sh && chmod +x create_ct.sh && bash create_ct.sh
After the setup is complete, you can execute cat ctlog to view the information, or check in the NOTES section on the web interface.
Delete All CT ​
  • Delete all CTs
  • Delete port mappings for all NATs
  • Restart the network
  • Delete log files
shell
pct list | awk 'NR>1{print $1}' | xargs -I {} sh -c 'pct stop {}; pct destroy {}'
+import{_ as s,v as e,b as a,R as t}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"LXC Virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_lxc.md","filePath":"en/guide/pve/pve_lxc.md","lastUpdated":1747730955000}'),n={name:"en/guide/pve/pve_lxc.md"},o=t(`
LXC Virtualization ​
WARNING
If you need to open more than 200 LXC containers on a single server, then it is not recommended to use this project, there may be problems with lxcfs access drift, which generates IO occupancy that cannot be released. (This is a native LXC problem that can't be fixed.)
Images available for creating LXC Containers ​
x86_64:
Auto-patching images: https://github.com/oneclickvirt/lxc_amd64_images/blob/main/fixed_images.txt
TIP
Automated daily pulls for compilation and patching
Self-patching images: https://github.com/oneclickvirt/pve_lxc_images/blob/main/fixed_images.txt
TIP
Some of these images are flawed and not guaranteed to be available for all PVEs, with names like ubuntu16.04, debian6, centos7, opensuse42.2, opensuse42.3 Don't use them unless necessary.
and
Run pveam available --section system to see the names and version numbers of the officially available systems.
Priority: Self-patching images (not supported by Proxmox-VE 5 and below) > Official default images (both supported) image
The version has been automatically recognized by a script to use the corresponding image.
arm:
https://github.com/oneclickvirt/lxc_arm_images/blob/main/fixed_images.txt
Supported systems can be viewed in the file above, which lists debian and ubuntu systems do not use the aliases in it, just use the numeric designators.
TIP
All system parameters are lowercase system names spliced with version numbers, e.g. debian11, ubuntu22, etc. (Self-patched images support some out-of-the-way systems, such as centos6, centos7, debian8, debian9, etc.)
The default CT username for all systems is root
TIP
Of course, sometimes there are special cases where the version may be current/base, in which case it is sufficient to use only the English system name, e.g. archlinux, gentoo, kali.
Creating Individual LXC Containers for Virtualization ​
WARNING
Before initial use, ensure that the current PVE (Proxmox Virtual Environment) is clean and the host machine has not undergone any port mapping, as conflicts in settings could lead to bugs.
TIP
Before creating containers, use the 'screen' command to run them in the background. This helps to avoid extended creation times that might lead to interruptions due to unstable SSH connections.
  • Automatically create NAT servers using the default Debian 11 image, or customize the system image as needed.
  • Automatically perform internal and external network port mapping, including ports 22, 80, 443, and 25 additional ports with identical numbers for both internal and external networks.
  • After generation, allow some time for the virtual machine to configure its internal network and login information. This process takes approximately 3 minutes.
  • The default network configuration includes port mappings for 22, 80, 443, and a range of 25 ports for both internal and external networks.
  • Customize the number of cores, memory size, disk size, and the storage disk on the host machine for allocation. Ensure that you calculate available resources before creating containers.
  • Optionally specify the storage disk location in the command. When not specified, it defaults to the local disk, which is the system disk. Alternatively, you can specify a mount disk as displayed in PVE.
  • The created containers are enabled with SSH by default, allowing root login. They are also configured to support nested virtualization for Docker.
  • Relevant container information will be stored in the respective container's notes, accessible through the web interface.
  • If the host machine has an IPV6 subnet, IPV6 networking will be automatically attached, but no public IPV6 addresses will be provided.
  • Optionally enable or disable standalone IPV6, requires the host to have at least one /64 subnet
Usage Instructions ​
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
Meaning of each parameter
shell
# ./buildct.sh CTID Password Number_of_CPU_Cores Memory Disk SSH_Port Port_80 Port_443 Start_Public_Port End_Public_Port System Storage_Disk Independent_IPV6_address(leave default N blank)
Test Example ​
shell
./buildct.sh 111 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
After setting up, you can execute cat ct111 to view the information, or check the NOTES section on the web interface.
Here is the information for the created example CT:
Please note that "CT" and other technical terms might have specific meanings in different contexts. If "CT" stands for something specific in your domain, you might want to provide additional context for accurate translation.
AttributeValue
CTID111
SSH Usernameroot
SSH Passwordoneclick123
Number of CPU Cores1
Memory Size512MB
Disk Size5G
SSH Port20001
Port 8020002
Port 44320003
Port Range for NAT30000 to 30025
Operating Systemdebian11
Host Storage Disklocal
IPV6 addressN
TIP
Note that only CTIDs from 100 to 256 can be used here, no other numbers can be used.
Deletion specific CT ​
  • Stop CT
  • Delete CT
  • Delete Port Mapping
  • Restart Network
  • Delete Log Files
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
Meaning of each parameter
You can delete the CT with the corresponding CTID, as demonstrated here using the example 111 above
shell
./pve_delete.sh 111
The actual number of deletions is not fixed, a space separates each CTID, and more than one can be deleted at a time.
Batch Creation of LXC Containers with NAT ​
WARNING
Make sure the current Proxmox Virtual Environment (PVE) is clean and the host machine has not undergone any port mapping before the first use, as conflicting settings may result in bugs.
TIP
Before initiating the creation process, it's recommended to use the 'screen' command to execute the batch creation. This will prevent interruptions due to potential instability in SSH during the extended creation time.
  • It is possible to run the batch container creation process multiple times. However, please be mindful of allocating enough memory to the host machine to prevent system crashes. For adding swap space, refer to this link.
  • There is a 60-second interval between creating each container to avoid sudden performance bottlenecks.
  • Customization options include selecting the number of CPU cores, memory size, disk size, and the storage drive on the host machine. Ensure that you have calculated available resources appropriately before initiating the process.
  • The created containers have SSH enabled by default, allowing root login. Additionally, they are configured to support nested virtualization for Docker usage.
  • Relevant information about the containers will be stored in the corresponding container's notes, which can be viewed on the web interface.
  • If the host machine has an IPv6 subnet, it will be automatically assigned to the containers. However, public IPv6 addresses will not be provided.
  • Optionally enable or disable standalone IPV6, requires the host to have at least one /64 subnet.
Usage Instructions ​
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_ct.sh -o create_ct.sh && chmod +x create_ct.sh && bash create_ct.sh
After the setup is complete, you can execute cat ctlog to view the information, or check in the NOTES section on the web interface.
Delete All CT ​
  • Delete all CTs
  • Delete port mappings for all NATs
  • Restart the network
  • Delete log files
shell
pct list | awk 'NR>1{print $1}' | xargs -I {} sh -c 'pct stop {}; pct destroy {}'
 rm -rf ct*
 iptables -t nat -F
 iptables -t filter -F
diff --git a/assets/en_guide_pve_pve_lxc.md.1cfce08a.lean.js b/assets/en_guide_pve_pve_lxc.md.7e809382.lean.js
similarity index 99%
rename from assets/en_guide_pve_pve_lxc.md.1cfce08a.lean.js
rename to assets/en_guide_pve_pve_lxc.md.7e809382.lean.js
index 67ef9ac5e4..3ca8830b05 100644
--- a/assets/en_guide_pve_pve_lxc.md.1cfce08a.lean.js
+++ b/assets/en_guide_pve_pve_lxc.md.7e809382.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as e,b as a,R as t}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"LXC Virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_lxc.md","filePath":"en/guide/pve/pve_lxc.md","lastUpdated":1747726389000}'),n={name:"en/guide/pve/pve_lxc.md"},o=t(`
LXC Virtualization ​
WARNING
If you need to open more than 200 LXC containers on a single server, then it is not recommended to use this project, there may be problems with lxcfs access drift, which generates IO occupancy that cannot be released. (This is a native LXC problem that can't be fixed.)
Images available for creating LXC Containers ​
x86_64:
Auto-patching images: https://github.com/oneclickvirt/lxc_amd64_images/blob/main/fixed_images.txt
TIP
Automated daily pulls for compilation and patching
Self-patching images: https://github.com/oneclickvirt/pve_lxc_images/blob/main/fixed_images.txt
TIP
Some of these images are flawed and not guaranteed to be available for all PVEs, with names like ubuntu16.04, debian6, centos7, opensuse42.2, opensuse42.3 Don't use them unless necessary.
and
Run pveam available --section system to see the names and version numbers of the officially available systems.
Priority: Self-patching images (not supported by Proxmox-VE 5 and below) > Official default images (both supported) image
The version has been automatically recognized by a script to use the corresponding image.
arm:
https://github.com/oneclickvirt/lxc_arm_images/blob/main/fixed_images.txt
Supported systems can be viewed in the file above, which lists debian and ubuntu systems do not use the aliases in it, just use the numeric designators.
TIP
All system parameters are lowercase system names spliced with version numbers, e.g. debian11, ubuntu22, etc. (Self-patched images support some out-of-the-way systems, such as centos6, centos7, debian8, debian9, etc.)
The default CT username for all systems is root
TIP
Of course, sometimes there are special cases where the version may be current/base, in which case it is sufficient to use only the English system name, e.g. archlinux, gentoo, kali.
Creating Individual LXC Containers for Virtualization ​
WARNING
Before initial use, ensure that the current PVE (Proxmox Virtual Environment) is clean and the host machine has not undergone any port mapping, as conflicts in settings could lead to bugs.
TIP
Before creating containers, use the 'screen' command to run them in the background. This helps to avoid extended creation times that might lead to interruptions due to unstable SSH connections.
  • Automatically create NAT servers using the default Debian 11 image, or customize the system image as needed.
  • Automatically perform internal and external network port mapping, including ports 22, 80, 443, and 25 additional ports with identical numbers for both internal and external networks.
  • After generation, allow some time for the virtual machine to configure its internal network and login information. This process takes approximately 3 minutes.
  • The default network configuration includes port mappings for 22, 80, 443, and a range of 25 ports for both internal and external networks.
  • Customize the number of cores, memory size, disk size, and the storage disk on the host machine for allocation. Ensure that you calculate available resources before creating containers.
  • Optionally specify the storage disk location in the command. When not specified, it defaults to the local disk, which is the system disk. Alternatively, you can specify a mount disk as displayed in PVE.
  • The created containers are enabled with SSH by default, allowing root login. They are also configured to support nested virtualization for Docker.
  • Relevant container information will be stored in the respective container's notes, accessible through the web interface.
  • If the host machine has an IPV6 subnet, IPV6 networking will be automatically attached, but no public IPV6 addresses will be provided.
  • Optionally enable or disable standalone IPV6, requires the host to have at least one /64 subnet
Usage Instructions ​
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
Meaning of each parameter
shell
# ./buildct.sh CTID Password Number_of_CPU_Cores Memory Disk SSH_Port Port_80 Port_443 Start_Public_Port End_Public_Port System Storage_Disk Independent_IPV6_address(leave default N blank)
Test Example ​
shell
./buildct.sh 111 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
After setting up, you can execute cat ct111 to view the information, or check the NOTES section on the web interface.
Here is the information for the created example CT:
Please note that "CT" and other technical terms might have specific meanings in different contexts. If "CT" stands for something specific in your domain, you might want to provide additional context for accurate translation.
AttributeValue
CTID111
SSH Usernameroot
SSH Passwordoneclick123
Number of CPU Cores1
Memory Size512MB
Disk Size5G
SSH Port20001
Port 8020002
Port 44320003
Port Range for NAT30000 to 30025
Operating Systemdebian11
Host Storage Disklocal
IPV6 addressN
TIP
Note that only CTIDs from 100 to 256 can be used here, no other numbers can be used.
Deletion specific CT ​
  • Stop CT
  • Delete CT
  • Delete Port Mapping
  • Restart Network
  • Delete Log Files
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
Meaning of each parameter
You can delete the CT with the corresponding CTID, as demonstrated here using the example 111 above
shell
./pve_delete.sh 111
The actual number of deletions is not fixed, a space separates each CTID, and more than one can be deleted at a time.
Batch Creation of LXC Containers with NAT ​
WARNING
Make sure the current Proxmox Virtual Environment (PVE) is clean and the host machine has not undergone any port mapping before the first use, as conflicting settings may result in bugs.
TIP
Before initiating the creation process, it's recommended to use the 'screen' command to execute the batch creation. This will prevent interruptions due to potential instability in SSH during the extended creation time.
  • It is possible to run the batch container creation process multiple times. However, please be mindful of allocating enough memory to the host machine to prevent system crashes. For adding swap space, refer to this link.
  • There is a 60-second interval between creating each container to avoid sudden performance bottlenecks.
  • Customization options include selecting the number of CPU cores, memory size, disk size, and the storage drive on the host machine. Ensure that you have calculated available resources appropriately before initiating the process.
  • The created containers have SSH enabled by default, allowing root login. Additionally, they are configured to support nested virtualization for Docker usage.
  • Relevant information about the containers will be stored in the corresponding container's notes, which can be viewed on the web interface.
  • If the host machine has an IPv6 subnet, it will be automatically assigned to the containers. However, public IPv6 addresses will not be provided.
  • Optionally enable or disable standalone IPV6, requires the host to have at least one /64 subnet.
Usage Instructions ​
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_ct.sh -o create_ct.sh && chmod +x create_ct.sh && bash create_ct.sh
After the setup is complete, you can execute cat ctlog to view the information, or check in the NOTES section on the web interface.
Delete All CT ​
  • Delete all CTs
  • Delete port mappings for all NATs
  • Restart the network
  • Delete log files
shell
pct list | awk 'NR>1{print $1}' | xargs -I {} sh -c 'pct stop {}; pct destroy {}'
+import{_ as s,v as e,b as a,R as t}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"LXC Virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_lxc.md","filePath":"en/guide/pve/pve_lxc.md","lastUpdated":1747730955000}'),n={name:"en/guide/pve/pve_lxc.md"},o=t(`
LXC Virtualization ​
WARNING
If you need to open more than 200 LXC containers on a single server, then it is not recommended to use this project, there may be problems with lxcfs access drift, which generates IO occupancy that cannot be released. (This is a native LXC problem that can't be fixed.)
Images available for creating LXC Containers ​
x86_64:
Auto-patching images: https://github.com/oneclickvirt/lxc_amd64_images/blob/main/fixed_images.txt
TIP
Automated daily pulls for compilation and patching
Self-patching images: https://github.com/oneclickvirt/pve_lxc_images/blob/main/fixed_images.txt
TIP
Some of these images are flawed and not guaranteed to be available for all PVEs, with names like ubuntu16.04, debian6, centos7, opensuse42.2, opensuse42.3 Don't use them unless necessary.
and
Run pveam available --section system to see the names and version numbers of the officially available systems.
Priority: Self-patching images (not supported by Proxmox-VE 5 and below) > Official default images (both supported) image
The version has been automatically recognized by a script to use the corresponding image.
arm:
https://github.com/oneclickvirt/lxc_arm_images/blob/main/fixed_images.txt
Supported systems can be viewed in the file above, which lists debian and ubuntu systems do not use the aliases in it, just use the numeric designators.
TIP
All system parameters are lowercase system names spliced with version numbers, e.g. debian11, ubuntu22, etc. (Self-patched images support some out-of-the-way systems, such as centos6, centos7, debian8, debian9, etc.)
The default CT username for all systems is root
TIP
Of course, sometimes there are special cases where the version may be current/base, in which case it is sufficient to use only the English system name, e.g. archlinux, gentoo, kali.
Creating Individual LXC Containers for Virtualization ​
WARNING
Before initial use, ensure that the current PVE (Proxmox Virtual Environment) is clean and the host machine has not undergone any port mapping, as conflicts in settings could lead to bugs.
TIP
Before creating containers, use the 'screen' command to run them in the background. This helps to avoid extended creation times that might lead to interruptions due to unstable SSH connections.
  • Automatically create NAT servers using the default Debian 11 image, or customize the system image as needed.
  • Automatically perform internal and external network port mapping, including ports 22, 80, 443, and 25 additional ports with identical numbers for both internal and external networks.
  • After generation, allow some time for the virtual machine to configure its internal network and login information. This process takes approximately 3 minutes.
  • The default network configuration includes port mappings for 22, 80, 443, and a range of 25 ports for both internal and external networks.
  • Customize the number of cores, memory size, disk size, and the storage disk on the host machine for allocation. Ensure that you calculate available resources before creating containers.
  • Optionally specify the storage disk location in the command. When not specified, it defaults to the local disk, which is the system disk. Alternatively, you can specify a mount disk as displayed in PVE.
  • The created containers are enabled with SSH by default, allowing root login. They are also configured to support nested virtualization for Docker.
  • Relevant container information will be stored in the respective container's notes, accessible through the web interface.
  • If the host machine has an IPV6 subnet, IPV6 networking will be automatically attached, but no public IPV6 addresses will be provided.
  • Optionally enable or disable standalone IPV6, requires the host to have at least one /64 subnet
Usage Instructions ​
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
Meaning of each parameter
shell
# ./buildct.sh CTID Password Number_of_CPU_Cores Memory Disk SSH_Port Port_80 Port_443 Start_Public_Port End_Public_Port System Storage_Disk Independent_IPV6_address(leave default N blank)
Test Example ​
shell
./buildct.sh 111 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
After setting up, you can execute cat ct111 to view the information, or check the NOTES section on the web interface.
Here is the information for the created example CT:
Please note that "CT" and other technical terms might have specific meanings in different contexts. If "CT" stands for something specific in your domain, you might want to provide additional context for accurate translation.
AttributeValue
CTID111
SSH Usernameroot
SSH Passwordoneclick123
Number of CPU Cores1
Memory Size512MB
Disk Size5G
SSH Port20001
Port 8020002
Port 44320003
Port Range for NAT30000 to 30025
Operating Systemdebian11
Host Storage Disklocal
IPV6 addressN
TIP
Note that only CTIDs from 100 to 256 can be used here, no other numbers can be used.
Deletion specific CT ​
  • Stop CT
  • Delete CT
  • Delete Port Mapping
  • Restart Network
  • Delete Log Files
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
Meaning of each parameter
You can delete the CT with the corresponding CTID, as demonstrated here using the example 111 above
shell
./pve_delete.sh 111
The actual number of deletions is not fixed, a space separates each CTID, and more than one can be deleted at a time.
Batch Creation of LXC Containers with NAT ​
WARNING
Make sure the current Proxmox Virtual Environment (PVE) is clean and the host machine has not undergone any port mapping before the first use, as conflicting settings may result in bugs.
TIP
Before initiating the creation process, it's recommended to use the 'screen' command to execute the batch creation. This will prevent interruptions due to potential instability in SSH during the extended creation time.
  • It is possible to run the batch container creation process multiple times. However, please be mindful of allocating enough memory to the host machine to prevent system crashes. For adding swap space, refer to this link.
  • There is a 60-second interval between creating each container to avoid sudden performance bottlenecks.
  • Customization options include selecting the number of CPU cores, memory size, disk size, and the storage drive on the host machine. Ensure that you have calculated available resources appropriately before initiating the process.
  • The created containers have SSH enabled by default, allowing root login. Additionally, they are configured to support nested virtualization for Docker usage.
  • Relevant information about the containers will be stored in the corresponding container's notes, which can be viewed on the web interface.
  • If the host machine has an IPv6 subnet, it will be automatically assigned to the containers. However, public IPv6 addresses will not be provided.
  • Optionally enable or disable standalone IPV6, requires the host to have at least one /64 subnet.
Usage Instructions ​
Download Script
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_ct.sh -o create_ct.sh && chmod +x create_ct.sh && bash create_ct.sh
After the setup is complete, you can execute cat ctlog to view the information, or check in the NOTES section on the web interface.
Delete All CT ​
  • Delete all CTs
  • Delete port mappings for all NATs
  • Restart the network
  • Delete log files
shell
pct list | awk 'NR>1{print $1}' | xargs -I {} sh -c 'pct stop {}; pct destroy {}'
 rm -rf ct*
 iptables -t nat -F
 iptables -t filter -F
diff --git a/assets/en_guide_pve_pve_macos.md.2629d0a7.js b/assets/en_guide_pve_pve_macos.md.8346a51d.js
similarity index 99%
rename from assets/en_guide_pve_pve_macos.md.2629d0a7.js
rename to assets/en_guide_pve_pve_macos.md.8346a51d.js
index 7eefd5b5d4..f8fe7a4076 100644
--- a/assets/en_guide_pve_pve_macos.md.2629d0a7.js
+++ b/assets/en_guide_pve_pve_macos.md.8346a51d.js
@@ -1,4 +1,4 @@
-import{_ as e,v as a,b as s,R as t}from"./chunks/framework.70afa331.js";import{_ as o}from"./chunks/wk7.776871bd.js";const n="/assets/mac0.935d53f3.png",i="/assets/mac00.4296be7b.png",l="/assets/mac1.3307e401.png",c="/assets/mac2.da6ce0bc.png",r="/assets/mac3.76a50b9f.png",p="/assets/mac4.c341ba50.png",d="/assets/mac5.39e1c9a4.png",m="/assets/mac6.1cc0462b.png",h="/assets/mac7.181275ae.png",u="/assets/mac8.dd556f02.png",y="/assets/mac9.c5d88eba.png",g="/assets/mac10.e9c284db.png",C="/assets/mac11.a7587e0e.png",f="/assets/mac12.06b051d3.png",b="/assets/mac13.7d4e3199.png",A="/assets/mac14.39a58b6a.png",k="/assets/mac15.f151793c.png",D="/assets/mac16.eae177db.png",w="/assets/mac17.be61913a.png",v="/assets/mac18.f9454618.png",_="/assets/mac19.845f5510.png",S="/assets/mac20.49a5800c.png",N=JSON.parse('{"title":"Setting Up MacOS Virtual Machine","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_macos.md","filePath":"en/guide/pve/pve_macos.md","lastUpdated":1747726389000}'),x={name:"en/guide/pve/pve_macos.md"},F=t(`
Setting Up MacOS Virtual Machine ​
Prerequisites ​
System and hardware configuration requirements --> Environment detection
You can only set up a MacOS virtual machine when the environment detection confirms that the host machine supports KVM nested virtualization. Otherwise, it will be detected by hardware and cannot be set up.
Setting Up the Prerequisites ​
  • Automatically identify CPU type (AMD or Intel) and set nested virtualization parameters according to the type.
  • Modify GRUB boot parameters to enable IOMMU and disable default framebuffer.
  • Add VFIO module support for hardware device passthrough.
  • Blacklist sound card and graphics card driver modules to avoid conflicts with macOS.
  • Configure KVM-related kernel parameters, ignore MSR errors, and improve compatibility.
  • Patch Proxmox frontend status detection logic to bypass status restrictions.
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/extra_scripts/configure_macos.sh -o configure_macos.sh && chmod +x configure_macos.sh && bash configure_macos.sh
After successful execution, it will show that the system will restart in 15 seconds. This is the normal process, as kernel parameters cannot take effect without restarting.
System Image Download ​
  • All images have pre-installed components and are relatively large (minimum about 4.9GB). Download and extraction tasks will run in the background.
  • Images are complete systems with all components and can be booted and used without internet connection.
  • If the free space on the system disk is less than twice the size of the image, the download will be rejected.
  • Images are in 7z compressed format and need to be extracted before use.
  • You can check the status of current download and extraction tasks at any time. Virtual machines can only be created after completion.
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_macos_images.sh -o install_macos_images.sh && chmod +x install_macos_images.sh && bash install_macos_images.sh --lang=en
Or
shell
bash install_macos_images.sh --lang=en
After the background download task starts, you can close the SSH window and wait for 30 minutes to 3 hours (depending on your server bandwidth and connectivity) to download the ISO 7z compressed package.
When the download task is complete and the current download task query shows empty, you can choose to execute the extraction task. The waiting time for extraction depends on your server's CPU performance.
When the extraction task is complete and the current extraction task query shows empty, all preparations are ready.
Tasks of the same type can run concurrently, and any task can be canceled at any time by entering the PID value.
Build from https://github.com/oneclickvirt/macos currently supported image compressed packages:
# Listed by system release date from old to new
+import{_ as e,v as a,b as s,R as t}from"./chunks/framework.70afa331.js";import{_ as o}from"./chunks/wk7.776871bd.js";const n="/assets/mac0.935d53f3.png",i="/assets/mac00.4296be7b.png",l="/assets/mac1.3307e401.png",c="/assets/mac2.da6ce0bc.png",r="/assets/mac3.76a50b9f.png",p="/assets/mac4.c341ba50.png",d="/assets/mac5.39e1c9a4.png",m="/assets/mac6.1cc0462b.png",h="/assets/mac7.181275ae.png",u="/assets/mac8.dd556f02.png",y="/assets/mac9.c5d88eba.png",g="/assets/mac10.e9c284db.png",C="/assets/mac11.a7587e0e.png",f="/assets/mac12.06b051d3.png",b="/assets/mac13.7d4e3199.png",A="/assets/mac14.39a58b6a.png",k="/assets/mac15.f151793c.png",D="/assets/mac16.eae177db.png",w="/assets/mac17.be61913a.png",v="/assets/mac18.f9454618.png",_="/assets/mac19.845f5510.png",S="/assets/mac20.49a5800c.png",N=JSON.parse('{"title":"Setting Up MacOS Virtual Machine","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_macos.md","filePath":"en/guide/pve/pve_macos.md","lastUpdated":1747730955000}'),x={name:"en/guide/pve/pve_macos.md"},F=t(`
Setting Up MacOS Virtual Machine ​
Prerequisites ​
System and hardware configuration requirements --> Environment detection
You can only set up a MacOS virtual machine when the environment detection confirms that the host machine supports KVM nested virtualization. Otherwise, it will be detected by hardware and cannot be set up.
Setting Up the Prerequisites ​
  • Automatically identify CPU type (AMD or Intel) and set nested virtualization parameters according to the type.
  • Modify GRUB boot parameters to enable IOMMU and disable default framebuffer.
  • Add VFIO module support for hardware device passthrough.
  • Blacklist sound card and graphics card driver modules to avoid conflicts with macOS.
  • Configure KVM-related kernel parameters, ignore MSR errors, and improve compatibility.
  • Patch Proxmox frontend status detection logic to bypass status restrictions.
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/extra_scripts/configure_macos.sh -o configure_macos.sh && chmod +x configure_macos.sh && bash configure_macos.sh
After successful execution, it will show that the system will restart in 15 seconds. This is the normal process, as kernel parameters cannot take effect without restarting.
System Image Download ​
  • All images have pre-installed components and are relatively large (minimum about 4.9GB). Download and extraction tasks will run in the background.
  • Images are complete systems with all components and can be booted and used without internet connection.
  • If the free space on the system disk is less than twice the size of the image, the download will be rejected.
  • Images are in 7z compressed format and need to be extracted before use.
  • You can check the status of current download and extraction tasks at any time. Virtual machines can only be created after completion.
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_macos_images.sh -o install_macos_images.sh && chmod +x install_macos_images.sh && bash install_macos_images.sh --lang=en
Or
shell
bash install_macos_images.sh --lang=en
After the background download task starts, you can close the SSH window and wait for 30 minutes to 3 hours (depending on your server bandwidth and connectivity) to download the ISO 7z compressed package.
When the download task is complete and the current download task query shows empty, you can choose to execute the extraction task. The waiting time for extraction depends on your server's CPU performance.
When the extraction task is complete and the current extraction task query shows empty, all preparations are ready.
Tasks of the same type can run concurrently, and any task can be canceled at any time by entering the PID value.
Build from https://github.com/oneclickvirt/macos currently supported image compressed packages:
# Listed by system release date from old to new
 high-sierra.iso.7z (Size: 5.23GB)
 mojave.iso.7z (Size: 6.03GB)
 catalina.iso.7z (Size: 8.33GB)
diff --git a/assets/en_guide_pve_pve_macos.md.2629d0a7.lean.js b/assets/en_guide_pve_pve_macos.md.8346a51d.lean.js
similarity index 99%
rename from assets/en_guide_pve_pve_macos.md.2629d0a7.lean.js
rename to assets/en_guide_pve_pve_macos.md.8346a51d.lean.js
index 7eefd5b5d4..f8fe7a4076 100644
--- a/assets/en_guide_pve_pve_macos.md.2629d0a7.lean.js
+++ b/assets/en_guide_pve_pve_macos.md.8346a51d.lean.js
@@ -1,4 +1,4 @@
-import{_ as e,v as a,b as s,R as t}from"./chunks/framework.70afa331.js";import{_ as o}from"./chunks/wk7.776871bd.js";const n="/assets/mac0.935d53f3.png",i="/assets/mac00.4296be7b.png",l="/assets/mac1.3307e401.png",c="/assets/mac2.da6ce0bc.png",r="/assets/mac3.76a50b9f.png",p="/assets/mac4.c341ba50.png",d="/assets/mac5.39e1c9a4.png",m="/assets/mac6.1cc0462b.png",h="/assets/mac7.181275ae.png",u="/assets/mac8.dd556f02.png",y="/assets/mac9.c5d88eba.png",g="/assets/mac10.e9c284db.png",C="/assets/mac11.a7587e0e.png",f="/assets/mac12.06b051d3.png",b="/assets/mac13.7d4e3199.png",A="/assets/mac14.39a58b6a.png",k="/assets/mac15.f151793c.png",D="/assets/mac16.eae177db.png",w="/assets/mac17.be61913a.png",v="/assets/mac18.f9454618.png",_="/assets/mac19.845f5510.png",S="/assets/mac20.49a5800c.png",N=JSON.parse('{"title":"Setting Up MacOS Virtual Machine","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_macos.md","filePath":"en/guide/pve/pve_macos.md","lastUpdated":1747726389000}'),x={name:"en/guide/pve/pve_macos.md"},F=t(`
Setting Up MacOS Virtual Machine ​
Prerequisites ​
System and hardware configuration requirements --> Environment detection
You can only set up a MacOS virtual machine when the environment detection confirms that the host machine supports KVM nested virtualization. Otherwise, it will be detected by hardware and cannot be set up.
Setting Up the Prerequisites ​
  • Automatically identify CPU type (AMD or Intel) and set nested virtualization parameters according to the type.
  • Modify GRUB boot parameters to enable IOMMU and disable default framebuffer.
  • Add VFIO module support for hardware device passthrough.
  • Blacklist sound card and graphics card driver modules to avoid conflicts with macOS.
  • Configure KVM-related kernel parameters, ignore MSR errors, and improve compatibility.
  • Patch Proxmox frontend status detection logic to bypass status restrictions.
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/extra_scripts/configure_macos.sh -o configure_macos.sh && chmod +x configure_macos.sh && bash configure_macos.sh
After successful execution, it will show that the system will restart in 15 seconds. This is the normal process, as kernel parameters cannot take effect without restarting.
System Image Download ​
  • All images have pre-installed components and are relatively large (minimum about 4.9GB). Download and extraction tasks will run in the background.
  • Images are complete systems with all components and can be booted and used without internet connection.
  • If the free space on the system disk is less than twice the size of the image, the download will be rejected.
  • Images are in 7z compressed format and need to be extracted before use.
  • You can check the status of current download and extraction tasks at any time. Virtual machines can only be created after completion.
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_macos_images.sh -o install_macos_images.sh && chmod +x install_macos_images.sh && bash install_macos_images.sh --lang=en
Or
shell
bash install_macos_images.sh --lang=en
After the background download task starts, you can close the SSH window and wait for 30 minutes to 3 hours (depending on your server bandwidth and connectivity) to download the ISO 7z compressed package.
When the download task is complete and the current download task query shows empty, you can choose to execute the extraction task. The waiting time for extraction depends on your server's CPU performance.
When the extraction task is complete and the current extraction task query shows empty, all preparations are ready.
Tasks of the same type can run concurrently, and any task can be canceled at any time by entering the PID value.
Build from https://github.com/oneclickvirt/macos currently supported image compressed packages:
# Listed by system release date from old to new
+import{_ as e,v as a,b as s,R as t}from"./chunks/framework.70afa331.js";import{_ as o}from"./chunks/wk7.776871bd.js";const n="/assets/mac0.935d53f3.png",i="/assets/mac00.4296be7b.png",l="/assets/mac1.3307e401.png",c="/assets/mac2.da6ce0bc.png",r="/assets/mac3.76a50b9f.png",p="/assets/mac4.c341ba50.png",d="/assets/mac5.39e1c9a4.png",m="/assets/mac6.1cc0462b.png",h="/assets/mac7.181275ae.png",u="/assets/mac8.dd556f02.png",y="/assets/mac9.c5d88eba.png",g="/assets/mac10.e9c284db.png",C="/assets/mac11.a7587e0e.png",f="/assets/mac12.06b051d3.png",b="/assets/mac13.7d4e3199.png",A="/assets/mac14.39a58b6a.png",k="/assets/mac15.f151793c.png",D="/assets/mac16.eae177db.png",w="/assets/mac17.be61913a.png",v="/assets/mac18.f9454618.png",_="/assets/mac19.845f5510.png",S="/assets/mac20.49a5800c.png",N=JSON.parse('{"title":"Setting Up MacOS Virtual Machine","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_macos.md","filePath":"en/guide/pve/pve_macos.md","lastUpdated":1747730955000}'),x={name:"en/guide/pve/pve_macos.md"},F=t(`
Setting Up MacOS Virtual Machine ​
Prerequisites ​
System and hardware configuration requirements --> Environment detection
You can only set up a MacOS virtual machine when the environment detection confirms that the host machine supports KVM nested virtualization. Otherwise, it will be detected by hardware and cannot be set up.
Setting Up the Prerequisites ​
  • Automatically identify CPU type (AMD or Intel) and set nested virtualization parameters according to the type.
  • Modify GRUB boot parameters to enable IOMMU and disable default framebuffer.
  • Add VFIO module support for hardware device passthrough.
  • Blacklist sound card and graphics card driver modules to avoid conflicts with macOS.
  • Configure KVM-related kernel parameters, ignore MSR errors, and improve compatibility.
  • Patch Proxmox frontend status detection logic to bypass status restrictions.
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/extra_scripts/configure_macos.sh -o configure_macos.sh && chmod +x configure_macos.sh && bash configure_macos.sh
After successful execution, it will show that the system will restart in 15 seconds. This is the normal process, as kernel parameters cannot take effect without restarting.
System Image Download ​
  • All images have pre-installed components and are relatively large (minimum about 4.9GB). Download and extraction tasks will run in the background.
  • Images are complete systems with all components and can be booted and used without internet connection.
  • If the free space on the system disk is less than twice the size of the image, the download will be rejected.
  • Images are in 7z compressed format and need to be extracted before use.
  • You can check the status of current download and extraction tasks at any time. Virtual machines can only be created after completion.
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_macos_images.sh -o install_macos_images.sh && chmod +x install_macos_images.sh && bash install_macos_images.sh --lang=en
Or
shell
bash install_macos_images.sh --lang=en
After the background download task starts, you can close the SSH window and wait for 30 minutes to 3 hours (depending on your server bandwidth and connectivity) to download the ISO 7z compressed package.
When the download task is complete and the current download task query shows empty, you can choose to execute the extraction task. The waiting time for extraction depends on your server's CPU performance.
When the extraction task is complete and the current extraction task query shows empty, all preparations are ready.
Tasks of the same type can run concurrently, and any task can be canceled at any time by entering the PID value.
Build from https://github.com/oneclickvirt/macos currently supported image compressed packages:
# Listed by system release date from old to new
 high-sierra.iso.7z (Size: 5.23GB)
 mojave.iso.7z (Size: 6.03GB)
 catalina.iso.7z (Size: 8.33GB)
diff --git a/assets/en_guide_pve_pve_precheck.md.c455282d.js b/assets/en_guide_pve_pve_precheck.md.b46c1a94.js
similarity index 99%
rename from assets/en_guide_pve_pve_precheck.md.c455282d.js
rename to assets/en_guide_pve_pve_precheck.md.b46c1a94.js
index bab6f03de7..62fcf35017 100644
--- a/assets/en_guide_pve_pve_precheck.md.c455282d.js
+++ b/assets/en_guide_pve_pve_precheck.md.b46c1a94.js
@@ -1,3 +1,3 @@
-import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const o="/assets/pve_kvm_1.0f7e84f0.png",n="/assets/pve_kvm_2.cefb9578.png",r="/assets/pve_kvm_3.1d307586.png",v=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_precheck.md","filePath":"en/guide/pve/pve_precheck.md","lastUpdated":1747726389000}'),i={name:"en/guide/pve/pve_precheck.md"},l=a(`
Preface ​
The following is the introduction of the non-customized part, the customized part has its own corresponding introduction, do not get confused!
If there are unadapted merchants or machines welcome to contact @spiritlhl_bot, will try to support it sometime!
WARNING
Will change the network structure of the host, please make sure that the host can reset the system at any time and that there is no important data on the host before running it.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/pve
Various requirements ​
It is recommended that debian try to use the latest stable version of the system before use.
Do not use this set of scripts in the dynamic IP server (reboot the machine automatically switch the local IP server is not supported, reboot the machine after the IP does not automatically switch the support)
The one-click installation script of this project only adapts to Debian systems, non-Debian can not be installed through the APT source, the official only gives the image of Debian, other systems can only use the ISO installation, or use custom partitions and other ways to solve the problem in the FAQ partition.
  • System requirements: Debian 8+
TIP
It is recommended to install debian11 instead of debian12, because the latter is a beta version, and the debian11 installation is the stable version.
  • Hardware requirements: 2 cores 2G RAM x86_64 or arm architecture server hard disk at least 20G
  • Hardware requirements for KVM: VM-X or AMD-V support (some VPS and all Dedicated servers support).
  • If hardware or system requirements are not met, you can use incus to batch open LXC containers Jump
If you use IPV6 tunnels for IPV6 subnet attachment on the host, be sure to add the contents in the corresponding file when PVE is successfully installed but the gateway is not automatically set, and do not add IPV6 tunnels at the very beginning (without installing PVE).
Setting up virtual memory (SWAP) (optional, not required) ​
TIP
Memory to open some swap lest the machine blow up, if your host computer does not have enough memory and a lot of free hard disk.
Unit conversion: Enter 1024 to generate 1G SWAP-virtual memory, virtual memory takes up hard disk space, when the actual memory is not enough to use the virtual memory will automatically use the virtual memory for memory use, but then bring the IO high occupancy and CPU performance occupancy!
It is recommended to use only twice the size of the actual memory as virtual memory.
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
Detecting the environment ​
  • This project related scripts must be executed before the execution of this script to detect the environment, if it does not meet the requirements of the installation of PVE will not be able to use the subsequent scripts
  • Detection of the local IPV6 network configuration (with or without IPV6 can be installed, just query)
  • Detection of the hardware configuration meets the minimum requirements
  • Detection of the hardware environment can be nested virtualization KVM type of servers, can not be nested virtualization KVM can also open QEMU TCG server, performance is poor
  • Detect whether the system environment can be nested virtualization KVM type of server, can not be nested virtualization KVM can also open QEMU TCG server, performance is poor
  • can not be nested virtualization KVM servers do not recommend the installation of the PVE, it is better to use incus for better performance.
Command:
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh)
If you need to update the IPV6 information before querying, then execute the following command before querying
bash
rm -rf /usr/local/bin/pve_ipv6*
+import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const o="/assets/pve_kvm_1.0f7e84f0.png",n="/assets/pve_kvm_2.cefb9578.png",r="/assets/pve_kvm_3.1d307586.png",v=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_precheck.md","filePath":"en/guide/pve/pve_precheck.md","lastUpdated":1747730955000}'),i={name:"en/guide/pve/pve_precheck.md"},l=a(`
Preface ​
The following is the introduction of the non-customized part, the customized part has its own corresponding introduction, do not get confused!
If there are unadapted merchants or machines welcome to contact @spiritlhl_bot, will try to support it sometime!
WARNING
Will change the network structure of the host, please make sure that the host can reset the system at any time and that there is no important data on the host before running it.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/pve
Various requirements ​
It is recommended that debian try to use the latest stable version of the system before use.
Do not use this set of scripts in the dynamic IP server (reboot the machine automatically switch the local IP server is not supported, reboot the machine after the IP does not automatically switch the support)
The one-click installation script of this project only adapts to Debian systems, non-Debian can not be installed through the APT source, the official only gives the image of Debian, other systems can only use the ISO installation, or use custom partitions and other ways to solve the problem in the FAQ partition.
  • System requirements: Debian 8+
TIP
It is recommended to install debian11 instead of debian12, because the latter is a beta version, and the debian11 installation is the stable version.
  • Hardware requirements: 2 cores 2G RAM x86_64 or arm architecture server hard disk at least 20G
  • Hardware requirements for KVM: VM-X or AMD-V support (some VPS and all Dedicated servers support).
  • If hardware or system requirements are not met, you can use incus to batch open LXC containers Jump
If you use IPV6 tunnels for IPV6 subnet attachment on the host, be sure to add the contents in the corresponding file when PVE is successfully installed but the gateway is not automatically set, and do not add IPV6 tunnels at the very beginning (without installing PVE).
Setting up virtual memory (SWAP) (optional, not required) ​
TIP
Memory to open some swap lest the machine blow up, if your host computer does not have enough memory and a lot of free hard disk.
Unit conversion: Enter 1024 to generate 1G SWAP-virtual memory, virtual memory takes up hard disk space, when the actual memory is not enough to use the virtual memory will automatically use the virtual memory for memory use, but then bring the IO high occupancy and CPU performance occupancy!
It is recommended to use only twice the size of the actual memory as virtual memory.
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
Detecting the environment ​
  • This project related scripts must be executed before the execution of this script to detect the environment, if it does not meet the requirements of the installation of PVE will not be able to use the subsequent scripts
  • Detection of the local IPV6 network configuration (with or without IPV6 can be installed, just query)
  • Detection of the hardware configuration meets the minimum requirements
  • Detection of the hardware environment can be nested virtualization KVM type of servers, can not be nested virtualization KVM can also open QEMU TCG server, performance is poor
  • Detect whether the system environment can be nested virtualization KVM type of server, can not be nested virtualization KVM can also open QEMU TCG server, performance is poor
  • can not be nested virtualization KVM servers do not recommend the installation of the PVE, it is better to use incus for better performance.
Command:
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh)
If you need to update the IPV6 information before querying, then execute the following command before querying
bash
rm -rf /usr/local/bin/pve_ipv6*
 rm -rf /usr/local/bin/pve_check_ipv6*
 rm -rf /usr/local/bin/pve_last_ipv6*
Commands to set up the testing environment for executing this project are as follows:
图片
To perform the above-mentioned query, you only need to use the one-click script below to automatically create a virtual machine. There is no need to manually modify settings on the web interface.
图片
After creating the virtual machines using the subsequent script as mentioned above, it may be necessary to manually modify the settings on the web interface. You will need to disable hardware nested virtualization for each respective virtual machine, as shown in the following diagram.
图片
Stop the virtual machine before making modifications. After the modifications are done, you can start the machine to use NOVNC. Failure to close it may result in bugs that render this virtual machine unusable.
If you forcibly install PVE to enable KVM, even if the startup fails, you can also disable this option and try to start the virtual machine to see if it works.
The reason for these issues is what was stated above, the host does not support nested virtualized KVMs for acceleration.
TIP
Please use the "screen" command to suspend execution before launching the virtual machine, in order to avoid prolonged startup times. Unstable SSH connections could lead to interruptions during the intermediate execution.


',37),p=[l];function c(h,u,m,d,y,b){return t(),s("div",null,p)}const g=e(i,[["render",c]]);export{v as __pageData,g as default};
diff --git a/assets/en_guide_pve_pve_precheck.md.c455282d.lean.js b/assets/en_guide_pve_pve_precheck.md.b46c1a94.lean.js
similarity index 99%
rename from assets/en_guide_pve_pve_precheck.md.c455282d.lean.js
rename to assets/en_guide_pve_pve_precheck.md.b46c1a94.lean.js
index bab6f03de7..62fcf35017 100644
--- a/assets/en_guide_pve_pve_precheck.md.c455282d.lean.js
+++ b/assets/en_guide_pve_pve_precheck.md.b46c1a94.lean.js
@@ -1,3 +1,3 @@
-import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const o="/assets/pve_kvm_1.0f7e84f0.png",n="/assets/pve_kvm_2.cefb9578.png",r="/assets/pve_kvm_3.1d307586.png",v=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_precheck.md","filePath":"en/guide/pve/pve_precheck.md","lastUpdated":1747726389000}'),i={name:"en/guide/pve/pve_precheck.md"},l=a(`
Preface ​
The following is the introduction of the non-customized part, the customized part has its own corresponding introduction, do not get confused!
If there are unadapted merchants or machines welcome to contact @spiritlhl_bot, will try to support it sometime!
WARNING
Will change the network structure of the host, please make sure that the host can reset the system at any time and that there is no important data on the host before running it.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/pve
Various requirements ​
It is recommended that debian try to use the latest stable version of the system before use.
Do not use this set of scripts in the dynamic IP server (reboot the machine automatically switch the local IP server is not supported, reboot the machine after the IP does not automatically switch the support)
The one-click installation script of this project only adapts to Debian systems, non-Debian can not be installed through the APT source, the official only gives the image of Debian, other systems can only use the ISO installation, or use custom partitions and other ways to solve the problem in the FAQ partition.
  • System requirements: Debian 8+
TIP
It is recommended to install debian11 instead of debian12, because the latter is a beta version, and the debian11 installation is the stable version.
  • Hardware requirements: 2 cores 2G RAM x86_64 or arm architecture server hard disk at least 20G
  • Hardware requirements for KVM: VM-X or AMD-V support (some VPS and all Dedicated servers support).
  • If hardware or system requirements are not met, you can use incus to batch open LXC containers Jump
If you use IPV6 tunnels for IPV6 subnet attachment on the host, be sure to add the contents in the corresponding file when PVE is successfully installed but the gateway is not automatically set, and do not add IPV6 tunnels at the very beginning (without installing PVE).
Setting up virtual memory (SWAP) (optional, not required) ​
TIP
Memory to open some swap lest the machine blow up, if your host computer does not have enough memory and a lot of free hard disk.
Unit conversion: Enter 1024 to generate 1G SWAP-virtual memory, virtual memory takes up hard disk space, when the actual memory is not enough to use the virtual memory will automatically use the virtual memory for memory use, but then bring the IO high occupancy and CPU performance occupancy!
It is recommended to use only twice the size of the actual memory as virtual memory.
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
Detecting the environment ​
  • This project related scripts must be executed before the execution of this script to detect the environment, if it does not meet the requirements of the installation of PVE will not be able to use the subsequent scripts
  • Detection of the local IPV6 network configuration (with or without IPV6 can be installed, just query)
  • Detection of the hardware configuration meets the minimum requirements
  • Detection of the hardware environment can be nested virtualization KVM type of servers, can not be nested virtualization KVM can also open QEMU TCG server, performance is poor
  • Detect whether the system environment can be nested virtualization KVM type of server, can not be nested virtualization KVM can also open QEMU TCG server, performance is poor
  • can not be nested virtualization KVM servers do not recommend the installation of the PVE, it is better to use incus for better performance.
Command:
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh)
If you need to update the IPV6 information before querying, then execute the following command before querying
bash
rm -rf /usr/local/bin/pve_ipv6*
+import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const o="/assets/pve_kvm_1.0f7e84f0.png",n="/assets/pve_kvm_2.cefb9578.png",r="/assets/pve_kvm_3.1d307586.png",v=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_precheck.md","filePath":"en/guide/pve/pve_precheck.md","lastUpdated":1747730955000}'),i={name:"en/guide/pve/pve_precheck.md"},l=a(`
Preface ​
The following is the introduction of the non-customized part, the customized part has its own corresponding introduction, do not get confused!
If there are unadapted merchants or machines welcome to contact @spiritlhl_bot, will try to support it sometime!
WARNING
Will change the network structure of the host, please make sure that the host can reset the system at any time and that there is no important data on the host before running it.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/pve
Various requirements ​
It is recommended that debian try to use the latest stable version of the system before use.
Do not use this set of scripts in the dynamic IP server (reboot the machine automatically switch the local IP server is not supported, reboot the machine after the IP does not automatically switch the support)
The one-click installation script of this project only adapts to Debian systems, non-Debian can not be installed through the APT source, the official only gives the image of Debian, other systems can only use the ISO installation, or use custom partitions and other ways to solve the problem in the FAQ partition.
  • System requirements: Debian 8+
TIP
It is recommended to install debian11 instead of debian12, because the latter is a beta version, and the debian11 installation is the stable version.
  • Hardware requirements: 2 cores 2G RAM x86_64 or arm architecture server hard disk at least 20G
  • Hardware requirements for KVM: VM-X or AMD-V support (some VPS and all Dedicated servers support).
  • If hardware or system requirements are not met, you can use incus to batch open LXC containers Jump
If you use IPV6 tunnels for IPV6 subnet attachment on the host, be sure to add the contents in the corresponding file when PVE is successfully installed but the gateway is not automatically set, and do not add IPV6 tunnels at the very beginning (without installing PVE).
Setting up virtual memory (SWAP) (optional, not required) ​
TIP
Memory to open some swap lest the machine blow up, if your host computer does not have enough memory and a lot of free hard disk.
Unit conversion: Enter 1024 to generate 1G SWAP-virtual memory, virtual memory takes up hard disk space, when the actual memory is not enough to use the virtual memory will automatically use the virtual memory for memory use, but then bring the IO high occupancy and CPU performance occupancy!
It is recommended to use only twice the size of the actual memory as virtual memory.
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
Detecting the environment ​
  • This project related scripts must be executed before the execution of this script to detect the environment, if it does not meet the requirements of the installation of PVE will not be able to use the subsequent scripts
  • Detection of the local IPV6 network configuration (with or without IPV6 can be installed, just query)
  • Detection of the hardware configuration meets the minimum requirements
  • Detection of the hardware environment can be nested virtualization KVM type of servers, can not be nested virtualization KVM can also open QEMU TCG server, performance is poor
  • Detect whether the system environment can be nested virtualization KVM type of server, can not be nested virtualization KVM can also open QEMU TCG server, performance is poor
  • can not be nested virtualization KVM servers do not recommend the installation of the PVE, it is better to use incus for better performance.
Command:
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh)
If you need to update the IPV6 information before querying, then execute the following command before querying
bash
rm -rf /usr/local/bin/pve_ipv6*
 rm -rf /usr/local/bin/pve_check_ipv6*
 rm -rf /usr/local/bin/pve_last_ipv6*
Commands to set up the testing environment for executing this project are as follows:
图片
To perform the above-mentioned query, you only need to use the one-click script below to automatically create a virtual machine. There is no need to manually modify settings on the web interface.
图片
After creating the virtual machines using the subsequent script as mentioned above, it may be necessary to manually modify the settings on the web interface. You will need to disable hardware nested virtualization for each respective virtual machine, as shown in the following diagram.
图片
Stop the virtual machine before making modifications. After the modifications are done, you can start the machine to use NOVNC. Failure to close it may result in bugs that render this virtual machine unusable.
If you forcibly install PVE to enable KVM, even if the startup fails, you can also disable this option and try to start the virtual machine to see if it works.
The reason for these issues is what was stated above, the host does not support nested virtualized KVMs for acceleration.
TIP
Please use the "screen" command to suspend execution before launching the virtual machine, in order to avoid prolonged startup times. Unstable SSH connections could lead to interruptions during the intermediate execution.


',37),p=[l];function c(h,u,m,d,y,b){return t(),s("div",null,p)}const g=e(i,[["render",c]]);export{v as __pageData,g as default};
diff --git a/assets/en_guide_pve_pve_qa.md.19a81901.js b/assets/en_guide_pve_pve_qa.md.d3982a2c.js
similarity index 99%
rename from assets/en_guide_pve_pve_qa.md.19a81901.js
rename to assets/en_guide_pve_pve_qa.md.d3982a2c.js
index d553ed8ee6..dce16dae87 100644
--- a/assets/en_guide_pve_pve_qa.md.19a81901.js
+++ b/assets/en_guide_pve_pve_qa.md.d3982a2c.js
@@ -1,4 +1,4 @@
-import{_ as e,v as s,b as a,R as t}from"./chunks/framework.70afa331.js";const o="/assets/onlinepkg.30da8d76.png",n="/assets/dns0.1beb9fa7.png",g=JSON.parse('{"title":"Solve the puzzle","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_qa.md","filePath":"en/guide/pve/pve_qa.md","lastUpdated":1747726389000}'),l={name:"en/guide/pve/pve_qa.md"},r=t(`
Solve the puzzle ​
Within 30 seconds of executing the script, the machine dropped. ​
Original system execution
systemctl restart networking
See if it is not directly offline, if so that is the machine native problem, hot plug or dhcp caused by the network can not restart, it is recommended to replace the host system or DD a new system to try!
Generally speaking, this situation occurs in the exclusive service Debian11 system, switch to Debian12 system will not be a problem!
Installation of PVE fails with an error saying that some packages do not exist. ​
Execute the following command to query the source of apt
shell
grep -r "deb " /etc/apt/sources.list /etc/apt/sources.list.d/
If you see
deb file://
+import{_ as e,v as s,b as a,R as t}from"./chunks/framework.70afa331.js";const o="/assets/onlinepkg.30da8d76.png",n="/assets/dns0.1beb9fa7.png",g=JSON.parse('{"title":"Solve the puzzle","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_qa.md","filePath":"en/guide/pve/pve_qa.md","lastUpdated":1747730955000}'),l={name:"en/guide/pve/pve_qa.md"},r=t(`
Solve the puzzle ​
Within 30 seconds of executing the script, the machine dropped. ​
Original system execution
systemctl restart networking
See if it is not directly offline, if so that is the machine native problem, hot plug or dhcp caused by the network can not restart, it is recommended to replace the host system or DD a new system to try!
Generally speaking, this situation occurs in the exclusive service Debian11 system, switch to Debian12 system will not be a problem!
Installation of PVE fails with an error saying that some packages do not exist. ​
Execute the following command to query the source of apt
shell
grep -r "deb " /etc/apt/sources.list /etc/apt/sources.list.d/
If you see
deb file://
 deb cdrom:[
A line starting like this proves that the host is using local sources instead of network sources, and you need to replace the sources in /etc/apt/sources.list with a line such as
pct
Replace the network source with the same to install using the PVE one-click install script.
Replacing the network source can be done using the following command for apt source replacement
bash <(curl -sSL https://raw.githubusercontent.com/SuperManito/LinuxMirrors/main/ChangeMirrors.sh) --abroad
Successful PVE Installation but Lost Connection After Reboot ​
If the machine successfully installs PVE and the web interface is accessible, but loses connection after a reboot, please execute the following commands after a successful PVE installation and before rebooting:
bash
auto_interface=$(grep '^auto ' /etc/network/interfaces | grep -v '^auto lo' | awk '{print $2}' | head -n 1)
 if ! grep -q "^post-up /sbin/ethtool" /etc/network/interfaces; then
     chattr -i /etc/network/interfaces
diff --git a/assets/en_guide_pve_pve_qa.md.19a81901.lean.js b/assets/en_guide_pve_pve_qa.md.d3982a2c.lean.js
similarity index 99%
rename from assets/en_guide_pve_pve_qa.md.19a81901.lean.js
rename to assets/en_guide_pve_pve_qa.md.d3982a2c.lean.js
index d553ed8ee6..dce16dae87 100644
--- a/assets/en_guide_pve_pve_qa.md.19a81901.lean.js
+++ b/assets/en_guide_pve_pve_qa.md.d3982a2c.lean.js
@@ -1,4 +1,4 @@
-import{_ as e,v as s,b as a,R as t}from"./chunks/framework.70afa331.js";const o="/assets/onlinepkg.30da8d76.png",n="/assets/dns0.1beb9fa7.png",g=JSON.parse('{"title":"Solve the puzzle","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_qa.md","filePath":"en/guide/pve/pve_qa.md","lastUpdated":1747726389000}'),l={name:"en/guide/pve/pve_qa.md"},r=t(`
Solve the puzzle ​
Within 30 seconds of executing the script, the machine dropped. ​
Original system execution
systemctl restart networking
See if it is not directly offline, if so that is the machine native problem, hot plug or dhcp caused by the network can not restart, it is recommended to replace the host system or DD a new system to try!
Generally speaking, this situation occurs in the exclusive service Debian11 system, switch to Debian12 system will not be a problem!
Installation of PVE fails with an error saying that some packages do not exist. ​
Execute the following command to query the source of apt
shell
grep -r "deb " /etc/apt/sources.list /etc/apt/sources.list.d/
If you see
deb file://
+import{_ as e,v as s,b as a,R as t}from"./chunks/framework.70afa331.js";const o="/assets/onlinepkg.30da8d76.png",n="/assets/dns0.1beb9fa7.png",g=JSON.parse('{"title":"Solve the puzzle","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_qa.md","filePath":"en/guide/pve/pve_qa.md","lastUpdated":1747730955000}'),l={name:"en/guide/pve/pve_qa.md"},r=t(`
Solve the puzzle ​
Within 30 seconds of executing the script, the machine dropped. ​
Original system execution
systemctl restart networking
See if it is not directly offline, if so that is the machine native problem, hot plug or dhcp caused by the network can not restart, it is recommended to replace the host system or DD a new system to try!
Generally speaking, this situation occurs in the exclusive service Debian11 system, switch to Debian12 system will not be a problem!
Installation of PVE fails with an error saying that some packages do not exist. ​
Execute the following command to query the source of apt
shell
grep -r "deb " /etc/apt/sources.list /etc/apt/sources.list.d/
If you see
deb file://
 deb cdrom:[
A line starting like this proves that the host is using local sources instead of network sources, and you need to replace the sources in /etc/apt/sources.list with a line such as
pct
Replace the network source with the same to install using the PVE one-click install script.
Replacing the network source can be done using the following command for apt source replacement
bash <(curl -sSL https://raw.githubusercontent.com/SuperManito/LinuxMirrors/main/ChangeMirrors.sh) --abroad
Successful PVE Installation but Lost Connection After Reboot ​
If the machine successfully installs PVE and the web interface is accessible, but loses connection after a reboot, please execute the following commands after a successful PVE installation and before rebooting:
bash
auto_interface=$(grep '^auto ' /etc/network/interfaces | grep -v '^auto lo' | awk '{print $2}' | head -n 1)
 if ! grep -q "^post-up /sbin/ethtool" /etc/network/interfaces; then
     chattr -i /etc/network/interfaces
diff --git a/assets/en_guide_pve_pve_thanks.md.699f61e5.js b/assets/en_guide_pve_pve_thanks.md.28da570a.js
similarity index 95%
rename from assets/en_guide_pve_pve_thanks.md.699f61e5.js
rename to assets/en_guide_pve_pve_thanks.md.28da570a.js
index bad5add762..c30ba3bcb8 100644
--- a/assets/en_guide_pve_pve_thanks.md.699f61e5.js
+++ b/assets/en_guide_pve_pve_thanks.md.28da570a.js
@@ -1 +1 @@
-import{_ as e,v as r,b as t,R as o}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/pve/pve_thanks.md","filePath":"en/guide/pve/pve_thanks.md","lastUpdated":1747726389000}'),a={name:"en/guide/pve/pve_thanks.md"},n=o('
Acknowledgements ​
https://forum.proxmox.com/
https://blog.ilolicon.com/archives/615
https://github.com/Ella-Alinda/somescripts/blob/main/nat.sh
https://pve.proxmox.com/pve-docs/qm.1.html
https://down.idc.wiki/Image/realServer-Template/
https://mirrors.tuna.tsinghua.edu.cn/proxmox/
https://github.com/roacn/pve/blob/main/pve.sh
https://github.com/spiritLHLS/lxc
https://github.com/leitbogioro/Tools
https://github.com/jiangcuo/Proxmox-Port
https://gitlab.com/minkebox/pimox
https://github.com/jiangcuo/run_proxmox_in_docker
https://github.com/yoursunny/ndpresponder
https://github.com/SuperManito/LinuxMirrors
Thank @Ella-Alinda for providing PVE guidance.
',16),p=[n];function s(i,h,l,m,c,g){return r(),t("div",null,p)}const d=e(a,[["render",s]]);export{u as __pageData,d as default};
+import{_ as e,v as r,b as t,R as o}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/pve/pve_thanks.md","filePath":"en/guide/pve/pve_thanks.md","lastUpdated":1747730955000}'),a={name:"en/guide/pve/pve_thanks.md"},n=o('
Acknowledgements ​
https://forum.proxmox.com/
https://blog.ilolicon.com/archives/615
https://github.com/Ella-Alinda/somescripts/blob/main/nat.sh
https://pve.proxmox.com/pve-docs/qm.1.html
https://down.idc.wiki/Image/realServer-Template/
https://mirrors.tuna.tsinghua.edu.cn/proxmox/
https://github.com/roacn/pve/blob/main/pve.sh
https://github.com/spiritLHLS/lxc
https://github.com/leitbogioro/Tools
https://github.com/jiangcuo/Proxmox-Port
https://gitlab.com/minkebox/pimox
https://github.com/jiangcuo/run_proxmox_in_docker
https://github.com/yoursunny/ndpresponder
https://github.com/SuperManito/LinuxMirrors
Thank @Ella-Alinda for providing PVE guidance.
',16),p=[n];function s(i,h,l,m,c,g){return r(),t("div",null,p)}const d=e(a,[["render",s]]);export{u as __pageData,d as default};
diff --git a/assets/en_guide_pve_pve_thanks.md.699f61e5.lean.js b/assets/en_guide_pve_pve_thanks.md.28da570a.lean.js
similarity index 95%
rename from assets/en_guide_pve_pve_thanks.md.699f61e5.lean.js
rename to assets/en_guide_pve_pve_thanks.md.28da570a.lean.js
index bad5add762..c30ba3bcb8 100644
--- a/assets/en_guide_pve_pve_thanks.md.699f61e5.lean.js
+++ b/assets/en_guide_pve_pve_thanks.md.28da570a.lean.js
@@ -1 +1 @@
-import{_ as e,v as r,b as t,R as o}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/pve/pve_thanks.md","filePath":"en/guide/pve/pve_thanks.md","lastUpdated":1747726389000}'),a={name:"en/guide/pve/pve_thanks.md"},n=o('
Acknowledgements ​
https://forum.proxmox.com/
https://blog.ilolicon.com/archives/615
https://github.com/Ella-Alinda/somescripts/blob/main/nat.sh
https://pve.proxmox.com/pve-docs/qm.1.html
https://down.idc.wiki/Image/realServer-Template/
https://mirrors.tuna.tsinghua.edu.cn/proxmox/
https://github.com/roacn/pve/blob/main/pve.sh
https://github.com/spiritLHLS/lxc
https://github.com/leitbogioro/Tools
https://github.com/jiangcuo/Proxmox-Port
https://gitlab.com/minkebox/pimox
https://github.com/jiangcuo/run_proxmox_in_docker
https://github.com/yoursunny/ndpresponder
https://github.com/SuperManito/LinuxMirrors
Thank @Ella-Alinda for providing PVE guidance.
',16),p=[n];function s(i,h,l,m,c,g){return r(),t("div",null,p)}const d=e(a,[["render",s]]);export{u as __pageData,d as default};
+import{_ as e,v as r,b as t,R as o}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/pve/pve_thanks.md","filePath":"en/guide/pve/pve_thanks.md","lastUpdated":1747730955000}'),a={name:"en/guide/pve/pve_thanks.md"},n=o('
Acknowledgements ​
https://forum.proxmox.com/
https://blog.ilolicon.com/archives/615
https://github.com/Ella-Alinda/somescripts/blob/main/nat.sh
https://pve.proxmox.com/pve-docs/qm.1.html
https://down.idc.wiki/Image/realServer-Template/
https://mirrors.tuna.tsinghua.edu.cn/proxmox/
https://github.com/roacn/pve/blob/main/pve.sh
https://github.com/spiritLHLS/lxc
https://github.com/leitbogioro/Tools
https://github.com/jiangcuo/Proxmox-Port
https://gitlab.com/minkebox/pimox
https://github.com/jiangcuo/run_proxmox_in_docker
https://github.com/yoursunny/ndpresponder
https://github.com/SuperManito/LinuxMirrors
Thank @Ella-Alinda for providing PVE guidance.
',16),p=[n];function s(i,h,l,m,c,g){return r(),t("div",null,p)}const d=e(a,[["render",s]]);export{u as __pageData,d as default};
diff --git a/assets/en_guide_pve_pve_windows.md.c5b7b7f6.js b/assets/en_guide_pve_pve_windows.md.7c33cbb1.js
similarity index 99%
rename from assets/en_guide_pve_pve_windows.md.c5b7b7f6.js
rename to assets/en_guide_pve_pve_windows.md.7c33cbb1.js
index 8c74c80f07..7c50b4d0fc 100644
--- a/assets/en_guide_pve_pve_windows.md.c5b7b7f6.js
+++ b/assets/en_guide_pve_pve_windows.md.7c33cbb1.js
@@ -1,2 +1,2 @@
-import{_ as t,v as o,b as i,R as s}from"./chunks/framework.70afa331.js";import{_ as e}from"./chunks/wk7.776871bd.js";const n="/assets/dlwiniso.a2c0c1ef.png",a="/assets/dlwiniso1.4fa2fea0.png",r="/assets/general.ea03923c.png",c="/assets/os.b2be1a5c.png",d="/assets/system.8e69987e.png",l="/assets/disks.8065a143.png",p="/assets/cpu.4618bc7b.png",h="/assets/memory.c4992870.png",g="/assets/network.48037353.png",m="/assets/finish.0c3eac87.png",u="/assets/start.3aebbfd4.png",w="/assets/gic1.42bfd260.png",f="/assets/gic2.ff78c941.png",k="/assets/gic3.4a04cf3d.png",_="/assets/gic4.e2343160.png",v="/assets/gic5.54522dff.png",I="/assets/gic6.97561122.png",b="/assets/gic7.a8679083.png",y="/assets/gic8.fe7d0b3c.png",O="/assets/gic9.4cdf4daa.png",x="/assets/net1.4f166207.png",S="/assets/net2.e2773ada.png",C="/assets/net3.40e8a226.png",V="/assets/net4.a81e777c.png",D="/assets/virtio.b42d8275.png",P="/assets/lower2.e782a20a.png",N="/assets/lower1.28498396.png",q="/assets/nodisk.5ec86f3b.png",U="/assets/nodisk1.671c1309.png",M="/assets/nodisk2.ff20bb76.png",A="/assets/nodisk3.71534a11.png",T="/assets/nodisk4.b08d75e3.png",W="/assets/wk4.004be17f.png",z="/assets/wk5.6cdba880.png",B="/assets/wk6.667c5c95.png",F="/assets/wk1.7d9f24d7.png",E="/assets/wk2.2e88d91a.png",R="/assets/wk3.975bc38e.png",te=JSON.parse('{"title":"Setting Up Windows Visual Machine","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_windows.md","filePath":"en/guide/pve/pve_windows.md","lastUpdated":1747726389000}'),G={name:"en/guide/pve/pve_windows.md"},L=s('
Setting Up Windows Visual Machine ​
Using ISO Image with VirtIO for VM Setup ​
1. Download the Image ​
Before installation, you need to download the image file via local(pve) --> ISO images --> Download from URL
For the download link (URL:), you can use files from: https://github.com/ILLKX/Windows-VirtIO
Enter win.iso as the File Name:
download
Click Download. After downloading is complete, you can see the file size of win.iso on the current page, confirming it's in ISO format.
downloaded
2. Setting Up the Template ​
Click Create VM in the top right corner of the page.
In the General window, select mypool for Resource Pool:, enter win for Name, then click Next.
general
In the OS window, select win.iso for ISO image. For Guest OS, select Microsoft Windows as the Type and choose the appropriate Version for your ISO. For example, if you downloaded Windows 2022, select 11/2022, then click Next.
OS
In the System window, select VirtIO-GPU for Graphic card, q35 for Machine, VirtIO SCSI for SCSI Controller, and Default (SeaBIOS) for BIOS, then click Next.
system
In the Disk window, select Write Back for Cache, enter your desired disk size in Disk size (GiB) (generally not less than 20), and choose the storage location in Storage. In this example, only the system disk local is available, so local is selected. Then click Next.
disk
In the CPU window, enter the number of cores needed in Cores, then click Next.
cpu
In the Memory window, enter the desired memory size in Memory (MiB), then click Next.
memory
In the Network window, select vmbr1 for Bridge, VirtIO (paravirtualized) for Model, uncheck Firewall, then click Next.
Network
In the Confirm window, click Finish.
finish
3. Graphical Installation Configuration ​
Click on the template you've set up on the left, click Start in the upper right corner to start the virtual machine, then click Console to enter the VNC interface and wait for the operating system to boot.
console
In the VNC, click Next, then Install now, then I don't have a product key, check Accept license, click Next, and then select Custom installation.
win0win1win2win3win4
If the image comes with VirtIO drivers, you should be able to see the available system storage disk and its size. Select it and click Next.
win5win6
Wait for the system to install. It may restart automatically several times and could take more than 10 minutes.
win7
After installation is complete, you'll be asked to set a password during first login.
win8
Once setup is complete, there's a pop-up box on the left side of the NOVNC page. Click the first button, then follow the login prompt by pressing Ctrl+Alt+last button to enter the login page.
4. Network Initialization ​
Since the PVE is set up with a static network through this project, you need to manually modify the bound IP address after logging in, rather than using DHCP.
Right-click in the bottom right corner of the desktop and select Open Network and Internet settings. In the settings page that appears, click Change adapter options. win9
In the Network Connections, select Ethernet and click Change settings of this connection. win10
In the popup window, select Internet Protocol Version 4 (TCP/IPv4) and click Properties. win11
In the new dialog box, select Use the following IP address and enter: IP address(I): 172.16.1.xxx (replace xxx with your desired IP, I used 100 for convenience as my vmid is 100) Subnet mask(U): 255.255.255.0 Default gateway(D): 172.16.1.1
Then select Use the following DNS server addresses and enter:
8.8.8.8
+import{_ as t,v as o,b as i,R as s}from"./chunks/framework.70afa331.js";import{_ as e}from"./chunks/wk7.776871bd.js";const n="/assets/dlwiniso.a2c0c1ef.png",a="/assets/dlwiniso1.4fa2fea0.png",r="/assets/general.ea03923c.png",c="/assets/os.b2be1a5c.png",d="/assets/system.8e69987e.png",l="/assets/disks.8065a143.png",p="/assets/cpu.4618bc7b.png",h="/assets/memory.c4992870.png",g="/assets/network.48037353.png",m="/assets/finish.0c3eac87.png",u="/assets/start.3aebbfd4.png",w="/assets/gic1.42bfd260.png",f="/assets/gic2.ff78c941.png",k="/assets/gic3.4a04cf3d.png",_="/assets/gic4.e2343160.png",v="/assets/gic5.54522dff.png",I="/assets/gic6.97561122.png",b="/assets/gic7.a8679083.png",y="/assets/gic8.fe7d0b3c.png",O="/assets/gic9.4cdf4daa.png",x="/assets/net1.4f166207.png",S="/assets/net2.e2773ada.png",C="/assets/net3.40e8a226.png",V="/assets/net4.a81e777c.png",D="/assets/virtio.b42d8275.png",P="/assets/lower2.e782a20a.png",N="/assets/lower1.28498396.png",q="/assets/nodisk.5ec86f3b.png",U="/assets/nodisk1.671c1309.png",M="/assets/nodisk2.ff20bb76.png",A="/assets/nodisk3.71534a11.png",T="/assets/nodisk4.b08d75e3.png",W="/assets/wk4.004be17f.png",z="/assets/wk5.6cdba880.png",B="/assets/wk6.667c5c95.png",F="/assets/wk1.7d9f24d7.png",E="/assets/wk2.2e88d91a.png",R="/assets/wk3.975bc38e.png",te=JSON.parse('{"title":"Setting Up Windows Visual Machine","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_windows.md","filePath":"en/guide/pve/pve_windows.md","lastUpdated":1747730955000}'),G={name:"en/guide/pve/pve_windows.md"},L=s('
Setting Up Windows Visual Machine ​
Using ISO Image with VirtIO for VM Setup ​
1. Download the Image ​
Before installation, you need to download the image file via local(pve) --> ISO images --> Download from URL
For the download link (URL:), you can use files from: https://github.com/ILLKX/Windows-VirtIO
Enter win.iso as the File Name:
download
Click Download. After downloading is complete, you can see the file size of win.iso on the current page, confirming it's in ISO format.
downloaded
2. Setting Up the Template ​
Click Create VM in the top right corner of the page.
In the General window, select mypool for Resource Pool:, enter win for Name, then click Next.
general
In the OS window, select win.iso for ISO image. For Guest OS, select Microsoft Windows as the Type and choose the appropriate Version for your ISO. For example, if you downloaded Windows 2022, select 11/2022, then click Next.
OS
In the System window, select VirtIO-GPU for Graphic card, q35 for Machine, VirtIO SCSI for SCSI Controller, and Default (SeaBIOS) for BIOS, then click Next.
system
In the Disk window, select Write Back for Cache, enter your desired disk size in Disk size (GiB) (generally not less than 20), and choose the storage location in Storage. In this example, only the system disk local is available, so local is selected. Then click Next.
disk
In the CPU window, enter the number of cores needed in Cores, then click Next.
cpu
In the Memory window, enter the desired memory size in Memory (MiB), then click Next.
memory
In the Network window, select vmbr1 for Bridge, VirtIO (paravirtualized) for Model, uncheck Firewall, then click Next.
Network
In the Confirm window, click Finish.
finish
3. Graphical Installation Configuration ​
Click on the template you've set up on the left, click Start in the upper right corner to start the virtual machine, then click Console to enter the VNC interface and wait for the operating system to boot.
console
In the VNC, click Next, then Install now, then I don't have a product key, check Accept license, click Next, and then select Custom installation.
win0win1win2win3win4
If the image comes with VirtIO drivers, you should be able to see the available system storage disk and its size. Select it and click Next.
win5win6
Wait for the system to install. It may restart automatically several times and could take more than 10 minutes.
win7
After installation is complete, you'll be asked to set a password during first login.
win8
Once setup is complete, there's a pop-up box on the left side of the NOVNC page. Click the first button, then follow the login prompt by pressing Ctrl+Alt+last button to enter the login page.
4. Network Initialization ​
Since the PVE is set up with a static network through this project, you need to manually modify the bound IP address after logging in, rather than using DHCP.
Right-click in the bottom right corner of the desktop and select Open Network and Internet settings. In the settings page that appears, click Change adapter options. win9
In the Network Connections, select Ethernet and click Change settings of this connection. win10
In the popup window, select Internet Protocol Version 4 (TCP/IPv4) and click Properties. win11
In the new dialog box, select Use the following IP address and enter: IP address(I): 172.16.1.xxx (replace xxx with your desired IP, I used 100 for convenience as my vmid is 100) Subnet mask(U): 255.255.255.0 Default gateway(D): 172.16.1.1
Then select Use the following DNS server addresses and enter:
8.8.8.8
 144.144.144.144
Click OK in the bottom right corner, and make sure Validate settings upon exit is NOT checked.
win12
Click OK and Yes for any other dialog boxes, and your virtual machine will now have network connectivity.
5. Unmounting the CD Drive ​
Manually click on the corresponding CD in the Hardware on the web side of ProxmoxVE and select Remove, then restart the VM and you can use it directly.
wk
Using ISO Images without VirtIO for VM Installation ​
1. Download Images ​
For Windows images without VirtIO, you can use:
https://down.idc.wiki/ISOS/Windows/
For VirtIO ISO images, you can use:
https://down.idc.wiki/ISOS/Toolkit/
or
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/
Alternatively, you can download just the MSI package, package it into an ISO format locally, and then upload it to ProxmoxVE.
This way, the package is smaller. The official package contains support for all Windows images and is about 500MB, while a self-packaged one is around 5MB.
2. VirtIO Import ​
Note that in ProxmoxVE version 8.x and later, you can select VirtIO boot loading by default in the OS section, as shown in the image:
virtio
In lower versions of ProxmoxVE, such as 7.x and 6.x, you cannot select VirtIO boot loading by default in the OS section:
lower
You need to manually add CD/DVD Drive by clicking Add in the Hardware section and selecting the downloaded VirtIO ISO file:
lower
Then proceed as usual until you reach:
nodisk
At this point, you can't find the hard disk. You need to select Load Driver:
nodisk
Then select the VirtIO as your driver disk, click open, and import the corresponding system driver from the amd64 directory:
nodisk
I'm using a Windows Server 2019 image, so I imported the 2k19 driver. After importing, select the imported driver and click Next:
nodisk
nodisk
Now you should be able to see the hard disk. Select it and continue with the installation steps as in the previous tutorial until the system installation is complete and you reach the desktop.
3. Installing Drivers via virtio-win-guest-tools ​
Once successfully installed and at the desktop, you still need to manually install the drivers.
Open the VirtIO driver's CD drive directory. At the bottom, there's a virtio-win-guest-tools program that will install the required VirtIO drivers, including the VirtIO network card driver:
wk
wk
wk
After clicking install, the network card driver will be installed. For subsequent network settings, refer to the network initialization tutorial mentioned earlier.
4. Installing Network Card Driver (Alternative) ​
After successful installation and reaching the desktop, you may still need to manually install the network card driver to connect to the network:
  1. Open Control Panel → Device Manager
  2. Find the Ethernet Controller, right-click and select Update Driver
  3. Select Browse my computer for driver software (R)
  4. Browse to the VirtIO driver's CD drive directory
  5. Open the NetKVM folder
  6. Select the driver folder corresponding to your current system version (like the above operation, I would choose the 2k19 folder with amd64 drivers)
  7. Confirm the installation, and after completion, the VirtIO network card driver will be successfully loaded
wk
wk
wk
For subsequent network settings, refer to the network initialization tutorial mentioned earlier.
5. Unmounting the CD Drive ​
In the ProxmoxVE web interface, manually click on the corresponding CD in the Hardware section, select Remove, and then restart the virtual machine. This way, you can use it directly:
wk
',97),K=[L];function H($,Y,j,X,J,Q){return o(),i("div",null,K)}const oe=t(G,[["render",H]]);export{te as __pageData,oe as default};
diff --git a/assets/en_guide_pve_pve_windows.md.c5b7b7f6.lean.js b/assets/en_guide_pve_pve_windows.md.7c33cbb1.lean.js
similarity index 99%
rename from assets/en_guide_pve_pve_windows.md.c5b7b7f6.lean.js
rename to assets/en_guide_pve_pve_windows.md.7c33cbb1.lean.js
index 8c74c80f07..7c50b4d0fc 100644
--- a/assets/en_guide_pve_pve_windows.md.c5b7b7f6.lean.js
+++ b/assets/en_guide_pve_pve_windows.md.7c33cbb1.lean.js
@@ -1,2 +1,2 @@
-import{_ as t,v as o,b as i,R as s}from"./chunks/framework.70afa331.js";import{_ as e}from"./chunks/wk7.776871bd.js";const n="/assets/dlwiniso.a2c0c1ef.png",a="/assets/dlwiniso1.4fa2fea0.png",r="/assets/general.ea03923c.png",c="/assets/os.b2be1a5c.png",d="/assets/system.8e69987e.png",l="/assets/disks.8065a143.png",p="/assets/cpu.4618bc7b.png",h="/assets/memory.c4992870.png",g="/assets/network.48037353.png",m="/assets/finish.0c3eac87.png",u="/assets/start.3aebbfd4.png",w="/assets/gic1.42bfd260.png",f="/assets/gic2.ff78c941.png",k="/assets/gic3.4a04cf3d.png",_="/assets/gic4.e2343160.png",v="/assets/gic5.54522dff.png",I="/assets/gic6.97561122.png",b="/assets/gic7.a8679083.png",y="/assets/gic8.fe7d0b3c.png",O="/assets/gic9.4cdf4daa.png",x="/assets/net1.4f166207.png",S="/assets/net2.e2773ada.png",C="/assets/net3.40e8a226.png",V="/assets/net4.a81e777c.png",D="/assets/virtio.b42d8275.png",P="/assets/lower2.e782a20a.png",N="/assets/lower1.28498396.png",q="/assets/nodisk.5ec86f3b.png",U="/assets/nodisk1.671c1309.png",M="/assets/nodisk2.ff20bb76.png",A="/assets/nodisk3.71534a11.png",T="/assets/nodisk4.b08d75e3.png",W="/assets/wk4.004be17f.png",z="/assets/wk5.6cdba880.png",B="/assets/wk6.667c5c95.png",F="/assets/wk1.7d9f24d7.png",E="/assets/wk2.2e88d91a.png",R="/assets/wk3.975bc38e.png",te=JSON.parse('{"title":"Setting Up Windows Visual Machine","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_windows.md","filePath":"en/guide/pve/pve_windows.md","lastUpdated":1747726389000}'),G={name:"en/guide/pve/pve_windows.md"},L=s('
Setting Up Windows Visual Machine ​
Using ISO Image with VirtIO for VM Setup ​
1. Download the Image ​
Before installation, you need to download the image file via local(pve) --> ISO images --> Download from URL
For the download link (URL:), you can use files from: https://github.com/ILLKX/Windows-VirtIO
Enter win.iso as the File Name:
download
Click Download. After downloading is complete, you can see the file size of win.iso on the current page, confirming it's in ISO format.
downloaded
2. Setting Up the Template ​
Click Create VM in the top right corner of the page.
In the General window, select mypool for Resource Pool:, enter win for Name, then click Next.
general
In the OS window, select win.iso for ISO image. For Guest OS, select Microsoft Windows as the Type and choose the appropriate Version for your ISO. For example, if you downloaded Windows 2022, select 11/2022, then click Next.
OS
In the System window, select VirtIO-GPU for Graphic card, q35 for Machine, VirtIO SCSI for SCSI Controller, and Default (SeaBIOS) for BIOS, then click Next.
system
In the Disk window, select Write Back for Cache, enter your desired disk size in Disk size (GiB) (generally not less than 20), and choose the storage location in Storage. In this example, only the system disk local is available, so local is selected. Then click Next.
disk
In the CPU window, enter the number of cores needed in Cores, then click Next.
cpu
In the Memory window, enter the desired memory size in Memory (MiB), then click Next.
memory
In the Network window, select vmbr1 for Bridge, VirtIO (paravirtualized) for Model, uncheck Firewall, then click Next.
Network
In the Confirm window, click Finish.
finish
3. Graphical Installation Configuration ​
Click on the template you've set up on the left, click Start in the upper right corner to start the virtual machine, then click Console to enter the VNC interface and wait for the operating system to boot.
console
In the VNC, click Next, then Install now, then I don't have a product key, check Accept license, click Next, and then select Custom installation.
win0win1win2win3win4
If the image comes with VirtIO drivers, you should be able to see the available system storage disk and its size. Select it and click Next.
win5win6
Wait for the system to install. It may restart automatically several times and could take more than 10 minutes.
win7
After installation is complete, you'll be asked to set a password during first login.
win8
Once setup is complete, there's a pop-up box on the left side of the NOVNC page. Click the first button, then follow the login prompt by pressing Ctrl+Alt+last button to enter the login page.
4. Network Initialization ​
Since the PVE is set up with a static network through this project, you need to manually modify the bound IP address after logging in, rather than using DHCP.
Right-click in the bottom right corner of the desktop and select Open Network and Internet settings. In the settings page that appears, click Change adapter options. win9
In the Network Connections, select Ethernet and click Change settings of this connection. win10
In the popup window, select Internet Protocol Version 4 (TCP/IPv4) and click Properties. win11
In the new dialog box, select Use the following IP address and enter: IP address(I): 172.16.1.xxx (replace xxx with your desired IP, I used 100 for convenience as my vmid is 100) Subnet mask(U): 255.255.255.0 Default gateway(D): 172.16.1.1
Then select Use the following DNS server addresses and enter:
8.8.8.8
+import{_ as t,v as o,b as i,R as s}from"./chunks/framework.70afa331.js";import{_ as e}from"./chunks/wk7.776871bd.js";const n="/assets/dlwiniso.a2c0c1ef.png",a="/assets/dlwiniso1.4fa2fea0.png",r="/assets/general.ea03923c.png",c="/assets/os.b2be1a5c.png",d="/assets/system.8e69987e.png",l="/assets/disks.8065a143.png",p="/assets/cpu.4618bc7b.png",h="/assets/memory.c4992870.png",g="/assets/network.48037353.png",m="/assets/finish.0c3eac87.png",u="/assets/start.3aebbfd4.png",w="/assets/gic1.42bfd260.png",f="/assets/gic2.ff78c941.png",k="/assets/gic3.4a04cf3d.png",_="/assets/gic4.e2343160.png",v="/assets/gic5.54522dff.png",I="/assets/gic6.97561122.png",b="/assets/gic7.a8679083.png",y="/assets/gic8.fe7d0b3c.png",O="/assets/gic9.4cdf4daa.png",x="/assets/net1.4f166207.png",S="/assets/net2.e2773ada.png",C="/assets/net3.40e8a226.png",V="/assets/net4.a81e777c.png",D="/assets/virtio.b42d8275.png",P="/assets/lower2.e782a20a.png",N="/assets/lower1.28498396.png",q="/assets/nodisk.5ec86f3b.png",U="/assets/nodisk1.671c1309.png",M="/assets/nodisk2.ff20bb76.png",A="/assets/nodisk3.71534a11.png",T="/assets/nodisk4.b08d75e3.png",W="/assets/wk4.004be17f.png",z="/assets/wk5.6cdba880.png",B="/assets/wk6.667c5c95.png",F="/assets/wk1.7d9f24d7.png",E="/assets/wk2.2e88d91a.png",R="/assets/wk3.975bc38e.png",te=JSON.parse('{"title":"Setting Up Windows Visual Machine","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_windows.md","filePath":"en/guide/pve/pve_windows.md","lastUpdated":1747730955000}'),G={name:"en/guide/pve/pve_windows.md"},L=s('
Setting Up Windows Visual Machine ​
Using ISO Image with VirtIO for VM Setup ​
1. Download the Image ​
Before installation, you need to download the image file via local(pve) --> ISO images --> Download from URL
For the download link (URL:), you can use files from: https://github.com/ILLKX/Windows-VirtIO
Enter win.iso as the File Name:
download
Click Download. After downloading is complete, you can see the file size of win.iso on the current page, confirming it's in ISO format.
downloaded
2. Setting Up the Template ​
Click Create VM in the top right corner of the page.
In the General window, select mypool for Resource Pool:, enter win for Name, then click Next.
general
In the OS window, select win.iso for ISO image. For Guest OS, select Microsoft Windows as the Type and choose the appropriate Version for your ISO. For example, if you downloaded Windows 2022, select 11/2022, then click Next.
OS
In the System window, select VirtIO-GPU for Graphic card, q35 for Machine, VirtIO SCSI for SCSI Controller, and Default (SeaBIOS) for BIOS, then click Next.
system
In the Disk window, select Write Back for Cache, enter your desired disk size in Disk size (GiB) (generally not less than 20), and choose the storage location in Storage. In this example, only the system disk local is available, so local is selected. Then click Next.
disk
In the CPU window, enter the number of cores needed in Cores, then click Next.
cpu
In the Memory window, enter the desired memory size in Memory (MiB), then click Next.
memory
In the Network window, select vmbr1 for Bridge, VirtIO (paravirtualized) for Model, uncheck Firewall, then click Next.
Network
In the Confirm window, click Finish.
finish
3. Graphical Installation Configuration ​
Click on the template you've set up on the left, click Start in the upper right corner to start the virtual machine, then click Console to enter the VNC interface and wait for the operating system to boot.
console
In the VNC, click Next, then Install now, then I don't have a product key, check Accept license, click Next, and then select Custom installation.
win0win1win2win3win4
If the image comes with VirtIO drivers, you should be able to see the available system storage disk and its size. Select it and click Next.
win5win6
Wait for the system to install. It may restart automatically several times and could take more than 10 minutes.
win7
After installation is complete, you'll be asked to set a password during first login.
win8
Once setup is complete, there's a pop-up box on the left side of the NOVNC page. Click the first button, then follow the login prompt by pressing Ctrl+Alt+last button to enter the login page.
4. Network Initialization ​
Since the PVE is set up with a static network through this project, you need to manually modify the bound IP address after logging in, rather than using DHCP.
Right-click in the bottom right corner of the desktop and select Open Network and Internet settings. In the settings page that appears, click Change adapter options. win9
In the Network Connections, select Ethernet and click Change settings of this connection. win10
In the popup window, select Internet Protocol Version 4 (TCP/IPv4) and click Properties. win11
In the new dialog box, select Use the following IP address and enter: IP address(I): 172.16.1.xxx (replace xxx with your desired IP, I used 100 for convenience as my vmid is 100) Subnet mask(U): 255.255.255.0 Default gateway(D): 172.16.1.1
Then select Use the following DNS server addresses and enter:
8.8.8.8
 144.144.144.144
Click OK in the bottom right corner, and make sure Validate settings upon exit is NOT checked.
win12
Click OK and Yes for any other dialog boxes, and your virtual machine will now have network connectivity.
5. Unmounting the CD Drive ​
Manually click on the corresponding CD in the Hardware on the web side of ProxmoxVE and select Remove, then restart the VM and you can use it directly.
wk
Using ISO Images without VirtIO for VM Installation ​
1. Download Images ​
For Windows images without VirtIO, you can use:
https://down.idc.wiki/ISOS/Windows/
For VirtIO ISO images, you can use:
https://down.idc.wiki/ISOS/Toolkit/
or
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/
Alternatively, you can download just the MSI package, package it into an ISO format locally, and then upload it to ProxmoxVE.
This way, the package is smaller. The official package contains support for all Windows images and is about 500MB, while a self-packaged one is around 5MB.
2. VirtIO Import ​
Note that in ProxmoxVE version 8.x and later, you can select VirtIO boot loading by default in the OS section, as shown in the image:
virtio
In lower versions of ProxmoxVE, such as 7.x and 6.x, you cannot select VirtIO boot loading by default in the OS section:
lower
You need to manually add CD/DVD Drive by clicking Add in the Hardware section and selecting the downloaded VirtIO ISO file:
lower
Then proceed as usual until you reach:
nodisk
At this point, you can't find the hard disk. You need to select Load Driver:
nodisk
Then select the VirtIO as your driver disk, click open, and import the corresponding system driver from the amd64 directory:
nodisk
I'm using a Windows Server 2019 image, so I imported the 2k19 driver. After importing, select the imported driver and click Next:
nodisk
nodisk
Now you should be able to see the hard disk. Select it and continue with the installation steps as in the previous tutorial until the system installation is complete and you reach the desktop.
3. Installing Drivers via virtio-win-guest-tools ​
Once successfully installed and at the desktop, you still need to manually install the drivers.
Open the VirtIO driver's CD drive directory. At the bottom, there's a virtio-win-guest-tools program that will install the required VirtIO drivers, including the VirtIO network card driver:
wk
wk
wk
After clicking install, the network card driver will be installed. For subsequent network settings, refer to the network initialization tutorial mentioned earlier.
4. Installing Network Card Driver (Alternative) ​
After successful installation and reaching the desktop, you may still need to manually install the network card driver to connect to the network:
  1. Open Control Panel → Device Manager
  2. Find the Ethernet Controller, right-click and select Update Driver
  3. Select Browse my computer for driver software (R)
  4. Browse to the VirtIO driver's CD drive directory
  5. Open the NetKVM folder
  6. Select the driver folder corresponding to your current system version (like the above operation, I would choose the 2k19 folder with amd64 drivers)
  7. Confirm the installation, and after completion, the VirtIO network card driver will be successfully loaded
wk
wk
wk
For subsequent network settings, refer to the network initialization tutorial mentioned earlier.
5. Unmounting the CD Drive ​
In the ProxmoxVE web interface, manually click on the corresponding CD in the Hardware section, select Remove, and then restart the virtual machine. This way, you can use it directly:
wk
',97),K=[L];function H($,Y,j,X,J,Q){return o(),i("div",null,K)}const oe=t(G,[["render",H]]);export{te as __pageData,oe as default};
diff --git a/assets/en_incomplete_bashvm.md.886829a2.js b/assets/en_incomplete_bashvm.md.1880d2a3.js
similarity index 95%
rename from assets/en_incomplete_bashvm.md.886829a2.js
rename to assets/en_incomplete_bashvm.md.1880d2a3.js
index 4421a749d7..a0a3f2d79e 100644
--- a/assets/en_incomplete_bashvm.md.886829a2.js
+++ b/assets/en_incomplete_bashvm.md.1880d2a3.js
@@ -1 +1 @@
-import{_ as a,v as e,b as t,R as o}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/bashvm.md","filePath":"en/incomplete/bashvm.md","lastUpdated":1747726389000}'),s={name:"en/incomplete/bashvm.md"},r=o('
Repo ​
https://github.com/babywhale321/bashvm
https://bashvm.com/
Description ​
If you want to go deeper into how to open a VM and how to forward ports, then this program will start completely from the bottom and teach you step by step how to open a VM!
Disadvantages ​
Very tedious and time consuming, not as fast as other programs to set up a network and open a VM
',7),n=[r];function i(h,p,d,c,l,m){return e(),t("div",null,n)}const u=a(s,[["render",i]]);export{f as __pageData,u as default};
+import{_ as a,v as e,b as t,R as o}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/bashvm.md","filePath":"en/incomplete/bashvm.md","lastUpdated":1747730955000}'),s={name:"en/incomplete/bashvm.md"},r=o('
Repo ​
https://github.com/babywhale321/bashvm
https://bashvm.com/
Description ​
If you want to go deeper into how to open a VM and how to forward ports, then this program will start completely from the bottom and teach you step by step how to open a VM!
Disadvantages ​
Very tedious and time consuming, not as fast as other programs to set up a network and open a VM
',7),n=[r];function i(h,p,d,c,l,m){return e(),t("div",null,n)}const u=a(s,[["render",i]]);export{f as __pageData,u as default};
diff --git a/assets/en_incomplete_bashvm.md.886829a2.lean.js b/assets/en_incomplete_bashvm.md.1880d2a3.lean.js
similarity index 95%
rename from assets/en_incomplete_bashvm.md.886829a2.lean.js
rename to assets/en_incomplete_bashvm.md.1880d2a3.lean.js
index 4421a749d7..a0a3f2d79e 100644
--- a/assets/en_incomplete_bashvm.md.886829a2.lean.js
+++ b/assets/en_incomplete_bashvm.md.1880d2a3.lean.js
@@ -1 +1 @@
-import{_ as a,v as e,b as t,R as o}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/bashvm.md","filePath":"en/incomplete/bashvm.md","lastUpdated":1747726389000}'),s={name:"en/incomplete/bashvm.md"},r=o('
Repo ​
https://github.com/babywhale321/bashvm
https://bashvm.com/
Description ​
If you want to go deeper into how to open a VM and how to forward ports, then this program will start completely from the bottom and teach you step by step how to open a VM!
Disadvantages ​
Very tedious and time consuming, not as fast as other programs to set up a network and open a VM
',7),n=[r];function i(h,p,d,c,l,m){return e(),t("div",null,n)}const u=a(s,[["render",i]]);export{f as __pageData,u as default};
+import{_ as a,v as e,b as t,R as o}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/bashvm.md","filePath":"en/incomplete/bashvm.md","lastUpdated":1747730955000}'),s={name:"en/incomplete/bashvm.md"},r=o('
Repo ​
https://github.com/babywhale321/bashvm
https://bashvm.com/
Description ​
If you want to go deeper into how to open a VM and how to forward ports, then this program will start completely from the bottom and teach you step by step how to open a VM!
Disadvantages ​
Very tedious and time consuming, not as fast as other programs to set up a network and open a VM
',7),n=[r];function i(h,p,d,c,l,m){return e(),t("div",null,n)}const u=a(s,[["render",i]]);export{f as __pageData,u as default};
diff --git a/assets/en_incomplete_cockpit.md.39705808.js b/assets/en_incomplete_cockpit.md.d72e9268.js
similarity index 98%
rename from assets/en_incomplete_cockpit.md.39705808.js
rename to assets/en_incomplete_cockpit.md.d72e9268.js
index 129457c12b..80e5ade1a6 100644
--- a/assets/en_incomplete_cockpit.md.39705808.js
+++ b/assets/en_incomplete_cockpit.md.d72e9268.js
@@ -1 +1 @@
-import{_ as s,v as a,b as e,R as l}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/cockpit.md","filePath":"en/incomplete/cockpit.md","lastUpdated":1747726389000}'),t={name:"en/incomplete/cockpit.md"},n=l('
Repo ​
hits
https://github.com/oneclickvirt/cockpit
Installation ​
Supported Systems: Debian，Ubuntu，Almalinux，Rockylinux，Fedora，Centos，Arch
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh
Install only with Podman containers
shell
bash install.sh --ct
Install only with virtual machines
shell
bash install.sh --vm
Panel Mount Only
shell
bash install.sh
Both container and VM dependencies are installed
shell
bash install.sh --all
Disadvantages ​
The network is self-configuring, the mirrors are self-importing, the ports are self-mapped, and there is just one more GUI interface than the command line.
Thanks ​
https://cockpit-project.org/running.html
',18),o=[n];function p(c,r,i,h,d,C){return a(),e("div",null,o)}const u=s(t,[["render",p]]);export{y as __pageData,u as default};
+import{_ as s,v as a,b as e,R as l}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/cockpit.md","filePath":"en/incomplete/cockpit.md","lastUpdated":1747730955000}'),t={name:"en/incomplete/cockpit.md"},n=l('
Repo ​
hits
https://github.com/oneclickvirt/cockpit
Installation ​
Supported Systems: Debian，Ubuntu，Almalinux，Rockylinux，Fedora，Centos，Arch
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh
Install only with Podman containers
shell
bash install.sh --ct
Install only with virtual machines
shell
bash install.sh --vm
Panel Mount Only
shell
bash install.sh
Both container and VM dependencies are installed
shell
bash install.sh --all
Disadvantages ​
The network is self-configuring, the mirrors are self-importing, the ports are self-mapped, and there is just one more GUI interface than the command line.
Thanks ​
https://cockpit-project.org/running.html
',18),o=[n];function p(c,r,i,h,d,C){return a(),e("div",null,o)}const u=s(t,[["render",p]]);export{y as __pageData,u as default};
diff --git a/assets/en_incomplete_cockpit.md.39705808.lean.js b/assets/en_incomplete_cockpit.md.d72e9268.lean.js
similarity index 98%
rename from assets/en_incomplete_cockpit.md.39705808.lean.js
rename to assets/en_incomplete_cockpit.md.d72e9268.lean.js
index 129457c12b..80e5ade1a6 100644
--- a/assets/en_incomplete_cockpit.md.39705808.lean.js
+++ b/assets/en_incomplete_cockpit.md.d72e9268.lean.js
@@ -1 +1 @@
-import{_ as s,v as a,b as e,R as l}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/cockpit.md","filePath":"en/incomplete/cockpit.md","lastUpdated":1747726389000}'),t={name:"en/incomplete/cockpit.md"},n=l('
Repo ​
hits
https://github.com/oneclickvirt/cockpit
Installation ​
Supported Systems: Debian，Ubuntu，Almalinux，Rockylinux，Fedora，Centos，Arch
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh
Install only with Podman containers
shell
bash install.sh --ct
Install only with virtual machines
shell
bash install.sh --vm
Panel Mount Only
shell
bash install.sh
Both container and VM dependencies are installed
shell
bash install.sh --all
Disadvantages ​
The network is self-configuring, the mirrors are self-importing, the ports are self-mapped, and there is just one more GUI interface than the command line.
Thanks ​
https://cockpit-project.org/running.html
',18),o=[n];function p(c,r,i,h,d,C){return a(),e("div",null,o)}const u=s(t,[["render",p]]);export{y as __pageData,u as default};
+import{_ as s,v as a,b as e,R as l}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/cockpit.md","filePath":"en/incomplete/cockpit.md","lastUpdated":1747730955000}'),t={name:"en/incomplete/cockpit.md"},n=l('
Repo ​
hits
https://github.com/oneclickvirt/cockpit
Installation ​
Supported Systems: Debian，Ubuntu，Almalinux，Rockylinux，Fedora，Centos，Arch
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh
Install only with Podman containers
shell
bash install.sh --ct
Install only with virtual machines
shell
bash install.sh --vm
Panel Mount Only
shell
bash install.sh
Both container and VM dependencies are installed
shell
bash install.sh --all
Disadvantages ​
The network is self-configuring, the mirrors are self-importing, the ports are self-mapped, and there is just one more GUI interface than the command line.
Thanks ​
https://cockpit-project.org/running.html
',18),o=[n];function p(c,r,i,h,d,C){return a(),e("div",null,o)}const u=s(t,[["render",p]]);export{y as __pageData,u as default};
diff --git a/assets/en_incomplete_convoy.md.99197d89.js b/assets/en_incomplete_convoy.md.cc6e43af.js
similarity index 98%
rename from assets/en_incomplete_convoy.md.99197d89.js
rename to assets/en_incomplete_convoy.md.cc6e43af.js
index 9ae943eec4..88e4799699 100644
--- a/assets/en_incomplete_convoy.md.99197d89.js
+++ b/assets/en_incomplete_convoy.md.cc6e43af.js
@@ -1 +1 @@
-import{_ as a,v as e,b as s,R as o}from"./chunks/framework.70afa331.js";const v=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/convoy.md","filePath":"en/incomplete/convoy.md","lastUpdated":1747726389000}'),t={name:"en/incomplete/convoy.md"},n=o('
Repo ​
https://github.com/oneclickvirt/convoypanel-scripts
hits
convoypanel-scripts ​
One-click installation of convoy panel ​
Prerequisites for installation:
  • PVE is installed, but not the same node(not the same machine)
  • System is debian 11
  • CPU at least 2 cores, hard disk at least 20G, memory at least 4G (memory covers swap)
I don't guarantee that this script is error-free, it's just for my own amusement.
shell
curl -L https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
Thanks ​
Base on https://github.com/oneclickvirt/pve
Base on https://docs.convoypanel.com/guide/deployment/#installation
Base on https://github.com/ConvoyPanel/panel
',13),l=[n];function p(r,c,i,h,y,m){return e(),s("div",null,l)}const C=a(t,[["render",p]]);export{v as __pageData,C as default};
+import{_ as a,v as e,b as s,R as o}from"./chunks/framework.70afa331.js";const v=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/convoy.md","filePath":"en/incomplete/convoy.md","lastUpdated":1747730955000}'),t={name:"en/incomplete/convoy.md"},n=o('
Repo ​
https://github.com/oneclickvirt/convoypanel-scripts
hits
convoypanel-scripts ​
One-click installation of convoy panel ​
Prerequisites for installation:
  • PVE is installed, but not the same node(not the same machine)
  • System is debian 11
  • CPU at least 2 cores, hard disk at least 20G, memory at least 4G (memory covers swap)
I don't guarantee that this script is error-free, it's just for my own amusement.
shell
curl -L https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
Thanks ​
Base on https://github.com/oneclickvirt/pve
Base on https://docs.convoypanel.com/guide/deployment/#installation
Base on https://github.com/ConvoyPanel/panel
',13),l=[n];function p(r,c,i,h,y,m){return e(),s("div",null,l)}const C=a(t,[["render",p]]);export{v as __pageData,C as default};
diff --git a/assets/en_incomplete_convoy.md.99197d89.lean.js b/assets/en_incomplete_convoy.md.cc6e43af.lean.js
similarity index 98%
rename from assets/en_incomplete_convoy.md.99197d89.lean.js
rename to assets/en_incomplete_convoy.md.cc6e43af.lean.js
index 9ae943eec4..88e4799699 100644
--- a/assets/en_incomplete_convoy.md.99197d89.lean.js
+++ b/assets/en_incomplete_convoy.md.cc6e43af.lean.js
@@ -1 +1 @@
-import{_ as a,v as e,b as s,R as o}from"./chunks/framework.70afa331.js";const v=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/convoy.md","filePath":"en/incomplete/convoy.md","lastUpdated":1747726389000}'),t={name:"en/incomplete/convoy.md"},n=o('
Repo ​
https://github.com/oneclickvirt/convoypanel-scripts
hits
convoypanel-scripts ​
One-click installation of convoy panel ​
Prerequisites for installation:
  • PVE is installed, but not the same node(not the same machine)
  • System is debian 11
  • CPU at least 2 cores, hard disk at least 20G, memory at least 4G (memory covers swap)
I don't guarantee that this script is error-free, it's just for my own amusement.
shell
curl -L https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
Thanks ​
Base on https://github.com/oneclickvirt/pve
Base on https://docs.convoypanel.com/guide/deployment/#installation
Base on https://github.com/ConvoyPanel/panel
',13),l=[n];function p(r,c,i,h,y,m){return e(),s("div",null,l)}const C=a(t,[["render",p]]);export{v as __pageData,C as default};
+import{_ as a,v as e,b as s,R as o}from"./chunks/framework.70afa331.js";const v=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/convoy.md","filePath":"en/incomplete/convoy.md","lastUpdated":1747730955000}'),t={name:"en/incomplete/convoy.md"},n=o('
Repo ​
https://github.com/oneclickvirt/convoypanel-scripts
hits
convoypanel-scripts ​
One-click installation of convoy panel ​
Prerequisites for installation:
  • PVE is installed, but not the same node(not the same machine)
  • System is debian 11
  • CPU at least 2 cores, hard disk at least 20G, memory at least 4G (memory covers swap)
I don't guarantee that this script is error-free, it's just for my own amusement.
shell
curl -L https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
Thanks ​
Base on https://github.com/oneclickvirt/pve
Base on https://docs.convoypanel.com/guide/deployment/#installation
Base on https://github.com/ConvoyPanel/panel
',13),l=[n];function p(r,c,i,h,y,m){return e(),s("div",null,l)}const C=a(t,[["render",p]]);export{v as __pageData,C as default};
diff --git a/assets/en_incomplete_index.md.634cf0f9.js b/assets/en_incomplete_index.md.c7971242.js
similarity index 95%
rename from assets/en_incomplete_index.md.634cf0f9.js
rename to assets/en_incomplete_index.md.c7971242.js
index 1ea3a2188d..4a5baaa1e3 100644
--- a/assets/en_incomplete_index.md.634cf0f9.js
+++ b/assets/en_incomplete_index.md.c7971242.js
@@ -1 +1 @@
-import{_ as e,v as t,b as i}from"./chunks/framework.70afa331.js";const m=JSON.parse(`{"title":"Other Virtualization Projects","titleTemplate":"Other Incomplete Virtualization Projects","description":"","frontmatter":{"layout":"home","title":"Other Virtualization Projects","titleTemplate":"Other Incomplete Virtualization Projects","hero":{"name":"Other Virtualization Projects","text":"Some incomplete virtualization projects","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"View Projects →","link":"/en/incomplete/webvirtcloud"}]},"features":[{"title":"Notes","details":"Each item in this block has a corresponding drawback, and each item is not as easy to use as the previous ones, and has a certain learning cost."},{"title":"Degree of difficulty","details":"Based on the difficulty of using the program itself, sorted from easiest to hardest, the further back you go the less guidance you'll get with this guide."},{"title":"Project disadvantages","details":"Each project has some drawbacks that result in it not being considered a complete one-click project, and there are some operations that require manual execution of commands that cannot be one-clicked."}]},"headers":[],"relativePath":"en/incomplete/index.md","filePath":"en/incomplete/index.md","lastUpdated":1747726389000}`),a={name:"en/incomplete/index.md"};function o(n,s,r,c,l,d){return t(),i("div")}const p=e(a,[["render",o]]);export{m as __pageData,p as default};
+import{_ as e,v as t,b as i}from"./chunks/framework.70afa331.js";const m=JSON.parse(`{"title":"Other Virtualization Projects","titleTemplate":"Other Incomplete Virtualization Projects","description":"","frontmatter":{"layout":"home","title":"Other Virtualization Projects","titleTemplate":"Other Incomplete Virtualization Projects","hero":{"name":"Other Virtualization Projects","text":"Some incomplete virtualization projects","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"View Projects →","link":"/en/incomplete/webvirtcloud"}]},"features":[{"title":"Notes","details":"Each item in this block has a corresponding drawback, and each item is not as easy to use as the previous ones, and has a certain learning cost."},{"title":"Degree of difficulty","details":"Based on the difficulty of using the program itself, sorted from easiest to hardest, the further back you go the less guidance you'll get with this guide."},{"title":"Project disadvantages","details":"Each project has some drawbacks that result in it not being considered a complete one-click project, and there are some operations that require manual execution of commands that cannot be one-clicked."}]},"headers":[],"relativePath":"en/incomplete/index.md","filePath":"en/incomplete/index.md","lastUpdated":1747730955000}`),a={name:"en/incomplete/index.md"};function o(n,s,r,c,l,d){return t(),i("div")}const p=e(a,[["render",o]]);export{m as __pageData,p as default};
diff --git a/assets/en_incomplete_index.md.634cf0f9.lean.js b/assets/en_incomplete_index.md.c7971242.lean.js
similarity index 95%
rename from assets/en_incomplete_index.md.634cf0f9.lean.js
rename to assets/en_incomplete_index.md.c7971242.lean.js
index 1ea3a2188d..4a5baaa1e3 100644
--- a/assets/en_incomplete_index.md.634cf0f9.lean.js
+++ b/assets/en_incomplete_index.md.c7971242.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as i}from"./chunks/framework.70afa331.js";const m=JSON.parse(`{"title":"Other Virtualization Projects","titleTemplate":"Other Incomplete Virtualization Projects","description":"","frontmatter":{"layout":"home","title":"Other Virtualization Projects","titleTemplate":"Other Incomplete Virtualization Projects","hero":{"name":"Other Virtualization Projects","text":"Some incomplete virtualization projects","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"View Projects →","link":"/en/incomplete/webvirtcloud"}]},"features":[{"title":"Notes","details":"Each item in this block has a corresponding drawback, and each item is not as easy to use as the previous ones, and has a certain learning cost."},{"title":"Degree of difficulty","details":"Based on the difficulty of using the program itself, sorted from easiest to hardest, the further back you go the less guidance you'll get with this guide."},{"title":"Project disadvantages","details":"Each project has some drawbacks that result in it not being considered a complete one-click project, and there are some operations that require manual execution of commands that cannot be one-clicked."}]},"headers":[],"relativePath":"en/incomplete/index.md","filePath":"en/incomplete/index.md","lastUpdated":1747726389000}`),a={name:"en/incomplete/index.md"};function o(n,s,r,c,l,d){return t(),i("div")}const p=e(a,[["render",o]]);export{m as __pageData,p as default};
+import{_ as e,v as t,b as i}from"./chunks/framework.70afa331.js";const m=JSON.parse(`{"title":"Other Virtualization Projects","titleTemplate":"Other Incomplete Virtualization Projects","description":"","frontmatter":{"layout":"home","title":"Other Virtualization Projects","titleTemplate":"Other Incomplete Virtualization Projects","hero":{"name":"Other Virtualization Projects","text":"Some incomplete virtualization projects","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"View Projects →","link":"/en/incomplete/webvirtcloud"}]},"features":[{"title":"Notes","details":"Each item in this block has a corresponding drawback, and each item is not as easy to use as the previous ones, and has a certain learning cost."},{"title":"Degree of difficulty","details":"Based on the difficulty of using the program itself, sorted from easiest to hardest, the further back you go the less guidance you'll get with this guide."},{"title":"Project disadvantages","details":"Each project has some drawbacks that result in it not being considered a complete one-click project, and there are some operations that require manual execution of commands that cannot be one-clicked."}]},"headers":[],"relativePath":"en/incomplete/index.md","filePath":"en/incomplete/index.md","lastUpdated":1747730955000}`),a={name:"en/incomplete/index.md"};function o(n,s,r,c,l,d){return t(),i("div")}const p=e(a,[["render",o]]);export{m as __pageData,p as default};
diff --git a/assets/en_incomplete_pterodactyl.md.5c85a6df.js b/assets/en_incomplete_pterodactyl.md.6649cbaf.js
similarity index 99%
rename from assets/en_incomplete_pterodactyl.md.5c85a6df.js
rename to assets/en_incomplete_pterodactyl.md.6649cbaf.js
index 1c39e28dd8..6fd51ef50c 100644
--- a/assets/en_incomplete_pterodactyl.md.5c85a6df.js
+++ b/assets/en_incomplete_pterodactyl.md.6649cbaf.js
@@ -1 +1 @@
-import{_ as s,v as a,b as t,R as e}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/pterodactyl.md","filePath":"en/incomplete/pterodactyl.md","lastUpdated":1747726389000}'),n={name:"en/incomplete/pterodactyl.md"},o=e('
Repo ​
https://github.com/oneclickvirt/pterodactyl
hits
pterodactyl-scripts ​
After further research, it was found that creating servers and binding users is too cumbersome compared to using native Docker directly, so further development is currently suspended.
Description ​
Currently supported systems:
OS TypeVersion RangeNotes
Ubuntu20.04 (recommended), 22.04, 24.04Supported
Debian11 (Bullseye), 12 (Bookworm)Supported
Panel ​
On the panel side, run:
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh
Wings ​
On the wings side, run:
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh
Import ​
On the panel side, run:
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh
This will generate a command to be executed on the wings side.
After executing the generated command, wait for more than 20 seconds to avoid issues caused by unfinished initialization processes. Then on the wings side, run:
shell
bash install_wings.sh
Then go to http://<your_ip>/admin/nodes and you should see your node has been automatically added and managed, with a green heartbeat.
Thanks ​
https://pterodactyl.io/
',23),l=[o];function p(r,c,i,d,h,y){return a(),t("div",null,l)}const u=s(n,[["render",p]]);export{m as __pageData,u as default};
+import{_ as s,v as a,b as t,R as e}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/pterodactyl.md","filePath":"en/incomplete/pterodactyl.md","lastUpdated":1747730955000}'),n={name:"en/incomplete/pterodactyl.md"},o=e('
Repo ​
https://github.com/oneclickvirt/pterodactyl
hits
pterodactyl-scripts ​
After further research, it was found that creating servers and binding users is too cumbersome compared to using native Docker directly, so further development is currently suspended.
Description ​
Currently supported systems:
OS TypeVersion RangeNotes
Ubuntu20.04 (recommended), 22.04, 24.04Supported
Debian11 (Bullseye), 12 (Bookworm)Supported
Panel ​
On the panel side, run:
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh
Wings ​
On the wings side, run:
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh
Import ​
On the panel side, run:
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh
This will generate a command to be executed on the wings side.
After executing the generated command, wait for more than 20 seconds to avoid issues caused by unfinished initialization processes. Then on the wings side, run:
shell
bash install_wings.sh
Then go to http://<your_ip>/admin/nodes and you should see your node has been automatically added and managed, with a green heartbeat.
Thanks ​
https://pterodactyl.io/
',23),l=[o];function p(r,c,i,d,h,y){return a(),t("div",null,l)}const u=s(n,[["render",p]]);export{m as __pageData,u as default};
diff --git a/assets/en_incomplete_pterodactyl.md.5c85a6df.lean.js b/assets/en_incomplete_pterodactyl.md.6649cbaf.lean.js
similarity index 99%
rename from assets/en_incomplete_pterodactyl.md.5c85a6df.lean.js
rename to assets/en_incomplete_pterodactyl.md.6649cbaf.lean.js
index 1c39e28dd8..6fd51ef50c 100644
--- a/assets/en_incomplete_pterodactyl.md.5c85a6df.lean.js
+++ b/assets/en_incomplete_pterodactyl.md.6649cbaf.lean.js
@@ -1 +1 @@
-import{_ as s,v as a,b as t,R as e}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/pterodactyl.md","filePath":"en/incomplete/pterodactyl.md","lastUpdated":1747726389000}'),n={name:"en/incomplete/pterodactyl.md"},o=e('
Repo ​
https://github.com/oneclickvirt/pterodactyl
hits
pterodactyl-scripts ​
After further research, it was found that creating servers and binding users is too cumbersome compared to using native Docker directly, so further development is currently suspended.
Description ​
Currently supported systems:
OS TypeVersion RangeNotes
Ubuntu20.04 (recommended), 22.04, 24.04Supported
Debian11 (Bullseye), 12 (Bookworm)Supported
Panel ​
On the panel side, run:
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh
Wings ​
On the wings side, run:
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh
Import ​
On the panel side, run:
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh
This will generate a command to be executed on the wings side.
After executing the generated command, wait for more than 20 seconds to avoid issues caused by unfinished initialization processes. Then on the wings side, run:
shell
bash install_wings.sh
Then go to http://<your_ip>/admin/nodes and you should see your node has been automatically added and managed, with a green heartbeat.
Thanks ​
https://pterodactyl.io/
',23),l=[o];function p(r,c,i,d,h,y){return a(),t("div",null,l)}const u=s(n,[["render",p]]);export{m as __pageData,u as default};
+import{_ as s,v as a,b as t,R as e}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/pterodactyl.md","filePath":"en/incomplete/pterodactyl.md","lastUpdated":1747730955000}'),n={name:"en/incomplete/pterodactyl.md"},o=e('
Repo ​
https://github.com/oneclickvirt/pterodactyl
hits
pterodactyl-scripts ​
After further research, it was found that creating servers and binding users is too cumbersome compared to using native Docker directly, so further development is currently suspended.
Description ​
Currently supported systems:
OS TypeVersion RangeNotes
Ubuntu20.04 (recommended), 22.04, 24.04Supported
Debian11 (Bullseye), 12 (Bookworm)Supported
Panel ​
On the panel side, run:
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh
Wings ​
On the wings side, run:
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh
Import ​
On the panel side, run:
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh
This will generate a command to be executed on the wings side.
After executing the generated command, wait for more than 20 seconds to avoid issues caused by unfinished initialization processes. Then on the wings side, run:
shell
bash install_wings.sh
Then go to http://<your_ip>/admin/nodes and you should see your node has been automatically added and managed, with a green heartbeat.
Thanks ​
https://pterodactyl.io/
',23),l=[o];function p(r,c,i,d,h,y){return a(),t("div",null,l)}const u=s(n,[["render",p]]);export{m as __pageData,u as default};
diff --git a/assets/en_incomplete_virtfusion.md.eceb8f07.js b/assets/en_incomplete_virtfusion.md.c9e0fa6d.js
similarity index 99%
rename from assets/en_incomplete_virtfusion.md.eceb8f07.js
rename to assets/en_incomplete_virtfusion.md.c9e0fa6d.js
index ba77b57f55..40c2b9cc2b 100644
--- a/assets/en_incomplete_virtfusion.md.eceb8f07.js
+++ b/assets/en_incomplete_virtfusion.md.c9e0fa6d.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/virtfusion.md","filePath":"en/incomplete/virtfusion.md","lastUpdated":1747726389000}'),o={name:"en/incomplete/virtfusion.md"},p=n(`
Official Documents ​
https://docs.virtfusion.com/next/installation/control-server/#activating-a-license
One-click Installation ​
debian11
shell
apt install curl -y
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/virtfusion.md","filePath":"en/incomplete/virtfusion.md","lastUpdated":1747730955000}'),o={name:"en/incomplete/virtfusion.md"},p=n(`
Official Documents ​
https://docs.virtfusion.com/next/installation/control-server/#activating-a-license
One-click Installation ​
debian11
shell
apt install curl -y
 curl https://install.virtfusion.net/install-control-debian-11.sh | sh -s -- --verbose
debian12
shell
apt install curl -y
 curl https://install.virtfusion.net/install-control-debian-12.sh | sh -s -- --verbose
RHEL8
shell
dnf install curl -y
 curl https://install.virtfusion.net/install-control-rhel-8.sh | sh -s -- --verbose
RHEL9
shell
dnf install curl -y
diff --git a/assets/en_incomplete_virtfusion.md.eceb8f07.lean.js b/assets/en_incomplete_virtfusion.md.c9e0fa6d.lean.js
similarity index 99%
rename from assets/en_incomplete_virtfusion.md.eceb8f07.lean.js
rename to assets/en_incomplete_virtfusion.md.c9e0fa6d.lean.js
index ba77b57f55..40c2b9cc2b 100644
--- a/assets/en_incomplete_virtfusion.md.eceb8f07.lean.js
+++ b/assets/en_incomplete_virtfusion.md.c9e0fa6d.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/virtfusion.md","filePath":"en/incomplete/virtfusion.md","lastUpdated":1747726389000}'),o={name:"en/incomplete/virtfusion.md"},p=n(`
Official Documents ​
https://docs.virtfusion.com/next/installation/control-server/#activating-a-license
One-click Installation ​
debian11
shell
apt install curl -y
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/virtfusion.md","filePath":"en/incomplete/virtfusion.md","lastUpdated":1747730955000}'),o={name:"en/incomplete/virtfusion.md"},p=n(`
Official Documents ​
https://docs.virtfusion.com/next/installation/control-server/#activating-a-license
One-click Installation ​
debian11
shell
apt install curl -y
 curl https://install.virtfusion.net/install-control-debian-11.sh | sh -s -- --verbose
debian12
shell
apt install curl -y
 curl https://install.virtfusion.net/install-control-debian-12.sh | sh -s -- --verbose
RHEL8
shell
dnf install curl -y
 curl https://install.virtfusion.net/install-control-rhel-8.sh | sh -s -- --verbose
RHEL9
shell
dnf install curl -y
diff --git a/assets/en_incomplete_virtualizor-docker.md.4e86b60d.js b/assets/en_incomplete_virtualizor-docker.md.7552a324.js
similarity index 95%
rename from assets/en_incomplete_virtualizor-docker.md.4e86b60d.js
rename to assets/en_incomplete_virtualizor-docker.md.7552a324.js
index 003420ccf3..6c9a2323ac 100644
--- a/assets/en_incomplete_virtualizor-docker.md.4e86b60d.js
+++ b/assets/en_incomplete_virtualizor-docker.md.7552a324.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a,R as i}from"./chunks/framework.70afa331.js";const v=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/virtualizor-docker.md","filePath":"en/incomplete/virtualizor-docker.md","lastUpdated":1747726389000}'),o={name:"en/incomplete/virtualizor-docker.md"},r=i('
Repo ​
https://github.com/ivstiv/virtualizor-docker
Description ​
The virtualizor opened in the docker
The certificate used is a trial certificate, valid for one day, and only the OpenVZ virtualization method is installed by default
Disadvantages ​
There is no community, so you have to figure it out on your own.
Ports for admin panel Don't look at the script's prompt messages, go with the repository instructions.
',8),s=[r];function n(d,c,p,l,h,u){return t(),a("div",null,s)}const f=e(o,[["render",n]]);export{v as __pageData,f as default};
+import{_ as e,v as t,b as a,R as i}from"./chunks/framework.70afa331.js";const v=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/virtualizor-docker.md","filePath":"en/incomplete/virtualizor-docker.md","lastUpdated":1747730955000}'),o={name:"en/incomplete/virtualizor-docker.md"},r=i('
Repo ​
https://github.com/ivstiv/virtualizor-docker
Description ​
The virtualizor opened in the docker
The certificate used is a trial certificate, valid for one day, and only the OpenVZ virtualization method is installed by default
Disadvantages ​
There is no community, so you have to figure it out on your own.
Ports for admin panel Don't look at the script's prompt messages, go with the repository instructions.
',8),s=[r];function n(d,c,p,l,h,u){return t(),a("div",null,s)}const f=e(o,[["render",n]]);export{v as __pageData,f as default};
diff --git a/assets/en_incomplete_virtualizor-docker.md.4e86b60d.lean.js b/assets/en_incomplete_virtualizor-docker.md.7552a324.lean.js
similarity index 95%
rename from assets/en_incomplete_virtualizor-docker.md.4e86b60d.lean.js
rename to assets/en_incomplete_virtualizor-docker.md.7552a324.lean.js
index 003420ccf3..6c9a2323ac 100644
--- a/assets/en_incomplete_virtualizor-docker.md.4e86b60d.lean.js
+++ b/assets/en_incomplete_virtualizor-docker.md.7552a324.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a,R as i}from"./chunks/framework.70afa331.js";const v=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/virtualizor-docker.md","filePath":"en/incomplete/virtualizor-docker.md","lastUpdated":1747726389000}'),o={name:"en/incomplete/virtualizor-docker.md"},r=i('
Repo ​
https://github.com/ivstiv/virtualizor-docker
Description ​
The virtualizor opened in the docker
The certificate used is a trial certificate, valid for one day, and only the OpenVZ virtualization method is installed by default
Disadvantages ​
There is no community, so you have to figure it out on your own.
Ports for admin panel Don't look at the script's prompt messages, go with the repository instructions.
',8),s=[r];function n(d,c,p,l,h,u){return t(),a("div",null,s)}const f=e(o,[["render",n]]);export{v as __pageData,f as default};
+import{_ as e,v as t,b as a,R as i}from"./chunks/framework.70afa331.js";const v=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/virtualizor-docker.md","filePath":"en/incomplete/virtualizor-docker.md","lastUpdated":1747730955000}'),o={name:"en/incomplete/virtualizor-docker.md"},r=i('
Repo ​
https://github.com/ivstiv/virtualizor-docker
Description ​
The virtualizor opened in the docker
The certificate used is a trial certificate, valid for one day, and only the OpenVZ virtualization method is installed by default
Disadvantages ​
There is no community, so you have to figure it out on your own.
Ports for admin panel Don't look at the script's prompt messages, go with the repository instructions.
',8),s=[r];function n(d,c,p,l,h,u){return t(),a("div",null,s)}const f=e(o,[["render",n]]);export{v as __pageData,f as default};
diff --git a/assets/en_incomplete_webvirtcloud.md.ad5d9cc5.js b/assets/en_incomplete_webvirtcloud.md.aa4dc433.js
similarity index 99%
rename from assets/en_incomplete_webvirtcloud.md.ad5d9cc5.js
rename to assets/en_incomplete_webvirtcloud.md.aa4dc433.js
index 5d923ca5f4..7a88fd4d39 100644
--- a/assets/en_incomplete_webvirtcloud.md.ad5d9cc5.js
+++ b/assets/en_incomplete_webvirtcloud.md.aa4dc433.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const o="/assets/wv1.5ac4a026.png",D=JSON.parse('{"title":"WebVirtCloud Installation Guide","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/webvirtcloud.md","filePath":"en/incomplete/webvirtcloud.md","lastUpdated":1747726389000}'),e={name:"en/incomplete/webvirtcloud.md"},t=l(`
WebVirtCloud Installation Guide ​
hits
Repository: https://github.com/oneclickvirt/webvirtcloud
Original project repository: https://github.com/webvirtcloud/webvirtcloud
1. Controller Installation ​
System Requirements ​
Minimum Requirements:
  • CPU: 1 core
  • Memory: 1 GB RAM
  • Storage: 10 GB free space
  • System: Debian11+, Ubuntu20.04+, Centos8+, AlmaLinux8+, RockyLinux8+
Default Login Information ​
  • Username: admin@webvirt.cloud
  • Password: admin
Panel Access ​
  • User Panel: https://192-168-0-114.nip.io
  • Admin Backend: https://192-168-0-114.nip.io/admin
Note: Replace 192.168.0.114 with your public IP to get the actual accessible address.
Installation Command ​
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud.sh -o install_webvirt_cloud.sh \\
+import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const o="/assets/wv1.5ac4a026.png",D=JSON.parse('{"title":"WebVirtCloud Installation Guide","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/webvirtcloud.md","filePath":"en/incomplete/webvirtcloud.md","lastUpdated":1747730955000}'),e={name:"en/incomplete/webvirtcloud.md"},t=l(`
WebVirtCloud Installation Guide ​
hits
Repository: https://github.com/oneclickvirt/webvirtcloud
Original project repository: https://github.com/webvirtcloud/webvirtcloud
1. Controller Installation ​
System Requirements ​
Minimum Requirements:
  • CPU: 1 core
  • Memory: 1 GB RAM
  • Storage: 10 GB free space
  • System: Debian11+, Ubuntu20.04+, Centos8+, AlmaLinux8+, RockyLinux8+
Default Login Information ​
  • Username: admin@webvirt.cloud
  • Password: admin
Panel Access ​
  • User Panel: https://192-168-0-114.nip.io
  • Admin Backend: https://192-168-0-114.nip.io/admin
Note: Replace 192.168.0.114 with your public IP to get the actual accessible address.
Installation Command ​
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud.sh -o install_webvirt_cloud.sh \\
 && chmod +x install_webvirt_cloud.sh \\
 && bash install_webvirt_cloud.sh
TIP
The execution process may be stuck in the clone repository has not been moving, at this time, press ctrl + c to exit the implementation, re-execution of the installation script on the line, the Department of Docker installation is stuck in the stage of the build project.
2. Compute Node Installation ​
Important: Hypervisor and Controller cannot be installed on the same virtual machine, otherwise network conflicts will occur.
System Requirements ​
Recommended Configuration:
  • CPU: 2 cores
  • Memory: 4 GB RAM
  • Storage: 40 GB free space
  • System: AlmaLinux8+, RockyLinux8+
Additional Notes:
  • Higher configurations are recommended for actual use; the test environment is only sufficient for running 4 minimal virtual machines.
  • Servers with KVM nested virtualization support are recommended. If VM-x/AMD-V/Hyper-V is not enabled, it will automatically switch to QEMU using TCG emulation to set up virtual machines, though performance will be reduced.
  • The installation skips environment checks and uses binary files directly, so no dependencies need to be installed.
Environment Check ​
Check if the server supports KVM nested virtualization:
bash
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/ecs/master/goecs.sh -o goecs.sh && chmod +x goecs.sh && ./goecs.sh install && goecs
Select hardware individual test
Compute Node Installation Steps ​
  1. Download the installation script:
    bash
    curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_hypervisor.sh -o install_hypervisor.sh \\
 && chmod +x install_hypervisor.sh
  2. Execute installation (replace with your Controller IP):
    bash
    bash install_hypervisor.sh x.x.x.x
    Replace x.x.x.x with the actual IP address of your Controller.
  3. Node Management in Panel
     After execution, there will be prompts for information needed in the Controller panel.
     In the panel, the Hostname to be entered is the current compute node's IPv4 address, and you need to enter the Token to identify the node.
NetworkManager Version Issue ​
During installation, you may encounter the following error:
Connection 'eth0' (bed050e9-ff49-4665-8112-24ddf2a1cd3c) successfully deleted.
diff --git a/assets/en_incomplete_webvirtcloud.md.ad5d9cc5.lean.js b/assets/en_incomplete_webvirtcloud.md.aa4dc433.lean.js
similarity index 99%
rename from assets/en_incomplete_webvirtcloud.md.ad5d9cc5.lean.js
rename to assets/en_incomplete_webvirtcloud.md.aa4dc433.lean.js
index 5d923ca5f4..7a88fd4d39 100644
--- a/assets/en_incomplete_webvirtcloud.md.ad5d9cc5.lean.js
+++ b/assets/en_incomplete_webvirtcloud.md.aa4dc433.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const o="/assets/wv1.5ac4a026.png",D=JSON.parse('{"title":"WebVirtCloud Installation Guide","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/webvirtcloud.md","filePath":"en/incomplete/webvirtcloud.md","lastUpdated":1747726389000}'),e={name:"en/incomplete/webvirtcloud.md"},t=l(`
WebVirtCloud Installation Guide ​
hits
Repository: https://github.com/oneclickvirt/webvirtcloud
Original project repository: https://github.com/webvirtcloud/webvirtcloud
1. Controller Installation ​
System Requirements ​
Minimum Requirements:
  • CPU: 1 core
  • Memory: 1 GB RAM
  • Storage: 10 GB free space
  • System: Debian11+, Ubuntu20.04+, Centos8+, AlmaLinux8+, RockyLinux8+
Default Login Information ​
  • Username: admin@webvirt.cloud
  • Password: admin
Panel Access ​
  • User Panel: https://192-168-0-114.nip.io
  • Admin Backend: https://192-168-0-114.nip.io/admin
Note: Replace 192.168.0.114 with your public IP to get the actual accessible address.
Installation Command ​
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud.sh -o install_webvirt_cloud.sh \\
+import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const o="/assets/wv1.5ac4a026.png",D=JSON.parse('{"title":"WebVirtCloud Installation Guide","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/webvirtcloud.md","filePath":"en/incomplete/webvirtcloud.md","lastUpdated":1747730955000}'),e={name:"en/incomplete/webvirtcloud.md"},t=l(`
WebVirtCloud Installation Guide ​
hits
Repository: https://github.com/oneclickvirt/webvirtcloud
Original project repository: https://github.com/webvirtcloud/webvirtcloud
1. Controller Installation ​
System Requirements ​
Minimum Requirements:
  • CPU: 1 core
  • Memory: 1 GB RAM
  • Storage: 10 GB free space
  • System: Debian11+, Ubuntu20.04+, Centos8+, AlmaLinux8+, RockyLinux8+
Default Login Information ​
  • Username: admin@webvirt.cloud
  • Password: admin
Panel Access ​
  • User Panel: https://192-168-0-114.nip.io
  • Admin Backend: https://192-168-0-114.nip.io/admin
Note: Replace 192.168.0.114 with your public IP to get the actual accessible address.
Installation Command ​
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud.sh -o install_webvirt_cloud.sh \\
 && chmod +x install_webvirt_cloud.sh \\
 && bash install_webvirt_cloud.sh
TIP
The execution process may be stuck in the clone repository has not been moving, at this time, press ctrl + c to exit the implementation, re-execution of the installation script on the line, the Department of Docker installation is stuck in the stage of the build project.
2. Compute Node Installation ​
Important: Hypervisor and Controller cannot be installed on the same virtual machine, otherwise network conflicts will occur.
System Requirements ​
Recommended Configuration:
  • CPU: 2 cores
  • Memory: 4 GB RAM
  • Storage: 40 GB free space
  • System: AlmaLinux8+, RockyLinux8+
Additional Notes:
  • Higher configurations are recommended for actual use; the test environment is only sufficient for running 4 minimal virtual machines.
  • Servers with KVM nested virtualization support are recommended. If VM-x/AMD-V/Hyper-V is not enabled, it will automatically switch to QEMU using TCG emulation to set up virtual machines, though performance will be reduced.
  • The installation skips environment checks and uses binary files directly, so no dependencies need to be installed.
Environment Check ​
Check if the server supports KVM nested virtualization:
bash
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/ecs/master/goecs.sh -o goecs.sh && chmod +x goecs.sh && ./goecs.sh install && goecs
Select hardware individual test
Compute Node Installation Steps ​
  1. Download the installation script:
    bash
    curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_hypervisor.sh -o install_hypervisor.sh \\
 && chmod +x install_hypervisor.sh
  2. Execute installation (replace with your Controller IP):
    bash
    bash install_hypervisor.sh x.x.x.x
    Replace x.x.x.x with the actual IP address of your Controller.
  3. Node Management in Panel
     After execution, there will be prompts for information needed in the Controller panel.
     In the panel, the Hostname to be entered is the current compute node's IPv4 address, and you need to enter the Token to identify the node.
NetworkManager Version Issue ​
During installation, you may encounter the following error:
Connection 'eth0' (bed050e9-ff49-4665-8112-24ddf2a1cd3c) successfully deleted.
diff --git a/assets/en_incomplete_webvirtcloud_retspen.md.bc959676.js b/assets/en_incomplete_webvirtcloud_retspen.md.062834e1.js
similarity index 99%
rename from assets/en_incomplete_webvirtcloud_retspen.md.bc959676.js
rename to assets/en_incomplete_webvirtcloud_retspen.md.062834e1.js
index 2449fba78b..d448abf34d 100644
--- a/assets/en_incomplete_webvirtcloud_retspen.md.bc959676.js
+++ b/assets/en_incomplete_webvirtcloud_retspen.md.062834e1.js
@@ -1,4 +1,4 @@
-import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const o="/assets/vcr1.30d933ab.jpg",n="/assets/vcr2.9b30a319.jpg",r="/assets/vcr3.0aa5a564.jpg",l="/assets/vcr4.18a1487e.jpg",i="/assets/vcr5.97deb479.jpg",c="/assets/vcr6.e706123b.jpg",p="/assets/vcr7.43c60335.jpg",d="/assets/vcr8.1bf1f353.jpg",m="/assets/vcr9.b5afa4b4.jpg",h="/assets/vcr10.548c566e.jpg",u="/assets/vcr11.58ce8ace.jpg",g="/assets/vcr12.3aa69b2a.jpg",v="/assets/vcr13.fcbcc557.jpg",b="/assets/vcr14.7009c833.jpg",q=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/webvirtcloud_retspen.md","filePath":"en/incomplete/webvirtcloud_retspen.md","lastUpdated":1747726389000}'),y={name:"en/incomplete/webvirtcloud_retspen.md"},_=a(`
WebVirtCloud Installation Guide ​
hits
Repository: https://github.com/oneclickvirt/webvirtcloud
Origin Repository:：https://github.com/retspen/webvirtcloud
Controller Node and Computer Node Installation ​
  • Supported Systems: Debian10+, Ubuntu18.04+, Centos8+, AlmaLinux8+, RockyLinux8+
  • Recommended system: Debian12+, Ubuntu22.04+.
  • Lower versions of the system will automatically compile the new version of python installation package before deployment, so it is recommended to use a new system without compiling directly installed!
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud_retspen.sh -o install_webvirt_cloud_retspen.sh \\
+import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const o="/assets/vcr1.30d933ab.jpg",n="/assets/vcr2.9b30a319.jpg",r="/assets/vcr3.0aa5a564.jpg",l="/assets/vcr4.18a1487e.jpg",i="/assets/vcr5.97deb479.jpg",c="/assets/vcr6.e706123b.jpg",p="/assets/vcr7.43c60335.jpg",d="/assets/vcr8.1bf1f353.jpg",m="/assets/vcr9.b5afa4b4.jpg",h="/assets/vcr10.548c566e.jpg",u="/assets/vcr11.58ce8ace.jpg",g="/assets/vcr12.3aa69b2a.jpg",v="/assets/vcr13.fcbcc557.jpg",b="/assets/vcr14.7009c833.jpg",q=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/webvirtcloud_retspen.md","filePath":"en/incomplete/webvirtcloud_retspen.md","lastUpdated":1747730955000}'),y={name:"en/incomplete/webvirtcloud_retspen.md"},_=a(`
WebVirtCloud Installation Guide ​
hits
Repository: https://github.com/oneclickvirt/webvirtcloud
Origin Repository:：https://github.com/retspen/webvirtcloud
Controller Node and Computer Node Installation ​
  • Supported Systems: Debian10+, Ubuntu18.04+, Centos8+, AlmaLinux8+, RockyLinux8+
  • Recommended system: Debian12+, Ubuntu22.04+.
  • Lower versions of the system will automatically compile the new version of python installation package before deployment, so it is recommended to use a new system without compiling directly installed!
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud_retspen.sh -o install_webvirt_cloud_retspen.sh \\
 && chmod +x install_webvirt_cloud_retspen.sh \\
 && bash install_webvirt_cloud_retspen.sh
After installation is complete, open the public IP address to access the login page.
The default login username and password are both admin. Make sure to change them after logging in.
Creating a Linux Virtual Machine ​
After entering the control panel and changing the admin password, you need to manually configure a compute node.
vcr1
Select the type as Local, and name it local.
vcr2
After creation, click the eye icon to enter the view.
vcr3
Under the Storage section, add a storage entry. Choose the type Dir and name it local. If you need to use an ISO for system boot, you’ll need to create a storage of type ISO. If not, just follow this guide and create only the Dir type.
vcr4
vcr5
After creation, download the appropriate qcow2 image for the system using the repository below:
https://github.com/oneclickvirt/pve_kvm_images/releases/tag/images
In the example, a Debian 12 qcow2 image is used:
shell
cd /var/lib/libvirt/images
 wget https://github.com/oneclickvirt/pve_kvm_images/releases/download/images/debian12.qcow2
diff --git a/assets/en_incomplete_webvirtcloud_retspen.md.bc959676.lean.js b/assets/en_incomplete_webvirtcloud_retspen.md.062834e1.lean.js
similarity index 99%
rename from assets/en_incomplete_webvirtcloud_retspen.md.bc959676.lean.js
rename to assets/en_incomplete_webvirtcloud_retspen.md.062834e1.lean.js
index 2449fba78b..d448abf34d 100644
--- a/assets/en_incomplete_webvirtcloud_retspen.md.bc959676.lean.js
+++ b/assets/en_incomplete_webvirtcloud_retspen.md.062834e1.lean.js
@@ -1,4 +1,4 @@
-import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const o="/assets/vcr1.30d933ab.jpg",n="/assets/vcr2.9b30a319.jpg",r="/assets/vcr3.0aa5a564.jpg",l="/assets/vcr4.18a1487e.jpg",i="/assets/vcr5.97deb479.jpg",c="/assets/vcr6.e706123b.jpg",p="/assets/vcr7.43c60335.jpg",d="/assets/vcr8.1bf1f353.jpg",m="/assets/vcr9.b5afa4b4.jpg",h="/assets/vcr10.548c566e.jpg",u="/assets/vcr11.58ce8ace.jpg",g="/assets/vcr12.3aa69b2a.jpg",v="/assets/vcr13.fcbcc557.jpg",b="/assets/vcr14.7009c833.jpg",q=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/webvirtcloud_retspen.md","filePath":"en/incomplete/webvirtcloud_retspen.md","lastUpdated":1747726389000}'),y={name:"en/incomplete/webvirtcloud_retspen.md"},_=a(`
WebVirtCloud Installation Guide ​
hits
Repository: https://github.com/oneclickvirt/webvirtcloud
Origin Repository:：https://github.com/retspen/webvirtcloud
Controller Node and Computer Node Installation ​
  • Supported Systems: Debian10+, Ubuntu18.04+, Centos8+, AlmaLinux8+, RockyLinux8+
  • Recommended system: Debian12+, Ubuntu22.04+.
  • Lower versions of the system will automatically compile the new version of python installation package before deployment, so it is recommended to use a new system without compiling directly installed!
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud_retspen.sh -o install_webvirt_cloud_retspen.sh \\
+import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const o="/assets/vcr1.30d933ab.jpg",n="/assets/vcr2.9b30a319.jpg",r="/assets/vcr3.0aa5a564.jpg",l="/assets/vcr4.18a1487e.jpg",i="/assets/vcr5.97deb479.jpg",c="/assets/vcr6.e706123b.jpg",p="/assets/vcr7.43c60335.jpg",d="/assets/vcr8.1bf1f353.jpg",m="/assets/vcr9.b5afa4b4.jpg",h="/assets/vcr10.548c566e.jpg",u="/assets/vcr11.58ce8ace.jpg",g="/assets/vcr12.3aa69b2a.jpg",v="/assets/vcr13.fcbcc557.jpg",b="/assets/vcr14.7009c833.jpg",q=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/webvirtcloud_retspen.md","filePath":"en/incomplete/webvirtcloud_retspen.md","lastUpdated":1747730955000}'),y={name:"en/incomplete/webvirtcloud_retspen.md"},_=a(`
WebVirtCloud Installation Guide ​
hits
Repository: https://github.com/oneclickvirt/webvirtcloud
Origin Repository:：https://github.com/retspen/webvirtcloud
Controller Node and Computer Node Installation ​
  • Supported Systems: Debian10+, Ubuntu18.04+, Centos8+, AlmaLinux8+, RockyLinux8+
  • Recommended system: Debian12+, Ubuntu22.04+.
  • Lower versions of the system will automatically compile the new version of python installation package before deployment, so it is recommended to use a new system without compiling directly installed!
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud_retspen.sh -o install_webvirt_cloud_retspen.sh \\
 && chmod +x install_webvirt_cloud_retspen.sh \\
 && bash install_webvirt_cloud_retspen.sh
After installation is complete, open the public IP address to access the login page.
The default login username and password are both admin. Make sure to change them after logging in.
Creating a Linux Virtual Machine ​
After entering the control panel and changing the admin password, you need to manually configure a compute node.
vcr1
Select the type as Local, and name it local.
vcr2
After creation, click the eye icon to enter the view.
vcr3
Under the Storage section, add a storage entry. Choose the type Dir and name it local. If you need to use an ISO for system boot, you’ll need to create a storage of type ISO. If not, just follow this guide and create only the Dir type.
vcr4
vcr5
After creation, download the appropriate qcow2 image for the system using the repository below:
https://github.com/oneclickvirt/pve_kvm_images/releases/tag/images
In the example, a Debian 12 qcow2 image is used:
shell
cd /var/lib/libvirt/images
 wget https://github.com/oneclickvirt/pve_kvm_images/releases/download/images/debian12.qcow2
diff --git a/assets/en_incomplete_webvirtmgr.md.6d45f601.js b/assets/en_incomplete_webvirtmgr.md.74f1937c.js
similarity index 98%
rename from assets/en_incomplete_webvirtmgr.md.6d45f601.js
rename to assets/en_incomplete_webvirtmgr.md.74f1937c.js
index c5fa3b988b..7fcd04a33e 100644
--- a/assets/en_incomplete_webvirtmgr.md.6d45f601.js
+++ b/assets/en_incomplete_webvirtmgr.md.74f1937c.js
@@ -1,3 +1,3 @@
-import{_ as t,v as e,b as a,R as s}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/webvirtmgr.md","filePath":"en/incomplete/webvirtmgr.md","lastUpdated":1747726389000}'),n={name:"en/incomplete/webvirtmgr.md"},l=s(`
WebVirtMgr Installation Guide ​
hits
Repository: https://github.com/oneclickvirt/webvirtcloud
Origin Repository: https://github.com/retspen/webvirtmgr
Control nodes and compute nodes installed at the same time ​
  • Supported systems: Debian[8,9,10]，Ubuntu[16.04,18.04,20.04]
  • The system will automatically compile python 2.7 installer and then deployed, there will be an error in the compilation process but do not pay attention to it, as long as the scripts are still running, it means that everything is fine!
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirtmgr.sh -o install_webvirtmgr.sh \\
+import{_ as t,v as e,b as a,R as s}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/webvirtmgr.md","filePath":"en/incomplete/webvirtmgr.md","lastUpdated":1747730955000}'),n={name:"en/incomplete/webvirtmgr.md"},l=s(`
WebVirtMgr Installation Guide ​
hits
Repository: https://github.com/oneclickvirt/webvirtcloud
Origin Repository: https://github.com/retspen/webvirtmgr
Control nodes and compute nodes installed at the same time ​
  • Supported systems: Debian[8,9,10]，Ubuntu[16.04,18.04,20.04]
  • The system will automatically compile python 2.7 installer and then deployed, there will be an error in the compilation process but do not pay attention to it, as long as the scripts are still running, it means that everything is fine!
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirtmgr.sh -o install_webvirtmgr.sh \\
 && chmod +x install_webvirtmgr.sh \\
 && bash install_webvirtmgr.sh
Disadvantages ​
The origin project is no longer maintained and is not recommended at all.
`,9),o=[l];function r(i,p,c,d,h,m){return e(),a("div",null,o)}const u=t(n,[["render",r]]);export{g as __pageData,u as default};
diff --git a/assets/en_incomplete_webvirtmgr.md.6d45f601.lean.js b/assets/en_incomplete_webvirtmgr.md.74f1937c.lean.js
similarity index 98%
rename from assets/en_incomplete_webvirtmgr.md.6d45f601.lean.js
rename to assets/en_incomplete_webvirtmgr.md.74f1937c.lean.js
index c5fa3b988b..7fcd04a33e 100644
--- a/assets/en_incomplete_webvirtmgr.md.6d45f601.lean.js
+++ b/assets/en_incomplete_webvirtmgr.md.74f1937c.lean.js
@@ -1,3 +1,3 @@
-import{_ as t,v as e,b as a,R as s}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/webvirtmgr.md","filePath":"en/incomplete/webvirtmgr.md","lastUpdated":1747726389000}'),n={name:"en/incomplete/webvirtmgr.md"},l=s(`
WebVirtMgr Installation Guide ​
hits
Repository: https://github.com/oneclickvirt/webvirtcloud
Origin Repository: https://github.com/retspen/webvirtmgr
Control nodes and compute nodes installed at the same time ​
  • Supported systems: Debian[8,9,10]，Ubuntu[16.04,18.04,20.04]
  • The system will automatically compile python 2.7 installer and then deployed, there will be an error in the compilation process but do not pay attention to it, as long as the scripts are still running, it means that everything is fine!
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirtmgr.sh -o install_webvirtmgr.sh \\
+import{_ as t,v as e,b as a,R as s}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/incomplete/webvirtmgr.md","filePath":"en/incomplete/webvirtmgr.md","lastUpdated":1747730955000}'),n={name:"en/incomplete/webvirtmgr.md"},l=s(`
WebVirtMgr Installation Guide ​
hits
Repository: https://github.com/oneclickvirt/webvirtcloud
Origin Repository: https://github.com/retspen/webvirtmgr
Control nodes and compute nodes installed at the same time ​
  • Supported systems: Debian[8,9,10]，Ubuntu[16.04,18.04,20.04]
  • The system will automatically compile python 2.7 installer and then deployed, there will be an error in the compilation process but do not pay attention to it, as long as the scripts are still running, it means that everything is fine!
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirtmgr.sh -o install_webvirtmgr.sh \\
 && chmod +x install_webvirtmgr.sh \\
 && bash install_webvirtmgr.sh
Disadvantages ​
The origin project is no longer maintained and is not recommended at all.
`,9),o=[l];function r(i,p,c,d,h,m){return e(),a("div",null,o)}const u=t(n,[["render",r]]);export{g as __pageData,u as default};
diff --git a/assets/en_index.md.4bb18770.js b/assets/en_index.md.be47d6f9.js
similarity index 97%
rename from assets/en_index.md.4bb18770.js
rename to assets/en_index.md.be47d6f9.js
index b795a2822f..26eb0c197d 100644
--- a/assets/en_index.md.4bb18770.js
+++ b/assets/en_index.md.be47d6f9.js
@@ -1 +1 @@
-import{_ as t,v as e,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse(`{"title":"K'thun","titleTemplate":"One Click Virtualization","description":"","frontmatter":{"layout":"home","title":"K'thun","titleTemplate":"One Click Virtualization","tagline":"Open source, easy to use server virtualization project","hero":{"name":"One Click Virtualization","text":"Open source, easy to use server virtualization project","image":"https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"Learn More →","link":"/en/guide/dashboard"}]},"features":[{"title":"One Click Use","details":"Supports one-click command installation and use, easy to create virtual machines or containers on X86_64 and ARM architecture servers"},{"title":"Based on mainstream systems development","details":"Based on long-term maintenance releases of Debian, Ubuntu, Centos, etc., there is always a way to virtualize containers or virtual machines, no matter what the system is."},{"title":"Port forwarding and IP assignment automation","details":"Self-contained internal and external port forwarding and automatic IP address allocation (including IPV6、IPV4), including TCP, UDP, VNC, RDP and other protocols, without manual management"},{"title":"Batch Virtualization","details":"Supports batch opening of containers or virtual machines using KVM, LXC, Docker virtualization"},{"title":"Multi-system and multi-environment support","details":"Open containers or virtual machines that support mainstream systems, including Linux, Windows, MacOS, Android as well as pure browser or desktop environments."},{"title":"Self-limiting abuse","details":"Some virtualized containers or VMs support the setting of masks and loading limits to avoid being used for abuse."},{"title":"FAQ","details":"All questions and problems that may arise during the program are answered."},{"title":"Development thanks","details":"Thanks to Evolution Host for supporting us with a DDoS protected VPS"}]},"headers":[],"relativePath":"en/index.md","filePath":"en/index.md","lastUpdated":1747726389000}`),n={name:"en/index.md"};function i(s,o,r,l,d,u){return e(),a("div")}const p=t(n,[["render",i]]);export{m as __pageData,p as default};
+import{_ as t,v as e,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse(`{"title":"K'thun","titleTemplate":"One Click Virtualization","description":"","frontmatter":{"layout":"home","title":"K'thun","titleTemplate":"One Click Virtualization","tagline":"Open source, easy to use server virtualization project","hero":{"name":"One Click Virtualization","text":"Open source, easy to use server virtualization project","image":"https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"Learn More →","link":"/en/guide/dashboard"}]},"features":[{"title":"One Click Use","details":"Supports one-click command installation and use, easy to create virtual machines or containers on X86_64 and ARM architecture servers"},{"title":"Based on mainstream systems development","details":"Based on long-term maintenance releases of Debian, Ubuntu, Centos, etc., there is always a way to virtualize containers or virtual machines, no matter what the system is."},{"title":"Port forwarding and IP assignment automation","details":"Self-contained internal and external port forwarding and automatic IP address allocation (including IPV6、IPV4), including TCP, UDP, VNC, RDP and other protocols, without manual management"},{"title":"Batch Virtualization","details":"Supports batch opening of containers or virtual machines using KVM, LXC, Docker virtualization"},{"title":"Multi-system and multi-environment support","details":"Open containers or virtual machines that support mainstream systems, including Linux, Windows, MacOS, Android as well as pure browser or desktop environments."},{"title":"Self-limiting abuse","details":"Some virtualized containers or VMs support the setting of masks and loading limits to avoid being used for abuse."},{"title":"FAQ","details":"All questions and problems that may arise during the program are answered."},{"title":"Development thanks","details":"Thanks to Evolution Host for supporting us with a DDoS protected VPS"}]},"headers":[],"relativePath":"en/index.md","filePath":"en/index.md","lastUpdated":1747730955000}`),n={name:"en/index.md"};function i(s,o,r,l,d,u){return e(),a("div")}const p=t(n,[["render",i]]);export{m as __pageData,p as default};
diff --git a/assets/en_index.md.4bb18770.lean.js b/assets/en_index.md.be47d6f9.lean.js
similarity index 97%
rename from assets/en_index.md.4bb18770.lean.js
rename to assets/en_index.md.be47d6f9.lean.js
index b795a2822f..26eb0c197d 100644
--- a/assets/en_index.md.4bb18770.lean.js
+++ b/assets/en_index.md.be47d6f9.lean.js
@@ -1 +1 @@
-import{_ as t,v as e,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse(`{"title":"K'thun","titleTemplate":"One Click Virtualization","description":"","frontmatter":{"layout":"home","title":"K'thun","titleTemplate":"One Click Virtualization","tagline":"Open source, easy to use server virtualization project","hero":{"name":"One Click Virtualization","text":"Open source, easy to use server virtualization project","image":"https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"Learn More →","link":"/en/guide/dashboard"}]},"features":[{"title":"One Click Use","details":"Supports one-click command installation and use, easy to create virtual machines or containers on X86_64 and ARM architecture servers"},{"title":"Based on mainstream systems development","details":"Based on long-term maintenance releases of Debian, Ubuntu, Centos, etc., there is always a way to virtualize containers or virtual machines, no matter what the system is."},{"title":"Port forwarding and IP assignment automation","details":"Self-contained internal and external port forwarding and automatic IP address allocation (including IPV6、IPV4), including TCP, UDP, VNC, RDP and other protocols, without manual management"},{"title":"Batch Virtualization","details":"Supports batch opening of containers or virtual machines using KVM, LXC, Docker virtualization"},{"title":"Multi-system and multi-environment support","details":"Open containers or virtual machines that support mainstream systems, including Linux, Windows, MacOS, Android as well as pure browser or desktop environments."},{"title":"Self-limiting abuse","details":"Some virtualized containers or VMs support the setting of masks and loading limits to avoid being used for abuse."},{"title":"FAQ","details":"All questions and problems that may arise during the program are answered."},{"title":"Development thanks","details":"Thanks to Evolution Host for supporting us with a DDoS protected VPS"}]},"headers":[],"relativePath":"en/index.md","filePath":"en/index.md","lastUpdated":1747726389000}`),n={name:"en/index.md"};function i(s,o,r,l,d,u){return e(),a("div")}const p=t(n,[["render",i]]);export{m as __pageData,p as default};
+import{_ as t,v as e,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse(`{"title":"K'thun","titleTemplate":"One Click Virtualization","description":"","frontmatter":{"layout":"home","title":"K'thun","titleTemplate":"One Click Virtualization","tagline":"Open source, easy to use server virtualization project","hero":{"name":"One Click Virtualization","text":"Open source, easy to use server virtualization project","image":"https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"Learn More →","link":"/en/guide/dashboard"}]},"features":[{"title":"One Click Use","details":"Supports one-click command installation and use, easy to create virtual machines or containers on X86_64 and ARM architecture servers"},{"title":"Based on mainstream systems development","details":"Based on long-term maintenance releases of Debian, Ubuntu, Centos, etc., there is always a way to virtualize containers or virtual machines, no matter what the system is."},{"title":"Port forwarding and IP assignment automation","details":"Self-contained internal and external port forwarding and automatic IP address allocation (including IPV6、IPV4), including TCP, UDP, VNC, RDP and other protocols, without manual management"},{"title":"Batch Virtualization","details":"Supports batch opening of containers or virtual machines using KVM, LXC, Docker virtualization"},{"title":"Multi-system and multi-environment support","details":"Open containers or virtual machines that support mainstream systems, including Linux, Windows, MacOS, Android as well as pure browser or desktop environments."},{"title":"Self-limiting abuse","details":"Some virtualized containers or VMs support the setting of masks and loading limits to avoid being used for abuse."},{"title":"FAQ","details":"All questions and problems that may arise during the program are answered."},{"title":"Development thanks","details":"Thanks to Evolution Host for supporting us with a DDoS protected VPS"}]},"headers":[],"relativePath":"en/index.md","filePath":"en/index.md","lastUpdated":1747730955000}`),n={name:"en/index.md"};function i(s,o,r,l,d,u){return e(),a("div")}const p=t(n,[["render",i]]);export{m as __pageData,p as default};
diff --git a/assets/guide_block_block_docker.md.e3283eaa.js b/assets/guide_block_block_docker.md.748c9ec3.js
similarity index 90%
rename from assets/guide_block_block_docker.md.e3283eaa.js
rename to assets/guide_block_block_docker.md.748c9ec3.js
index 03d16b42a9..06ceeb4d29 100644
--- a/assets/guide_block_block_docker.md.e3283eaa.js
+++ b/assets/guide_block_block_docker.md.748c9ec3.js
@@ -1 +1 @@
-import{_ as a,v as t,b as o,F as e,L as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"待开发，敬请期待","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_docker.md","filePath":"guide/block/block_docker.md","lastUpdated":1747726389000}'),c={name:"guide/block/block_docker.md"},r=e("h1",{id:"待开发-敬请期待",tabindex:"-1"},[s("待开发，敬请期待 "),e("a",{class:"header-anchor",href:"#待开发-敬请期待","aria-label":'Permalink to "待开发，敬请期待"'},"​")],-1),d=[r];function i(n,l,_,k,p,b){return t(),o("div",null,d)}const m=a(c,[["render",i]]);export{f as __pageData,m as default};
+import{_ as a,v as t,b as o,F as e,L as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"待开发，敬请期待","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_docker.md","filePath":"guide/block/block_docker.md","lastUpdated":1747730955000}'),c={name:"guide/block/block_docker.md"},r=e("h1",{id:"待开发-敬请期待",tabindex:"-1"},[s("待开发，敬请期待 "),e("a",{class:"header-anchor",href:"#待开发-敬请期待","aria-label":'Permalink to "待开发，敬请期待"'},"​")],-1),d=[r];function i(n,l,_,k,p,b){return t(),o("div",null,d)}const m=a(c,[["render",i]]);export{f as __pageData,m as default};
diff --git a/assets/guide_block_block_docker.md.e3283eaa.lean.js b/assets/guide_block_block_docker.md.748c9ec3.lean.js
similarity index 90%
rename from assets/guide_block_block_docker.md.e3283eaa.lean.js
rename to assets/guide_block_block_docker.md.748c9ec3.lean.js
index 03d16b42a9..06ceeb4d29 100644
--- a/assets/guide_block_block_docker.md.e3283eaa.lean.js
+++ b/assets/guide_block_block_docker.md.748c9ec3.lean.js
@@ -1 +1 @@
-import{_ as a,v as t,b as o,F as e,L as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"待开发，敬请期待","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_docker.md","filePath":"guide/block/block_docker.md","lastUpdated":1747726389000}'),c={name:"guide/block/block_docker.md"},r=e("h1",{id:"待开发-敬请期待",tabindex:"-1"},[s("待开发，敬请期待 "),e("a",{class:"header-anchor",href:"#待开发-敬请期待","aria-label":'Permalink to "待开发，敬请期待"'},"​")],-1),d=[r];function i(n,l,_,k,p,b){return t(),o("div",null,d)}const m=a(c,[["render",i]]);export{f as __pageData,m as default};
+import{_ as a,v as t,b as o,F as e,L as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"待开发，敬请期待","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_docker.md","filePath":"guide/block/block_docker.md","lastUpdated":1747730955000}'),c={name:"guide/block/block_docker.md"},r=e("h1",{id:"待开发-敬请期待",tabindex:"-1"},[s("待开发，敬请期待 "),e("a",{class:"header-anchor",href:"#待开发-敬请期待","aria-label":'Permalink to "待开发，敬请期待"'},"​")],-1),d=[r];function i(n,l,_,k,p,b){return t(),o("div",null,d)}const m=a(c,[["render",i]]);export{f as __pageData,m as default};
diff --git a/assets/guide_block_block_incus.md.5275e5c8.js b/assets/guide_block_block_incus.md.c0c2cbd2.js
similarity index 99%
rename from assets/guide_block_block_incus.md.5275e5c8.js
rename to assets/guide_block_block_incus.md.c0c2cbd2.js
index ad1a863a6f..d7a7644020 100644
--- a/assets/guide_block_block_incus.md.5275e5c8.js
+++ b/assets/guide_block_block_incus.md.c0c2cbd2.js
@@ -1 +1 @@
-import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"通过shell脚本屏蔽滥用行为","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_incus.md","filePath":"guide/block/block_incus.md","lastUpdated":1747726389000}'),o={name:"guide/block/block_incus.md"},p=n('
通过shell脚本屏蔽滥用行为 ​
屏蔽容易被滥用的端口的出入流量以屏蔽端口和屏蔽滥用工具包 ​
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事前预防
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
使用screen配置监控屏蔽某些进程的执行遇到某些进程的出现直接关闭容器 ​
  • 如需停止监控可使用screen命令停止lxc_moniter这个名字的窗口并删除
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事后停机
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
',13),e=[p];function t(c,r,C,i,y,D){return a(),l("div",null,e)}const u=s(o,[["render",t]]);export{h as __pageData,u as default};
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"通过shell脚本屏蔽滥用行为","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_incus.md","filePath":"guide/block/block_incus.md","lastUpdated":1747730955000}'),o={name:"guide/block/block_incus.md"},p=n('
通过shell脚本屏蔽滥用行为 ​
屏蔽容易被滥用的端口的出入流量以屏蔽端口和屏蔽滥用工具包 ​
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事前预防
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
使用screen配置监控屏蔽某些进程的执行遇到某些进程的出现直接关闭容器 ​
  • 如需停止监控可使用screen命令停止lxc_moniter这个名字的窗口并删除
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事后停机
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
',13),e=[p];function t(c,r,C,i,y,D){return a(),l("div",null,e)}const u=s(o,[["render",t]]);export{h as __pageData,u as default};
diff --git a/assets/guide_block_block_incus.md.5275e5c8.lean.js b/assets/guide_block_block_incus.md.c0c2cbd2.lean.js
similarity index 99%
rename from assets/guide_block_block_incus.md.5275e5c8.lean.js
rename to assets/guide_block_block_incus.md.c0c2cbd2.lean.js
index ad1a863a6f..d7a7644020 100644
--- a/assets/guide_block_block_incus.md.5275e5c8.lean.js
+++ b/assets/guide_block_block_incus.md.c0c2cbd2.lean.js
@@ -1 +1 @@
-import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"通过shell脚本屏蔽滥用行为","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_incus.md","filePath":"guide/block/block_incus.md","lastUpdated":1747726389000}'),o={name:"guide/block/block_incus.md"},p=n('
通过shell脚本屏蔽滥用行为 ​
屏蔽容易被滥用的端口的出入流量以屏蔽端口和屏蔽滥用工具包 ​
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事前预防
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
使用screen配置监控屏蔽某些进程的执行遇到某些进程的出现直接关闭容器 ​
  • 如需停止监控可使用screen命令停止lxc_moniter这个名字的窗口并删除
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事后停机
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
',13),e=[p];function t(c,r,C,i,y,D){return a(),l("div",null,e)}const u=s(o,[["render",t]]);export{h as __pageData,u as default};
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"通过shell脚本屏蔽滥用行为","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_incus.md","filePath":"guide/block/block_incus.md","lastUpdated":1747730955000}'),o={name:"guide/block/block_incus.md"},p=n('
通过shell脚本屏蔽滥用行为 ​
屏蔽容易被滥用的端口的出入流量以屏蔽端口和屏蔽滥用工具包 ​
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事前预防
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
使用screen配置监控屏蔽某些进程的执行遇到某些进程的出现直接关闭容器 ​
  • 如需停止监控可使用screen命令停止lxc_moniter这个名字的窗口并删除
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事后停机
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
',13),e=[p];function t(c,r,C,i,y,D){return a(),l("div",null,e)}const u=s(o,[["render",t]]);export{h as __pageData,u as default};
diff --git a/assets/guide_block_block_iptables.md.f0c17491.js b/assets/guide_block_block_iptables.md.c570a8e7.js
similarity index 99%
rename from assets/guide_block_block_iptables.md.f0c17491.js
rename to assets/guide_block_block_iptables.md.c570a8e7.js
index 6782afef86..2aa8fe1f39 100644
--- a/assets/guide_block_block_iptables.md.f0c17491.js
+++ b/assets/guide_block_block_iptables.md.c570a8e7.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"通过iptables屏蔽滥用","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_iptables.md","filePath":"guide/block/block_iptables.md","lastUpdated":1747726389000}'),o={name:"guide/block/block_iptables.md"},p=l(`
通过iptables屏蔽滥用 ​
iptables的基础使用说明 ​
1. 启动 iptables ​
在大多数 Linux 发行版中，iptables 服务可以通过以下命令启动：
bash
sudo systemctl start iptables
2. 设置规则 ​
在启动 iptables 后，可以设置相应的规则来屏蔽滥用流量。例如，以下命令将阻止来自特定IPV4地址的流量：
bash
sudo iptables -A INPUT -s xxx.xxx.xxx.xxx -j DROP
3. 查询规则 ​
设置完规则后，可以使用以下命令查看当前的 iptables 规则：
bash
sudo iptables -L
这将列出所有输入、输出和转发的规则。
4. 停止 iptables ​
如果需要停止 iptables 服务，可以使用以下命令：
bash
sudo systemctl stop iptables
5. 保存规则 ​
为了确保在重启后规则依然生效，可以保存当前的规则：
bash
sudo iptables-save | sudo tee /etc/iptables/rules.v4
6. 恢复规则 ​
在需要恢复规则时，可以使用以下命令：
bash
sudo iptables-restore < /etc/iptables/rules.v4
7. 其他常用命令 ​
  • 列出规则（详细信息）：
    bash
    sudo iptables -L -v
  • 删除特定规则：
    bash
    sudo iptables -D INPUT -s 192.168.1.100 -j DROP
  • 清空所有规则：
    bash
    sudo iptables -F
在宿主机上屏蔽滥用行为 ​
屏蔽挖矿行为 ​
strings=(
+import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"通过iptables屏蔽滥用","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_iptables.md","filePath":"guide/block/block_iptables.md","lastUpdated":1747730955000}'),o={name:"guide/block/block_iptables.md"},p=l(`
通过iptables屏蔽滥用 ​
iptables的基础使用说明 ​
1. 启动 iptables ​
在大多数 Linux 发行版中，iptables 服务可以通过以下命令启动：
bash
sudo systemctl start iptables
2. 设置规则 ​
在启动 iptables 后，可以设置相应的规则来屏蔽滥用流量。例如，以下命令将阻止来自特定IPV4地址的流量：
bash
sudo iptables -A INPUT -s xxx.xxx.xxx.xxx -j DROP
3. 查询规则 ​
设置完规则后，可以使用以下命令查看当前的 iptables 规则：
bash
sudo iptables -L
这将列出所有输入、输出和转发的规则。
4. 停止 iptables ​
如果需要停止 iptables 服务，可以使用以下命令：
bash
sudo systemctl stop iptables
5. 保存规则 ​
为了确保在重启后规则依然生效，可以保存当前的规则：
bash
sudo iptables-save | sudo tee /etc/iptables/rules.v4
6. 恢复规则 ​
在需要恢复规则时，可以使用以下命令：
bash
sudo iptables-restore < /etc/iptables/rules.v4
7. 其他常用命令 ​
  • 列出规则（详细信息）：
    bash
    sudo iptables -L -v
  • 删除特定规则：
    bash
    sudo iptables -D INPUT -s 192.168.1.100 -j DROP
  • 清空所有规则：
    bash
    sudo iptables -F
在宿主机上屏蔽滥用行为 ​
屏蔽挖矿行为 ​
strings=(
     "ethermine.com"
     "antpool.one"
     "antpool.com"
diff --git a/assets/guide_block_block_iptables.md.f0c17491.lean.js b/assets/guide_block_block_iptables.md.c570a8e7.lean.js
similarity index 99%
rename from assets/guide_block_block_iptables.md.f0c17491.lean.js
rename to assets/guide_block_block_iptables.md.c570a8e7.lean.js
index 6782afef86..2aa8fe1f39 100644
--- a/assets/guide_block_block_iptables.md.f0c17491.lean.js
+++ b/assets/guide_block_block_iptables.md.c570a8e7.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"通过iptables屏蔽滥用","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_iptables.md","filePath":"guide/block/block_iptables.md","lastUpdated":1747726389000}'),o={name:"guide/block/block_iptables.md"},p=l(`
通过iptables屏蔽滥用 ​
iptables的基础使用说明 ​
1. 启动 iptables ​
在大多数 Linux 发行版中，iptables 服务可以通过以下命令启动：
bash
sudo systemctl start iptables
2. 设置规则 ​
在启动 iptables 后，可以设置相应的规则来屏蔽滥用流量。例如，以下命令将阻止来自特定IPV4地址的流量：
bash
sudo iptables -A INPUT -s xxx.xxx.xxx.xxx -j DROP
3. 查询规则 ​
设置完规则后，可以使用以下命令查看当前的 iptables 规则：
bash
sudo iptables -L
这将列出所有输入、输出和转发的规则。
4. 停止 iptables ​
如果需要停止 iptables 服务，可以使用以下命令：
bash
sudo systemctl stop iptables
5. 保存规则 ​
为了确保在重启后规则依然生效，可以保存当前的规则：
bash
sudo iptables-save | sudo tee /etc/iptables/rules.v4
6. 恢复规则 ​
在需要恢复规则时，可以使用以下命令：
bash
sudo iptables-restore < /etc/iptables/rules.v4
7. 其他常用命令 ​
  • 列出规则（详细信息）：
    bash
    sudo iptables -L -v
  • 删除特定规则：
    bash
    sudo iptables -D INPUT -s 192.168.1.100 -j DROP
  • 清空所有规则：
    bash
    sudo iptables -F
在宿主机上屏蔽滥用行为 ​
屏蔽挖矿行为 ​
strings=(
+import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"通过iptables屏蔽滥用","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_iptables.md","filePath":"guide/block/block_iptables.md","lastUpdated":1747730955000}'),o={name:"guide/block/block_iptables.md"},p=l(`
通过iptables屏蔽滥用 ​
iptables的基础使用说明 ​
1. 启动 iptables ​
在大多数 Linux 发行版中，iptables 服务可以通过以下命令启动：
bash
sudo systemctl start iptables
2. 设置规则 ​
在启动 iptables 后，可以设置相应的规则来屏蔽滥用流量。例如，以下命令将阻止来自特定IPV4地址的流量：
bash
sudo iptables -A INPUT -s xxx.xxx.xxx.xxx -j DROP
3. 查询规则 ​
设置完规则后，可以使用以下命令查看当前的 iptables 规则：
bash
sudo iptables -L
这将列出所有输入、输出和转发的规则。
4. 停止 iptables ​
如果需要停止 iptables 服务，可以使用以下命令：
bash
sudo systemctl stop iptables
5. 保存规则 ​
为了确保在重启后规则依然生效，可以保存当前的规则：
bash
sudo iptables-save | sudo tee /etc/iptables/rules.v4
6. 恢复规则 ​
在需要恢复规则时，可以使用以下命令：
bash
sudo iptables-restore < /etc/iptables/rules.v4
7. 其他常用命令 ​
  • 列出规则（详细信息）：
    bash
    sudo iptables -L -v
  • 删除特定规则：
    bash
    sudo iptables -D INPUT -s 192.168.1.100 -j DROP
  • 清空所有规则：
    bash
    sudo iptables -F
在宿主机上屏蔽滥用行为 ​
屏蔽挖矿行为 ​
strings=(
     "ethermine.com"
     "antpool.one"
     "antpool.com"
diff --git a/assets/guide_block_block_lxd.md.069ac4f4.js b/assets/guide_block_block_lxd.md.f9861f9e.js
similarity index 99%
rename from assets/guide_block_block_lxd.md.069ac4f4.js
rename to assets/guide_block_block_lxd.md.f9861f9e.js
index be05fc0d06..33bc2b6840 100644
--- a/assets/guide_block_block_lxd.md.069ac4f4.js
+++ b/assets/guide_block_block_lxd.md.f9861f9e.js
@@ -1 +1 @@
-import{_ as s,v as l,b as a,R as o}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"通过shell脚本屏蔽滥用行为","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_lxd.md","filePath":"guide/block/block_lxd.md","lastUpdated":1747726389000}'),n={name:"guide/block/block_lxd.md"},p=o('
通过shell脚本屏蔽滥用行为 ​
屏蔽容易被滥用的端口的出入流量以屏蔽端口和屏蔽滥用工具包 ​
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事前预防
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
使用screen配置监控屏蔽某些进程的执行遇到某些进程的出现直接关闭容器 ​
  • 如需停止监控可使用screen命令停止lxc_moniter这个名字的窗口并删除
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事后停机
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
',13),e=[p];function t(c,r,C,i,y,D){return l(),a("div",null,e)}const d=s(n,[["render",t]]);export{h as __pageData,d as default};
+import{_ as s,v as l,b as a,R as o}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"通过shell脚本屏蔽滥用行为","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_lxd.md","filePath":"guide/block/block_lxd.md","lastUpdated":1747730955000}'),n={name:"guide/block/block_lxd.md"},p=o('
通过shell脚本屏蔽滥用行为 ​
屏蔽容易被滥用的端口的出入流量以屏蔽端口和屏蔽滥用工具包 ​
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事前预防
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
使用screen配置监控屏蔽某些进程的执行遇到某些进程的出现直接关闭容器 ​
  • 如需停止监控可使用screen命令停止lxc_moniter这个名字的窗口并删除
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事后停机
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
',13),e=[p];function t(c,r,C,i,y,D){return l(),a("div",null,e)}const d=s(n,[["render",t]]);export{h as __pageData,d as default};
diff --git a/assets/guide_block_block_lxd.md.069ac4f4.lean.js b/assets/guide_block_block_lxd.md.f9861f9e.lean.js
similarity index 99%
rename from assets/guide_block_block_lxd.md.069ac4f4.lean.js
rename to assets/guide_block_block_lxd.md.f9861f9e.lean.js
index be05fc0d06..33bc2b6840 100644
--- a/assets/guide_block_block_lxd.md.069ac4f4.lean.js
+++ b/assets/guide_block_block_lxd.md.f9861f9e.lean.js
@@ -1 +1 @@
-import{_ as s,v as l,b as a,R as o}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"通过shell脚本屏蔽滥用行为","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_lxd.md","filePath":"guide/block/block_lxd.md","lastUpdated":1747726389000}'),n={name:"guide/block/block_lxd.md"},p=o('
通过shell脚本屏蔽滥用行为 ​
屏蔽容易被滥用的端口的出入流量以屏蔽端口和屏蔽滥用工具包 ​
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事前预防
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
使用screen配置监控屏蔽某些进程的执行遇到某些进程的出现直接关闭容器 ​
  • 如需停止监控可使用screen命令停止lxc_moniter这个名字的窗口并删除
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事后停机
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
',13),e=[p];function t(c,r,C,i,y,D){return l(),a("div",null,e)}const d=s(n,[["render",t]]);export{h as __pageData,d as default};
+import{_ as s,v as l,b as a,R as o}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"通过shell脚本屏蔽滥用行为","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_lxd.md","filePath":"guide/block/block_lxd.md","lastUpdated":1747730955000}'),n={name:"guide/block/block_lxd.md"},p=o('
通过shell脚本屏蔽滥用行为 ​
屏蔽容易被滥用的端口的出入流量以屏蔽端口和屏蔽滥用工具包 ​
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事前预防
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
使用screen配置监控屏蔽某些进程的执行遇到某些进程的出现直接关闭容器 ​
  • 如需停止监控可使用screen命令停止lxc_moniter这个名字的窗口并删除
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事后停机
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
',13),e=[p];function t(c,r,C,i,y,D){return l(),a("div",null,e)}const d=s(n,[["render",t]]);export{h as __pageData,d as default};
diff --git a/assets/guide_block_block_pve.md.683b1a49.js b/assets/guide_block_block_pve.md.1ce49359.js
similarity index 97%
rename from assets/guide_block_block_pve.md.683b1a49.js
rename to assets/guide_block_block_pve.md.1ce49359.js
index c4b443f060..9cfbfe11ee 100644
--- a/assets/guide_block_block_pve.md.683b1a49.js
+++ b/assets/guide_block_block_pve.md.1ce49359.js
@@ -1,4 +1,4 @@
-import{_ as s,v as e,b as a,R as t}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"通过设置防火墙限制虚拟机使用的IP避免盗用","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_pve.md","filePath":"guide/block/block_pve.md","lastUpdated":1747726389000}'),l={name:"guide/block/block_pve.md"},o=t(`
通过设置防火墙限制虚拟机使用的IP避免盗用 ​
在PVE的宿主机下创建以下文件
shell
/etc/pve/firewall/<VMID>.fw
+import{_ as s,v as e,b as a,R as t}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"通过设置防火墙限制虚拟机使用的IP避免盗用","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_pve.md","filePath":"guide/block/block_pve.md","lastUpdated":1747730955000}'),l={name:"guide/block/block_pve.md"},o=t(`
通过设置防火墙限制虚拟机使用的IP避免盗用 ​
在PVE的宿主机下创建以下文件
shell
/etc/pve/firewall/<VMID>.fw
 
 [IPSET ipfilter-<net0>]
 xxx.xxx.xxx.xxx
<VMID>替换为虚拟机的VMID数字，<net0>替换为网络设备中对应的别名(一般不用修改，除非你限制的IPV6)，xxx.xxx.xxx.xxx替换为公网IP地址，注意此IP对应前面的网络设备。
这里的意思是net0只能使用xxx.xxx.xxx.xxx这个IP，如果使用其他的IP数据将会被丢弃，从而达到限制虚拟机只能使用此IP的目的。
这里可以有多个IP，一旦启用此规则该VM就无法使用除此之外的任何IP，如果你没有写IPv6地址则代表该VM无法使用IPv6地址。
TIP
本设置仅推荐在开设非NAT全端口映射的独立IP的虚拟机时使用，否则可能导致奇奇怪怪的问题造成服务器没网。
该方法不适合开设任何NAT虚拟机/容器的PVE上使用。
`,8),p=[o];function n(c,i,x,r,d,P){return e(),a("div",null,p)}const g=s(l,[["render",n]]);export{_ as __pageData,g as default};
diff --git a/assets/guide_block_block_pve.md.683b1a49.lean.js b/assets/guide_block_block_pve.md.1ce49359.lean.js
similarity index 97%
rename from assets/guide_block_block_pve.md.683b1a49.lean.js
rename to assets/guide_block_block_pve.md.1ce49359.lean.js
index c4b443f060..9cfbfe11ee 100644
--- a/assets/guide_block_block_pve.md.683b1a49.lean.js
+++ b/assets/guide_block_block_pve.md.1ce49359.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as e,b as a,R as t}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"通过设置防火墙限制虚拟机使用的IP避免盗用","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_pve.md","filePath":"guide/block/block_pve.md","lastUpdated":1747726389000}'),l={name:"guide/block/block_pve.md"},o=t(`
通过设置防火墙限制虚拟机使用的IP避免盗用 ​
在PVE的宿主机下创建以下文件
shell
/etc/pve/firewall/<VMID>.fw
+import{_ as s,v as e,b as a,R as t}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"通过设置防火墙限制虚拟机使用的IP避免盗用","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/block/block_pve.md","filePath":"guide/block/block_pve.md","lastUpdated":1747730955000}'),l={name:"guide/block/block_pve.md"},o=t(`
通过设置防火墙限制虚拟机使用的IP避免盗用 ​
在PVE的宿主机下创建以下文件
shell
/etc/pve/firewall/<VMID>.fw
 
 [IPSET ipfilter-<net0>]
 xxx.xxx.xxx.xxx
<VMID>替换为虚拟机的VMID数字，<net0>替换为网络设备中对应的别名(一般不用修改，除非你限制的IPV6)，xxx.xxx.xxx.xxx替换为公网IP地址，注意此IP对应前面的网络设备。
这里的意思是net0只能使用xxx.xxx.xxx.xxx这个IP，如果使用其他的IP数据将会被丢弃，从而达到限制虚拟机只能使用此IP的目的。
这里可以有多个IP，一旦启用此规则该VM就无法使用除此之外的任何IP，如果你没有写IPv6地址则代表该VM无法使用IPv6地址。
TIP
本设置仅推荐在开设非NAT全端口映射的独立IP的虚拟机时使用，否则可能导致奇奇怪怪的问题造成服务器没网。
该方法不适合开设任何NAT虚拟机/容器的PVE上使用。
`,8),p=[o];function n(c,i,x,r,d,P){return e(),a("div",null,p)}const g=s(l,[["render",n]]);export{_ as __pageData,g as default};
diff --git a/assets/guide_dashboard.md.9a6230ec.js b/assets/guide_dashboard.md.e77e20e6.js
similarity index 96%
rename from assets/guide_dashboard.md.9a6230ec.js
rename to assets/guide_dashboard.md.e77e20e6.js
index 09c4a11a0b..76a34ec407 100644
--- a/assets/guide_dashboard.md.9a6230ec.js
+++ b/assets/guide_dashboard.md.e77e20e6.js
@@ -1 +1 @@
-import{_ as t,v as e,b as a,R as r}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/dashboard.md","filePath":"guide/dashboard.md","lastUpdated":1747726389000}'),i={name:"guide/dashboard.md"},l=r('
准备工作 ​
需要虚拟化出服务器，你需要：
  1. 一台可以连接公网的服务器( VPS 或 Dedicated Server)，最好能完美访问 Github 的 RAW 页面，部分项目部分组件可能未使用 CDN 加速
TIP
如果您位于中国大陆，访问 Github 有困难，请注意配套脚本和项目是否有说明已使用 CDN 加速
  1. 本地可以稳定连接SSH，如果不能稳定连接，请使用screen命令创建窗口后，在窗口内执行命令
TIP
不会用screen命令的，自行查找相关教程学习，或者用tmux替代也行
  1. 确保服务器的系统和硬件满足对应项目的要求，详见对应项目说明
本文档将以VPS作为范例，且该VPS纯净，无原生环境问题，如有必要请重装系统保证初始环境的纯净
WARNING
PVE项目可能造成宿主机出现问题，如果你不会看Bug和修复系统，那么不建议你在生产环境中使用，使用PVE相关脚本请确保宿主机随时可重装系统
项目仓库 ​
欢迎Star和Fork，所有资源均开源，无非开源部分，转载以及使用请写上来源于本站，谢谢
PVE ​
https://github.com/oneclickvirt/pve
Hits
incus ​
https://github.com/oneclickvirt/incus
Hits
Docker ​
https://github.com/oneclickvirt/docker
Hits
LXD ​
https://github.com/oneclickvirt/lxd
Hits
',23),s=[l];function o(c,h,p,n,d,b){return e(),a("div",null,s)}const g=t(i,[["render",o]]);export{m as __pageData,g as default};
+import{_ as t,v as e,b as a,R as r}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/dashboard.md","filePath":"guide/dashboard.md","lastUpdated":1747730955000}'),i={name:"guide/dashboard.md"},l=r('
准备工作 ​
需要虚拟化出服务器，你需要：
  1. 一台可以连接公网的服务器( VPS 或 Dedicated Server)，最好能完美访问 Github 的 RAW 页面，部分项目部分组件可能未使用 CDN 加速
TIP
如果您位于中国大陆，访问 Github 有困难，请注意配套脚本和项目是否有说明已使用 CDN 加速
  1. 本地可以稳定连接SSH，如果不能稳定连接，请使用screen命令创建窗口后，在窗口内执行命令
TIP
不会用screen命令的，自行查找相关教程学习，或者用tmux替代也行
  1. 确保服务器的系统和硬件满足对应项目的要求，详见对应项目说明
本文档将以VPS作为范例，且该VPS纯净，无原生环境问题，如有必要请重装系统保证初始环境的纯净
WARNING
PVE项目可能造成宿主机出现问题，如果你不会看Bug和修复系统，那么不建议你在生产环境中使用，使用PVE相关脚本请确保宿主机随时可重装系统
项目仓库 ​
欢迎Star和Fork，所有资源均开源，无非开源部分，转载以及使用请写上来源于本站，谢谢
PVE ​
https://github.com/oneclickvirt/pve
Hits
incus ​
https://github.com/oneclickvirt/incus
Hits
Docker ​
https://github.com/oneclickvirt/docker
Hits
LXD ​
https://github.com/oneclickvirt/lxd
Hits
',23),s=[l];function o(c,h,p,n,d,b){return e(),a("div",null,s)}const g=t(i,[["render",o]]);export{m as __pageData,g as default};
diff --git a/assets/guide_dashboard.md.9a6230ec.lean.js b/assets/guide_dashboard.md.e77e20e6.lean.js
similarity index 96%
rename from assets/guide_dashboard.md.9a6230ec.lean.js
rename to assets/guide_dashboard.md.e77e20e6.lean.js
index 09c4a11a0b..76a34ec407 100644
--- a/assets/guide_dashboard.md.9a6230ec.lean.js
+++ b/assets/guide_dashboard.md.e77e20e6.lean.js
@@ -1 +1 @@
-import{_ as t,v as e,b as a,R as r}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/dashboard.md","filePath":"guide/dashboard.md","lastUpdated":1747726389000}'),i={name:"guide/dashboard.md"},l=r('
准备工作 ​
需要虚拟化出服务器，你需要：
  1. 一台可以连接公网的服务器( VPS 或 Dedicated Server)，最好能完美访问 Github 的 RAW 页面，部分项目部分组件可能未使用 CDN 加速
TIP
如果您位于中国大陆，访问 Github 有困难，请注意配套脚本和项目是否有说明已使用 CDN 加速
  1. 本地可以稳定连接SSH，如果不能稳定连接，请使用screen命令创建窗口后，在窗口内执行命令
TIP
不会用screen命令的，自行查找相关教程学习，或者用tmux替代也行
  1. 确保服务器的系统和硬件满足对应项目的要求，详见对应项目说明
本文档将以VPS作为范例，且该VPS纯净，无原生环境问题，如有必要请重装系统保证初始环境的纯净
WARNING
PVE项目可能造成宿主机出现问题，如果你不会看Bug和修复系统，那么不建议你在生产环境中使用，使用PVE相关脚本请确保宿主机随时可重装系统
项目仓库 ​
欢迎Star和Fork，所有资源均开源，无非开源部分，转载以及使用请写上来源于本站，谢谢
PVE ​
https://github.com/oneclickvirt/pve
Hits
incus ​
https://github.com/oneclickvirt/incus
Hits
Docker ​
https://github.com/oneclickvirt/docker
Hits
LXD ​
https://github.com/oneclickvirt/lxd
Hits
',23),s=[l];function o(c,h,p,n,d,b){return e(),a("div",null,s)}const g=t(i,[["render",o]]);export{m as __pageData,g as default};
+import{_ as t,v as e,b as a,R as r}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/dashboard.md","filePath":"guide/dashboard.md","lastUpdated":1747730955000}'),i={name:"guide/dashboard.md"},l=r('
准备工作 ​
需要虚拟化出服务器，你需要：
  1. 一台可以连接公网的服务器( VPS 或 Dedicated Server)，最好能完美访问 Github 的 RAW 页面，部分项目部分组件可能未使用 CDN 加速
TIP
如果您位于中国大陆，访问 Github 有困难，请注意配套脚本和项目是否有说明已使用 CDN 加速
  1. 本地可以稳定连接SSH，如果不能稳定连接，请使用screen命令创建窗口后，在窗口内执行命令
TIP
不会用screen命令的，自行查找相关教程学习，或者用tmux替代也行
  1. 确保服务器的系统和硬件满足对应项目的要求，详见对应项目说明
本文档将以VPS作为范例，且该VPS纯净，无原生环境问题，如有必要请重装系统保证初始环境的纯净
WARNING
PVE项目可能造成宿主机出现问题，如果你不会看Bug和修复系统，那么不建议你在生产环境中使用，使用PVE相关脚本请确保宿主机随时可重装系统
项目仓库 ​
欢迎Star和Fork，所有资源均开源，无非开源部分，转载以及使用请写上来源于本站，谢谢
PVE ​
https://github.com/oneclickvirt/pve
Hits
incus ​
https://github.com/oneclickvirt/incus
Hits
Docker ​
https://github.com/oneclickvirt/docker
Hits
LXD ​
https://github.com/oneclickvirt/lxd
Hits
',23),s=[l];function o(c,h,p,n,d,b){return e(),a("div",null,s)}const g=t(i,[["render",o]]);export{m as __pageData,g as default};
diff --git a/assets/guide_dashboardq.md.dfccd0d0.js b/assets/guide_dashboardq.md.adc64497.js
similarity index 94%
rename from assets/guide_dashboardq.md.dfccd0d0.js
rename to assets/guide_dashboardq.md.adc64497.js
index d845ef0160..ca2532dcb8 100644
--- a/assets/guide_dashboardq.md.dfccd0d0.js
+++ b/assets/guide_dashboardq.md.adc64497.js
@@ -1 +1 @@
-import{_ as a,v as s,b as e,R as t}from"./chunks/framework.70afa331.js";const p="/assets/wechat.e3b2e06e.jpg",_=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/dashboardq.md","filePath":"guide/dashboardq.md","lastUpdated":1747726389000}'),o={name:"guide/dashboardq.md"},n=t('
Give me a cup of coffee.
https://ko-fi.com/spiritlhl
WeChat
WeChat
USDT-TRC20
bash
TNqjaPYAmDsm9pbpLY79pixE8z1ce3Zj1B
USDT-Polygon/Matic
bash
0xb81b44cb00f9e6e084f85e5da604ec479e7ffab6
',8),c=[n];function i(l,r,d,h,b,f){return s(),e("div",null,c)}const g=a(o,[["render",i]]);export{_ as __pageData,g as default};
+import{_ as a,v as s,b as e,R as t}from"./chunks/framework.70afa331.js";const p="/assets/wechat.e3b2e06e.jpg",_=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/dashboardq.md","filePath":"guide/dashboardq.md","lastUpdated":1747730955000}'),o={name:"guide/dashboardq.md"},n=t('
Give me a cup of coffee.
https://ko-fi.com/spiritlhl
WeChat
WeChat
USDT-TRC20
bash
TNqjaPYAmDsm9pbpLY79pixE8z1ce3Zj1B
USDT-Polygon/Matic
bash
0xb81b44cb00f9e6e084f85e5da604ec479e7ffab6
',8),c=[n];function i(l,r,d,h,b,f){return s(),e("div",null,c)}const g=a(o,[["render",i]]);export{_ as __pageData,g as default};
diff --git a/assets/guide_dashboardq.md.dfccd0d0.lean.js b/assets/guide_dashboardq.md.adc64497.lean.js
similarity index 94%
rename from assets/guide_dashboardq.md.dfccd0d0.lean.js
rename to assets/guide_dashboardq.md.adc64497.lean.js
index d845ef0160..ca2532dcb8 100644
--- a/assets/guide_dashboardq.md.dfccd0d0.lean.js
+++ b/assets/guide_dashboardq.md.adc64497.lean.js
@@ -1 +1 @@
-import{_ as a,v as s,b as e,R as t}from"./chunks/framework.70afa331.js";const p="/assets/wechat.e3b2e06e.jpg",_=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/dashboardq.md","filePath":"guide/dashboardq.md","lastUpdated":1747726389000}'),o={name:"guide/dashboardq.md"},n=t('
Give me a cup of coffee.
https://ko-fi.com/spiritlhl
WeChat
WeChat
USDT-TRC20
bash
TNqjaPYAmDsm9pbpLY79pixE8z1ce3Zj1B
USDT-Polygon/Matic
bash
0xb81b44cb00f9e6e084f85e5da604ec479e7ffab6
',8),c=[n];function i(l,r,d,h,b,f){return s(),e("div",null,c)}const g=a(o,[["render",i]]);export{_ as __pageData,g as default};
+import{_ as a,v as s,b as e,R as t}from"./chunks/framework.70afa331.js";const p="/assets/wechat.e3b2e06e.jpg",_=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/dashboardq.md","filePath":"guide/dashboardq.md","lastUpdated":1747730955000}'),o={name:"guide/dashboardq.md"},n=t('
Give me a cup of coffee.
https://ko-fi.com/spiritlhl
WeChat
WeChat
USDT-TRC20
bash
TNqjaPYAmDsm9pbpLY79pixE8z1ce3Zj1B
USDT-Polygon/Matic
bash
0xb81b44cb00f9e6e084f85e5da604ec479e7ffab6
',8),c=[n];function i(l,r,d,h,b,f){return s(),e("div",null,c)}const g=a(o,[["render",i]]);export{_ as __pageData,g as default};
diff --git a/assets/guide_docker_docker_android.md.732be5ab.js b/assets/guide_docker_docker_android.md.f7ffc5df.js
similarity index 98%
rename from assets/guide_docker_docker_android.md.732be5ab.js
rename to assets/guide_docker_docker_android.md.f7ffc5df.js
index cdb7dbccd4..1abf86a31f 100644
--- a/assets/guide_docker_docker_android.md.732be5ab.js
+++ b/assets/guide_docker_docker_android.md.f7ffc5df.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"在Docker中开设Android虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_android.md","filePath":"guide/docker/docker_android.md","lastUpdated":1747726389000}'),e={name:"guide/docker/docker_android.md"},p=o(`
在Docker中开设Android虚拟机 ​
一键开设 ​
  • 自定义安卓版本
  • 自动创建带校验的web网站
  • 自动进行nginx安装和反向代理的配置，可选择是否绑定域名，默认回车不绑定使用80端口
  • 无需考虑宿主机是否支持嵌套虚拟化
  • 支持x86_64和ARM架构
宿主机的配置至少要有1核2G内存15G硬盘，否则开设可能会导致宿主机卡死
宿主机推荐 Ubuntu 系统，Debian 系统可能导致安卓屏幕白屏
安卓版本越新占用越大，以上的配置要求是最低版本安卓的配置要求 (个人测试到 12.0.0-latest 的tag可用，更高版本映射白屏了，自己测试哪个能用吧)
如果开设后，过了5分钟浏览器网页的登录验证还是一直失败，那么请查询安卓容器的日志，大概率安卓容器崩溃了，建议更换更低的安卓系统版本的容器进行安装
开设
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/create_android.sh -o create_android.sh && chmod +x create_android.sh && bash create_android.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/create_android.sh -o create_android.sh && chmod +x create_android.sh && bash create_android.sh
命令执行后按照提示输入即可，注意选择版本输入的是序号，对应选项的数字序号，安装完毕后打开本机IPV4+80端口可登录
如果需要查询生成的安卓信息和web登录信息，执行cat /root/android_info可查询信息
默认的用户名 onea
默认密码 oneclick
远程的桌面点击H264 Converter跳转就是了
暂时只支持生成一个安卓容器，勿要重复生成，如需替换版本请执行后续命令删除后再次开设
暂时只支持开设后一直使用，不可重启服务器，重启后可能无法自重启映射成功，自测
删除
  • 删除容器
  • 删除容器对应镜像
  • 删除配置文件
docker rm -f android
+import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"在Docker中开设Android虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_android.md","filePath":"guide/docker/docker_android.md","lastUpdated":1747730955000}'),e={name:"guide/docker/docker_android.md"},p=o(`
在Docker中开设Android虚拟机 ​
一键开设 ​
  • 自定义安卓版本
  • 自动创建带校验的web网站
  • 自动进行nginx安装和反向代理的配置，可选择是否绑定域名，默认回车不绑定使用80端口
  • 无需考虑宿主机是否支持嵌套虚拟化
  • 支持x86_64和ARM架构
宿主机的配置至少要有1核2G内存15G硬盘，否则开设可能会导致宿主机卡死
宿主机推荐 Ubuntu 系统，Debian 系统可能导致安卓屏幕白屏
安卓版本越新占用越大，以上的配置要求是最低版本安卓的配置要求 (个人测试到 12.0.0-latest 的tag可用，更高版本映射白屏了，自己测试哪个能用吧)
如果开设后，过了5分钟浏览器网页的登录验证还是一直失败，那么请查询安卓容器的日志，大概率安卓容器崩溃了，建议更换更低的安卓系统版本的容器进行安装
开设
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/create_android.sh -o create_android.sh && chmod +x create_android.sh && bash create_android.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/create_android.sh -o create_android.sh && chmod +x create_android.sh && bash create_android.sh
命令执行后按照提示输入即可，注意选择版本输入的是序号，对应选项的数字序号，安装完毕后打开本机IPV4+80端口可登录
如果需要查询生成的安卓信息和web登录信息，执行cat /root/android_info可查询信息
默认的用户名 onea
默认密码 oneclick
远程的桌面点击H264 Converter跳转就是了
暂时只支持生成一个安卓容器，勿要重复生成，如需替换版本请执行后续命令删除后再次开设
暂时只支持开设后一直使用，不可重启服务器，重启后可能无法自重启映射成功，自测
删除
  • 删除容器
  • 删除容器对应镜像
  • 删除配置文件
docker rm -f android
 docker rmi $(docker images | grep "redroid" | awk '{print $3}')
 rm -rf /etc/nginx/sites-enabled/reverse-proxy
 rm -rf /etc/nginx/sites-available/reverse-proxy
diff --git a/assets/guide_docker_docker_android.md.732be5ab.lean.js b/assets/guide_docker_docker_android.md.f7ffc5df.lean.js
similarity index 98%
rename from assets/guide_docker_docker_android.md.732be5ab.lean.js
rename to assets/guide_docker_docker_android.md.f7ffc5df.lean.js
index cdb7dbccd4..1abf86a31f 100644
--- a/assets/guide_docker_docker_android.md.732be5ab.lean.js
+++ b/assets/guide_docker_docker_android.md.f7ffc5df.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"在Docker中开设Android虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_android.md","filePath":"guide/docker/docker_android.md","lastUpdated":1747726389000}'),e={name:"guide/docker/docker_android.md"},p=o(`
在Docker中开设Android虚拟机 ​
一键开设 ​
  • 自定义安卓版本
  • 自动创建带校验的web网站
  • 自动进行nginx安装和反向代理的配置，可选择是否绑定域名，默认回车不绑定使用80端口
  • 无需考虑宿主机是否支持嵌套虚拟化
  • 支持x86_64和ARM架构
宿主机的配置至少要有1核2G内存15G硬盘，否则开设可能会导致宿主机卡死
宿主机推荐 Ubuntu 系统，Debian 系统可能导致安卓屏幕白屏
安卓版本越新占用越大，以上的配置要求是最低版本安卓的配置要求 (个人测试到 12.0.0-latest 的tag可用，更高版本映射白屏了，自己测试哪个能用吧)
如果开设后，过了5分钟浏览器网页的登录验证还是一直失败，那么请查询安卓容器的日志，大概率安卓容器崩溃了，建议更换更低的安卓系统版本的容器进行安装
开设
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/create_android.sh -o create_android.sh && chmod +x create_android.sh && bash create_android.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/create_android.sh -o create_android.sh && chmod +x create_android.sh && bash create_android.sh
命令执行后按照提示输入即可，注意选择版本输入的是序号，对应选项的数字序号，安装完毕后打开本机IPV4+80端口可登录
如果需要查询生成的安卓信息和web登录信息，执行cat /root/android_info可查询信息
默认的用户名 onea
默认密码 oneclick
远程的桌面点击H264 Converter跳转就是了
暂时只支持生成一个安卓容器，勿要重复生成，如需替换版本请执行后续命令删除后再次开设
暂时只支持开设后一直使用，不可重启服务器，重启后可能无法自重启映射成功，自测
删除
  • 删除容器
  • 删除容器对应镜像
  • 删除配置文件
docker rm -f android
+import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"在Docker中开设Android虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_android.md","filePath":"guide/docker/docker_android.md","lastUpdated":1747730955000}'),e={name:"guide/docker/docker_android.md"},p=o(`
在Docker中开设Android虚拟机 ​
一键开设 ​
  • 自定义安卓版本
  • 自动创建带校验的web网站
  • 自动进行nginx安装和反向代理的配置，可选择是否绑定域名，默认回车不绑定使用80端口
  • 无需考虑宿主机是否支持嵌套虚拟化
  • 支持x86_64和ARM架构
宿主机的配置至少要有1核2G内存15G硬盘，否则开设可能会导致宿主机卡死
宿主机推荐 Ubuntu 系统，Debian 系统可能导致安卓屏幕白屏
安卓版本越新占用越大，以上的配置要求是最低版本安卓的配置要求 (个人测试到 12.0.0-latest 的tag可用，更高版本映射白屏了，自己测试哪个能用吧)
如果开设后，过了5分钟浏览器网页的登录验证还是一直失败，那么请查询安卓容器的日志，大概率安卓容器崩溃了，建议更换更低的安卓系统版本的容器进行安装
开设
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/create_android.sh -o create_android.sh && chmod +x create_android.sh && bash create_android.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/create_android.sh -o create_android.sh && chmod +x create_android.sh && bash create_android.sh
命令执行后按照提示输入即可，注意选择版本输入的是序号，对应选项的数字序号，安装完毕后打开本机IPV4+80端口可登录
如果需要查询生成的安卓信息和web登录信息，执行cat /root/android_info可查询信息
默认的用户名 onea
默认密码 oneclick
远程的桌面点击H264 Converter跳转就是了
暂时只支持生成一个安卓容器，勿要重复生成，如需替换版本请执行后续命令删除后再次开设
暂时只支持开设后一直使用，不可重启服务器，重启后可能无法自重启映射成功，自测
删除
  • 删除容器
  • 删除容器对应镜像
  • 删除配置文件
docker rm -f android
 docker rmi $(docker images | grep "redroid" | awk '{print $3}')
 rm -rf /etc/nginx/sites-enabled/reverse-proxy
 rm -rf /etc/nginx/sites-available/reverse-proxy
diff --git a/assets/guide_docker_docker_build.md.ddbb905f.js b/assets/guide_docker_docker_build.md.42a051cd.js
similarity index 99%
rename from assets/guide_docker_docker_build.md.ddbb905f.js
rename to assets/guide_docker_docker_build.md.42a051cd.js
index eab72adb54..5f8e1556c6 100644
--- a/assets/guide_docker_docker_build.md.ddbb905f.js
+++ b/assets/guide_docker_docker_build.md.42a051cd.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_build.md","filePath":"guide/docker/docker_build.md","lastUpdated":1747726389000}'),o={name:"guide/docker/docker_build.md"},p=l(`
前言 ​
两种开设方式
单独开设 ​
  • 只生成一个docker，这里有判断为国际服务器还是国内服务器，如果在国内服务器上开设，容器内的包管理源自动替换为清华源
  • 可配置绑定独立的IPV6地址，但需要先前使用本套脚本的环境安装命令安装的docker，且需要宿主机至少绑定了/112的IPV6子网
  • 支持x86_64和ARM架构的服务器
下载脚本 ​
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
示例 ​
运行支持的变量
./onedocker.sh name cpu memory password sshport startport endport <independent_ipv6> <system>
目前system仅支持选择
  • alpine
  • debian
  • ubuntu
  • almalinux
默认不填则是debian
shell
./onedocker.sh test 1 512 123456 25000 34975 35000 N debian
以下为开设的示例容器的信息：
属性值
容器名字test
SSH登录的用户名root
SSH登录的密码123456
CPU核数1
内存大小512MB
SSH端口25000
内外网映射端口一致的区间34975到35000
系统debian
是否绑定独立的IPV6地址N
相关操作 ​
删除示例
shell
docker rm -f test
+import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_build.md","filePath":"guide/docker/docker_build.md","lastUpdated":1747730955000}'),o={name:"guide/docker/docker_build.md"},p=l(`
前言 ​
两种开设方式
单独开设 ​
  • 只生成一个docker，这里有判断为国际服务器还是国内服务器，如果在国内服务器上开设，容器内的包管理源自动替换为清华源
  • 可配置绑定独立的IPV6地址，但需要先前使用本套脚本的环境安装命令安装的docker，且需要宿主机至少绑定了/112的IPV6子网
  • 支持x86_64和ARM架构的服务器
下载脚本 ​
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
示例 ​
运行支持的变量
./onedocker.sh name cpu memory password sshport startport endport <independent_ipv6> <system>
目前system仅支持选择
  • alpine
  • debian
  • ubuntu
  • almalinux
默认不填则是debian
shell
./onedocker.sh test 1 512 123456 25000 34975 35000 N debian
以下为开设的示例容器的信息：
属性值
容器名字test
SSH登录的用户名root
SSH登录的密码123456
CPU核数1
内存大小512MB
SSH端口25000
内外网映射端口一致的区间34975到35000
系统debian
是否绑定独立的IPV6地址N
相关操作 ​
删除示例
shell
docker rm -f test
 rm -rf test
 ls
进入示例
shell
docker exec -it test /bin/bash
要退出容器就执行exit退出。
查询已开设的信息
shell
cat 容器名字
输出格式
容器名字 SSH端口 登陆的root密码 核数 内存 外网端口起 外网端口止
docker的ipv6地址只能在容器内自己查询，在docker的配置中是不存在的
批量开设 ​
  • 批量多次运行继承配置生成
  • 生成多个时为避免SSH连接中断建议在screen中执行
  • 支持x86_64和ARM架构的服务器
运行 ​
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/create_docker.sh -o create_docker.sh && chmod +x create_docker.sh && bash create_docker.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
查询批量开设的信息 ​
shell
cat dclog
输出格式
容器名字 SSH端口 登陆的root密码 核数 内存 外网端口起 外网端口止
一行一个容器对应的信息，docker的ipv6地址只能在容器内自己查询，在docker的配置中是不存在的
卸载所有docker容器和镜像 ​
以下命令卸载会忽略ndpresponder，以防止IPV6的配置失效
shell
docker ps -aq --format '{{.Names}}' | grep -E '^ndpresponder' | xargs -r docker rm -f
 docker images -aq --format '{{.Repository}}:{{.Tag}}' | grep -E '^ndpresponder' | xargs -r docker rmi
diff --git a/assets/guide_docker_docker_build.md.ddbb905f.lean.js b/assets/guide_docker_docker_build.md.42a051cd.lean.js
similarity index 99%
rename from assets/guide_docker_docker_build.md.ddbb905f.lean.js
rename to assets/guide_docker_docker_build.md.42a051cd.lean.js
index eab72adb54..5f8e1556c6 100644
--- a/assets/guide_docker_docker_build.md.ddbb905f.lean.js
+++ b/assets/guide_docker_docker_build.md.42a051cd.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_build.md","filePath":"guide/docker/docker_build.md","lastUpdated":1747726389000}'),o={name:"guide/docker/docker_build.md"},p=l(`
前言 ​
两种开设方式
单独开设 ​
  • 只生成一个docker，这里有判断为国际服务器还是国内服务器，如果在国内服务器上开设，容器内的包管理源自动替换为清华源
  • 可配置绑定独立的IPV6地址，但需要先前使用本套脚本的环境安装命令安装的docker，且需要宿主机至少绑定了/112的IPV6子网
  • 支持x86_64和ARM架构的服务器
下载脚本 ​
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
示例 ​
运行支持的变量
./onedocker.sh name cpu memory password sshport startport endport <independent_ipv6> <system>
目前system仅支持选择
  • alpine
  • debian
  • ubuntu
  • almalinux
默认不填则是debian
shell
./onedocker.sh test 1 512 123456 25000 34975 35000 N debian
以下为开设的示例容器的信息：
属性值
容器名字test
SSH登录的用户名root
SSH登录的密码123456
CPU核数1
内存大小512MB
SSH端口25000
内外网映射端口一致的区间34975到35000
系统debian
是否绑定独立的IPV6地址N
相关操作 ​
删除示例
shell
docker rm -f test
+import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_build.md","filePath":"guide/docker/docker_build.md","lastUpdated":1747730955000}'),o={name:"guide/docker/docker_build.md"},p=l(`
前言 ​
两种开设方式
单独开设 ​
  • 只生成一个docker，这里有判断为国际服务器还是国内服务器，如果在国内服务器上开设，容器内的包管理源自动替换为清华源
  • 可配置绑定独立的IPV6地址，但需要先前使用本套脚本的环境安装命令安装的docker，且需要宿主机至少绑定了/112的IPV6子网
  • 支持x86_64和ARM架构的服务器
下载脚本 ​
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
示例 ​
运行支持的变量
./onedocker.sh name cpu memory password sshport startport endport <independent_ipv6> <system>
目前system仅支持选择
  • alpine
  • debian
  • ubuntu
  • almalinux
默认不填则是debian
shell
./onedocker.sh test 1 512 123456 25000 34975 35000 N debian
以下为开设的示例容器的信息：
属性值
容器名字test
SSH登录的用户名root
SSH登录的密码123456
CPU核数1
内存大小512MB
SSH端口25000
内外网映射端口一致的区间34975到35000
系统debian
是否绑定独立的IPV6地址N
相关操作 ​
删除示例
shell
docker rm -f test
 rm -rf test
 ls
进入示例
shell
docker exec -it test /bin/bash
要退出容器就执行exit退出。
查询已开设的信息
shell
cat 容器名字
输出格式
容器名字 SSH端口 登陆的root密码 核数 内存 外网端口起 外网端口止
docker的ipv6地址只能在容器内自己查询，在docker的配置中是不存在的
批量开设 ​
  • 批量多次运行继承配置生成
  • 生成多个时为避免SSH连接中断建议在screen中执行
  • 支持x86_64和ARM架构的服务器
运行 ​
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/create_docker.sh -o create_docker.sh && chmod +x create_docker.sh && bash create_docker.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
查询批量开设的信息 ​
shell
cat dclog
输出格式
容器名字 SSH端口 登陆的root密码 核数 内存 外网端口起 外网端口止
一行一个容器对应的信息，docker的ipv6地址只能在容器内自己查询，在docker的配置中是不存在的
卸载所有docker容器和镜像 ​
以下命令卸载会忽略ndpresponder，以防止IPV6的配置失效
shell
docker ps -aq --format '{{.Names}}' | grep -E '^ndpresponder' | xargs -r docker rm -f
 docker images -aq --format '{{.Repository}}:{{.Tag}}' | grep -E '^ndpresponder' | xargs -r docker rmi
diff --git a/assets/guide_docker_docker_custom.md.0a00ad78.js b/assets/guide_docker_docker_custom.md.ff937d60.js
similarity index 99%
rename from assets/guide_docker_docker_custom.md.0a00ad78.js
rename to assets/guide_docker_docker_custom.md.ff937d60.js
index 8ddfcd7c9d..df5affdd67 100644
--- a/assets/guide_docker_docker_custom.md.0a00ad78.js
+++ b/assets/guide_docker_docker_custom.md.ff937d60.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as o}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"使用Docker一键安装某些容器的脚本","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_custom.md","filePath":"guide/docker/docker_custom.md","lastUpdated":1747726389000}'),p={name:"guide/docker/docker_custom.md"},n=o(`
使用Docker一键安装某些容器的脚本 ​
每个容器都有对应的配置要求，自行查看，内存不够的用https://github.com/spiritLHLS/addswap的
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
开设虚拟内存补足也行
注意，以下脚本使用前务必使用本套教程中的环境安装脚本进行前期环境安装
一键开设Firefox浏览器的容器 ​
  • 已设置崩溃自启
  • 已设置带中文字体
  • 自带web的校验，可自设置密码
  • 可自定义容器最大的内存占用
  • 可选是否开启VNC端口，默认不开启
  • 无需考虑是否支持嵌套虚拟化和服务器的架构
  • 不支持声音映射，无论是WEB端还是VNC端都无法传输声音
宿主机需要至少1核2G内存5G硬盘，开设的容器大小将占用起码1G硬盘
开设
如果未设置自定义密码，开设后默认的密码是oneclick。
默认的web端口是3003，开设后打开本机IPV4:端口即可
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onefirefox.sh -o onefirefox.sh && chmod +x onefirefox.sh && bash onefirefox.sh
删除
修改以下端口号3003为你实际的端口号，然后执行命令回车两次即可删除容器、配置文件、对应镜像
shell
PORT="3003"
+import{_ as s,v as a,b as l,R as o}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"使用Docker一键安装某些容器的脚本","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_custom.md","filePath":"guide/docker/docker_custom.md","lastUpdated":1747730955000}'),p={name:"guide/docker/docker_custom.md"},n=o(`
使用Docker一键安装某些容器的脚本 ​
每个容器都有对应的配置要求，自行查看，内存不够的用https://github.com/spiritLHLS/addswap的
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
开设虚拟内存补足也行
注意，以下脚本使用前务必使用本套教程中的环境安装脚本进行前期环境安装
一键开设Firefox浏览器的容器 ​
  • 已设置崩溃自启
  • 已设置带中文字体
  • 自带web的校验，可自设置密码
  • 可自定义容器最大的内存占用
  • 可选是否开启VNC端口，默认不开启
  • 无需考虑是否支持嵌套虚拟化和服务器的架构
  • 不支持声音映射，无论是WEB端还是VNC端都无法传输声音
宿主机需要至少1核2G内存5G硬盘，开设的容器大小将占用起码1G硬盘
开设
如果未设置自定义密码，开设后默认的密码是oneclick。
默认的web端口是3003，开设后打开本机IPV4:端口即可
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onefirefox.sh -o onefirefox.sh && chmod +x onefirefox.sh && bash onefirefox.sh
删除
修改以下端口号3003为你实际的端口号，然后执行命令回车两次即可删除容器、配置文件、对应镜像
shell
PORT="3003"
 docker stop firefox_\${PORT}
 docker rm -f firefox_\${PORT}
 rm -rf /usr/local/bin/firefox_\${PORT}
diff --git a/assets/guide_docker_docker_custom.md.0a00ad78.lean.js b/assets/guide_docker_docker_custom.md.ff937d60.lean.js
similarity index 99%
rename from assets/guide_docker_docker_custom.md.0a00ad78.lean.js
rename to assets/guide_docker_docker_custom.md.ff937d60.lean.js
index 8ddfcd7c9d..df5affdd67 100644
--- a/assets/guide_docker_docker_custom.md.0a00ad78.lean.js
+++ b/assets/guide_docker_docker_custom.md.ff937d60.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as o}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"使用Docker一键安装某些容器的脚本","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_custom.md","filePath":"guide/docker/docker_custom.md","lastUpdated":1747726389000}'),p={name:"guide/docker/docker_custom.md"},n=o(`
使用Docker一键安装某些容器的脚本 ​
每个容器都有对应的配置要求，自行查看，内存不够的用https://github.com/spiritLHLS/addswap的
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
开设虚拟内存补足也行
注意，以下脚本使用前务必使用本套教程中的环境安装脚本进行前期环境安装
一键开设Firefox浏览器的容器 ​
  • 已设置崩溃自启
  • 已设置带中文字体
  • 自带web的校验，可自设置密码
  • 可自定义容器最大的内存占用
  • 可选是否开启VNC端口，默认不开启
  • 无需考虑是否支持嵌套虚拟化和服务器的架构
  • 不支持声音映射，无论是WEB端还是VNC端都无法传输声音
宿主机需要至少1核2G内存5G硬盘，开设的容器大小将占用起码1G硬盘
开设
如果未设置自定义密码，开设后默认的密码是oneclick。
默认的web端口是3003，开设后打开本机IPV4:端口即可
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onefirefox.sh -o onefirefox.sh && chmod +x onefirefox.sh && bash onefirefox.sh
删除
修改以下端口号3003为你实际的端口号，然后执行命令回车两次即可删除容器、配置文件、对应镜像
shell
PORT="3003"
+import{_ as s,v as a,b as l,R as o}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"使用Docker一键安装某些容器的脚本","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_custom.md","filePath":"guide/docker/docker_custom.md","lastUpdated":1747730955000}'),p={name:"guide/docker/docker_custom.md"},n=o(`
使用Docker一键安装某些容器的脚本 ​
每个容器都有对应的配置要求，自行查看，内存不够的用https://github.com/spiritLHLS/addswap的
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
开设虚拟内存补足也行
注意，以下脚本使用前务必使用本套教程中的环境安装脚本进行前期环境安装
一键开设Firefox浏览器的容器 ​
  • 已设置崩溃自启
  • 已设置带中文字体
  • 自带web的校验，可自设置密码
  • 可自定义容器最大的内存占用
  • 可选是否开启VNC端口，默认不开启
  • 无需考虑是否支持嵌套虚拟化和服务器的架构
  • 不支持声音映射，无论是WEB端还是VNC端都无法传输声音
宿主机需要至少1核2G内存5G硬盘，开设的容器大小将占用起码1G硬盘
开设
如果未设置自定义密码，开设后默认的密码是oneclick。
默认的web端口是3003，开设后打开本机IPV4:端口即可
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onefirefox.sh -o onefirefox.sh && chmod +x onefirefox.sh && bash onefirefox.sh
删除
修改以下端口号3003为你实际的端口号，然后执行命令回车两次即可删除容器、配置文件、对应镜像
shell
PORT="3003"
 docker stop firefox_\${PORT}
 docker rm -f firefox_\${PORT}
 rm -rf /usr/local/bin/firefox_\${PORT}
diff --git a/assets/guide_docker_docker_install.md.fceac313.js b/assets/guide_docker_docker_install.md.2fea9650.js
similarity index 99%
rename from assets/guide_docker_docker_install.md.fceac313.js
rename to assets/guide_docker_docker_install.md.2fea9650.js
index f14c48f3c1..c7b1ee5020 100644
--- a/assets/guide_docker_docker_install.md.fceac313.js
+++ b/assets/guide_docker_docker_install.md.2fea9650.js
@@ -1 +1 @@
-import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_install.md","filePath":"guide/docker/docker_install.md","lastUpdated":1747726389000}'),o={name:"guide/docker/docker_install.md"},n=p('
前言 ​
支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
开设虚拟内存 ​
TIP
内存开点swap免得机器炸了
单位换算：输入 1024 产生 1G SWAP-虚拟内存，虚拟内存占用硬盘空间，当实际内存不够用时将自动使用虚拟内存做内存使用，但随之带来IO高占用以及CPU性能占用
建议只开实际内存大小两倍大小的虚拟内存
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
环境预设 ​
  • 检测系统环境，安装对应组件
  • 安装docker和docker-compose，这里有判断为国际服务器还是国内服务器，自动安装对应源的docker
  • 下载默认需要的一些配置脚本
  • 检测如果存在IPV6地址，检测其是否大于或等于/112，如果符合条件，则配置docker的ipv6的网络
  • 如果上述条件都符合，创建ndpresponder的docker和radvd，使得IPV6的分配支持ndp广播和自动分配
  • 支持x86_64和ARM架构的服务器
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
或
bash dockerinstall.sh
TIP
环境安装过程中可能要求你重启服务器后再次执行脚本，详见脚本运行后的说明
',20),e=[n];function t(c,r,C,i,d,y){return a(),l("div",null,e)}const h=s(o,[["render",t]]);export{D as __pageData,h as default};
+import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_install.md","filePath":"guide/docker/docker_install.md","lastUpdated":1747730955000}'),o={name:"guide/docker/docker_install.md"},n=p('
前言 ​
支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
开设虚拟内存 ​
TIP
内存开点swap免得机器炸了
单位换算：输入 1024 产生 1G SWAP-虚拟内存，虚拟内存占用硬盘空间，当实际内存不够用时将自动使用虚拟内存做内存使用，但随之带来IO高占用以及CPU性能占用
建议只开实际内存大小两倍大小的虚拟内存
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
环境预设 ​
  • 检测系统环境，安装对应组件
  • 安装docker和docker-compose，这里有判断为国际服务器还是国内服务器，自动安装对应源的docker
  • 下载默认需要的一些配置脚本
  • 检测如果存在IPV6地址，检测其是否大于或等于/112，如果符合条件，则配置docker的ipv6的网络
  • 如果上述条件都符合，创建ndpresponder的docker和radvd，使得IPV6的分配支持ndp广播和自动分配
  • 支持x86_64和ARM架构的服务器
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
或
bash dockerinstall.sh
TIP
环境安装过程中可能要求你重启服务器后再次执行脚本，详见脚本运行后的说明
',20),e=[n];function t(c,r,C,i,d,y){return a(),l("div",null,e)}const h=s(o,[["render",t]]);export{D as __pageData,h as default};
diff --git a/assets/guide_docker_docker_install.md.fceac313.lean.js b/assets/guide_docker_docker_install.md.2fea9650.lean.js
similarity index 99%
rename from assets/guide_docker_docker_install.md.fceac313.lean.js
rename to assets/guide_docker_docker_install.md.2fea9650.lean.js
index f14c48f3c1..c7b1ee5020 100644
--- a/assets/guide_docker_docker_install.md.fceac313.lean.js
+++ b/assets/guide_docker_docker_install.md.2fea9650.lean.js
@@ -1 +1 @@
-import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_install.md","filePath":"guide/docker/docker_install.md","lastUpdated":1747726389000}'),o={name:"guide/docker/docker_install.md"},n=p('
前言 ​
支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
开设虚拟内存 ​
TIP
内存开点swap免得机器炸了
单位换算：输入 1024 产生 1G SWAP-虚拟内存，虚拟内存占用硬盘空间，当实际内存不够用时将自动使用虚拟内存做内存使用，但随之带来IO高占用以及CPU性能占用
建议只开实际内存大小两倍大小的虚拟内存
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
环境预设 ​
  • 检测系统环境，安装对应组件
  • 安装docker和docker-compose，这里有判断为国际服务器还是国内服务器，自动安装对应源的docker
  • 下载默认需要的一些配置脚本
  • 检测如果存在IPV6地址，检测其是否大于或等于/112，如果符合条件，则配置docker的ipv6的网络
  • 如果上述条件都符合，创建ndpresponder的docker和radvd，使得IPV6的分配支持ndp广播和自动分配
  • 支持x86_64和ARM架构的服务器
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
或
bash dockerinstall.sh
TIP
环境安装过程中可能要求你重启服务器后再次执行脚本，详见脚本运行后的说明
',20),e=[n];function t(c,r,C,i,d,y){return a(),l("div",null,e)}const h=s(o,[["render",t]]);export{D as __pageData,h as default};
+import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_install.md","filePath":"guide/docker/docker_install.md","lastUpdated":1747730955000}'),o={name:"guide/docker/docker_install.md"},n=p('
前言 ​
支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
开设虚拟内存 ​
TIP
内存开点swap免得机器炸了
单位换算：输入 1024 产生 1G SWAP-虚拟内存，虚拟内存占用硬盘空间，当实际内存不够用时将自动使用虚拟内存做内存使用，但随之带来IO高占用以及CPU性能占用
建议只开实际内存大小两倍大小的虚拟内存
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
环境预设 ​
  • 检测系统环境，安装对应组件
  • 安装docker和docker-compose，这里有判断为国际服务器还是国内服务器，自动安装对应源的docker
  • 下载默认需要的一些配置脚本
  • 检测如果存在IPV6地址，检测其是否大于或等于/112，如果符合条件，则配置docker的ipv6的网络
  • 如果上述条件都符合，创建ndpresponder的docker和radvd，使得IPV6的分配支持ndp广播和自动分配
  • 支持x86_64和ARM架构的服务器
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
或
bash dockerinstall.sh
TIP
环境安装过程中可能要求你重启服务器后再次执行脚本，详见脚本运行后的说明
',20),e=[n];function t(c,r,C,i,d,y){return a(),l("div",null,e)}const h=s(o,[["render",t]]);export{D as __pageData,h as default};
diff --git a/assets/guide_docker_docker_macos.md.27299bbe.js b/assets/guide_docker_docker_macos.md.317f7a9d.js
similarity index 95%
rename from assets/guide_docker_docker_macos.md.27299bbe.js
rename to assets/guide_docker_docker_macos.md.317f7a9d.js
index 0b83492437..ed9185b643 100644
--- a/assets/guide_docker_docker_macos.md.27299bbe.js
+++ b/assets/guide_docker_docker_macos.md.317f7a9d.js
@@ -1 +1 @@
-import{_ as e,v as a,b as o,R as r}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"在Docker中开设Macos虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_macos.md","filePath":"guide/docker/docker_macos.md","lastUpdated":1747726389000}'),c={name:"guide/docker/docker_macos.md"},t=r('
在Docker中开设Macos虚拟机 ​
通过dockur开设 ​
原始项目
https://github.com/dockur/macos
通过OSX开设 ​
原始项目
https://github.com/sickcodes/Docker-OSX
',7),s=[t];function d(i,h,n,k,u,l){return a(),o("div",null,s)}const _=e(c,[["render",d]]);export{m as __pageData,_ as default};
+import{_ as e,v as a,b as o,R as r}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"在Docker中开设Macos虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_macos.md","filePath":"guide/docker/docker_macos.md","lastUpdated":1747730955000}'),c={name:"guide/docker/docker_macos.md"},t=r('
在Docker中开设Macos虚拟机 ​
通过dockur开设 ​
原始项目
https://github.com/dockur/macos
通过OSX开设 ​
原始项目
https://github.com/sickcodes/Docker-OSX
',7),s=[t];function d(i,h,n,k,u,l){return a(),o("div",null,s)}const _=e(c,[["render",d]]);export{m as __pageData,_ as default};
diff --git a/assets/guide_docker_docker_macos.md.27299bbe.lean.js b/assets/guide_docker_docker_macos.md.317f7a9d.lean.js
similarity index 95%
rename from assets/guide_docker_docker_macos.md.27299bbe.lean.js
rename to assets/guide_docker_docker_macos.md.317f7a9d.lean.js
index 0b83492437..ed9185b643 100644
--- a/assets/guide_docker_docker_macos.md.27299bbe.lean.js
+++ b/assets/guide_docker_docker_macos.md.317f7a9d.lean.js
@@ -1 +1 @@
-import{_ as e,v as a,b as o,R as r}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"在Docker中开设Macos虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_macos.md","filePath":"guide/docker/docker_macos.md","lastUpdated":1747726389000}'),c={name:"guide/docker/docker_macos.md"},t=r('
在Docker中开设Macos虚拟机 ​
通过dockur开设 ​
原始项目
https://github.com/dockur/macos
通过OSX开设 ​
原始项目
https://github.com/sickcodes/Docker-OSX
',7),s=[t];function d(i,h,n,k,u,l){return a(),o("div",null,s)}const _=e(c,[["render",d]]);export{m as __pageData,_ as default};
+import{_ as e,v as a,b as o,R as r}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"在Docker中开设Macos虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_macos.md","filePath":"guide/docker/docker_macos.md","lastUpdated":1747730955000}'),c={name:"guide/docker/docker_macos.md"},t=r('
在Docker中开设Macos虚拟机 ​
通过dockur开设 ​
原始项目
https://github.com/dockur/macos
通过OSX开设 ​
原始项目
https://github.com/sickcodes/Docker-OSX
',7),s=[t];function d(i,h,n,k,u,l){return a(),o("div",null,s)}const _=e(c,[["render",d]]);export{m as __pageData,_ as default};
diff --git a/assets/guide_docker_docker_precheck.md.db800b72.js b/assets/guide_docker_docker_precheck.md.fe9630c3.js
similarity index 98%
rename from assets/guide_docker_docker_precheck.md.db800b72.js
rename to assets/guide_docker_docker_precheck.md.fe9630c3.js
index 08924358c3..ccb547a9d7 100644
--- a/assets/guide_docker_docker_precheck.md.db800b72.js
+++ b/assets/guide_docker_docker_precheck.md.fe9630c3.js
@@ -1 +1 @@
-import{_ as e,v as r,b as o,R as a}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_precheck.md","filePath":"guide/docker/docker_precheck.md","lastUpdated":1747726389000}'),t={name:"guide/docker/docker_precheck.md"},c=a('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
WARNING
如果宿主机带IPV6网络的话，安装会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/docker
项目特点 ​
通过docker批量或单独开设NAT服务器(Bulk or individual NAT server provisioning via docker)
默认使用debian系统可选alpine系统，每个容器自带1个外网ssh端口，25个内外网一致端口，可选择是否绑定IPV6地址
默认创建的是非特权容器，且不挂载与宿主机的docker的守护进程之间的通信，所以宿主机创建的docker虚拟化的NAT服务器内无法再嵌套虚拟化docker
默认安装并启用lxcfs，使得在容器内的查询资源时CPU和内存使用的是配置的视图而不是宿主机的视图
由于大部分云服务器是ext4文件系统，docker默认的存储引擎是overlayfs2，即便宿主机的文件系统是xfs，默认也不会启用pquota选项，所以默认共享宿主机硬盘，无法限制每个容器的磁盘大小
配置要求 ​
系统可安装docker即可用，网络能连接Github的raw界面就能用，硬件配置只要不拉跨就行，空闲硬盘有3G就行
(如果需要绑定IPV6地址，那么请保证使用本套脚本的环境预设脚本进行环境安装，需要它自动预设部分设置)
如果硬件资源只是好了一点，需要限制更多东西并需要限制硬盘大小，可使用LXD分区的脚本批量开LXC虚拟化的容器
如果硬件非常好资源很多，可使用PVE分区的脚本批量开KVM虚拟化的虚拟机
推荐在开设NAT服务器前先增加部分SWAP虚拟内存，避免突发的内存占用导致宿主机卡死
',17),d=[c];function p(s,i,n,l,h,k){return r(),o("div",null,d)}const f=e(t,[["render",p]]);export{_ as __pageData,f as default};
+import{_ as e,v as r,b as o,R as a}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_precheck.md","filePath":"guide/docker/docker_precheck.md","lastUpdated":1747730955000}'),t={name:"guide/docker/docker_precheck.md"},c=a('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
WARNING
如果宿主机带IPV6网络的话，安装会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/docker
项目特点 ​
通过docker批量或单独开设NAT服务器(Bulk or individual NAT server provisioning via docker)
默认使用debian系统可选alpine系统，每个容器自带1个外网ssh端口，25个内外网一致端口，可选择是否绑定IPV6地址
默认创建的是非特权容器，且不挂载与宿主机的docker的守护进程之间的通信，所以宿主机创建的docker虚拟化的NAT服务器内无法再嵌套虚拟化docker
默认安装并启用lxcfs，使得在容器内的查询资源时CPU和内存使用的是配置的视图而不是宿主机的视图
由于大部分云服务器是ext4文件系统，docker默认的存储引擎是overlayfs2，即便宿主机的文件系统是xfs，默认也不会启用pquota选项，所以默认共享宿主机硬盘，无法限制每个容器的磁盘大小
配置要求 ​
系统可安装docker即可用，网络能连接Github的raw界面就能用，硬件配置只要不拉跨就行，空闲硬盘有3G就行
(如果需要绑定IPV6地址，那么请保证使用本套脚本的环境预设脚本进行环境安装，需要它自动预设部分设置)
如果硬件资源只是好了一点，需要限制更多东西并需要限制硬盘大小，可使用LXD分区的脚本批量开LXC虚拟化的容器
如果硬件非常好资源很多，可使用PVE分区的脚本批量开KVM虚拟化的虚拟机
推荐在开设NAT服务器前先增加部分SWAP虚拟内存，避免突发的内存占用导致宿主机卡死
',17),d=[c];function p(s,i,n,l,h,k){return r(),o("div",null,d)}const f=e(t,[["render",p]]);export{_ as __pageData,f as default};
diff --git a/assets/guide_docker_docker_precheck.md.db800b72.lean.js b/assets/guide_docker_docker_precheck.md.fe9630c3.lean.js
similarity index 98%
rename from assets/guide_docker_docker_precheck.md.db800b72.lean.js
rename to assets/guide_docker_docker_precheck.md.fe9630c3.lean.js
index 08924358c3..ccb547a9d7 100644
--- a/assets/guide_docker_docker_precheck.md.db800b72.lean.js
+++ b/assets/guide_docker_docker_precheck.md.fe9630c3.lean.js
@@ -1 +1 @@
-import{_ as e,v as r,b as o,R as a}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_precheck.md","filePath":"guide/docker/docker_precheck.md","lastUpdated":1747726389000}'),t={name:"guide/docker/docker_precheck.md"},c=a('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
WARNING
如果宿主机带IPV6网络的话，安装会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/docker
项目特点 ​
通过docker批量或单独开设NAT服务器(Bulk or individual NAT server provisioning via docker)
默认使用debian系统可选alpine系统，每个容器自带1个外网ssh端口，25个内外网一致端口，可选择是否绑定IPV6地址
默认创建的是非特权容器，且不挂载与宿主机的docker的守护进程之间的通信，所以宿主机创建的docker虚拟化的NAT服务器内无法再嵌套虚拟化docker
默认安装并启用lxcfs，使得在容器内的查询资源时CPU和内存使用的是配置的视图而不是宿主机的视图
由于大部分云服务器是ext4文件系统，docker默认的存储引擎是overlayfs2，即便宿主机的文件系统是xfs，默认也不会启用pquota选项，所以默认共享宿主机硬盘，无法限制每个容器的磁盘大小
配置要求 ​
系统可安装docker即可用，网络能连接Github的raw界面就能用，硬件配置只要不拉跨就行，空闲硬盘有3G就行
(如果需要绑定IPV6地址，那么请保证使用本套脚本的环境预设脚本进行环境安装，需要它自动预设部分设置)
如果硬件资源只是好了一点，需要限制更多东西并需要限制硬盘大小，可使用LXD分区的脚本批量开LXC虚拟化的容器
如果硬件非常好资源很多，可使用PVE分区的脚本批量开KVM虚拟化的虚拟机
推荐在开设NAT服务器前先增加部分SWAP虚拟内存，避免突发的内存占用导致宿主机卡死
',17),d=[c];function p(s,i,n,l,h,k){return r(),o("div",null,d)}const f=e(t,[["render",p]]);export{_ as __pageData,f as default};
+import{_ as e,v as r,b as o,R as a}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_precheck.md","filePath":"guide/docker/docker_precheck.md","lastUpdated":1747730955000}'),t={name:"guide/docker/docker_precheck.md"},c=a('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
WARNING
如果宿主机带IPV6网络的话，安装会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/docker
项目特点 ​
通过docker批量或单独开设NAT服务器(Bulk or individual NAT server provisioning via docker)
默认使用debian系统可选alpine系统，每个容器自带1个外网ssh端口，25个内外网一致端口，可选择是否绑定IPV6地址
默认创建的是非特权容器，且不挂载与宿主机的docker的守护进程之间的通信，所以宿主机创建的docker虚拟化的NAT服务器内无法再嵌套虚拟化docker
默认安装并启用lxcfs，使得在容器内的查询资源时CPU和内存使用的是配置的视图而不是宿主机的视图
由于大部分云服务器是ext4文件系统，docker默认的存储引擎是overlayfs2，即便宿主机的文件系统是xfs，默认也不会启用pquota选项，所以默认共享宿主机硬盘，无法限制每个容器的磁盘大小
配置要求 ​
系统可安装docker即可用，网络能连接Github的raw界面就能用，硬件配置只要不拉跨就行，空闲硬盘有3G就行
(如果需要绑定IPV6地址，那么请保证使用本套脚本的环境预设脚本进行环境安装，需要它自动预设部分设置)
如果硬件资源只是好了一点，需要限制更多东西并需要限制硬盘大小，可使用LXD分区的脚本批量开LXC虚拟化的容器
如果硬件非常好资源很多，可使用PVE分区的脚本批量开KVM虚拟化的虚拟机
推荐在开设NAT服务器前先增加部分SWAP虚拟内存，避免突发的内存占用导致宿主机卡死
',17),d=[c];function p(s,i,n,l,h,k){return r(),o("div",null,d)}const f=e(t,[["render",p]]);export{_ as __pageData,f as default};
diff --git a/assets/guide_docker_docker_qa.md.d9111f4e.js b/assets/guide_docker_docker_qa.md.e107175a.js
similarity index 98%
rename from assets/guide_docker_docker_qa.md.d9111f4e.js
rename to assets/guide_docker_docker_qa.md.e107175a.js
index f2f247ec08..75689f091d 100644
--- a/assets/guide_docker_docker_qa.md.d9111f4e.js
+++ b/assets/guide_docker_docker_qa.md.e107175a.js
@@ -1 +1 @@
-import{_ as a,v as s,b as e,R as l}from"./chunks/framework.70afa331.js";const k=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_qa.md","filePath":"guide/docker/docker_qa.md","lastUpdated":1747726389000}'),n={name:"guide/docker/docker_qa.md"},p=l('
解惑 ​
常见的一些docker命令 ​
查询某个容器的实时占用
docker stats 容器名字
进入某个容器
docker exec -it 容器名字 /bin/bash
清理 Docker 缓存，清理未使用的资源，包括镜像、容器、网络等
docker system prune -a
卸载所有docker的镜像和容器
docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)
查看对应容器日志
docker logs 容器名字或ID
查看docker整体的disk占用
docker system df
查看所有容器
docker ps -a
查看所有镜像
docker images
删除某个特定容器
docker rm -f 容器名字或ID
删除某个特定镜像
docker rmi 镜像名字或ID
',22),o=[p];function t(c,i,d,r,g,h){return s(),e("div",null,o)}const C=a(n,[["render",t]]);export{k as __pageData,C as default};
+import{_ as a,v as s,b as e,R as l}from"./chunks/framework.70afa331.js";const k=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_qa.md","filePath":"guide/docker/docker_qa.md","lastUpdated":1747730955000}'),n={name:"guide/docker/docker_qa.md"},p=l('
解惑 ​
常见的一些docker命令 ​
查询某个容器的实时占用
docker stats 容器名字
进入某个容器
docker exec -it 容器名字 /bin/bash
清理 Docker 缓存，清理未使用的资源，包括镜像、容器、网络等
docker system prune -a
卸载所有docker的镜像和容器
docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)
查看对应容器日志
docker logs 容器名字或ID
查看docker整体的disk占用
docker system df
查看所有容器
docker ps -a
查看所有镜像
docker images
删除某个特定容器
docker rm -f 容器名字或ID
删除某个特定镜像
docker rmi 镜像名字或ID
',22),o=[p];function t(c,i,d,r,g,h){return s(),e("div",null,o)}const C=a(n,[["render",t]]);export{k as __pageData,C as default};
diff --git a/assets/guide_docker_docker_qa.md.d9111f4e.lean.js b/assets/guide_docker_docker_qa.md.e107175a.lean.js
similarity index 98%
rename from assets/guide_docker_docker_qa.md.d9111f4e.lean.js
rename to assets/guide_docker_docker_qa.md.e107175a.lean.js
index f2f247ec08..75689f091d 100644
--- a/assets/guide_docker_docker_qa.md.d9111f4e.lean.js
+++ b/assets/guide_docker_docker_qa.md.e107175a.lean.js
@@ -1 +1 @@
-import{_ as a,v as s,b as e,R as l}from"./chunks/framework.70afa331.js";const k=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_qa.md","filePath":"guide/docker/docker_qa.md","lastUpdated":1747726389000}'),n={name:"guide/docker/docker_qa.md"},p=l('
解惑 ​
常见的一些docker命令 ​
查询某个容器的实时占用
docker stats 容器名字
进入某个容器
docker exec -it 容器名字 /bin/bash
清理 Docker 缓存，清理未使用的资源，包括镜像、容器、网络等
docker system prune -a
卸载所有docker的镜像和容器
docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)
查看对应容器日志
docker logs 容器名字或ID
查看docker整体的disk占用
docker system df
查看所有容器
docker ps -a
查看所有镜像
docker images
删除某个特定容器
docker rm -f 容器名字或ID
删除某个特定镜像
docker rmi 镜像名字或ID
',22),o=[p];function t(c,i,d,r,g,h){return s(),e("div",null,o)}const C=a(n,[["render",t]]);export{k as __pageData,C as default};
+import{_ as a,v as s,b as e,R as l}from"./chunks/framework.70afa331.js";const k=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_qa.md","filePath":"guide/docker/docker_qa.md","lastUpdated":1747730955000}'),n={name:"guide/docker/docker_qa.md"},p=l('
解惑 ​
常见的一些docker命令 ​
查询某个容器的实时占用
docker stats 容器名字
进入某个容器
docker exec -it 容器名字 /bin/bash
清理 Docker 缓存，清理未使用的资源，包括镜像、容器、网络等
docker system prune -a
卸载所有docker的镜像和容器
docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)
查看对应容器日志
docker logs 容器名字或ID
查看docker整体的disk占用
docker system df
查看所有容器
docker ps -a
查看所有镜像
docker images
删除某个特定容器
docker rm -f 容器名字或ID
删除某个特定镜像
docker rmi 镜像名字或ID
',22),o=[p];function t(c,i,d,r,g,h){return s(),e("div",null,o)}const C=a(n,[["render",t]]);export{k as __pageData,C as default};
diff --git a/assets/guide_docker_docker_thanks.md.1dfc27a0.js b/assets/guide_docker_docker_thanks.md.3f680801.js
similarity index 98%
rename from assets/guide_docker_docker_thanks.md.1dfc27a0.js
rename to assets/guide_docker_docker_thanks.md.3f680801.js
index 676fd3fb37..fb4aadd8a3 100644
--- a/assets/guide_docker_docker_thanks.md.1dfc27a0.js
+++ b/assets/guide_docker_docker_thanks.md.3f680801.js
@@ -1 +1 @@
-import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/docker/docker_thanks.md","filePath":"guide/docker/docker_thanks.md","lastUpdated":1747726389000}'),o={name:"guide/docker/docker_thanks.md"},n=a('
致谢 ​
https://hub.docker.com/_/debian
https://hub.docker.com/r/redroid/redroid
https://github.com/NetrisTV/ws-scrcpy
https://guacamole.apache.org/doc/gug/introduction.html
https://blog.imoeq.com/oracle-arm-run-android-by-docker
https://blog.imoeq.com/scrcpy-run-a-android-web-page
https://github.com/NetrisTV/ws-scrcpy
https://www.howtoforge.com/how-to-install-apache-guacamole-as-docker-container-on-ubuntu/
https://releases.hashicorp.com/vagrant/
https://github.com/hashicorp/vagrant/
https://app.vagrantup.com/peru
https://medium.com/axon-technologies/installing-a-windows-virtual-machine-in-a-linux-docker-container-c78e4c3f9ba1
https://forum.garudalinux.org/t/error-while-attempting-to-create-a-virtual-machine-with-virt-manager/18534/4
https://github.com/jlesage/docker-firefox
https://github.com/linuxserver/docker-webtop
https://github.com/rustdesk/rustdesk
https://github.com/yoursunny/ndpresponder
https://github.com/linuxserver/docker-chromium
https://github.com/SuperManito/LinuxMirrors
感谢 @Ella-Alinda 和 @CoiaPrant 提供的Docker指导
',21),h=[n];function p(c,s,i,l,u,d){return e(),t("div",null,h)}const b=r(o,[["render",p]]);export{m as __pageData,b as default};
+import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/docker/docker_thanks.md","filePath":"guide/docker/docker_thanks.md","lastUpdated":1747730955000}'),o={name:"guide/docker/docker_thanks.md"},n=a('
致谢 ​
https://hub.docker.com/_/debian
https://hub.docker.com/r/redroid/redroid
https://github.com/NetrisTV/ws-scrcpy
https://guacamole.apache.org/doc/gug/introduction.html
https://blog.imoeq.com/oracle-arm-run-android-by-docker
https://blog.imoeq.com/scrcpy-run-a-android-web-page
https://github.com/NetrisTV/ws-scrcpy
https://www.howtoforge.com/how-to-install-apache-guacamole-as-docker-container-on-ubuntu/
https://releases.hashicorp.com/vagrant/
https://github.com/hashicorp/vagrant/
https://app.vagrantup.com/peru
https://medium.com/axon-technologies/installing-a-windows-virtual-machine-in-a-linux-docker-container-c78e4c3f9ba1
https://forum.garudalinux.org/t/error-while-attempting-to-create-a-virtual-machine-with-virt-manager/18534/4
https://github.com/jlesage/docker-firefox
https://github.com/linuxserver/docker-webtop
https://github.com/rustdesk/rustdesk
https://github.com/yoursunny/ndpresponder
https://github.com/linuxserver/docker-chromium
https://github.com/SuperManito/LinuxMirrors
感谢 @Ella-Alinda 和 @CoiaPrant 提供的Docker指导
',21),h=[n];function p(c,s,i,l,u,d){return e(),t("div",null,h)}const b=r(o,[["render",p]]);export{m as __pageData,b as default};
diff --git a/assets/guide_docker_docker_thanks.md.1dfc27a0.lean.js b/assets/guide_docker_docker_thanks.md.3f680801.lean.js
similarity index 98%
rename from assets/guide_docker_docker_thanks.md.1dfc27a0.lean.js
rename to assets/guide_docker_docker_thanks.md.3f680801.lean.js
index 676fd3fb37..fb4aadd8a3 100644
--- a/assets/guide_docker_docker_thanks.md.1dfc27a0.lean.js
+++ b/assets/guide_docker_docker_thanks.md.3f680801.lean.js
@@ -1 +1 @@
-import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/docker/docker_thanks.md","filePath":"guide/docker/docker_thanks.md","lastUpdated":1747726389000}'),o={name:"guide/docker/docker_thanks.md"},n=a('
致谢 ​
https://hub.docker.com/_/debian
https://hub.docker.com/r/redroid/redroid
https://github.com/NetrisTV/ws-scrcpy
https://guacamole.apache.org/doc/gug/introduction.html
https://blog.imoeq.com/oracle-arm-run-android-by-docker
https://blog.imoeq.com/scrcpy-run-a-android-web-page
https://github.com/NetrisTV/ws-scrcpy
https://www.howtoforge.com/how-to-install-apache-guacamole-as-docker-container-on-ubuntu/
https://releases.hashicorp.com/vagrant/
https://github.com/hashicorp/vagrant/
https://app.vagrantup.com/peru
https://medium.com/axon-technologies/installing-a-windows-virtual-machine-in-a-linux-docker-container-c78e4c3f9ba1
https://forum.garudalinux.org/t/error-while-attempting-to-create-a-virtual-machine-with-virt-manager/18534/4
https://github.com/jlesage/docker-firefox
https://github.com/linuxserver/docker-webtop
https://github.com/rustdesk/rustdesk
https://github.com/yoursunny/ndpresponder
https://github.com/linuxserver/docker-chromium
https://github.com/SuperManito/LinuxMirrors
感谢 @Ella-Alinda 和 @CoiaPrant 提供的Docker指导
',21),h=[n];function p(c,s,i,l,u,d){return e(),t("div",null,h)}const b=r(o,[["render",p]]);export{m as __pageData,b as default};
+import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/docker/docker_thanks.md","filePath":"guide/docker/docker_thanks.md","lastUpdated":1747730955000}'),o={name:"guide/docker/docker_thanks.md"},n=a('
致谢 ​
https://hub.docker.com/_/debian
https://hub.docker.com/r/redroid/redroid
https://github.com/NetrisTV/ws-scrcpy
https://guacamole.apache.org/doc/gug/introduction.html
https://blog.imoeq.com/oracle-arm-run-android-by-docker
https://blog.imoeq.com/scrcpy-run-a-android-web-page
https://github.com/NetrisTV/ws-scrcpy
https://www.howtoforge.com/how-to-install-apache-guacamole-as-docker-container-on-ubuntu/
https://releases.hashicorp.com/vagrant/
https://github.com/hashicorp/vagrant/
https://app.vagrantup.com/peru
https://medium.com/axon-technologies/installing-a-windows-virtual-machine-in-a-linux-docker-container-c78e4c3f9ba1
https://forum.garudalinux.org/t/error-while-attempting-to-create-a-virtual-machine-with-virt-manager/18534/4
https://github.com/jlesage/docker-firefox
https://github.com/linuxserver/docker-webtop
https://github.com/rustdesk/rustdesk
https://github.com/yoursunny/ndpresponder
https://github.com/linuxserver/docker-chromium
https://github.com/SuperManito/LinuxMirrors
感谢 @Ella-Alinda 和 @CoiaPrant 提供的Docker指导
',21),h=[n];function p(c,s,i,l,u,d){return e(),t("div",null,h)}const b=r(o,[["render",p]]);export{m as __pageData,b as default};
diff --git a/assets/guide_docker_docker_windows.md.b1cad127.js b/assets/guide_docker_docker_windows.md.2689cc79.js
similarity index 99%
rename from assets/guide_docker_docker_windows.md.b1cad127.js
rename to assets/guide_docker_docker_windows.md.2689cc79.js
index b650dff0f2..ba14fe06bc 100644
--- a/assets/guide_docker_docker_windows.md.b1cad127.js
+++ b/assets/guide_docker_docker_windows.md.2689cc79.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"在Docker中开设Windows系统虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_windows.md","filePath":"guide/docker/docker_windows.md","lastUpdated":1747726389000}'),l={name:"guide/docker/docker_windows.md"},p=o(`
在Docker中开设Windows系统虚拟机 ​
一键开设(通过vagrant) ​
  • 共享宿主机所有资源(CPU、内存、硬盘)，基于docker所以只占用系统的大小，适合多开
  • 共享IP，做了docker的NAT映射，可选择是否映射到外网或仅内网
  • 设置的win系统默认最多占用为1核2G内存50G硬盘，实际占用看使用情况
  • 无需iptables进行NAT映射，删除容器时自动删除了端口的映射，方便维护
  • 需要考虑宿主机是否支持嵌套虚拟化，暂时只支持X86_64架构的系统
宿主机需要支持嵌套虚拟化，且暂时只支持X86_64架构的系统，否则不可开设
执行
egrep -c '(vmx|svm)' /proc/cpuinfo
结果需要大于或等于1，不能为0
然后需要先设置docker切换使用v1版cgroup启动
sed -i 's/GRUB_CMDLINE_LINUX="\\(.*\\)"/GRUB_CMDLINE_LINUX="\\1 systemd.unified_cgroup_hierarchy=0"/' /etc/default/grub
+import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"在Docker中开设Windows系统虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_windows.md","filePath":"guide/docker/docker_windows.md","lastUpdated":1747730955000}'),l={name:"guide/docker/docker_windows.md"},p=o(`
在Docker中开设Windows系统虚拟机 ​
一键开设(通过vagrant) ​
  • 共享宿主机所有资源(CPU、内存、硬盘)，基于docker所以只占用系统的大小，适合多开
  • 共享IP，做了docker的NAT映射，可选择是否映射到外网或仅内网
  • 设置的win系统默认最多占用为1核2G内存50G硬盘，实际占用看使用情况
  • 无需iptables进行NAT映射，删除容器时自动删除了端口的映射，方便维护
  • 需要考虑宿主机是否支持嵌套虚拟化，暂时只支持X86_64架构的系统
宿主机需要支持嵌套虚拟化，且暂时只支持X86_64架构的系统，否则不可开设
执行
egrep -c '(vmx|svm)' /proc/cpuinfo
结果需要大于或等于1，不能为0
然后需要先设置docker切换使用v1版cgroup启动
sed -i 's/GRUB_CMDLINE_LINUX="\\(.*\\)"/GRUB_CMDLINE_LINUX="\\1 systemd.unified_cgroup_hierarchy=0"/' /etc/default/grub
 update-grub
 ls
如果执行都无报错，执行reboot重启系统以使得设置生效
支持的镜像
使用的自建的镜像：https://hub.docker.com/r/spiritlhl/wds
镜像名字镜像大小
1020G
202217.5G
201917G
创建出的容器大小会比镜像大小大一丢丢，但不多
下载脚本
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onewindows.sh -o onewindows.sh && chmod +x onewindows.sh
使用方法
开设前务必在screen窗口中执行，避免SSH长期链接造成掉线卡死
./onewindows.sh 容器名字 系统版本 RDP的端口 是否为外网映射(留空则默认是N，可选Y)
开设前需要确认宿主机至少有镜像大小的两倍大小加10G硬盘的大小，因为docker在创建容器时得先将镜像拉到本地再创建
创建过程中，硬盘占用峰值为宿主机系统+镜像大小+容器大小
比如开设容器名字为test，占用最低的Windows 2019系统的容器，映射外网RDP端口为13389，设置为外网映射(映射到你的服务器外网IPV4地址)
./onewindows.sh test 2019 13389 Y
开设后默认的用户名是Administrator和vagrant
默认的密码是vagrant
如果你选择开设映射的外网端口，务必登录后修改对应账户的密码(两个账户都可能有，自行尝试)，否则可能被人爆破滥用
删除
需要删除对应镜像和容器，先执行docker ps -a和docker images查询镜像是spiritlhl/wds的ID，然后对应使用
docker rm -f 容器的ID
 docker rmi 镜像的ID
删除后可开设别的版本的windows容器
(在宿主机上使用Docker安装Windows系统，好像绕过了某些商家不允许DD成Win系统的TOS限制)
手动开设（通过 Dockur 项目） ​
本项目支持在宿主机不支持嵌套虚拟化的情况下，使用 QEMU 进行虚拟机创建。
原始项目地址 ​
注意事项：
  • 原始项目仅为启动器，不包含 Windows 镜像；
  • 使用时需下载镜像文件，在境内网络环境下首次启动容器需约 4 小时（含镜像下载和安装）；
  • 默认要求宿主机具备以下最低硬件资源（可通过修改脚本进行调整）：
    • CPU：至少 4 核
    • 内存：至少 4G
    • 硬盘：至少 64G
如需魔改启动脚本以减少资源占用或调整其他参数，可参考以下文章：
对于 x86_64 架构用户 ​
提供一个已魔改的启动器（单文件版本），方便自行构建 Windows 镜像。该版本将系统文件和镜像直接写入 Docker 写入层中，无需额外挂载镜像文件：
下载链接： https://github.com/oneclickvirt/docker/releases/download/amd64_builder/builder.tar
导入 Docker 镜像：
bash
docker load -i builder.tar
使用自定义 Windows ISO 镜像启动容器 ​
首先从以下地址下载 Windows ISO 镜像： https://down.idc.wiki/ISOS/Windows/
启动容器示例命令：
bash
docker run -it -d \\
diff --git a/assets/guide_docker_docker_windows.md.b1cad127.lean.js b/assets/guide_docker_docker_windows.md.2689cc79.lean.js
similarity index 99%
rename from assets/guide_docker_docker_windows.md.b1cad127.lean.js
rename to assets/guide_docker_docker_windows.md.2689cc79.lean.js
index b650dff0f2..ba14fe06bc 100644
--- a/assets/guide_docker_docker_windows.md.b1cad127.lean.js
+++ b/assets/guide_docker_docker_windows.md.2689cc79.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"在Docker中开设Windows系统虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_windows.md","filePath":"guide/docker/docker_windows.md","lastUpdated":1747726389000}'),l={name:"guide/docker/docker_windows.md"},p=o(`
在Docker中开设Windows系统虚拟机 ​
一键开设(通过vagrant) ​
  • 共享宿主机所有资源(CPU、内存、硬盘)，基于docker所以只占用系统的大小，适合多开
  • 共享IP，做了docker的NAT映射，可选择是否映射到外网或仅内网
  • 设置的win系统默认最多占用为1核2G内存50G硬盘，实际占用看使用情况
  • 无需iptables进行NAT映射，删除容器时自动删除了端口的映射，方便维护
  • 需要考虑宿主机是否支持嵌套虚拟化，暂时只支持X86_64架构的系统
宿主机需要支持嵌套虚拟化，且暂时只支持X86_64架构的系统，否则不可开设
执行
egrep -c '(vmx|svm)' /proc/cpuinfo
结果需要大于或等于1，不能为0
然后需要先设置docker切换使用v1版cgroup启动
sed -i 's/GRUB_CMDLINE_LINUX="\\(.*\\)"/GRUB_CMDLINE_LINUX="\\1 systemd.unified_cgroup_hierarchy=0"/' /etc/default/grub
+import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"在Docker中开设Windows系统虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_windows.md","filePath":"guide/docker/docker_windows.md","lastUpdated":1747730955000}'),l={name:"guide/docker/docker_windows.md"},p=o(`
在Docker中开设Windows系统虚拟机 ​
一键开设(通过vagrant) ​
  • 共享宿主机所有资源(CPU、内存、硬盘)，基于docker所以只占用系统的大小，适合多开
  • 共享IP，做了docker的NAT映射，可选择是否映射到外网或仅内网
  • 设置的win系统默认最多占用为1核2G内存50G硬盘，实际占用看使用情况
  • 无需iptables进行NAT映射，删除容器时自动删除了端口的映射，方便维护
  • 需要考虑宿主机是否支持嵌套虚拟化，暂时只支持X86_64架构的系统
宿主机需要支持嵌套虚拟化，且暂时只支持X86_64架构的系统，否则不可开设
执行
egrep -c '(vmx|svm)' /proc/cpuinfo
结果需要大于或等于1，不能为0
然后需要先设置docker切换使用v1版cgroup启动
sed -i 's/GRUB_CMDLINE_LINUX="\\(.*\\)"/GRUB_CMDLINE_LINUX="\\1 systemd.unified_cgroup_hierarchy=0"/' /etc/default/grub
 update-grub
 ls
如果执行都无报错，执行reboot重启系统以使得设置生效
支持的镜像
使用的自建的镜像：https://hub.docker.com/r/spiritlhl/wds
镜像名字镜像大小
1020G
202217.5G
201917G
创建出的容器大小会比镜像大小大一丢丢，但不多
下载脚本
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onewindows.sh -o onewindows.sh && chmod +x onewindows.sh
使用方法
开设前务必在screen窗口中执行，避免SSH长期链接造成掉线卡死
./onewindows.sh 容器名字 系统版本 RDP的端口 是否为外网映射(留空则默认是N，可选Y)
开设前需要确认宿主机至少有镜像大小的两倍大小加10G硬盘的大小，因为docker在创建容器时得先将镜像拉到本地再创建
创建过程中，硬盘占用峰值为宿主机系统+镜像大小+容器大小
比如开设容器名字为test，占用最低的Windows 2019系统的容器，映射外网RDP端口为13389，设置为外网映射(映射到你的服务器外网IPV4地址)
./onewindows.sh test 2019 13389 Y
开设后默认的用户名是Administrator和vagrant
默认的密码是vagrant
如果你选择开设映射的外网端口，务必登录后修改对应账户的密码(两个账户都可能有，自行尝试)，否则可能被人爆破滥用
删除
需要删除对应镜像和容器，先执行docker ps -a和docker images查询镜像是spiritlhl/wds的ID，然后对应使用
docker rm -f 容器的ID
 docker rmi 镜像的ID
删除后可开设别的版本的windows容器
(在宿主机上使用Docker安装Windows系统，好像绕过了某些商家不允许DD成Win系统的TOS限制)
手动开设（通过 Dockur 项目） ​
本项目支持在宿主机不支持嵌套虚拟化的情况下，使用 QEMU 进行虚拟机创建。
原始项目地址 ​
注意事项：
  • 原始项目仅为启动器，不包含 Windows 镜像；
  • 使用时需下载镜像文件，在境内网络环境下首次启动容器需约 4 小时（含镜像下载和安装）；
  • 默认要求宿主机具备以下最低硬件资源（可通过修改脚本进行调整）：
    • CPU：至少 4 核
    • 内存：至少 4G
    • 硬盘：至少 64G
如需魔改启动脚本以减少资源占用或调整其他参数，可参考以下文章：
对于 x86_64 架构用户 ​
提供一个已魔改的启动器（单文件版本），方便自行构建 Windows 镜像。该版本将系统文件和镜像直接写入 Docker 写入层中，无需额外挂载镜像文件：
下载链接： https://github.com/oneclickvirt/docker/releases/download/amd64_builder/builder.tar
导入 Docker 镜像：
bash
docker load -i builder.tar
使用自定义 Windows ISO 镜像启动容器 ​
首先从以下地址下载 Windows ISO 镜像： https://down.idc.wiki/ISOS/Windows/
启动容器示例命令：
bash
docker run -it -d \\
diff --git a/assets/guide_incus_incus_custom.md.1b194673.js b/assets/guide_incus_incus_custom.md.0507c488.js
similarity index 99%
rename from assets/guide_incus_incus_custom.md.1b194673.js
rename to assets/guide_incus_incus_custom.md.0507c488.js
index e429c67306..7292b3e007 100644
--- a/assets/guide_incus_incus_custom.md.1b194673.js
+++ b/assets/guide_incus_incus_custom.md.0507c488.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const t="/assets/lxd1.78537e30.png",l="/assets/lxd2.da10b5ec.png",p="/assets/lxd3.917f56de.png",o="/assets/lxd4.83a1a121.png",i="/assets/lxd5.4ebc1444.png",c="/assets/lxd6.572825bf.png",r="/assets/lxd7.b73982c7.png",d="/assets/lxd8.9fcc21e5.png",u="/assets/lxd9.00250a32.png",h="/assets/lxd10.a25a745c.png",C="/assets/lxd11.b83f953c.png",g="/assets/lxd12.0da335dd.png",y="/assets/lxd13.308fe0de.png",A="/assets/lxd14.8dbfdcd6.png",m="/assets/lxd15.70114933.png",b="/assets/lxd16.a595fa36.png",v="/assets/lxd17.d7ea65d8.png",f="/assets/lxd18.d6225daa.png",k="/assets/lxd19.69674669.png",D="/assets/lxd20.179fc6e1.png",P="/assets/lxd21.48123d6a.png",_="/assets/lxd22.4386597e.png",w="/assets/lxd23.c26427e3.png",U=JSON.parse('{"title":"自定义","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_custom.md","filePath":"guide/incus/incus_custom.md","lastUpdated":1747726389000}'),I={name:"guide/incus/incus_custom.md"},x=n(`
自定义 ​
给incus启用官方的web面板进行控制 ​
先查看 incus论坛活跃用户分享的第三方教程
不懂的部分见 给机房的Ubuntu22.04安装LXD共享GPU资源-配置web 部分的内容
给宿主机附加免费的IPV6地址段 ​
有的机器本身没有IPV6的/64子网，这里给出一个方法免费附加IPV6的子网。
这里是使用6in4方法解决宿主机本身没有IPV6地址的问题。
TIP
本页面的操作务必在原始系统上操作，保证未使用本项目的其他脚本安装环境(除了PVE，PVE需要先安装好)，否则可能导致环境冲突
以下是2023年目前还在运行的免费提供IPV6子网的平台
支持的平台对应需要的安装包协议通道/子网数量
tunnelbroker.netifupdown 或 ifupdown2v4tunnel 或 sit3✖/64 或 5✖/64
tunnelbroker.chifupdown 或 ifupdown2v4tunnel 或 sit3✖/64
ip4market.ruifupdown 或 ifupdown2v4tunnel 或 sit1✖/64
netassist.uaifupdown 或 ifupdown2v4tunnel 或 sit1✖/64
https://github.com/oneclickvirt/6in4ifupdown2sit、gre、ipip自定义
免费的平台只解决IPV6有没有的问题，不提供优质的IPV6带宽。
如需优质的带宽，请自建隧道，当ifupdown和ifupdown2都可时，先尝试ifupdown是否可安装成功，否则就安装ifupdown2.
安装完毕后，安装了哪个包后面就选择哪个包进行格式转换。
初始环境修改 ​
执行
touch /etc/cloud/cloud-init.disabled
关闭cloud-init的自动化覆写先，然后查看本机使用什么管理网络，执行
systemctl is-active systemd-networkd
和
systemctl is-active networking
看看属于哪种情况，如果是前者active，后者inactive，你需要重装/DD一个不是这样配置的系统，或者切换本机使用ifupdown/ifupdown2管理网络
# 是否需要禁用原网络管理自行评判
+import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const t="/assets/lxd1.78537e30.png",l="/assets/lxd2.da10b5ec.png",p="/assets/lxd3.917f56de.png",o="/assets/lxd4.83a1a121.png",i="/assets/lxd5.4ebc1444.png",c="/assets/lxd6.572825bf.png",r="/assets/lxd7.b73982c7.png",d="/assets/lxd8.9fcc21e5.png",u="/assets/lxd9.00250a32.png",h="/assets/lxd10.a25a745c.png",C="/assets/lxd11.b83f953c.png",g="/assets/lxd12.0da335dd.png",y="/assets/lxd13.308fe0de.png",A="/assets/lxd14.8dbfdcd6.png",m="/assets/lxd15.70114933.png",b="/assets/lxd16.a595fa36.png",v="/assets/lxd17.d7ea65d8.png",f="/assets/lxd18.d6225daa.png",k="/assets/lxd19.69674669.png",D="/assets/lxd20.179fc6e1.png",P="/assets/lxd21.48123d6a.png",_="/assets/lxd22.4386597e.png",w="/assets/lxd23.c26427e3.png",U=JSON.parse('{"title":"自定义","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_custom.md","filePath":"guide/incus/incus_custom.md","lastUpdated":1747730955000}'),I={name:"guide/incus/incus_custom.md"},x=n(`
自定义 ​
给incus启用官方的web面板进行控制 ​
先查看 incus论坛活跃用户分享的第三方教程
不懂的部分见 给机房的Ubuntu22.04安装LXD共享GPU资源-配置web 部分的内容
给宿主机附加免费的IPV6地址段 ​
有的机器本身没有IPV6的/64子网，这里给出一个方法免费附加IPV6的子网。
这里是使用6in4方法解决宿主机本身没有IPV6地址的问题。
TIP
本页面的操作务必在原始系统上操作，保证未使用本项目的其他脚本安装环境(除了PVE，PVE需要先安装好)，否则可能导致环境冲突
以下是2023年目前还在运行的免费提供IPV6子网的平台
支持的平台对应需要的安装包协议通道/子网数量
tunnelbroker.netifupdown 或 ifupdown2v4tunnel 或 sit3✖/64 或 5✖/64
tunnelbroker.chifupdown 或 ifupdown2v4tunnel 或 sit3✖/64
ip4market.ruifupdown 或 ifupdown2v4tunnel 或 sit1✖/64
netassist.uaifupdown 或 ifupdown2v4tunnel 或 sit1✖/64
https://github.com/oneclickvirt/6in4ifupdown2sit、gre、ipip自定义
免费的平台只解决IPV6有没有的问题，不提供优质的IPV6带宽。
如需优质的带宽，请自建隧道，当ifupdown和ifupdown2都可时，先尝试ifupdown是否可安装成功，否则就安装ifupdown2.
安装完毕后，安装了哪个包后面就选择哪个包进行格式转换。
初始环境修改 ​
执行
touch /etc/cloud/cloud-init.disabled
关闭cloud-init的自动化覆写先，然后查看本机使用什么管理网络，执行
systemctl is-active systemd-networkd
和
systemctl is-active networking
看看属于哪种情况，如果是前者active，后者inactive，你需要重装/DD一个不是这样配置的系统，或者切换本机使用ifupdown/ifupdown2管理网络
# 是否需要禁用原网络管理自行评判
 # systemctl stop systemd-networkd
 # systemctl disable systemd-networkd
 # systemctl stop systemd-networkd.socket
diff --git a/assets/guide_incus_incus_custom.md.1b194673.lean.js b/assets/guide_incus_incus_custom.md.0507c488.lean.js
similarity index 99%
rename from assets/guide_incus_incus_custom.md.1b194673.lean.js
rename to assets/guide_incus_incus_custom.md.0507c488.lean.js
index e429c67306..7292b3e007 100644
--- a/assets/guide_incus_incus_custom.md.1b194673.lean.js
+++ b/assets/guide_incus_incus_custom.md.0507c488.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const t="/assets/lxd1.78537e30.png",l="/assets/lxd2.da10b5ec.png",p="/assets/lxd3.917f56de.png",o="/assets/lxd4.83a1a121.png",i="/assets/lxd5.4ebc1444.png",c="/assets/lxd6.572825bf.png",r="/assets/lxd7.b73982c7.png",d="/assets/lxd8.9fcc21e5.png",u="/assets/lxd9.00250a32.png",h="/assets/lxd10.a25a745c.png",C="/assets/lxd11.b83f953c.png",g="/assets/lxd12.0da335dd.png",y="/assets/lxd13.308fe0de.png",A="/assets/lxd14.8dbfdcd6.png",m="/assets/lxd15.70114933.png",b="/assets/lxd16.a595fa36.png",v="/assets/lxd17.d7ea65d8.png",f="/assets/lxd18.d6225daa.png",k="/assets/lxd19.69674669.png",D="/assets/lxd20.179fc6e1.png",P="/assets/lxd21.48123d6a.png",_="/assets/lxd22.4386597e.png",w="/assets/lxd23.c26427e3.png",U=JSON.parse('{"title":"自定义","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_custom.md","filePath":"guide/incus/incus_custom.md","lastUpdated":1747726389000}'),I={name:"guide/incus/incus_custom.md"},x=n(`
自定义 ​
给incus启用官方的web面板进行控制 ​
先查看 incus论坛活跃用户分享的第三方教程
不懂的部分见 给机房的Ubuntu22.04安装LXD共享GPU资源-配置web 部分的内容
给宿主机附加免费的IPV6地址段 ​
有的机器本身没有IPV6的/64子网，这里给出一个方法免费附加IPV6的子网。
这里是使用6in4方法解决宿主机本身没有IPV6地址的问题。
TIP
本页面的操作务必在原始系统上操作，保证未使用本项目的其他脚本安装环境(除了PVE，PVE需要先安装好)，否则可能导致环境冲突
以下是2023年目前还在运行的免费提供IPV6子网的平台
支持的平台对应需要的安装包协议通道/子网数量
tunnelbroker.netifupdown 或 ifupdown2v4tunnel 或 sit3✖/64 或 5✖/64
tunnelbroker.chifupdown 或 ifupdown2v4tunnel 或 sit3✖/64
ip4market.ruifupdown 或 ifupdown2v4tunnel 或 sit1✖/64
netassist.uaifupdown 或 ifupdown2v4tunnel 或 sit1✖/64
https://github.com/oneclickvirt/6in4ifupdown2sit、gre、ipip自定义
免费的平台只解决IPV6有没有的问题，不提供优质的IPV6带宽。
如需优质的带宽，请自建隧道，当ifupdown和ifupdown2都可时，先尝试ifupdown是否可安装成功，否则就安装ifupdown2.
安装完毕后，安装了哪个包后面就选择哪个包进行格式转换。
初始环境修改 ​
执行
touch /etc/cloud/cloud-init.disabled
关闭cloud-init的自动化覆写先，然后查看本机使用什么管理网络，执行
systemctl is-active systemd-networkd
和
systemctl is-active networking
看看属于哪种情况，如果是前者active，后者inactive，你需要重装/DD一个不是这样配置的系统，或者切换本机使用ifupdown/ifupdown2管理网络
# 是否需要禁用原网络管理自行评判
+import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const t="/assets/lxd1.78537e30.png",l="/assets/lxd2.da10b5ec.png",p="/assets/lxd3.917f56de.png",o="/assets/lxd4.83a1a121.png",i="/assets/lxd5.4ebc1444.png",c="/assets/lxd6.572825bf.png",r="/assets/lxd7.b73982c7.png",d="/assets/lxd8.9fcc21e5.png",u="/assets/lxd9.00250a32.png",h="/assets/lxd10.a25a745c.png",C="/assets/lxd11.b83f953c.png",g="/assets/lxd12.0da335dd.png",y="/assets/lxd13.308fe0de.png",A="/assets/lxd14.8dbfdcd6.png",m="/assets/lxd15.70114933.png",b="/assets/lxd16.a595fa36.png",v="/assets/lxd17.d7ea65d8.png",f="/assets/lxd18.d6225daa.png",k="/assets/lxd19.69674669.png",D="/assets/lxd20.179fc6e1.png",P="/assets/lxd21.48123d6a.png",_="/assets/lxd22.4386597e.png",w="/assets/lxd23.c26427e3.png",U=JSON.parse('{"title":"自定义","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_custom.md","filePath":"guide/incus/incus_custom.md","lastUpdated":1747730955000}'),I={name:"guide/incus/incus_custom.md"},x=n(`
自定义 ​
给incus启用官方的web面板进行控制 ​
先查看 incus论坛活跃用户分享的第三方教程
不懂的部分见 给机房的Ubuntu22.04安装LXD共享GPU资源-配置web 部分的内容
给宿主机附加免费的IPV6地址段 ​
有的机器本身没有IPV6的/64子网，这里给出一个方法免费附加IPV6的子网。
这里是使用6in4方法解决宿主机本身没有IPV6地址的问题。
TIP
本页面的操作务必在原始系统上操作，保证未使用本项目的其他脚本安装环境(除了PVE，PVE需要先安装好)，否则可能导致环境冲突
以下是2023年目前还在运行的免费提供IPV6子网的平台
支持的平台对应需要的安装包协议通道/子网数量
tunnelbroker.netifupdown 或 ifupdown2v4tunnel 或 sit3✖/64 或 5✖/64
tunnelbroker.chifupdown 或 ifupdown2v4tunnel 或 sit3✖/64
ip4market.ruifupdown 或 ifupdown2v4tunnel 或 sit1✖/64
netassist.uaifupdown 或 ifupdown2v4tunnel 或 sit1✖/64
https://github.com/oneclickvirt/6in4ifupdown2sit、gre、ipip自定义
免费的平台只解决IPV6有没有的问题，不提供优质的IPV6带宽。
如需优质的带宽，请自建隧道，当ifupdown和ifupdown2都可时，先尝试ifupdown是否可安装成功，否则就安装ifupdown2.
安装完毕后，安装了哪个包后面就选择哪个包进行格式转换。
初始环境修改 ​
执行
touch /etc/cloud/cloud-init.disabled
关闭cloud-init的自动化覆写先，然后查看本机使用什么管理网络，执行
systemctl is-active systemd-networkd
和
systemctl is-active networking
看看属于哪种情况，如果是前者active，后者inactive，你需要重装/DD一个不是这样配置的系统，或者切换本机使用ifupdown/ifupdown2管理网络
# 是否需要禁用原网络管理自行评判
 # systemctl stop systemd-networkd
 # systemctl disable systemd-networkd
 # systemctl stop systemd-networkd.socket
diff --git a/assets/guide_incus_incus_extra_config.md.19aa23f2.js b/assets/guide_incus_incus_extra_config.md.bca9f168.js
similarity index 99%
rename from assets/guide_incus_incus_extra_config.md.19aa23f2.js
rename to assets/guide_incus_incus_extra_config.md.bca9f168.js
index ea05f7cc1b..1963a41bac 100644
--- a/assets/guide_incus_incus_extra_config.md.19aa23f2.js
+++ b/assets/guide_incus_incus_extra_config.md.bca9f168.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"其他自定义配置","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_extra_config.md","filePath":"guide/incus/incus_extra_config.md","lastUpdated":1747726389000}'),p={name:"guide/incus/incus_extra_config.md"},o=l(`
其他自定义配置 ​
TIP
以下的配置安装会加重宿主机的负担，非必要不要安装
自动配置IPV6地址 ​
  • (非必须，不使用的也没问题)
  • 该脚本仅适用于宿主机有给IPV6子网且是至少/112的，且宿主机绑定了子网的第一个IP做宿主机的IPV6地址或IPV6的gateway
  • 自动为incus创建的LXC容器配置IPV6地址
  • 已集成到buildone.sh中可使用变量控制且无需事先下载，该脚本可不手动使用，在使用buildone.sh时配置Y开启即可
下载脚本
国际
bash
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
自动为容器配置IPV6映射地址(默认不使用iptables进行映射)
bash
bash build_ipv6_network.sh 容器名称
映射完毕会打印信息
示例(给test容器自动配置IPV6地址，配置完成会写入一个test_v6的文件信息)
bash
bash build_ipv6_network.sh test
PS：增加ipv6处理过程中可选择是否使用ip6tables进行映射，默认不使用ip6tables方式进行映射而使用新增网络设备的方式进行映射
使用ip6tables进行映射
bash
bash build_ipv6_network.sh 容器名称 Y
若使用了ip6tables进行映射，则删除所有IPV6已映射的规则可用：
bash
ip6tables -t nat -F PREROUTING
+import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"其他自定义配置","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_extra_config.md","filePath":"guide/incus/incus_extra_config.md","lastUpdated":1747730955000}'),p={name:"guide/incus/incus_extra_config.md"},o=l(`
其他自定义配置 ​
TIP
以下的配置安装会加重宿主机的负担，非必要不要安装
自动配置IPV6地址 ​
  • (非必须，不使用的也没问题)
  • 该脚本仅适用于宿主机有给IPV6子网且是至少/112的，且宿主机绑定了子网的第一个IP做宿主机的IPV6地址或IPV6的gateway
  • 自动为incus创建的LXC容器配置IPV6地址
  • 已集成到buildone.sh中可使用变量控制且无需事先下载，该脚本可不手动使用，在使用buildone.sh时配置Y开启即可
下载脚本
国际
bash
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
自动为容器配置IPV6映射地址(默认不使用iptables进行映射)
bash
bash build_ipv6_network.sh 容器名称
映射完毕会打印信息
示例(给test容器自动配置IPV6地址，配置完成会写入一个test_v6的文件信息)
bash
bash build_ipv6_network.sh test
PS：增加ipv6处理过程中可选择是否使用ip6tables进行映射，默认不使用ip6tables方式进行映射而使用新增网络设备的方式进行映射
使用ip6tables进行映射
bash
bash build_ipv6_network.sh 容器名称 Y
若使用了ip6tables进行映射，则删除所有IPV6已映射的规则可用：
bash
ip6tables -t nat -F PREROUTING
 ip6tables-legacy -t nat -F PREROUTING
 ip6tables-save > /etc/iptables/rules.v6
 netfilter-persistent save
diff --git a/assets/guide_incus_incus_extra_config.md.19aa23f2.lean.js b/assets/guide_incus_incus_extra_config.md.bca9f168.lean.js
similarity index 99%
rename from assets/guide_incus_incus_extra_config.md.19aa23f2.lean.js
rename to assets/guide_incus_incus_extra_config.md.bca9f168.lean.js
index ea05f7cc1b..1963a41bac 100644
--- a/assets/guide_incus_incus_extra_config.md.19aa23f2.lean.js
+++ b/assets/guide_incus_incus_extra_config.md.bca9f168.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"其他自定义配置","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_extra_config.md","filePath":"guide/incus/incus_extra_config.md","lastUpdated":1747726389000}'),p={name:"guide/incus/incus_extra_config.md"},o=l(`
其他自定义配置 ​
TIP
以下的配置安装会加重宿主机的负担，非必要不要安装
自动配置IPV6地址 ​
  • (非必须，不使用的也没问题)
  • 该脚本仅适用于宿主机有给IPV6子网且是至少/112的，且宿主机绑定了子网的第一个IP做宿主机的IPV6地址或IPV6的gateway
  • 自动为incus创建的LXC容器配置IPV6地址
  • 已集成到buildone.sh中可使用变量控制且无需事先下载，该脚本可不手动使用，在使用buildone.sh时配置Y开启即可
下载脚本
国际
bash
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
自动为容器配置IPV6映射地址(默认不使用iptables进行映射)
bash
bash build_ipv6_network.sh 容器名称
映射完毕会打印信息
示例(给test容器自动配置IPV6地址，配置完成会写入一个test_v6的文件信息)
bash
bash build_ipv6_network.sh test
PS：增加ipv6处理过程中可选择是否使用ip6tables进行映射，默认不使用ip6tables方式进行映射而使用新增网络设备的方式进行映射
使用ip6tables进行映射
bash
bash build_ipv6_network.sh 容器名称 Y
若使用了ip6tables进行映射，则删除所有IPV6已映射的规则可用：
bash
ip6tables -t nat -F PREROUTING
+import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"其他自定义配置","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_extra_config.md","filePath":"guide/incus/incus_extra_config.md","lastUpdated":1747730955000}'),p={name:"guide/incus/incus_extra_config.md"},o=l(`
其他自定义配置 ​
TIP
以下的配置安装会加重宿主机的负担，非必要不要安装
自动配置IPV6地址 ​
  • (非必须，不使用的也没问题)
  • 该脚本仅适用于宿主机有给IPV6子网且是至少/112的，且宿主机绑定了子网的第一个IP做宿主机的IPV6地址或IPV6的gateway
  • 自动为incus创建的LXC容器配置IPV6地址
  • 已集成到buildone.sh中可使用变量控制且无需事先下载，该脚本可不手动使用，在使用buildone.sh时配置Y开启即可
下载脚本
国际
bash
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
自动为容器配置IPV6映射地址(默认不使用iptables进行映射)
bash
bash build_ipv6_network.sh 容器名称
映射完毕会打印信息
示例(给test容器自动配置IPV6地址，配置完成会写入一个test_v6的文件信息)
bash
bash build_ipv6_network.sh test
PS：增加ipv6处理过程中可选择是否使用ip6tables进行映射，默认不使用ip6tables方式进行映射而使用新增网络设备的方式进行映射
使用ip6tables进行映射
bash
bash build_ipv6_network.sh 容器名称 Y
若使用了ip6tables进行映射，则删除所有IPV6已映射的规则可用：
bash
ip6tables -t nat -F PREROUTING
 ip6tables-legacy -t nat -F PREROUTING
 ip6tables-save > /etc/iptables/rules.v6
 netfilter-persistent save
diff --git a/assets/guide_incus_incus_install.md.95f8a621.js b/assets/guide_incus_incus_install.md.cae3da3f.js
similarity index 99%
rename from assets/guide_incus_incus_install.md.95f8a621.js
rename to assets/guide_incus_incus_install.md.cae3da3f.js
index 4df40f2d91..b87553cb36 100644
--- a/assets/guide_incus_incus_install.md.95f8a621.js
+++ b/assets/guide_incus_incus_install.md.cae3da3f.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"incus主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_install.md","filePath":"guide/incus/incus_install.md","lastUpdated":1747726389000}'),p={name:"guide/incus/incus_install.md"},o=l(`
incus主体安装 ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
一键安装 ​
WARNING
如果是全新的服务器，务必保证curl命令可用且update无问题再执行本脚本。
  • 环境要求：Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程后需要重启服务器以加载一些默认配置
  • 默认启用lxd的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/incus_install.sh -o incus_install.sh && chmod +x incus_install.sh && bash incus_install.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/incus_install.sh -o incus_install.sh && chmod +x incus_install.sh && bash incus_install.sh
或
shell
bash incus_install.sh
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
TIP
执行过程中可能会要求手动重启加载存储类型到内核中，安装完毕执行到最后会自动进行服务器重启，首次完整安装完毕后的重启大概耗时400~500秒，请耐心等待
WARNING
如果你需要在一台服务器上开启超过200个INCUS容器，那么不推荐你使用本项目，可能会出现lxcfs访问漂移的问题，产生IO占用无法释放。(系lxc原生问题无法修复)
手动安装(备选) ​
不推荐，只是为了一些奇葩环境一键脚本跑不动的时候进行安装
关闭防火墙 ​
bash
apt update
+import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"incus主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_install.md","filePath":"guide/incus/incus_install.md","lastUpdated":1747730955000}'),p={name:"guide/incus/incus_install.md"},o=l(`
incus主体安装 ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
一键安装 ​
WARNING
如果是全新的服务器，务必保证curl命令可用且update无问题再执行本脚本。
  • 环境要求：Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程后需要重启服务器以加载一些默认配置
  • 默认启用lxd的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/incus_install.sh -o incus_install.sh && chmod +x incus_install.sh && bash incus_install.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/incus_install.sh -o incus_install.sh && chmod +x incus_install.sh && bash incus_install.sh
或
shell
bash incus_install.sh
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
TIP
执行过程中可能会要求手动重启加载存储类型到内核中，安装完毕执行到最后会自动进行服务器重启，首次完整安装完毕后的重启大概耗时400~500秒，请耐心等待
WARNING
如果你需要在一台服务器上开启超过200个INCUS容器，那么不推荐你使用本项目，可能会出现lxcfs访问漂移的问题，产生IO占用无法释放。(系lxc原生问题无法修复)
手动安装(备选) ​
不推荐，只是为了一些奇葩环境一键脚本跑不动的时候进行安装
关闭防火墙 ​
bash
apt update
 apt install curl wget sudo dos2unix ufw jq -y
 ufw disable
开设虚拟内存SWAP ​
内存看你开多少服务器，这里如果要开8个，换算需要2G内存，实际内存如果是512MB内存，还需要开1.5G，保守点开2G虚拟内存即可
执行下面命令，输入1，再输入2048，代表开2G虚拟内存
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
安装incus ​
实际swap开的虚拟内存应该是实际内存的2倍，也就是开1G是合理的，上面我描述的情况属于超开了
sudo -i
 mkdir -p /etc/apt/keyrings/
diff --git a/assets/guide_incus_incus_install.md.95f8a621.lean.js b/assets/guide_incus_incus_install.md.cae3da3f.lean.js
similarity index 99%
rename from assets/guide_incus_incus_install.md.95f8a621.lean.js
rename to assets/guide_incus_incus_install.md.cae3da3f.lean.js
index 4df40f2d91..b87553cb36 100644
--- a/assets/guide_incus_incus_install.md.95f8a621.lean.js
+++ b/assets/guide_incus_incus_install.md.cae3da3f.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"incus主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_install.md","filePath":"guide/incus/incus_install.md","lastUpdated":1747726389000}'),p={name:"guide/incus/incus_install.md"},o=l(`
incus主体安装 ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
一键安装 ​
WARNING
如果是全新的服务器，务必保证curl命令可用且update无问题再执行本脚本。
  • 环境要求：Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程后需要重启服务器以加载一些默认配置
  • 默认启用lxd的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/incus_install.sh -o incus_install.sh && chmod +x incus_install.sh && bash incus_install.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/incus_install.sh -o incus_install.sh && chmod +x incus_install.sh && bash incus_install.sh
或
shell
bash incus_install.sh
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
TIP
执行过程中可能会要求手动重启加载存储类型到内核中，安装完毕执行到最后会自动进行服务器重启，首次完整安装完毕后的重启大概耗时400~500秒，请耐心等待
WARNING
如果你需要在一台服务器上开启超过200个INCUS容器，那么不推荐你使用本项目，可能会出现lxcfs访问漂移的问题，产生IO占用无法释放。(系lxc原生问题无法修复)
手动安装(备选) ​
不推荐，只是为了一些奇葩环境一键脚本跑不动的时候进行安装
关闭防火墙 ​
bash
apt update
+import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"incus主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_install.md","filePath":"guide/incus/incus_install.md","lastUpdated":1747730955000}'),p={name:"guide/incus/incus_install.md"},o=l(`
incus主体安装 ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
一键安装 ​
WARNING
如果是全新的服务器，务必保证curl命令可用且update无问题再执行本脚本。
  • 环境要求：Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程后需要重启服务器以加载一些默认配置
  • 默认启用lxd的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/incus_install.sh -o incus_install.sh && chmod +x incus_install.sh && bash incus_install.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/incus_install.sh -o incus_install.sh && chmod +x incus_install.sh && bash incus_install.sh
或
shell
bash incus_install.sh
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
TIP
执行过程中可能会要求手动重启加载存储类型到内核中，安装完毕执行到最后会自动进行服务器重启，首次完整安装完毕后的重启大概耗时400~500秒，请耐心等待
WARNING
如果你需要在一台服务器上开启超过200个INCUS容器，那么不推荐你使用本项目，可能会出现lxcfs访问漂移的问题，产生IO占用无法释放。(系lxc原生问题无法修复)
手动安装(备选) ​
不推荐，只是为了一些奇葩环境一键脚本跑不动的时候进行安装
关闭防火墙 ​
bash
apt update
 apt install curl wget sudo dos2unix ufw jq -y
 ufw disable
开设虚拟内存SWAP ​
内存看你开多少服务器，这里如果要开8个，换算需要2G内存，实际内存如果是512MB内存，还需要开1.5G，保守点开2G虚拟内存即可
执行下面命令，输入1，再输入2048，代表开2G虚拟内存
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
安装incus ​
实际swap开的虚拟内存应该是实际内存的2倍，也就是开1G是合理的，上面我描述的情况属于超开了
sudo -i
 mkdir -p /etc/apt/keyrings/
diff --git a/assets/guide_incus_incus_lxc.md.9c1f30a1.js b/assets/guide_incus_incus_lxc.md.d08d1e90.js
similarity index 99%
rename from assets/guide_incus_incus_lxc.md.9c1f30a1.js
rename to assets/guide_incus_incus_lxc.md.d08d1e90.js
index b839540088..08ee107d26 100644
--- a/assets/guide_incus_incus_lxc.md.9c1f30a1.js
+++ b/assets/guide_incus_incus_lxc.md.d08d1e90.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"在 Incus 中运行 LXC 容器","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_lxc.md","filePath":"guide/incus/incus_lxc.md","lastUpdated":1747726389000}'),p={name:"guide/incus/incus_lxc.md"},o=n(`
在 Incus 中运行 LXC 容器 ​
开设LXC容器可使用的镜像 ​
这里展示一部分可使用的系统参数供你参考：
  • debian10，debian11，debian12
  • ubuntu18，ubuntu20，ubuntu22
  • centos8，centos9 (实际开设出来都是Stream版本)
  • alpine3.15，alpine3.16，alpine3.17，alpine3.18
  • openwrt21，openwrt22，fedora37，fedora38，fedora39
  • rockylinux8，rockylinux9，oralce8，oracle9
  • oralce7，centos7 (都需要在GRUB中启用CGroupV1否则无法启动，详细介绍见常见问题答疑)
  • kali，archlinux
  • 注意都是小写字母+数字的组合或仅小写字母，自行尝试，如果搜索无该系统则会自动退出脚本
  • 版本号可以带英文小数点，为了适配alpine的版本号已支持
  • 开不起来的可能是硬盘或内存不够大或者本身就不适配宿主机，自行尝试查看开不起来的报错
  • 目前使用的容器系统有三重筛选，优先级：自编译、官方、opsmaru
  • 自编译镜像完整的支持系统的列表：x86_64_fixed_images.txt 和 arm64_fixed_images.txt
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载脚本 ​
下载开机脚本是非必须的，如果你使用过一键安装incus的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
使用方法 ​
./buildone.sh 服务器名称 CPU核数 内存大小 硬盘大小 SSH端口 外网起端口 外网止端口 下载速度 上传速度 是否启用IPV6(Y or N) 系统(留空则为debian11)
CPU核数需要小于或等于宿主机的核数，内存大小以MB计算，硬盘大小以GB计算，下载速度上传速度以Mbit计算，是否启用IPV6不一定要填Y或者N，没有这个参数也行，留空默认不开启IPV6
如果外网起端口和外网止端口都设置为0则不做区间外网端口映射了，只映射基础的SSH端口，注意不能为空，不进行映射需要设置为0
支持自定义服务器的系统，不填写留空时默认使用debian11，注意传入参数为系统名字+版本号
示例 ​
以下为开设的示例服务器的信息：
属性值
服务器名字test
SSH登录的用户名root
SSH登录的密码随机生成
CPU核数1
内存大小256MB
磁盘大小2G
内外网映射端口一致的区间20002到20025
上传带宽500Mbit
下载带宽500Mbit
自动设置外网IPV6地址N
系统debian11
./buildone.sh test 1 256 2 20001 20002 20025 500 500 N debian11
需要进入容器内部则执行
incus exec test /bin/bash
退出则输入exit回车即可
需要查看信息则执行
shell
cat 服务器名字
比如查询示例的信息就是
shell
cat test
如果已通过以上方法生成过服务器，还需要批量生成服务器，可使用自定义批量生成版本的脚本，但注意先删除测试服务器再进行批量生成服务器
删除测试服务器 ​
shell
incus stop test
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"在 Incus 中运行 LXC 容器","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_lxc.md","filePath":"guide/incus/incus_lxc.md","lastUpdated":1747730955000}'),p={name:"guide/incus/incus_lxc.md"},o=n(`
在 Incus 中运行 LXC 容器 ​
开设LXC容器可使用的镜像 ​
这里展示一部分可使用的系统参数供你参考：
  • debian10，debian11，debian12
  • ubuntu18，ubuntu20，ubuntu22
  • centos8，centos9 (实际开设出来都是Stream版本)
  • alpine3.15，alpine3.16，alpine3.17，alpine3.18
  • openwrt21，openwrt22，fedora37，fedora38，fedora39
  • rockylinux8，rockylinux9，oralce8，oracle9
  • oralce7，centos7 (都需要在GRUB中启用CGroupV1否则无法启动，详细介绍见常见问题答疑)
  • kali，archlinux
  • 注意都是小写字母+数字的组合或仅小写字母，自行尝试，如果搜索无该系统则会自动退出脚本
  • 版本号可以带英文小数点，为了适配alpine的版本号已支持
  • 开不起来的可能是硬盘或内存不够大或者本身就不适配宿主机，自行尝试查看开不起来的报错
  • 目前使用的容器系统有三重筛选，优先级：自编译、官方、opsmaru
  • 自编译镜像完整的支持系统的列表：x86_64_fixed_images.txt 和 arm64_fixed_images.txt
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载脚本 ​
下载开机脚本是非必须的，如果你使用过一键安装incus的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
使用方法 ​
./buildone.sh 服务器名称 CPU核数 内存大小 硬盘大小 SSH端口 外网起端口 外网止端口 下载速度 上传速度 是否启用IPV6(Y or N) 系统(留空则为debian11)
CPU核数需要小于或等于宿主机的核数，内存大小以MB计算，硬盘大小以GB计算，下载速度上传速度以Mbit计算，是否启用IPV6不一定要填Y或者N，没有这个参数也行，留空默认不开启IPV6
如果外网起端口和外网止端口都设置为0则不做区间外网端口映射了，只映射基础的SSH端口，注意不能为空，不进行映射需要设置为0
支持自定义服务器的系统，不填写留空时默认使用debian11，注意传入参数为系统名字+版本号
示例 ​
以下为开设的示例服务器的信息：
属性值
服务器名字test
SSH登录的用户名root
SSH登录的密码随机生成
CPU核数1
内存大小256MB
磁盘大小2G
内外网映射端口一致的区间20002到20025
上传带宽500Mbit
下载带宽500Mbit
自动设置外网IPV6地址N
系统debian11
./buildone.sh test 1 256 2 20001 20002 20025 500 500 N debian11
需要进入容器内部则执行
incus exec test /bin/bash
退出则输入exit回车即可
需要查看信息则执行
shell
cat 服务器名字
比如查询示例的信息就是
shell
cat test
如果已通过以上方法生成过服务器，还需要批量生成服务器，可使用自定义批量生成版本的脚本，但注意先删除测试服务器再进行批量生成服务器
删除测试服务器 ​
shell
incus stop test
 incus delete test
 rm -rf test
 rm -rf test_v6
diff --git a/assets/guide_incus_incus_lxc.md.9c1f30a1.lean.js b/assets/guide_incus_incus_lxc.md.d08d1e90.lean.js
similarity index 99%
rename from assets/guide_incus_incus_lxc.md.9c1f30a1.lean.js
rename to assets/guide_incus_incus_lxc.md.d08d1e90.lean.js
index b839540088..08ee107d26 100644
--- a/assets/guide_incus_incus_lxc.md.9c1f30a1.lean.js
+++ b/assets/guide_incus_incus_lxc.md.d08d1e90.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"在 Incus 中运行 LXC 容器","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_lxc.md","filePath":"guide/incus/incus_lxc.md","lastUpdated":1747726389000}'),p={name:"guide/incus/incus_lxc.md"},o=n(`
在 Incus 中运行 LXC 容器 ​
开设LXC容器可使用的镜像 ​
这里展示一部分可使用的系统参数供你参考：
  • debian10，debian11，debian12
  • ubuntu18，ubuntu20，ubuntu22
  • centos8，centos9 (实际开设出来都是Stream版本)
  • alpine3.15，alpine3.16，alpine3.17，alpine3.18
  • openwrt21，openwrt22，fedora37，fedora38，fedora39
  • rockylinux8，rockylinux9，oralce8，oracle9
  • oralce7，centos7 (都需要在GRUB中启用CGroupV1否则无法启动，详细介绍见常见问题答疑)
  • kali，archlinux
  • 注意都是小写字母+数字的组合或仅小写字母，自行尝试，如果搜索无该系统则会自动退出脚本
  • 版本号可以带英文小数点，为了适配alpine的版本号已支持
  • 开不起来的可能是硬盘或内存不够大或者本身就不适配宿主机，自行尝试查看开不起来的报错
  • 目前使用的容器系统有三重筛选，优先级：自编译、官方、opsmaru
  • 自编译镜像完整的支持系统的列表：x86_64_fixed_images.txt 和 arm64_fixed_images.txt
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载脚本 ​
下载开机脚本是非必须的，如果你使用过一键安装incus的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
使用方法 ​
./buildone.sh 服务器名称 CPU核数 内存大小 硬盘大小 SSH端口 外网起端口 外网止端口 下载速度 上传速度 是否启用IPV6(Y or N) 系统(留空则为debian11)
CPU核数需要小于或等于宿主机的核数，内存大小以MB计算，硬盘大小以GB计算，下载速度上传速度以Mbit计算，是否启用IPV6不一定要填Y或者N，没有这个参数也行，留空默认不开启IPV6
如果外网起端口和外网止端口都设置为0则不做区间外网端口映射了，只映射基础的SSH端口，注意不能为空，不进行映射需要设置为0
支持自定义服务器的系统，不填写留空时默认使用debian11，注意传入参数为系统名字+版本号
示例 ​
以下为开设的示例服务器的信息：
属性值
服务器名字test
SSH登录的用户名root
SSH登录的密码随机生成
CPU核数1
内存大小256MB
磁盘大小2G
内外网映射端口一致的区间20002到20025
上传带宽500Mbit
下载带宽500Mbit
自动设置外网IPV6地址N
系统debian11
./buildone.sh test 1 256 2 20001 20002 20025 500 500 N debian11
需要进入容器内部则执行
incus exec test /bin/bash
退出则输入exit回车即可
需要查看信息则执行
shell
cat 服务器名字
比如查询示例的信息就是
shell
cat test
如果已通过以上方法生成过服务器，还需要批量生成服务器，可使用自定义批量生成版本的脚本，但注意先删除测试服务器再进行批量生成服务器
删除测试服务器 ​
shell
incus stop test
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"在 Incus 中运行 LXC 容器","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_lxc.md","filePath":"guide/incus/incus_lxc.md","lastUpdated":1747730955000}'),p={name:"guide/incus/incus_lxc.md"},o=n(`
在 Incus 中运行 LXC 容器 ​
开设LXC容器可使用的镜像 ​
这里展示一部分可使用的系统参数供你参考：
  • debian10，debian11，debian12
  • ubuntu18，ubuntu20，ubuntu22
  • centos8，centos9 (实际开设出来都是Stream版本)
  • alpine3.15，alpine3.16，alpine3.17，alpine3.18
  • openwrt21，openwrt22，fedora37，fedora38，fedora39
  • rockylinux8，rockylinux9，oralce8，oracle9
  • oralce7，centos7 (都需要在GRUB中启用CGroupV1否则无法启动，详细介绍见常见问题答疑)
  • kali，archlinux
  • 注意都是小写字母+数字的组合或仅小写字母，自行尝试，如果搜索无该系统则会自动退出脚本
  • 版本号可以带英文小数点，为了适配alpine的版本号已支持
  • 开不起来的可能是硬盘或内存不够大或者本身就不适配宿主机，自行尝试查看开不起来的报错
  • 目前使用的容器系统有三重筛选，优先级：自编译、官方、opsmaru
  • 自编译镜像完整的支持系统的列表：x86_64_fixed_images.txt 和 arm64_fixed_images.txt
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载脚本 ​
下载开机脚本是非必须的，如果你使用过一键安装incus的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
使用方法 ​
./buildone.sh 服务器名称 CPU核数 内存大小 硬盘大小 SSH端口 外网起端口 外网止端口 下载速度 上传速度 是否启用IPV6(Y or N) 系统(留空则为debian11)
CPU核数需要小于或等于宿主机的核数，内存大小以MB计算，硬盘大小以GB计算，下载速度上传速度以Mbit计算，是否启用IPV6不一定要填Y或者N，没有这个参数也行，留空默认不开启IPV6
如果外网起端口和外网止端口都设置为0则不做区间外网端口映射了，只映射基础的SSH端口，注意不能为空，不进行映射需要设置为0
支持自定义服务器的系统，不填写留空时默认使用debian11，注意传入参数为系统名字+版本号
示例 ​
以下为开设的示例服务器的信息：
属性值
服务器名字test
SSH登录的用户名root
SSH登录的密码随机生成
CPU核数1
内存大小256MB
磁盘大小2G
内外网映射端口一致的区间20002到20025
上传带宽500Mbit
下载带宽500Mbit
自动设置外网IPV6地址N
系统debian11
./buildone.sh test 1 256 2 20001 20002 20025 500 500 N debian11
需要进入容器内部则执行
incus exec test /bin/bash
退出则输入exit回车即可
需要查看信息则执行
shell
cat 服务器名字
比如查询示例的信息就是
shell
cat test
如果已通过以上方法生成过服务器，还需要批量生成服务器，可使用自定义批量生成版本的脚本，但注意先删除测试服务器再进行批量生成服务器
删除测试服务器 ​
shell
incus stop test
 incus delete test
 rm -rf test
 rm -rf test_v6
diff --git a/assets/guide_incus_incus_precheck.md.f831343c.js b/assets/guide_incus_incus_precheck.md.3821ff11.js
similarity index 98%
rename from assets/guide_incus_incus_precheck.md.f831343c.js
rename to assets/guide_incus_incus_precheck.md.3821ff11.js
index b5a2ee52b4..8dedf31b31 100644
--- a/assets/guide_incus_incus_precheck.md.f831343c.js
+++ b/assets/guide_incus_incus_precheck.md.3821ff11.js
@@ -1 +1 @@
-import{_ as e,v as t,b as i,R as a}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_precheck.md","filePath":"guide/incus/incus_precheck.md","lastUpdated":1747726389000}'),c={name:"guide/incus/incus_precheck.md"},s=a('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/incus
要求 ​
硬件要求:
  • 系统：Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转
项目特点 ​
  • 本套脚本开发使用的Ubuntu24和Debian12，别的长期维护版本应该也没问题，某个存储类型无法使用时自动切换(优先级: btrfs > lvm > zfs > ceph > dir )
  • 已设置同时进行TCP和UDP转发，除了SSH端口其他的映射内网外网端口一致
  • 已设置支持开出的LXC容器进行docker嵌套虚拟，默认普通版本和纯探针版本使用debian11系统
  • 已设置默认启用lxcfs，使得在容器内的查询资源时使用的是配置的视图而不是宿主机的视图
  • 已屏蔽容器内可能用于滥用的工具包和IPV4网络的TCP/UDP协议的端口( 3389 8888 54321 65432 )，以防止容器被用于扫描和爆破，且可外置进程检查有问题自动停机
  • 已支持一键为LXC容器配置IPV6地址(前提是宿主机有IPV6子网，无IPV6地址则不配置)，自动适配子网大小
  • 已增加各种第三方镜像源，如果官方镜像丢失时，将使用镜像源下载容器镜像(含自修复镜像)
  • 保证你要开的盘为默认的系统盘(sda或者sda1)而不是挂载的盘(sdb之类的)，不确定的使用fdisk -l和df查看
  • 挂载其他盘的详看 其他说明
  • 一键脚本支持自定义限制所有内容，普通版本支持多次运行批量生成不覆盖先前生成的配置
检测环境 ​
使用后续脚本的务必执行本命令检测宿主机是否符合要求
国际
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)
国内
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)
',17),r=[s];function l(n,o,p,h,d,u){return t(),i("div",null,r)}const k=e(c,[["render",l]]);export{g as __pageData,k as default};
+import{_ as e,v as t,b as i,R as a}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_precheck.md","filePath":"guide/incus/incus_precheck.md","lastUpdated":1747730955000}'),c={name:"guide/incus/incus_precheck.md"},s=a('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/incus
要求 ​
硬件要求:
  • 系统：Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转
项目特点 ​
  • 本套脚本开发使用的Ubuntu24和Debian12，别的长期维护版本应该也没问题，某个存储类型无法使用时自动切换(优先级: btrfs > lvm > zfs > ceph > dir )
  • 已设置同时进行TCP和UDP转发，除了SSH端口其他的映射内网外网端口一致
  • 已设置支持开出的LXC容器进行docker嵌套虚拟，默认普通版本和纯探针版本使用debian11系统
  • 已设置默认启用lxcfs，使得在容器内的查询资源时使用的是配置的视图而不是宿主机的视图
  • 已屏蔽容器内可能用于滥用的工具包和IPV4网络的TCP/UDP协议的端口( 3389 8888 54321 65432 )，以防止容器被用于扫描和爆破，且可外置进程检查有问题自动停机
  • 已支持一键为LXC容器配置IPV6地址(前提是宿主机有IPV6子网，无IPV6地址则不配置)，自动适配子网大小
  • 已增加各种第三方镜像源，如果官方镜像丢失时，将使用镜像源下载容器镜像(含自修复镜像)
  • 保证你要开的盘为默认的系统盘(sda或者sda1)而不是挂载的盘(sdb之类的)，不确定的使用fdisk -l和df查看
  • 挂载其他盘的详看 其他说明
  • 一键脚本支持自定义限制所有内容，普通版本支持多次运行批量生成不覆盖先前生成的配置
检测环境 ​
使用后续脚本的务必执行本命令检测宿主机是否符合要求
国际
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)
国内
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)
',17),r=[s];function l(n,o,p,h,d,u){return t(),i("div",null,r)}const k=e(c,[["render",l]]);export{g as __pageData,k as default};
diff --git a/assets/guide_incus_incus_precheck.md.f831343c.lean.js b/assets/guide_incus_incus_precheck.md.3821ff11.lean.js
similarity index 98%
rename from assets/guide_incus_incus_precheck.md.f831343c.lean.js
rename to assets/guide_incus_incus_precheck.md.3821ff11.lean.js
index b5a2ee52b4..8dedf31b31 100644
--- a/assets/guide_incus_incus_precheck.md.f831343c.lean.js
+++ b/assets/guide_incus_incus_precheck.md.3821ff11.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as i,R as a}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_precheck.md","filePath":"guide/incus/incus_precheck.md","lastUpdated":1747726389000}'),c={name:"guide/incus/incus_precheck.md"},s=a('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/incus
要求 ​
硬件要求:
  • 系统：Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转
项目特点 ​
  • 本套脚本开发使用的Ubuntu24和Debian12，别的长期维护版本应该也没问题，某个存储类型无法使用时自动切换(优先级: btrfs > lvm > zfs > ceph > dir )
  • 已设置同时进行TCP和UDP转发，除了SSH端口其他的映射内网外网端口一致
  • 已设置支持开出的LXC容器进行docker嵌套虚拟，默认普通版本和纯探针版本使用debian11系统
  • 已设置默认启用lxcfs，使得在容器内的查询资源时使用的是配置的视图而不是宿主机的视图
  • 已屏蔽容器内可能用于滥用的工具包和IPV4网络的TCP/UDP协议的端口( 3389 8888 54321 65432 )，以防止容器被用于扫描和爆破，且可外置进程检查有问题自动停机
  • 已支持一键为LXC容器配置IPV6地址(前提是宿主机有IPV6子网，无IPV6地址则不配置)，自动适配子网大小
  • 已增加各种第三方镜像源，如果官方镜像丢失时，将使用镜像源下载容器镜像(含自修复镜像)
  • 保证你要开的盘为默认的系统盘(sda或者sda1)而不是挂载的盘(sdb之类的)，不确定的使用fdisk -l和df查看
  • 挂载其他盘的详看 其他说明
  • 一键脚本支持自定义限制所有内容，普通版本支持多次运行批量生成不覆盖先前生成的配置
检测环境 ​
使用后续脚本的务必执行本命令检测宿主机是否符合要求
国际
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)
国内
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)
',17),r=[s];function l(n,o,p,h,d,u){return t(),i("div",null,r)}const k=e(c,[["render",l]]);export{g as __pageData,k as default};
+import{_ as e,v as t,b as i,R as a}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_precheck.md","filePath":"guide/incus/incus_precheck.md","lastUpdated":1747730955000}'),c={name:"guide/incus/incus_precheck.md"},s=a('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/incus
要求 ​
硬件要求:
  • 系统：Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转
项目特点 ​
  • 本套脚本开发使用的Ubuntu24和Debian12，别的长期维护版本应该也没问题，某个存储类型无法使用时自动切换(优先级: btrfs > lvm > zfs > ceph > dir )
  • 已设置同时进行TCP和UDP转发，除了SSH端口其他的映射内网外网端口一致
  • 已设置支持开出的LXC容器进行docker嵌套虚拟，默认普通版本和纯探针版本使用debian11系统
  • 已设置默认启用lxcfs，使得在容器内的查询资源时使用的是配置的视图而不是宿主机的视图
  • 已屏蔽容器内可能用于滥用的工具包和IPV4网络的TCP/UDP协议的端口( 3389 8888 54321 65432 )，以防止容器被用于扫描和爆破，且可外置进程检查有问题自动停机
  • 已支持一键为LXC容器配置IPV6地址(前提是宿主机有IPV6子网，无IPV6地址则不配置)，自动适配子网大小
  • 已增加各种第三方镜像源，如果官方镜像丢失时，将使用镜像源下载容器镜像(含自修复镜像)
  • 保证你要开的盘为默认的系统盘(sda或者sda1)而不是挂载的盘(sdb之类的)，不确定的使用fdisk -l和df查看
  • 挂载其他盘的详看 其他说明
  • 一键脚本支持自定义限制所有内容，普通版本支持多次运行批量生成不覆盖先前生成的配置
检测环境 ​
使用后续脚本的务必执行本命令检测宿主机是否符合要求
国际
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)
国内
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)
',17),r=[s];function l(n,o,p,h,d,u){return t(),i("div",null,r)}const k=e(c,[["render",l]]);export{g as __pageData,k as default};
diff --git a/assets/guide_incus_incus_qa.md.d3bc8315.js b/assets/guide_incus_incus_qa.md.dbe0aeb5.js
similarity index 97%
rename from assets/guide_incus_incus_qa.md.d3bc8315.js
rename to assets/guide_incus_incus_qa.md.dbe0aeb5.js
index a9222ab1a8..6234888d2e 100644
--- a/assets/guide_incus_incus_qa.md.d3bc8315.js
+++ b/assets/guide_incus_incus_qa.md.dbe0aeb5.js
@@ -1 +1 @@
-import{_ as a,v as e,b as s,R as t}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_qa.md","filePath":"guide/incus/incus_qa.md","lastUpdated":1747726389000}'),o={name:"guide/incus/incus_qa.md"},r=t('
解惑 ​
开设centos7发现报错CGroupV1不支持怎么办 ​
启用CGroup V1：要在Ubuntu系统上启用CGroup V1，需要编辑内核启动参数。
请注意，在更改内核启动参数之前，请务必备份重要的数据和设置，以防止意外的问题。
编辑/etc/default/grub文件，将GRUB_CMDLINE_LINUX_DEFAULT中的参数末尾加上systemd.unified_cgroup_hierarchy=0，如
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"
保存文件并运行以下命令更新GRUB引导。
bash
sudo update-grub
重启系统，使更改生效
如果上述更改仍旧不支持开设centos7，那么请使用别的宿主机系统尝试
目前已验证可开带独立IPV6地址容器的VPS商家 ​
kuroit 中的 美国凤凰城 regular
datalix 中的 德国AMD 促销款
',13),n=[r];function p(c,i,l,d,u,h){return e(),s("div",null,n)}const g=a(o,[["render",p]]);export{f as __pageData,g as default};
+import{_ as a,v as e,b as s,R as t}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_qa.md","filePath":"guide/incus/incus_qa.md","lastUpdated":1747730955000}'),o={name:"guide/incus/incus_qa.md"},r=t('
解惑 ​
开设centos7发现报错CGroupV1不支持怎么办 ​
启用CGroup V1：要在Ubuntu系统上启用CGroup V1，需要编辑内核启动参数。
请注意，在更改内核启动参数之前，请务必备份重要的数据和设置，以防止意外的问题。
编辑/etc/default/grub文件，将GRUB_CMDLINE_LINUX_DEFAULT中的参数末尾加上systemd.unified_cgroup_hierarchy=0，如
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"
保存文件并运行以下命令更新GRUB引导。
bash
sudo update-grub
重启系统，使更改生效
如果上述更改仍旧不支持开设centos7，那么请使用别的宿主机系统尝试
目前已验证可开带独立IPV6地址容器的VPS商家 ​
kuroit 中的 美国凤凰城 regular
datalix 中的 德国AMD 促销款
',13),n=[r];function p(c,i,l,d,u,h){return e(),s("div",null,n)}const g=a(o,[["render",p]]);export{f as __pageData,g as default};
diff --git a/assets/guide_incus_incus_qa.md.d3bc8315.lean.js b/assets/guide_incus_incus_qa.md.dbe0aeb5.lean.js
similarity index 97%
rename from assets/guide_incus_incus_qa.md.d3bc8315.lean.js
rename to assets/guide_incus_incus_qa.md.dbe0aeb5.lean.js
index a9222ab1a8..6234888d2e 100644
--- a/assets/guide_incus_incus_qa.md.d3bc8315.lean.js
+++ b/assets/guide_incus_incus_qa.md.dbe0aeb5.lean.js
@@ -1 +1 @@
-import{_ as a,v as e,b as s,R as t}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_qa.md","filePath":"guide/incus/incus_qa.md","lastUpdated":1747726389000}'),o={name:"guide/incus/incus_qa.md"},r=t('
解惑 ​
开设centos7发现报错CGroupV1不支持怎么办 ​
启用CGroup V1：要在Ubuntu系统上启用CGroup V1，需要编辑内核启动参数。
请注意，在更改内核启动参数之前，请务必备份重要的数据和设置，以防止意外的问题。
编辑/etc/default/grub文件，将GRUB_CMDLINE_LINUX_DEFAULT中的参数末尾加上systemd.unified_cgroup_hierarchy=0，如
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"
保存文件并运行以下命令更新GRUB引导。
bash
sudo update-grub
重启系统，使更改生效
如果上述更改仍旧不支持开设centos7，那么请使用别的宿主机系统尝试
目前已验证可开带独立IPV6地址容器的VPS商家 ​
kuroit 中的 美国凤凰城 regular
datalix 中的 德国AMD 促销款
',13),n=[r];function p(c,i,l,d,u,h){return e(),s("div",null,n)}const g=a(o,[["render",p]]);export{f as __pageData,g as default};
+import{_ as a,v as e,b as s,R as t}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_qa.md","filePath":"guide/incus/incus_qa.md","lastUpdated":1747730955000}'),o={name:"guide/incus/incus_qa.md"},r=t('
解惑 ​
开设centos7发现报错CGroupV1不支持怎么办 ​
启用CGroup V1：要在Ubuntu系统上启用CGroup V1，需要编辑内核启动参数。
请注意，在更改内核启动参数之前，请务必备份重要的数据和设置，以防止意外的问题。
编辑/etc/default/grub文件，将GRUB_CMDLINE_LINUX_DEFAULT中的参数末尾加上systemd.unified_cgroup_hierarchy=0，如
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"
保存文件并运行以下命令更新GRUB引导。
bash
sudo update-grub
重启系统，使更改生效
如果上述更改仍旧不支持开设centos7，那么请使用别的宿主机系统尝试
目前已验证可开带独立IPV6地址容器的VPS商家 ​
kuroit 中的 美国凤凰城 regular
datalix 中的 德国AMD 促销款
',13),n=[r];function p(c,i,l,d,u,h){return e(),s("div",null,n)}const g=a(o,[["render",p]]);export{f as __pageData,g as default};
diff --git a/assets/guide_incus_incus_thanks.md.8677232b.js b/assets/guide_incus_incus_thanks.md.769f470e.js
similarity index 96%
rename from assets/guide_incus_incus_thanks.md.8677232b.js
rename to assets/guide_incus_incus_thanks.md.769f470e.js
index 8715119ce6..b03a29d813 100644
--- a/assets/guide_incus_incus_thanks.md.8677232b.js
+++ b/assets/guide_incus_incus_thanks.md.769f470e.js
@@ -1 +1 @@
-import{_ as t,v as r,b as e,R as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/incus/incus_thanks.md","filePath":"guide/incus/incus_thanks.md","lastUpdated":1747726389000}'),n={name:"guide/incus/incus_thanks.md"},a=s('
致谢 ​
https://github.com/lxc/lxd
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
https://github.com/SuperManito/LinuxMirrors
https://github.com/zabbly/incus
',10),i=[a];function o(c,p,h,u,l,d){return r(),e("div",null,i)}const b=t(n,[["render",o]]);export{f as __pageData,b as default};
+import{_ as t,v as r,b as e,R as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/incus/incus_thanks.md","filePath":"guide/incus/incus_thanks.md","lastUpdated":1747730955000}'),n={name:"guide/incus/incus_thanks.md"},a=s('
致谢 ​
https://github.com/lxc/lxd
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
https://github.com/SuperManito/LinuxMirrors
https://github.com/zabbly/incus
',10),i=[a];function o(c,p,h,u,l,d){return r(),e("div",null,i)}const b=t(n,[["render",o]]);export{f as __pageData,b as default};
diff --git a/assets/guide_incus_incus_thanks.md.8677232b.lean.js b/assets/guide_incus_incus_thanks.md.769f470e.lean.js
similarity index 96%
rename from assets/guide_incus_incus_thanks.md.8677232b.lean.js
rename to assets/guide_incus_incus_thanks.md.769f470e.lean.js
index 8715119ce6..b03a29d813 100644
--- a/assets/guide_incus_incus_thanks.md.8677232b.lean.js
+++ b/assets/guide_incus_incus_thanks.md.769f470e.lean.js
@@ -1 +1 @@
-import{_ as t,v as r,b as e,R as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/incus/incus_thanks.md","filePath":"guide/incus/incus_thanks.md","lastUpdated":1747726389000}'),n={name:"guide/incus/incus_thanks.md"},a=s('
致谢 ​
https://github.com/lxc/lxd
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
https://github.com/SuperManito/LinuxMirrors
https://github.com/zabbly/incus
',10),i=[a];function o(c,p,h,u,l,d){return r(),e("div",null,i)}const b=t(n,[["render",o]]);export{f as __pageData,b as default};
+import{_ as t,v as r,b as e,R as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/incus/incus_thanks.md","filePath":"guide/incus/incus_thanks.md","lastUpdated":1747730955000}'),n={name:"guide/incus/incus_thanks.md"},a=s('
致谢 ​
https://github.com/lxc/lxd
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
https://github.com/SuperManito/LinuxMirrors
https://github.com/zabbly/incus
',10),i=[a];function o(c,p,h,u,l,d){return r(),e("div",null,i)}const b=t(n,[["render",o]]);export{f as __pageData,b as default};
diff --git a/assets/guide_incus_incus_windows.md.e840e6f0.js b/assets/guide_incus_incus_windows.md.30f7892d.js
similarity index 99%
rename from assets/guide_incus_incus_windows.md.e840e6f0.js
rename to assets/guide_incus_incus_windows.md.30f7892d.js
index 761bf99d88..d7cee75c29 100644
--- a/assets/guide_incus_incus_windows.md.e840e6f0.js
+++ b/assets/guide_incus_incus_windows.md.30f7892d.js
@@ -1,4 +1,4 @@
-import{_ as s,v as n,b as a,R as l}from"./chunks/framework.70afa331.js";const p="/assets/win1.7d3fc058.png",d=JSON.parse('{"title":"在 Incus 中运行 Windows 虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_windows.md","filePath":"guide/incus/incus_windows.md","lastUpdated":1747726389000}'),o={name:"guide/incus/incus_windows.md"},e=l(`
在 Incus 中运行 Windows 虚拟机 ​
检查 Incus 驱动 ​
确保 incus info 输出中含有 driver: qemu，否则无法创建 VM：
shell
incus info | grep -i driver:
+import{_ as s,v as n,b as a,R as l}from"./chunks/framework.70afa331.js";const p="/assets/win1.7d3fc058.png",d=JSON.parse('{"title":"在 Incus 中运行 Windows 虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_windows.md","filePath":"guide/incus/incus_windows.md","lastUpdated":1747730955000}'),o={name:"guide/incus/incus_windows.md"},e=l(`
在 Incus 中运行 Windows 虚拟机 ​
检查 Incus 驱动 ​
确保 incus info 输出中含有 driver: qemu，否则无法创建 VM：
shell
incus info | grep -i driver:
 # 正确示例：
 # driver: qemu
若显示 driver: lxc，请在 /etc/incus/daemon.conf 中调整为 driver = qemu 并重启 Incus 服务。
准备环境和修补镜像 ​
在 /root 目录下按顺序执行以下命令：
shell
apt update
 apt install -y snapd libguestfs-tools wimtools rsync libhivex-bin libwin-hivex-perl genisoimage || apt install -y mkisofs
diff --git a/assets/guide_incus_incus_windows.md.e840e6f0.lean.js b/assets/guide_incus_incus_windows.md.30f7892d.lean.js
similarity index 99%
rename from assets/guide_incus_incus_windows.md.e840e6f0.lean.js
rename to assets/guide_incus_incus_windows.md.30f7892d.lean.js
index 761bf99d88..d7cee75c29 100644
--- a/assets/guide_incus_incus_windows.md.e840e6f0.lean.js
+++ b/assets/guide_incus_incus_windows.md.30f7892d.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as n,b as a,R as l}from"./chunks/framework.70afa331.js";const p="/assets/win1.7d3fc058.png",d=JSON.parse('{"title":"在 Incus 中运行 Windows 虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_windows.md","filePath":"guide/incus/incus_windows.md","lastUpdated":1747726389000}'),o={name:"guide/incus/incus_windows.md"},e=l(`
在 Incus 中运行 Windows 虚拟机 ​
检查 Incus 驱动 ​
确保 incus info 输出中含有 driver: qemu，否则无法创建 VM：
shell
incus info | grep -i driver:
+import{_ as s,v as n,b as a,R as l}from"./chunks/framework.70afa331.js";const p="/assets/win1.7d3fc058.png",d=JSON.parse('{"title":"在 Incus 中运行 Windows 虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_windows.md","filePath":"guide/incus/incus_windows.md","lastUpdated":1747730955000}'),o={name:"guide/incus/incus_windows.md"},e=l(`
在 Incus 中运行 Windows 虚拟机 ​
检查 Incus 驱动 ​
确保 incus info 输出中含有 driver: qemu，否则无法创建 VM：
shell
incus info | grep -i driver:
 # 正确示例：
 # driver: qemu
若显示 driver: lxc，请在 /etc/incus/daemon.conf 中调整为 driver = qemu 并重启 Incus 服务。
准备环境和修补镜像 ​
在 /root 目录下按顺序执行以下命令：
shell
apt update
 apt install -y snapd libguestfs-tools wimtools rsync libhivex-bin libwin-hivex-perl genisoimage || apt install -y mkisofs
diff --git a/assets/guide_lxd_lxd_custom.md.5a0d7c6d.js b/assets/guide_lxd_lxd_custom.md.b762875f.js
similarity index 99%
rename from assets/guide_lxd_lxd_custom.md.5a0d7c6d.js
rename to assets/guide_lxd_lxd_custom.md.b762875f.js
index 322e3c558f..9dac790e83 100644
--- a/assets/guide_lxd_lxd_custom.md.5a0d7c6d.js
+++ b/assets/guide_lxd_lxd_custom.md.b762875f.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const t="/assets/lxd1.78537e30.png",l="/assets/lxd2.da10b5ec.png",p="/assets/lxd3.917f56de.png",o="/assets/lxd4.83a1a121.png",i="/assets/lxd5.4ebc1444.png",c="/assets/lxd6.572825bf.png",r="/assets/lxd7.b73982c7.png",d="/assets/lxd8.9fcc21e5.png",h="/assets/lxd9.00250a32.png",u="/assets/lxd10.a25a745c.png",C="/assets/lxd11.b83f953c.png",g="/assets/lxd12.0da335dd.png",y="/assets/lxd13.308fe0de.png",A="/assets/lxd14.8dbfdcd6.png",m="/assets/lxd15.70114933.png",b="/assets/lxd16.a595fa36.png",v="/assets/lxd17.d7ea65d8.png",f="/assets/lxd18.d6225daa.png",k="/assets/lxd19.69674669.png",D="/assets/lxd20.179fc6e1.png",P="/assets/lxd21.48123d6a.png",_="/assets/lxd22.4386597e.png",w="/assets/lxd23.c26427e3.png",U=JSON.parse('{"title":"自定义","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_custom.md","filePath":"guide/lxd/lxd_custom.md","lastUpdated":1747726389000}'),I={name:"guide/lxd/lxd_custom.md"},x=n(`
自定义 ​
给lxd启用官方的web面板 ​
见 给机房的Ubuntu22.04安装LXD共享GPU资源-配置web 部分的内容
给宿主机附加免费的IPV6地址段 ​
有的机器本身没有IPV6的/64子网，这里给出一个方法免费附加IPV6的子网。
这里是使用6in4方法解决宿主机本身没有IPV6地址的问题。
TIP
本页面的操作务必在原始系统上操作，保证未使用本项目的其他脚本安装环境(除了PVE，PVE需要先安装好)，否则可能导致环境冲突
以下是2023年目前还在运行的免费提供IPV6子网的平台
支持的平台对应需要的安装包协议通道/子网数量
tunnelbroker.netifupdown 或 ifupdown2v4tunnel 或 sit3✖/64 或 5✖/64
tunnelbroker.chifupdown 或 ifupdown2v4tunnel 或 sit3✖/64
ip4market.ruifupdown 或 ifupdown2v4tunnel 或 sit1✖/64
netassist.uaifupdown 或 ifupdown2v4tunnel 或 sit1✖/64
https://github.com/oneclickvirt/6in4ifupdown2sit、gre、ipip自定义
免费的平台只解决IPV6有没有的问题，不提供优质的IPV6带宽。
如需优质的带宽，请自建隧道，当ifupdown和ifupdown2都可时，先尝试ifupdown是否可安装成功，否则就安装ifupdown2.
安装完毕后，安装了哪个包后面就选择哪个包进行格式转换。
初始环境修改 ​
执行
touch /etc/cloud/cloud-init.disabled
关闭cloud-init的自动化覆写先，然后查看本机使用什么管理网络，执行
systemctl is-active systemd-networkd
和
systemctl is-active networking
看看属于哪种情况，如果是前者active，后者inactive，你需要重装/DD一个不是这样配置的系统，或者切换本机使用ifupdown/ifupdown2管理网络
# 是否需要禁用原网络管理自行评判
+import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const t="/assets/lxd1.78537e30.png",l="/assets/lxd2.da10b5ec.png",p="/assets/lxd3.917f56de.png",o="/assets/lxd4.83a1a121.png",i="/assets/lxd5.4ebc1444.png",c="/assets/lxd6.572825bf.png",r="/assets/lxd7.b73982c7.png",d="/assets/lxd8.9fcc21e5.png",h="/assets/lxd9.00250a32.png",u="/assets/lxd10.a25a745c.png",C="/assets/lxd11.b83f953c.png",g="/assets/lxd12.0da335dd.png",y="/assets/lxd13.308fe0de.png",A="/assets/lxd14.8dbfdcd6.png",m="/assets/lxd15.70114933.png",b="/assets/lxd16.a595fa36.png",v="/assets/lxd17.d7ea65d8.png",f="/assets/lxd18.d6225daa.png",k="/assets/lxd19.69674669.png",D="/assets/lxd20.179fc6e1.png",P="/assets/lxd21.48123d6a.png",_="/assets/lxd22.4386597e.png",w="/assets/lxd23.c26427e3.png",U=JSON.parse('{"title":"自定义","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_custom.md","filePath":"guide/lxd/lxd_custom.md","lastUpdated":1747730955000}'),I={name:"guide/lxd/lxd_custom.md"},x=n(`
自定义 ​
给lxd启用官方的web面板 ​
见 给机房的Ubuntu22.04安装LXD共享GPU资源-配置web 部分的内容
给宿主机附加免费的IPV6地址段 ​
有的机器本身没有IPV6的/64子网，这里给出一个方法免费附加IPV6的子网。
这里是使用6in4方法解决宿主机本身没有IPV6地址的问题。
TIP
本页面的操作务必在原始系统上操作，保证未使用本项目的其他脚本安装环境(除了PVE，PVE需要先安装好)，否则可能导致环境冲突
以下是2023年目前还在运行的免费提供IPV6子网的平台
支持的平台对应需要的安装包协议通道/子网数量
tunnelbroker.netifupdown 或 ifupdown2v4tunnel 或 sit3✖/64 或 5✖/64
tunnelbroker.chifupdown 或 ifupdown2v4tunnel 或 sit3✖/64
ip4market.ruifupdown 或 ifupdown2v4tunnel 或 sit1✖/64
netassist.uaifupdown 或 ifupdown2v4tunnel 或 sit1✖/64
https://github.com/oneclickvirt/6in4ifupdown2sit、gre、ipip自定义
免费的平台只解决IPV6有没有的问题，不提供优质的IPV6带宽。
如需优质的带宽，请自建隧道，当ifupdown和ifupdown2都可时，先尝试ifupdown是否可安装成功，否则就安装ifupdown2.
安装完毕后，安装了哪个包后面就选择哪个包进行格式转换。
初始环境修改 ​
执行
touch /etc/cloud/cloud-init.disabled
关闭cloud-init的自动化覆写先，然后查看本机使用什么管理网络，执行
systemctl is-active systemd-networkd
和
systemctl is-active networking
看看属于哪种情况，如果是前者active，后者inactive，你需要重装/DD一个不是这样配置的系统，或者切换本机使用ifupdown/ifupdown2管理网络
# 是否需要禁用原网络管理自行评判
 # systemctl stop systemd-networkd
 # systemctl disable systemd-networkd
 # systemctl stop systemd-networkd.socket
diff --git a/assets/guide_lxd_lxd_custom.md.5a0d7c6d.lean.js b/assets/guide_lxd_lxd_custom.md.b762875f.lean.js
similarity index 99%
rename from assets/guide_lxd_lxd_custom.md.5a0d7c6d.lean.js
rename to assets/guide_lxd_lxd_custom.md.b762875f.lean.js
index 322e3c558f..9dac790e83 100644
--- a/assets/guide_lxd_lxd_custom.md.5a0d7c6d.lean.js
+++ b/assets/guide_lxd_lxd_custom.md.b762875f.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const t="/assets/lxd1.78537e30.png",l="/assets/lxd2.da10b5ec.png",p="/assets/lxd3.917f56de.png",o="/assets/lxd4.83a1a121.png",i="/assets/lxd5.4ebc1444.png",c="/assets/lxd6.572825bf.png",r="/assets/lxd7.b73982c7.png",d="/assets/lxd8.9fcc21e5.png",h="/assets/lxd9.00250a32.png",u="/assets/lxd10.a25a745c.png",C="/assets/lxd11.b83f953c.png",g="/assets/lxd12.0da335dd.png",y="/assets/lxd13.308fe0de.png",A="/assets/lxd14.8dbfdcd6.png",m="/assets/lxd15.70114933.png",b="/assets/lxd16.a595fa36.png",v="/assets/lxd17.d7ea65d8.png",f="/assets/lxd18.d6225daa.png",k="/assets/lxd19.69674669.png",D="/assets/lxd20.179fc6e1.png",P="/assets/lxd21.48123d6a.png",_="/assets/lxd22.4386597e.png",w="/assets/lxd23.c26427e3.png",U=JSON.parse('{"title":"自定义","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_custom.md","filePath":"guide/lxd/lxd_custom.md","lastUpdated":1747726389000}'),I={name:"guide/lxd/lxd_custom.md"},x=n(`
自定义 ​
给lxd启用官方的web面板 ​
见 给机房的Ubuntu22.04安装LXD共享GPU资源-配置web 部分的内容
给宿主机附加免费的IPV6地址段 ​
有的机器本身没有IPV6的/64子网，这里给出一个方法免费附加IPV6的子网。
这里是使用6in4方法解决宿主机本身没有IPV6地址的问题。
TIP
本页面的操作务必在原始系统上操作，保证未使用本项目的其他脚本安装环境(除了PVE，PVE需要先安装好)，否则可能导致环境冲突
以下是2023年目前还在运行的免费提供IPV6子网的平台
支持的平台对应需要的安装包协议通道/子网数量
tunnelbroker.netifupdown 或 ifupdown2v4tunnel 或 sit3✖/64 或 5✖/64
tunnelbroker.chifupdown 或 ifupdown2v4tunnel 或 sit3✖/64
ip4market.ruifupdown 或 ifupdown2v4tunnel 或 sit1✖/64
netassist.uaifupdown 或 ifupdown2v4tunnel 或 sit1✖/64
https://github.com/oneclickvirt/6in4ifupdown2sit、gre、ipip自定义
免费的平台只解决IPV6有没有的问题，不提供优质的IPV6带宽。
如需优质的带宽，请自建隧道，当ifupdown和ifupdown2都可时，先尝试ifupdown是否可安装成功，否则就安装ifupdown2.
安装完毕后，安装了哪个包后面就选择哪个包进行格式转换。
初始环境修改 ​
执行
touch /etc/cloud/cloud-init.disabled
关闭cloud-init的自动化覆写先，然后查看本机使用什么管理网络，执行
systemctl is-active systemd-networkd
和
systemctl is-active networking
看看属于哪种情况，如果是前者active，后者inactive，你需要重装/DD一个不是这样配置的系统，或者切换本机使用ifupdown/ifupdown2管理网络
# 是否需要禁用原网络管理自行评判
+import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const t="/assets/lxd1.78537e30.png",l="/assets/lxd2.da10b5ec.png",p="/assets/lxd3.917f56de.png",o="/assets/lxd4.83a1a121.png",i="/assets/lxd5.4ebc1444.png",c="/assets/lxd6.572825bf.png",r="/assets/lxd7.b73982c7.png",d="/assets/lxd8.9fcc21e5.png",h="/assets/lxd9.00250a32.png",u="/assets/lxd10.a25a745c.png",C="/assets/lxd11.b83f953c.png",g="/assets/lxd12.0da335dd.png",y="/assets/lxd13.308fe0de.png",A="/assets/lxd14.8dbfdcd6.png",m="/assets/lxd15.70114933.png",b="/assets/lxd16.a595fa36.png",v="/assets/lxd17.d7ea65d8.png",f="/assets/lxd18.d6225daa.png",k="/assets/lxd19.69674669.png",D="/assets/lxd20.179fc6e1.png",P="/assets/lxd21.48123d6a.png",_="/assets/lxd22.4386597e.png",w="/assets/lxd23.c26427e3.png",U=JSON.parse('{"title":"自定义","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_custom.md","filePath":"guide/lxd/lxd_custom.md","lastUpdated":1747730955000}'),I={name:"guide/lxd/lxd_custom.md"},x=n(`
自定义 ​
给lxd启用官方的web面板 ​
见 给机房的Ubuntu22.04安装LXD共享GPU资源-配置web 部分的内容
给宿主机附加免费的IPV6地址段 ​
有的机器本身没有IPV6的/64子网，这里给出一个方法免费附加IPV6的子网。
这里是使用6in4方法解决宿主机本身没有IPV6地址的问题。
TIP
本页面的操作务必在原始系统上操作，保证未使用本项目的其他脚本安装环境(除了PVE，PVE需要先安装好)，否则可能导致环境冲突
以下是2023年目前还在运行的免费提供IPV6子网的平台
支持的平台对应需要的安装包协议通道/子网数量
tunnelbroker.netifupdown 或 ifupdown2v4tunnel 或 sit3✖/64 或 5✖/64
tunnelbroker.chifupdown 或 ifupdown2v4tunnel 或 sit3✖/64
ip4market.ruifupdown 或 ifupdown2v4tunnel 或 sit1✖/64
netassist.uaifupdown 或 ifupdown2v4tunnel 或 sit1✖/64
https://github.com/oneclickvirt/6in4ifupdown2sit、gre、ipip自定义
免费的平台只解决IPV6有没有的问题，不提供优质的IPV6带宽。
如需优质的带宽，请自建隧道，当ifupdown和ifupdown2都可时，先尝试ifupdown是否可安装成功，否则就安装ifupdown2.
安装完毕后，安装了哪个包后面就选择哪个包进行格式转换。
初始环境修改 ​
执行
touch /etc/cloud/cloud-init.disabled
关闭cloud-init的自动化覆写先，然后查看本机使用什么管理网络，执行
systemctl is-active systemd-networkd
和
systemctl is-active networking
看看属于哪种情况，如果是前者active，后者inactive，你需要重装/DD一个不是这样配置的系统，或者切换本机使用ifupdown/ifupdown2管理网络
# 是否需要禁用原网络管理自行评判
 # systemctl stop systemd-networkd
 # systemctl disable systemd-networkd
 # systemctl stop systemd-networkd.socket
diff --git a/assets/guide_lxd_lxd_extra_config.md.8fbc121f.js b/assets/guide_lxd_lxd_extra_config.md.36535e50.js
similarity index 99%
rename from assets/guide_lxd_lxd_extra_config.md.8fbc121f.js
rename to assets/guide_lxd_lxd_extra_config.md.36535e50.js
index 0aaba460f1..3d30cbe1d0 100644
--- a/assets/guide_lxd_lxd_extra_config.md.8fbc121f.js
+++ b/assets/guide_lxd_lxd_extra_config.md.36535e50.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"其他自定义配置","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_extra_config.md","filePath":"guide/lxd/lxd_extra_config.md","lastUpdated":1747726389000}'),p={name:"guide/lxd/lxd_extra_config.md"},o=n(`
其他自定义配置 ​
TIP
以下的配置安装会加重宿主机的负担，非必要不要安装
自动配置IPV6地址 ​
  • (非必须，不使用的也没问题)
  • 该脚本仅适用于宿主机有给IPV6子网且是至少/112的，且宿主机绑定了子网的第一个IP做宿主机的IPV6地址或IPV6的gateway
  • 自动为LXD创建的LXC容器配置IPV6地址
  • 已集成到buildone.sh中可使用变量控制且无需事先下载，该脚本可不手动使用，在使用buildone.sh时配置Y开启即可
下载脚本
国际
bash
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
自动为容器配置IPV6映射地址(默认不使用iptables进行映射)
bash
bash build_ipv6_network.sh 容器名称
映射完毕会打印信息
示例(给test容器自动配置IPV6地址，配置完成会写入一个test_v6的文件信息)
bash
bash build_ipv6_network.sh test
PS：增加ipv6处理过程中可选择是否使用ip6tables进行映射，默认不使用ip6tables方式进行映射而使用新增网络设备的方式进行映射
使用ip6tables进行映射
bash
bash build_ipv6_network.sh 容器名称 Y
若使用了ip6tables进行映射，则删除所有IPV6已映射的规则可用：
bash
ip6tables -t nat -F PREROUTING
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"其他自定义配置","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_extra_config.md","filePath":"guide/lxd/lxd_extra_config.md","lastUpdated":1747730955000}'),p={name:"guide/lxd/lxd_extra_config.md"},o=n(`
其他自定义配置 ​
TIP
以下的配置安装会加重宿主机的负担，非必要不要安装
自动配置IPV6地址 ​
  • (非必须，不使用的也没问题)
  • 该脚本仅适用于宿主机有给IPV6子网且是至少/112的，且宿主机绑定了子网的第一个IP做宿主机的IPV6地址或IPV6的gateway
  • 自动为LXD创建的LXC容器配置IPV6地址
  • 已集成到buildone.sh中可使用变量控制且无需事先下载，该脚本可不手动使用，在使用buildone.sh时配置Y开启即可
下载脚本
国际
bash
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
自动为容器配置IPV6映射地址(默认不使用iptables进行映射)
bash
bash build_ipv6_network.sh 容器名称
映射完毕会打印信息
示例(给test容器自动配置IPV6地址，配置完成会写入一个test_v6的文件信息)
bash
bash build_ipv6_network.sh test
PS：增加ipv6处理过程中可选择是否使用ip6tables进行映射，默认不使用ip6tables方式进行映射而使用新增网络设备的方式进行映射
使用ip6tables进行映射
bash
bash build_ipv6_network.sh 容器名称 Y
若使用了ip6tables进行映射，则删除所有IPV6已映射的规则可用：
bash
ip6tables -t nat -F PREROUTING
 ip6tables-legacy -t nat -F PREROUTING
 ip6tables-save > /etc/iptables/rules.v6
 netfilter-persistent save
diff --git a/assets/guide_lxd_lxd_extra_config.md.8fbc121f.lean.js b/assets/guide_lxd_lxd_extra_config.md.36535e50.lean.js
similarity index 99%
rename from assets/guide_lxd_lxd_extra_config.md.8fbc121f.lean.js
rename to assets/guide_lxd_lxd_extra_config.md.36535e50.lean.js
index 0aaba460f1..3d30cbe1d0 100644
--- a/assets/guide_lxd_lxd_extra_config.md.8fbc121f.lean.js
+++ b/assets/guide_lxd_lxd_extra_config.md.36535e50.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"其他自定义配置","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_extra_config.md","filePath":"guide/lxd/lxd_extra_config.md","lastUpdated":1747726389000}'),p={name:"guide/lxd/lxd_extra_config.md"},o=n(`
其他自定义配置 ​
TIP
以下的配置安装会加重宿主机的负担，非必要不要安装
自动配置IPV6地址 ​
  • (非必须，不使用的也没问题)
  • 该脚本仅适用于宿主机有给IPV6子网且是至少/112的，且宿主机绑定了子网的第一个IP做宿主机的IPV6地址或IPV6的gateway
  • 自动为LXD创建的LXC容器配置IPV6地址
  • 已集成到buildone.sh中可使用变量控制且无需事先下载，该脚本可不手动使用，在使用buildone.sh时配置Y开启即可
下载脚本
国际
bash
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
自动为容器配置IPV6映射地址(默认不使用iptables进行映射)
bash
bash build_ipv6_network.sh 容器名称
映射完毕会打印信息
示例(给test容器自动配置IPV6地址，配置完成会写入一个test_v6的文件信息)
bash
bash build_ipv6_network.sh test
PS：增加ipv6处理过程中可选择是否使用ip6tables进行映射，默认不使用ip6tables方式进行映射而使用新增网络设备的方式进行映射
使用ip6tables进行映射
bash
bash build_ipv6_network.sh 容器名称 Y
若使用了ip6tables进行映射，则删除所有IPV6已映射的规则可用：
bash
ip6tables -t nat -F PREROUTING
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"其他自定义配置","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_extra_config.md","filePath":"guide/lxd/lxd_extra_config.md","lastUpdated":1747730955000}'),p={name:"guide/lxd/lxd_extra_config.md"},o=n(`
其他自定义配置 ​
TIP
以下的配置安装会加重宿主机的负担，非必要不要安装
自动配置IPV6地址 ​
  • (非必须，不使用的也没问题)
  • 该脚本仅适用于宿主机有给IPV6子网且是至少/112的，且宿主机绑定了子网的第一个IP做宿主机的IPV6地址或IPV6的gateway
  • 自动为LXD创建的LXC容器配置IPV6地址
  • 已集成到buildone.sh中可使用变量控制且无需事先下载，该脚本可不手动使用，在使用buildone.sh时配置Y开启即可
下载脚本
国际
bash
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
自动为容器配置IPV6映射地址(默认不使用iptables进行映射)
bash
bash build_ipv6_network.sh 容器名称
映射完毕会打印信息
示例(给test容器自动配置IPV6地址，配置完成会写入一个test_v6的文件信息)
bash
bash build_ipv6_network.sh test
PS：增加ipv6处理过程中可选择是否使用ip6tables进行映射，默认不使用ip6tables方式进行映射而使用新增网络设备的方式进行映射
使用ip6tables进行映射
bash
bash build_ipv6_network.sh 容器名称 Y
若使用了ip6tables进行映射，则删除所有IPV6已映射的规则可用：
bash
ip6tables -t nat -F PREROUTING
 ip6tables-legacy -t nat -F PREROUTING
 ip6tables-save > /etc/iptables/rules.v6
 netfilter-persistent save
diff --git a/assets/guide_lxd_lxd_install.md.1ff608ee.js b/assets/guide_lxd_lxd_install.md.1ebd74c2.js
similarity index 58%
rename from assets/guide_lxd_lxd_install.md.1ff608ee.js
rename to assets/guide_lxd_lxd_install.md.1ebd74c2.js
index 3647118fd5..8d90b3c912 100644
--- a/assets/guide_lxd_lxd_install.md.1ff608ee.js
+++ b/assets/guide_lxd_lxd_install.md.1ebd74c2.js
@@ -1,6 +1,6 @@
-import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const n="/assets/lxdd1.433ff357.png",o="/assets/lxdd2.6a93138a.png",e="/assets/lxdd3.f56cf598.png",t="/assets/lxdd4.28d80b71.png",c="/assets/lxdd0.b1d6b8bc.png",g=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_install.md","filePath":"guide/lxd/lxd_install.md","lastUpdated":1747726389000}'),r={name:"guide/lxd/lxd_install.md"},C=p('
LXD ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
LXD主体安装 ​
WARNING
如果是全新的服务器，务必保证apt update和apt install curl都无问题再执行本脚本。建议预装btrfs-progs以加速后续的安装流程，安装后建议重启系统以加载设置，若未预安装也没问题，只需按照提示执行脚本即可。且自开机起最好等待5分钟后再执行以下命令，避免系统默认设置中就执行了本脚本导致apt源卡死
  • 环境要求：Ubuntu 18+(推荐)，Debian 8+(仅限x86_64架构)
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程后需要重启服务器以加载一些默认配置
  • 默认启用lxd的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
WARNING
如果你需要在一台服务器上开启超过200个LXD容器，那么不推荐你使用本项目，可能会出现lxcfs访问漂移的问题，产生IO占用无法释放。(系lxc原生问题无法修复)
安装WEB控制面板 ​
自定义 教程中有关于官方面板怎么启用的教程，但这里不选择使用官方的面板，因为官方面板为了安全性，牺牲了很多用户体验，这块使用
https://github.com/turtle0x1/LxdMosaic
的第三方面板
shell
sudo snap install lxdmosaic
直接进行一键安装，然后打开当前宿主机的https://<公网IP地址>/，强制访问，就能进入设置页面
lxd
lxd
lxd
这块如果你需要设置网站名字可以改改
lxd
聊胜于无只能说，没有RBAC权限控制进行分用户隔离
手动安装(备选) ​
不推荐，只是为了一些奇葩环境一键脚本跑不动的时候进行安装
关闭防火墙 ​
bash
apt update
+import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const n="/assets/lxdd1.433ff357.png",o="/assets/lxdd2.6a93138a.png",e="/assets/lxdd3.f56cf598.png",t="/assets/lxdd4.28d80b71.png",c="/assets/lxdd0.b1d6b8bc.png",x=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_install.md","filePath":"guide/lxd/lxd_install.md","lastUpdated":1747730955000}'),r={name:"guide/lxd/lxd_install.md"},C=p('
LXD ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
LXD主体安装 ​
WARNING
如果是全新的服务器，务必保证apt update和apt install curl都无问题再执行本脚本。
  • 环境要求：Ubuntu 18+(推荐)，Debian 8+(仅限x86_64架构)
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程后需要重启服务器以加载一些默认配置
  • 默认启用lxd的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
WARNING
如果你需要在一台服务器上开启超过200个LXD容器，那么不推荐你使用本项目，可能会出现lxcfs访问漂移的问题，产生IO占用无法释放。(系lxc原生问题无法修复)
安装WEB控制面板 ​
自定义 教程中有关于官方面板怎么启用的教程，但这里不选择使用官方的面板，因为官方面板为了安全性，牺牲了很多用户体验，这块使用
https://github.com/turtle0x1/LxdMosaic
的第三方面板
shell
sudo snap install lxdmosaic
直接进行一键安装，然后打开当前宿主机的https://<公网IP地址>/，强制访问，就能进入设置页面
lxd
lxd
lxd
这块如果你需要设置网站名字可以改改
lxd
聊胜于无只能说，没有RBAC权限控制进行分用户隔离
手动安装(备选) ​
不推荐，只是为了一些奇葩环境一键脚本跑不动的时候进行安装
关闭防火墙 ​
bash
apt update
 apt install curl wget sudo dos2unix ufw jq -y
 ufw disable
开设虚拟内存SWAP ​
内存看你开多少服务器，这里如果要开8个，换算需要2G内存，实际内存如果是512MB内存，还需要开1.5G，保守点开2G虚拟内存即可
执行下面命令，输入1，再输入2048，代表开2G虚拟内存
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
安装LXD ​
实际swap开的虚拟内存应该是实际内存的2倍，也就是开1G是合理的，上面我描述的情况属于超开了
apt install snapd -y
 snap install lxd
 /snap/bin/lxd init
如果上面的命令中出现下面的错误
(snap "lxd" assumes unsupported features: snapd2.39 (try to update snapd and refresh the core snap))
使用命令修补后再进行lxd的安装
snap install core
如果无异常，上面三行命令执行结果如下
图片
一般的选项回车默认即可
选择配置物理盘大小(提示默认最小1GB那个选项)，一般我填空闲磁盘大小减去内存大小后乘以0.95并向下取整，这里我填了10GB
提示带auto的更新image的选项记得选no，避免更新占用系统
测试lxc有没有软连接上
lxc -h
如果报错则执行以下命令软连接lxc命令
bash
! lxc -h >/dev/null 2>&1 && echo 'alias lxc="/snap/bin/lxc"' >> /root/.bashrc && source /root/.bashrc
-export PATH=$PATH:/snap/bin
连接后再测试lxc命令是否有报错找不到
`,52),i=[C];function y(d,D,A,h,u,m){return a(),l("div",null,i)}const x=s(r,[["render",y]]);export{g as __pageData,x as default};
+export PATH=$PATH:/snap/bin
连接后再测试lxc命令是否有报错找不到
`,52),i=[C];function y(d,D,A,h,u,m){return a(),l("div",null,i)}const g=s(r,[["render",y]]);export{x as __pageData,g as default};
diff --git a/assets/guide_lxd_lxd_install.md.1ff608ee.lean.js b/assets/guide_lxd_lxd_install.md.1ebd74c2.lean.js
similarity index 58%
rename from assets/guide_lxd_lxd_install.md.1ff608ee.lean.js
rename to assets/guide_lxd_lxd_install.md.1ebd74c2.lean.js
index 3647118fd5..8d90b3c912 100644
--- a/assets/guide_lxd_lxd_install.md.1ff608ee.lean.js
+++ b/assets/guide_lxd_lxd_install.md.1ebd74c2.lean.js
@@ -1,6 +1,6 @@
-import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const n="/assets/lxdd1.433ff357.png",o="/assets/lxdd2.6a93138a.png",e="/assets/lxdd3.f56cf598.png",t="/assets/lxdd4.28d80b71.png",c="/assets/lxdd0.b1d6b8bc.png",g=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_install.md","filePath":"guide/lxd/lxd_install.md","lastUpdated":1747726389000}'),r={name:"guide/lxd/lxd_install.md"},C=p('
LXD ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
LXD主体安装 ​
WARNING
如果是全新的服务器，务必保证apt update和apt install curl都无问题再执行本脚本。建议预装btrfs-progs以加速后续的安装流程，安装后建议重启系统以加载设置，若未预安装也没问题，只需按照提示执行脚本即可。且自开机起最好等待5分钟后再执行以下命令，避免系统默认设置中就执行了本脚本导致apt源卡死
  • 环境要求：Ubuntu 18+(推荐)，Debian 8+(仅限x86_64架构)
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程后需要重启服务器以加载一些默认配置
  • 默认启用lxd的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
WARNING
如果你需要在一台服务器上开启超过200个LXD容器，那么不推荐你使用本项目，可能会出现lxcfs访问漂移的问题，产生IO占用无法释放。(系lxc原生问题无法修复)
安装WEB控制面板 ​
自定义 教程中有关于官方面板怎么启用的教程，但这里不选择使用官方的面板，因为官方面板为了安全性，牺牲了很多用户体验，这块使用
https://github.com/turtle0x1/LxdMosaic
的第三方面板
shell
sudo snap install lxdmosaic
直接进行一键安装，然后打开当前宿主机的https://<公网IP地址>/，强制访问，就能进入设置页面
lxd
lxd
lxd
这块如果你需要设置网站名字可以改改
lxd
聊胜于无只能说，没有RBAC权限控制进行分用户隔离
手动安装(备选) ​
不推荐，只是为了一些奇葩环境一键脚本跑不动的时候进行安装
关闭防火墙 ​
bash
apt update
+import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const n="/assets/lxdd1.433ff357.png",o="/assets/lxdd2.6a93138a.png",e="/assets/lxdd3.f56cf598.png",t="/assets/lxdd4.28d80b71.png",c="/assets/lxdd0.b1d6b8bc.png",x=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_install.md","filePath":"guide/lxd/lxd_install.md","lastUpdated":1747730955000}'),r={name:"guide/lxd/lxd_install.md"},C=p('
LXD ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
LXD主体安装 ​
WARNING
如果是全新的服务器，务必保证apt update和apt install curl都无问题再执行本脚本。
  • 环境要求：Ubuntu 18+(推荐)，Debian 8+(仅限x86_64架构)
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程后需要重启服务器以加载一些默认配置
  • 默认启用lxd的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
WARNING
如果你需要在一台服务器上开启超过200个LXD容器，那么不推荐你使用本项目，可能会出现lxcfs访问漂移的问题，产生IO占用无法释放。(系lxc原生问题无法修复)
安装WEB控制面板 ​
自定义 教程中有关于官方面板怎么启用的教程，但这里不选择使用官方的面板，因为官方面板为了安全性，牺牲了很多用户体验，这块使用
https://github.com/turtle0x1/LxdMosaic
的第三方面板
shell
sudo snap install lxdmosaic
直接进行一键安装，然后打开当前宿主机的https://<公网IP地址>/，强制访问，就能进入设置页面
lxd
lxd
lxd
这块如果你需要设置网站名字可以改改
lxd
聊胜于无只能说，没有RBAC权限控制进行分用户隔离
手动安装(备选) ​
不推荐，只是为了一些奇葩环境一键脚本跑不动的时候进行安装
关闭防火墙 ​
bash
apt update
 apt install curl wget sudo dos2unix ufw jq -y
 ufw disable
开设虚拟内存SWAP ​
内存看你开多少服务器，这里如果要开8个，换算需要2G内存，实际内存如果是512MB内存，还需要开1.5G，保守点开2G虚拟内存即可
执行下面命令，输入1，再输入2048，代表开2G虚拟内存
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
安装LXD ​
实际swap开的虚拟内存应该是实际内存的2倍，也就是开1G是合理的，上面我描述的情况属于超开了
apt install snapd -y
 snap install lxd
 /snap/bin/lxd init
如果上面的命令中出现下面的错误
(snap "lxd" assumes unsupported features: snapd2.39 (try to update snapd and refresh the core snap))
使用命令修补后再进行lxd的安装
snap install core
如果无异常，上面三行命令执行结果如下
图片
一般的选项回车默认即可
选择配置物理盘大小(提示默认最小1GB那个选项)，一般我填空闲磁盘大小减去内存大小后乘以0.95并向下取整，这里我填了10GB
提示带auto的更新image的选项记得选no，避免更新占用系统
测试lxc有没有软连接上
lxc -h
如果报错则执行以下命令软连接lxc命令
bash
! lxc -h >/dev/null 2>&1 && echo 'alias lxc="/snap/bin/lxc"' >> /root/.bashrc && source /root/.bashrc
-export PATH=$PATH:/snap/bin
连接后再测试lxc命令是否有报错找不到
`,52),i=[C];function y(d,D,A,h,u,m){return a(),l("div",null,i)}const x=s(r,[["render",y]]);export{g as __pageData,x as default};
+export PATH=$PATH:/snap/bin
连接后再测试lxc命令是否有报错找不到
`,52),i=[C];function y(d,D,A,h,u,m){return a(),l("div",null,i)}const g=s(r,[["render",y]]);export{x as __pageData,g as default};
diff --git a/assets/guide_lxd_lxd_lxc.md.650076ad.js b/assets/guide_lxd_lxd_lxc.md.e2540b4f.js
similarity index 99%
rename from assets/guide_lxd_lxd_lxc.md.650076ad.js
rename to assets/guide_lxd_lxd_lxc.md.e2540b4f.js
index bdd809a3a0..d031cb6572 100644
--- a/assets/guide_lxd_lxd_lxc.md.650076ad.js
+++ b/assets/guide_lxd_lxd_lxc.md.e2540b4f.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"LXC虚拟化","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_lxc.md","filePath":"guide/lxd/lxd_lxc.md","lastUpdated":1747726389000}'),p={name:"guide/lxd/lxd_lxc.md"},o=n(`
LXC虚拟化 ​
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载开机脚本是非必须的，如果你使用过一键安装LXD的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
使用方法 ​
./buildone.sh 服务器名称 CPU核数 内存大小 硬盘大小 SSH端口 外网起端口 外网止端口 下载速度 上传速度 是否启用IPV6(Y or N) 系统(留空则为debian11)
CPU核数需要小于或等于宿主机的核数，内存大小以MB计算，硬盘大小以GB计算，下载速度上传速度以Mbit计算，是否启用IPV6不一定要填Y或者N，没有这个参数也行，留空默认不开启IPV6
如果外网起端口和外网止端口都设置为0则不做区间外网端口映射了，只映射基础的SSH端口，注意不能为空，不进行映射需要设置为0
支持自定义服务器的系统，不填写留空时默认使用debian12，注意传入参数为系统名字+版本号，如：
  • debian12，debian13
  • ubuntu22，ubuntu24
  • centos8，centos9 (实际都是Stream版本)
  • alpine3.16，alpine3.17，alpine3.18，alpine3.19
  • 注意都是小写字母+数字的组合或仅小写字母，自行尝试，如果搜索无该系统则会自动退出脚本
  • 版本号可以带英文小数点，为了适配alpine的版本号已支持
  • 开不起来的可能是硬盘或内存不够大或者本身就不适配宿主机，自行尝试查看开不起来的报错
  • 目前使用的容器系统有三重筛选，优先级：自编译、官方、opsmaru
  • 自编译镜像完整的支持系统的列表：x86_64_fixed_images.txt 和 arm64_fixed_images.txt
示例 ​
以下为开设的示例服务器的信息：
属性值
服务器名字test
SSH登录的用户名root
SSH登录的密码随机生成
CPU核数1
内存大小256MB
磁盘大小2G
内外网映射端口一致的区间20002到20025
上传带宽500Mbit
下载带宽500Mbit
自动设置外网IPV6地址N
系统debian12
./buildone.sh test 1 256 2 20001 20002 20025 500 500 N debian12
需要进入容器内部则执行
lxc exec test /bin/bash
退出则输入exit回车即可
需要查看信息则执行
shell
cat 服务器名字
比如查询示例的信息就是
shell
cat test
如果已通过以上方法生成过服务器，还需要批量生成服务器，可使用自定义批量生成版本的脚本，但注意先删除测试服务器再进行批量生成服务器
删除测试服务器 ​
shell
lxc stop test
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"LXC虚拟化","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_lxc.md","filePath":"guide/lxd/lxd_lxc.md","lastUpdated":1747730955000}'),p={name:"guide/lxd/lxd_lxc.md"},o=n(`
LXC虚拟化 ​
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载开机脚本是非必须的，如果你使用过一键安装LXD的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
使用方法 ​
./buildone.sh 服务器名称 CPU核数 内存大小 硬盘大小 SSH端口 外网起端口 外网止端口 下载速度 上传速度 是否启用IPV6(Y or N) 系统(留空则为debian11)
CPU核数需要小于或等于宿主机的核数，内存大小以MB计算，硬盘大小以GB计算，下载速度上传速度以Mbit计算，是否启用IPV6不一定要填Y或者N，没有这个参数也行，留空默认不开启IPV6
如果外网起端口和外网止端口都设置为0则不做区间外网端口映射了，只映射基础的SSH端口，注意不能为空，不进行映射需要设置为0
支持自定义服务器的系统，不填写留空时默认使用debian12，注意传入参数为系统名字+版本号，如：
  • debian12，debian13
  • ubuntu22，ubuntu24
  • centos8，centos9 (实际都是Stream版本)
  • alpine3.16，alpine3.17，alpine3.18，alpine3.19
  • 注意都是小写字母+数字的组合或仅小写字母，自行尝试，如果搜索无该系统则会自动退出脚本
  • 版本号可以带英文小数点，为了适配alpine的版本号已支持
  • 开不起来的可能是硬盘或内存不够大或者本身就不适配宿主机，自行尝试查看开不起来的报错
  • 目前使用的容器系统有三重筛选，优先级：自编译、官方、opsmaru
  • 自编译镜像完整的支持系统的列表：x86_64_fixed_images.txt 和 arm64_fixed_images.txt
示例 ​
以下为开设的示例服务器的信息：
属性值
服务器名字test
SSH登录的用户名root
SSH登录的密码随机生成
CPU核数1
内存大小256MB
磁盘大小2G
内外网映射端口一致的区间20002到20025
上传带宽500Mbit
下载带宽500Mbit
自动设置外网IPV6地址N
系统debian12
./buildone.sh test 1 256 2 20001 20002 20025 500 500 N debian12
需要进入容器内部则执行
lxc exec test /bin/bash
退出则输入exit回车即可
需要查看信息则执行
shell
cat 服务器名字
比如查询示例的信息就是
shell
cat test
如果已通过以上方法生成过服务器，还需要批量生成服务器，可使用自定义批量生成版本的脚本，但注意先删除测试服务器再进行批量生成服务器
删除测试服务器 ​
shell
lxc stop test
 lxc delete test
 rm -rf test
 rm -rf test_v6
diff --git a/assets/guide_lxd_lxd_lxc.md.650076ad.lean.js b/assets/guide_lxd_lxd_lxc.md.e2540b4f.lean.js
similarity index 99%
rename from assets/guide_lxd_lxd_lxc.md.650076ad.lean.js
rename to assets/guide_lxd_lxd_lxc.md.e2540b4f.lean.js
index bdd809a3a0..d031cb6572 100644
--- a/assets/guide_lxd_lxd_lxc.md.650076ad.lean.js
+++ b/assets/guide_lxd_lxd_lxc.md.e2540b4f.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"LXC虚拟化","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_lxc.md","filePath":"guide/lxd/lxd_lxc.md","lastUpdated":1747726389000}'),p={name:"guide/lxd/lxd_lxc.md"},o=n(`
LXC虚拟化 ​
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载开机脚本是非必须的，如果你使用过一键安装LXD的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
使用方法 ​
./buildone.sh 服务器名称 CPU核数 内存大小 硬盘大小 SSH端口 外网起端口 外网止端口 下载速度 上传速度 是否启用IPV6(Y or N) 系统(留空则为debian11)
CPU核数需要小于或等于宿主机的核数，内存大小以MB计算，硬盘大小以GB计算，下载速度上传速度以Mbit计算，是否启用IPV6不一定要填Y或者N，没有这个参数也行，留空默认不开启IPV6
如果外网起端口和外网止端口都设置为0则不做区间外网端口映射了，只映射基础的SSH端口，注意不能为空，不进行映射需要设置为0
支持自定义服务器的系统，不填写留空时默认使用debian12，注意传入参数为系统名字+版本号，如：
  • debian12，debian13
  • ubuntu22，ubuntu24
  • centos8，centos9 (实际都是Stream版本)
  • alpine3.16，alpine3.17，alpine3.18，alpine3.19
  • 注意都是小写字母+数字的组合或仅小写字母，自行尝试，如果搜索无该系统则会自动退出脚本
  • 版本号可以带英文小数点，为了适配alpine的版本号已支持
  • 开不起来的可能是硬盘或内存不够大或者本身就不适配宿主机，自行尝试查看开不起来的报错
  • 目前使用的容器系统有三重筛选，优先级：自编译、官方、opsmaru
  • 自编译镜像完整的支持系统的列表：x86_64_fixed_images.txt 和 arm64_fixed_images.txt
示例 ​
以下为开设的示例服务器的信息：
属性值
服务器名字test
SSH登录的用户名root
SSH登录的密码随机生成
CPU核数1
内存大小256MB
磁盘大小2G
内外网映射端口一致的区间20002到20025
上传带宽500Mbit
下载带宽500Mbit
自动设置外网IPV6地址N
系统debian12
./buildone.sh test 1 256 2 20001 20002 20025 500 500 N debian12
需要进入容器内部则执行
lxc exec test /bin/bash
退出则输入exit回车即可
需要查看信息则执行
shell
cat 服务器名字
比如查询示例的信息就是
shell
cat test
如果已通过以上方法生成过服务器，还需要批量生成服务器，可使用自定义批量生成版本的脚本，但注意先删除测试服务器再进行批量生成服务器
删除测试服务器 ​
shell
lxc stop test
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"LXC虚拟化","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_lxc.md","filePath":"guide/lxd/lxd_lxc.md","lastUpdated":1747730955000}'),p={name:"guide/lxd/lxd_lxc.md"},o=n(`
LXC虚拟化 ​
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载开机脚本是非必须的，如果你使用过一键安装LXD的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
使用方法 ​
./buildone.sh 服务器名称 CPU核数 内存大小 硬盘大小 SSH端口 外网起端口 外网止端口 下载速度 上传速度 是否启用IPV6(Y or N) 系统(留空则为debian11)
CPU核数需要小于或等于宿主机的核数，内存大小以MB计算，硬盘大小以GB计算，下载速度上传速度以Mbit计算，是否启用IPV6不一定要填Y或者N，没有这个参数也行，留空默认不开启IPV6
如果外网起端口和外网止端口都设置为0则不做区间外网端口映射了，只映射基础的SSH端口，注意不能为空，不进行映射需要设置为0
支持自定义服务器的系统，不填写留空时默认使用debian12，注意传入参数为系统名字+版本号，如：
  • debian12，debian13
  • ubuntu22，ubuntu24
  • centos8，centos9 (实际都是Stream版本)
  • alpine3.16，alpine3.17，alpine3.18，alpine3.19
  • 注意都是小写字母+数字的组合或仅小写字母，自行尝试，如果搜索无该系统则会自动退出脚本
  • 版本号可以带英文小数点，为了适配alpine的版本号已支持
  • 开不起来的可能是硬盘或内存不够大或者本身就不适配宿主机，自行尝试查看开不起来的报错
  • 目前使用的容器系统有三重筛选，优先级：自编译、官方、opsmaru
  • 自编译镜像完整的支持系统的列表：x86_64_fixed_images.txt 和 arm64_fixed_images.txt
示例 ​
以下为开设的示例服务器的信息：
属性值
服务器名字test
SSH登录的用户名root
SSH登录的密码随机生成
CPU核数1
内存大小256MB
磁盘大小2G
内外网映射端口一致的区间20002到20025
上传带宽500Mbit
下载带宽500Mbit
自动设置外网IPV6地址N
系统debian12
./buildone.sh test 1 256 2 20001 20002 20025 500 500 N debian12
需要进入容器内部则执行
lxc exec test /bin/bash
退出则输入exit回车即可
需要查看信息则执行
shell
cat 服务器名字
比如查询示例的信息就是
shell
cat test
如果已通过以上方法生成过服务器，还需要批量生成服务器，可使用自定义批量生成版本的脚本，但注意先删除测试服务器再进行批量生成服务器
删除测试服务器 ​
shell
lxc stop test
 lxc delete test
 rm -rf test
 rm -rf test_v6
diff --git a/assets/guide_lxd_lxd_precheck.md.06ae4f7a.js b/assets/guide_lxd_lxd_precheck.md.c6ab8d98.js
similarity index 98%
rename from assets/guide_lxd_lxd_precheck.md.06ae4f7a.js
rename to assets/guide_lxd_lxd_precheck.md.c6ab8d98.js
index aef0a4ed50..569f6d174a 100644
--- a/assets/guide_lxd_lxd_precheck.md.06ae4f7a.js
+++ b/assets/guide_lxd_lxd_precheck.md.c6ab8d98.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a,R as l}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_precheck.md","filePath":"guide/lxd/lxd_precheck.md","lastUpdated":1747726389000}'),i={name:"guide/lxd/lxd_precheck.md"},r=l('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/lxd
要求 ​
硬件要求:
  • 系统：Debian 8+, Ubuntu 18+(推荐20.04)
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转
项目特点 ​
  • 本套脚本开发使用的Ubuntu20，Ubuntu别的长期维护版本应该也没问题，某个存储类型无法使用时自动切换
  • 已设置同时进行TCP和UDP转发，除了SSH端口其他的映射内网外网端口一致
  • 已设置支持开出的LXC容器进行docker嵌套虚拟，默认普通版本和纯探针版本使用debian11系统
  • 已设置默认启用lxcfs，使得在容器内的查询资源时使用的是配置的视图而不是宿主机的视图
  • 已屏蔽容器内可能用于滥用的工具包和IPV4网络的TCP/UDP协议的端口( 3389 8888 54321 65432 )，以防止容器被用于扫描和爆破，且可外置进程检查有问题自动停机
  • 已支持一键为LXC容器配置IPV6地址(前提是宿主机有IPV6子网，无IPV6地址则不配置)，自动适配子网大小
  • 已增加清华镜像源，如果官方镜像丢失时，将使用镜像源下载容器镜像
  • 保证你要开的盘为默认的系统盘(sda或者sda1)而不是挂载的盘(sdb之类的)，不确定的使用fdisk -l和df查看
  • 挂载其他盘的详看 其他说明
  • 一键脚本支持自定义限制所有内容，普通版本支持多次运行批量生成不覆盖先前生成的配置
检测环境 ​
使用后续脚本的务必执行本命令检测宿主机是否符合要求
国际
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)
国内
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)
',17),c=[r];function s(o,p,n,d,h,u){return t(),a("div",null,c)}const k=e(i,[["render",s]]);export{g as __pageData,k as default};
+import{_ as e,v as t,b as a,R as l}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_precheck.md","filePath":"guide/lxd/lxd_precheck.md","lastUpdated":1747730955000}'),i={name:"guide/lxd/lxd_precheck.md"},r=l('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/lxd
要求 ​
硬件要求:
  • 系统：Debian 8+, Ubuntu 18+(推荐20.04)
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转
项目特点 ​
  • 本套脚本开发使用的Ubuntu20，Ubuntu别的长期维护版本应该也没问题，某个存储类型无法使用时自动切换
  • 已设置同时进行TCP和UDP转发，除了SSH端口其他的映射内网外网端口一致
  • 已设置支持开出的LXC容器进行docker嵌套虚拟，默认普通版本和纯探针版本使用debian11系统
  • 已设置默认启用lxcfs，使得在容器内的查询资源时使用的是配置的视图而不是宿主机的视图
  • 已屏蔽容器内可能用于滥用的工具包和IPV4网络的TCP/UDP协议的端口( 3389 8888 54321 65432 )，以防止容器被用于扫描和爆破，且可外置进程检查有问题自动停机
  • 已支持一键为LXC容器配置IPV6地址(前提是宿主机有IPV6子网，无IPV6地址则不配置)，自动适配子网大小
  • 已增加清华镜像源，如果官方镜像丢失时，将使用镜像源下载容器镜像
  • 保证你要开的盘为默认的系统盘(sda或者sda1)而不是挂载的盘(sdb之类的)，不确定的使用fdisk -l和df查看
  • 挂载其他盘的详看 其他说明
  • 一键脚本支持自定义限制所有内容，普通版本支持多次运行批量生成不覆盖先前生成的配置
检测环境 ​
使用后续脚本的务必执行本命令检测宿主机是否符合要求
国际
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)
国内
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)
',17),c=[r];function s(o,p,n,d,h,u){return t(),a("div",null,c)}const k=e(i,[["render",s]]);export{g as __pageData,k as default};
diff --git a/assets/guide_lxd_lxd_precheck.md.06ae4f7a.lean.js b/assets/guide_lxd_lxd_precheck.md.c6ab8d98.lean.js
similarity index 98%
rename from assets/guide_lxd_lxd_precheck.md.06ae4f7a.lean.js
rename to assets/guide_lxd_lxd_precheck.md.c6ab8d98.lean.js
index aef0a4ed50..569f6d174a 100644
--- a/assets/guide_lxd_lxd_precheck.md.06ae4f7a.lean.js
+++ b/assets/guide_lxd_lxd_precheck.md.c6ab8d98.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a,R as l}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_precheck.md","filePath":"guide/lxd/lxd_precheck.md","lastUpdated":1747726389000}'),i={name:"guide/lxd/lxd_precheck.md"},r=l('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/lxd
要求 ​
硬件要求:
  • 系统：Debian 8+, Ubuntu 18+(推荐20.04)
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转
项目特点 ​
  • 本套脚本开发使用的Ubuntu20，Ubuntu别的长期维护版本应该也没问题，某个存储类型无法使用时自动切换
  • 已设置同时进行TCP和UDP转发，除了SSH端口其他的映射内网外网端口一致
  • 已设置支持开出的LXC容器进行docker嵌套虚拟，默认普通版本和纯探针版本使用debian11系统
  • 已设置默认启用lxcfs，使得在容器内的查询资源时使用的是配置的视图而不是宿主机的视图
  • 已屏蔽容器内可能用于滥用的工具包和IPV4网络的TCP/UDP协议的端口( 3389 8888 54321 65432 )，以防止容器被用于扫描和爆破，且可外置进程检查有问题自动停机
  • 已支持一键为LXC容器配置IPV6地址(前提是宿主机有IPV6子网，无IPV6地址则不配置)，自动适配子网大小
  • 已增加清华镜像源，如果官方镜像丢失时，将使用镜像源下载容器镜像
  • 保证你要开的盘为默认的系统盘(sda或者sda1)而不是挂载的盘(sdb之类的)，不确定的使用fdisk -l和df查看
  • 挂载其他盘的详看 其他说明
  • 一键脚本支持自定义限制所有内容，普通版本支持多次运行批量生成不覆盖先前生成的配置
检测环境 ​
使用后续脚本的务必执行本命令检测宿主机是否符合要求
国际
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)
国内
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)
',17),c=[r];function s(o,p,n,d,h,u){return t(),a("div",null,c)}const k=e(i,[["render",s]]);export{g as __pageData,k as default};
+import{_ as e,v as t,b as a,R as l}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_precheck.md","filePath":"guide/lxd/lxd_precheck.md","lastUpdated":1747730955000}'),i={name:"guide/lxd/lxd_precheck.md"},r=l('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/lxd
要求 ​
硬件要求:
  • 系统：Debian 8+, Ubuntu 18+(推荐20.04)
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转
项目特点 ​
  • 本套脚本开发使用的Ubuntu20，Ubuntu别的长期维护版本应该也没问题，某个存储类型无法使用时自动切换
  • 已设置同时进行TCP和UDP转发，除了SSH端口其他的映射内网外网端口一致
  • 已设置支持开出的LXC容器进行docker嵌套虚拟，默认普通版本和纯探针版本使用debian11系统
  • 已设置默认启用lxcfs，使得在容器内的查询资源时使用的是配置的视图而不是宿主机的视图
  • 已屏蔽容器内可能用于滥用的工具包和IPV4网络的TCP/UDP协议的端口( 3389 8888 54321 65432 )，以防止容器被用于扫描和爆破，且可外置进程检查有问题自动停机
  • 已支持一键为LXC容器配置IPV6地址(前提是宿主机有IPV6子网，无IPV6地址则不配置)，自动适配子网大小
  • 已增加清华镜像源，如果官方镜像丢失时，将使用镜像源下载容器镜像
  • 保证你要开的盘为默认的系统盘(sda或者sda1)而不是挂载的盘(sdb之类的)，不确定的使用fdisk -l和df查看
  • 挂载其他盘的详看 其他说明
  • 一键脚本支持自定义限制所有内容，普通版本支持多次运行批量生成不覆盖先前生成的配置
检测环境 ​
使用后续脚本的务必执行本命令检测宿主机是否符合要求
国际
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)
国内
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)
',17),c=[r];function s(o,p,n,d,h,u){return t(),a("div",null,c)}const k=e(i,[["render",s]]);export{g as __pageData,k as default};
diff --git a/assets/guide_lxd_lxd_qa.md.cdaa1368.js b/assets/guide_lxd_lxd_qa.md.37100cda.js
similarity index 98%
rename from assets/guide_lxd_lxd_qa.md.cdaa1368.js
rename to assets/guide_lxd_lxd_qa.md.37100cda.js
index b7980dea75..ef98802bf6 100644
--- a/assets/guide_lxd_lxd_qa.md.cdaa1368.js
+++ b/assets/guide_lxd_lxd_qa.md.37100cda.js
@@ -1,2 +1,2 @@
-import{_ as a,v as e,b as s,R as t}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_qa.md","filePath":"guide/lxd/lxd_qa.md","lastUpdated":1747726389000}'),l={name:"guide/lxd/lxd_qa.md"},o=t(`
解惑 ​
如果LXD安装后lxc命令显示找不到怎么办 ​
! lxc -h >/dev/null 2>&1 && echo 'alias lxc="/snap/bin/lxc"' >> /root/.bashrc && source /root/.bashrc
+import{_ as a,v as e,b as s,R as t}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_qa.md","filePath":"guide/lxd/lxd_qa.md","lastUpdated":1747730955000}'),l={name:"guide/lxd/lxd_qa.md"},o=t(`
解惑 ​
如果LXD安装后lxc命令显示找不到怎么办 ​
! lxc -h >/dev/null 2>&1 && echo 'alias lxc="/snap/bin/lxc"' >> /root/.bashrc && source /root/.bashrc
 export PATH=$PATH:/snap/bin
执行这个命令后尝试
lxc -h
看看lxc命令是否已修复
开设centos7发现报错CGroupV1不支持怎么办 ​
启用CGroup V1：要在Ubuntu系统上启用CGroup V1，需要编辑内核启动参数。
请注意，在更改内核启动参数之前，请务必备份重要的数据和设置，以防止意外的问题。
编辑/etc/default/grub文件，将GRUB_CMDLINE_LINUX_DEFAULT中的参数末尾加上systemd.unified_cgroup_hierarchy=0，如
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"
保存文件并运行以下命令更新GRUB引导。
bash
sudo update-grub
重启系统，使更改生效
如果上述更改仍旧不支持开设centos7，那么请使用别的宿主机系统尝试
目前已验证可开带独立IPV6地址容器的VPS商家 ​
kuroit 中的 美国凤凰城 regular
datalix 中的 德国AMD 促销
`,18),p=[o];function n(r,c,i,d,u,h){return e(),s("div",null,p)}const m=a(l,[["render",n]]);export{_ as __pageData,m as default};
diff --git a/assets/guide_lxd_lxd_qa.md.cdaa1368.lean.js b/assets/guide_lxd_lxd_qa.md.37100cda.lean.js
similarity index 98%
rename from assets/guide_lxd_lxd_qa.md.cdaa1368.lean.js
rename to assets/guide_lxd_lxd_qa.md.37100cda.lean.js
index b7980dea75..ef98802bf6 100644
--- a/assets/guide_lxd_lxd_qa.md.cdaa1368.lean.js
+++ b/assets/guide_lxd_lxd_qa.md.37100cda.lean.js
@@ -1,2 +1,2 @@
-import{_ as a,v as e,b as s,R as t}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_qa.md","filePath":"guide/lxd/lxd_qa.md","lastUpdated":1747726389000}'),l={name:"guide/lxd/lxd_qa.md"},o=t(`
解惑 ​
如果LXD安装后lxc命令显示找不到怎么办 ​
! lxc -h >/dev/null 2>&1 && echo 'alias lxc="/snap/bin/lxc"' >> /root/.bashrc && source /root/.bashrc
+import{_ as a,v as e,b as s,R as t}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_qa.md","filePath":"guide/lxd/lxd_qa.md","lastUpdated":1747730955000}'),l={name:"guide/lxd/lxd_qa.md"},o=t(`
解惑 ​
如果LXD安装后lxc命令显示找不到怎么办 ​
! lxc -h >/dev/null 2>&1 && echo 'alias lxc="/snap/bin/lxc"' >> /root/.bashrc && source /root/.bashrc
 export PATH=$PATH:/snap/bin
执行这个命令后尝试
lxc -h
看看lxc命令是否已修复
开设centos7发现报错CGroupV1不支持怎么办 ​
启用CGroup V1：要在Ubuntu系统上启用CGroup V1，需要编辑内核启动参数。
请注意，在更改内核启动参数之前，请务必备份重要的数据和设置，以防止意外的问题。
编辑/etc/default/grub文件，将GRUB_CMDLINE_LINUX_DEFAULT中的参数末尾加上systemd.unified_cgroup_hierarchy=0，如
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"
保存文件并运行以下命令更新GRUB引导。
bash
sudo update-grub
重启系统，使更改生效
如果上述更改仍旧不支持开设centos7，那么请使用别的宿主机系统尝试
目前已验证可开带独立IPV6地址容器的VPS商家 ​
kuroit 中的 美国凤凰城 regular
datalix 中的 德国AMD 促销
`,18),p=[o];function n(r,c,i,d,u,h){return e(),s("div",null,p)}const m=a(l,[["render",n]]);export{_ as __pageData,m as default};
diff --git a/assets/guide_lxd_lxd_thanks.md.035309c4.js b/assets/guide_lxd_lxd_thanks.md.14c8ba84.js
similarity index 97%
rename from assets/guide_lxd_lxd_thanks.md.035309c4.js
rename to assets/guide_lxd_lxd_thanks.md.14c8ba84.js
index 1186f07323..c2316446a8 100644
--- a/assets/guide_lxd_lxd_thanks.md.035309c4.js
+++ b/assets/guide_lxd_lxd_thanks.md.14c8ba84.js
@@ -1 +1 @@
-import{_ as t,v as r,b as e,R as a}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/lxd/lxd_thanks.md","filePath":"guide/lxd/lxd_thanks.md","lastUpdated":1747726389000}'),s={name:"guide/lxd/lxd_thanks.md"},n=a('
致谢 ​
https://github.com/lxc/lxd
https://lxdware.com/
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
https://github.com/SuperManito/LinuxMirrors
https://images.opsmaru.dev/
感谢 @Ella-Alinda @fscarmen 提供的指导
',12),o=[n];function i(p,l,c,h,d,u){return r(),e("div",null,o)}const x=t(s,[["render",i]]);export{g as __pageData,x as default};
+import{_ as t,v as r,b as e,R as a}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/lxd/lxd_thanks.md","filePath":"guide/lxd/lxd_thanks.md","lastUpdated":1747730955000}'),s={name:"guide/lxd/lxd_thanks.md"},n=a('
致谢 ​
https://github.com/lxc/lxd
https://lxdware.com/
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
https://github.com/SuperManito/LinuxMirrors
https://images.opsmaru.dev/
感谢 @Ella-Alinda @fscarmen 提供的指导
',12),o=[n];function i(p,l,c,h,d,u){return r(),e("div",null,o)}const x=t(s,[["render",i]]);export{g as __pageData,x as default};
diff --git a/assets/guide_lxd_lxd_thanks.md.035309c4.lean.js b/assets/guide_lxd_lxd_thanks.md.14c8ba84.lean.js
similarity index 97%
rename from assets/guide_lxd_lxd_thanks.md.035309c4.lean.js
rename to assets/guide_lxd_lxd_thanks.md.14c8ba84.lean.js
index 1186f07323..c2316446a8 100644
--- a/assets/guide_lxd_lxd_thanks.md.035309c4.lean.js
+++ b/assets/guide_lxd_lxd_thanks.md.14c8ba84.lean.js
@@ -1 +1 @@
-import{_ as t,v as r,b as e,R as a}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/lxd/lxd_thanks.md","filePath":"guide/lxd/lxd_thanks.md","lastUpdated":1747726389000}'),s={name:"guide/lxd/lxd_thanks.md"},n=a('
致谢 ​
https://github.com/lxc/lxd
https://lxdware.com/
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
https://github.com/SuperManito/LinuxMirrors
https://images.opsmaru.dev/
感谢 @Ella-Alinda @fscarmen 提供的指导
',12),o=[n];function i(p,l,c,h,d,u){return r(),e("div",null,o)}const x=t(s,[["render",i]]);export{g as __pageData,x as default};
+import{_ as t,v as r,b as e,R as a}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/lxd/lxd_thanks.md","filePath":"guide/lxd/lxd_thanks.md","lastUpdated":1747730955000}'),s={name:"guide/lxd/lxd_thanks.md"},n=a('
致谢 ​
https://github.com/lxc/lxd
https://lxdware.com/
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
https://github.com/SuperManito/LinuxMirrors
https://images.opsmaru.dev/
感谢 @Ella-Alinda @fscarmen 提供的指导
',12),o=[n];function i(p,l,c,h,d,u){return r(),e("div",null,o)}const x=t(s,[["render",i]]);export{g as __pageData,x as default};
diff --git a/assets/guide_pve_images_readme.md.0fcbd5ad.js b/assets/guide_pve_images_readme.md.db0a99a0.js
similarity index 72%
rename from assets/guide_pve_images_readme.md.0fcbd5ad.js
rename to assets/guide_pve_images_readme.md.db0a99a0.js
index 3d530baf18..246d1744b3 100644
--- a/assets/guide_pve_images_readme.md.0fcbd5ad.js
+++ b/assets/guide_pve_images_readme.md.db0a99a0.js
@@ -1 +1 @@
-import{_ as e,v as a,b as t,F as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/pve/images/readme.md","filePath":"guide/pve/images/readme.md","lastUpdated":1747726389000}'),d={name:"guide/pve/images/readme.md"},r=s("p",null,"暂存图片",-1),i=[r];function n(o,m,p,_,c,l){return a(),t("div",null,i)}const g=e(d,[["render",n]]);export{f as __pageData,g as default};
+import{_ as e,v as a,b as t,F as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/pve/images/readme.md","filePath":"guide/pve/images/readme.md","lastUpdated":1747730955000}'),d={name:"guide/pve/images/readme.md"},r=s("p",null,"暂存图片",-1),i=[r];function n(o,m,p,_,c,l){return a(),t("div",null,i)}const g=e(d,[["render",n]]);export{f as __pageData,g as default};
diff --git a/assets/guide_pve_images_readme.md.0fcbd5ad.lean.js b/assets/guide_pve_images_readme.md.db0a99a0.lean.js
similarity index 72%
rename from assets/guide_pve_images_readme.md.0fcbd5ad.lean.js
rename to assets/guide_pve_images_readme.md.db0a99a0.lean.js
index 3d530baf18..246d1744b3 100644
--- a/assets/guide_pve_images_readme.md.0fcbd5ad.lean.js
+++ b/assets/guide_pve_images_readme.md.db0a99a0.lean.js
@@ -1 +1 @@
-import{_ as e,v as a,b as t,F as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/pve/images/readme.md","filePath":"guide/pve/images/readme.md","lastUpdated":1747726389000}'),d={name:"guide/pve/images/readme.md"},r=s("p",null,"暂存图片",-1),i=[r];function n(o,m,p,_,c,l){return a(),t("div",null,i)}const g=e(d,[["render",n]]);export{f as __pageData,g as default};
+import{_ as e,v as a,b as t,F as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/pve/images/readme.md","filePath":"guide/pve/images/readme.md","lastUpdated":1747730955000}'),d={name:"guide/pve/images/readme.md"},r=s("p",null,"暂存图片",-1),i=[r];function n(o,m,p,_,c,l){return a(),t("div",null,i)}const g=e(d,[["render",n]]);export{f as __pageData,g as default};
diff --git a/assets/guide_pve_pve_android.md.541a2bf0.js b/assets/guide_pve_pve_android.md.579cbfc0.js
similarity index 99%
rename from assets/guide_pve_pve_android.md.541a2bf0.js
rename to assets/guide_pve_pve_android.md.579cbfc0.js
index 12709408c0..dbf854f65e 100644
--- a/assets/guide_pve_pve_android.md.541a2bf0.js
+++ b/assets/guide_pve_pve_android.md.579cbfc0.js
@@ -1 +1 @@
-import{_ as s,v as p,b as e,R as o}from"./chunks/framework.70afa331.js";const a="/assets/a1.662d9415.png",t="/assets/a2.1d7d86db.png",c="/assets/a3.178777a1.png",d="/assets/a4.65c15963.png",r="/assets/a5.01b8514f.png",i="/assets/a6.67efded0.png",n="/assets/a7.b8de9a6c.png",l="/assets/a8.69056d9a.png",m="/assets/a9.d4cc5fc0.png",g="/assets/a10.36860678.png",_="/assets/a11.bbc20080.png",b="/assets/a12.da46fe54.png",h="/assets/a13.b49276aa.png",f="/assets/a14.908480a6.png",u="/assets/a15.9533f30d.png",x="/assets/a16.2257f2d8.png",q="/assets/a17.b57c7755.png",I="/assets/a18.c3a22602.png",O="/assets/a19.1eefd81d.png",P="/assets/a20.24042237.png",C="/assets/a21.2bb37c9a.png",A="/assets/a22.44ab6d75.png",v="/assets/a23.191de0ca.png",k="/assets/a24.d2a9c729.png",G="/assets/a25.3e24d99b.png",V="/assets/a26.2fce6332.png",w="/assets/ar.0d8bb8f3.png",y="/assets/a27.dd61884c.png",F="/assets/a31.6d3a9d85.png",K="/assets/a32.d9973307.png",U="/assets/a33.8b54ce3f.png",D="/assets/a34.07f5cc75.png",B="/assets/a35.78be61d4.png",E="/assets/a36.a36765c2.png",S="/assets/a37.e6740eaa.png",N="/assets/a38.999b4ffb.png",M="/assets/a39.9dac95e1.png",R="/assets/a40.7f5ad4ea.png",L="/assets/a41.bbc5e317.png",T="/assets/a42.de7d1da7.png",W="/assets/a43.e713599d.png",z="/assets/a44.5c4e5e0a.png",j="/assets/a45.2c32612e.png",Q="/assets/b1.c1fdb506.png",$="/assets/b2.519a9bf0.png",Y="/assets/b3.42fd37a2.png",H="/assets/b4.b6d283a7.png",J="/assets/b5.4cd5361f.png",X="/assets/b6.36f0470d.png",Z="/assets/b7.9714bb16.png",ss="/assets/b8.2eb373bf.png",ps="/assets/b9.3f01ffdc.png",es="/assets/b10.52a93636.png",os="/assets/b11.2e525d8d.png",as="/assets/b12.54c3189d.png",ts="/assets/b13.3b3ae784.png",cs="/assets/b14.662b1a1b.png",ds="/assets/b15.0c5536d8.png",rs="/assets/b16.0fbcfcb1.png",is="/assets/b17.4e7429fe.png",ns="/assets/b18.8211f293.png",ls="/assets/b19.2128d0fa.png",ms="/assets/b20.8a62698b.png",gs="/assets/b21.dfe1e8f0.png",_s="/assets/b22.13e3438c.png",bs="/assets/b23.e293a560.png",hs="/assets/b24.23cbc29a.png",fs="/assets/b25.f2c2ebd7.png",us="/assets/b26.b7136167.png",xs="/assets/b27.cc8f8644.png",qs="/assets/b28.2bf4d8b9.png",Is="/assets/b29.8d301c10.png",Os="/assets/b30.a50bc8f3.png",Ps="/assets/b31.4881ca1d.png",Cs="/assets/b32.b857654b.png",As="/assets/b33.1125a81c.png",vs="/assets/b34.2101ce9a.png",ks="/assets/b35.83c5a766.png",Gs="/assets/b36.ea1f048c.png",Vs="/assets/b37.b60405a9.png",ws="/assets/br.bb3418b4.png",ys="/assets/b38.4d73fbe3.png",Fs="/assets/b39.c59ccabe.png",Ks="/assets/b40.c1d0ee00.png",Us="/assets/b41.0c6d7432.png",Ds="/assets/b42.66cc353b.png",Bs="/assets/b43.a775b641.png",Es="/assets/b44.2d540844.png",Ss="/assets/b45.fe0240c6.png",Ns="/assets/b46.f6b9da14.png",Js=JSON.parse('{"title":"Android 虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_android.md","filePath":"guide/pve/pve_android.md","lastUpdated":1747726389000}'),Ms={name:"guide/pve/pve_android.md"},Rs=o('
Android 虚拟机 ​
安卓系统镜像下载 ​
Android系统版本9及以前的镜像下载地址：
国际
https://www.fosshub.com/Android-x86.html
https://sourceforge.net/projects/android-x86/files/
国内
https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/
Android系统版本10及以后的新镜像下载地址：
https://blissos.org/index.html#download
虚拟机开设 ​
以安卓版本9及以前的镜像开设Android虚拟机 ​
本指南以
https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/71931/android-x86_64-9.0-rc2.iso
作为示例进行演示
1
模板设置 ​
开设VMID为100的虚拟机选择对应的存储盘
2
选择安卓镜像，然后Type选择Linux，Version选择含2.6版本的选项
3
Graphic card选择Vmware compatible，其他选项选择默认如图所示
4
磁盘格式选择SATA，具体需要分配多大的磁盘自选，推荐至少30G
5
CPU数量至少2核
如果你的宿主机支持嵌套虚拟化，CPU的类型请选择host(经验证无问题)
如果你的宿主机不支持嵌套虚拟化，CPU的类型请选择qemu64，同时在模板设置成功后，需要在Options中点击KVM hardware virtualization取消勾选后再启动虚拟机(不保证后面系统初始化无问题)
6
内存至少4G内存，填写至少4096
7
绑定的网桥选择vmbr1，Model选择VirtIO (paravirtualized)，取消Firewall的勾选
8
后续点击continue按钮后，模板成功创建出来，需要手动点击启动并进入VNC界面
9
系统安装 ​
进入引导后，选择Installation开头的选项
10
然后需要创建分区写入，这块如果选择不了的话按键盘按钮c，就能选中了
11
选择不使用GPT格式
12
显示空白盘后，选择New
13
选择分区类型Primary
14
然后会提示划分多大的空间，默认回车就行，使用全部的空间
15
然后是选择Flags，移动到Bootable后，按回车，直到Flags下方显示Boot
16
然后移动到Write，回车，进行写入
17
这时候会让你确认是否继续，输入yes后回车继续
18
一段进度条跑过后，回到了最初的菜单，选择Quit退出菜单，一切准备就绪了
19
然后这时候回到了UI界面，使用前面初始化好的盘，选择OK按钮回车
20
文件系统按方向键选择ext4类型，选择OK按钮回车
21
确认进行格式化，选择Yes按钮回车
22
确认GRUB引导安装，选择OK按钮回车
23
确认文件系统可读写，选择OK按钮回车
24
跑了一段时间进度条后，显示安装成功，此时选择Reboot，选择OK按钮回车
25
然后一段时间后进入安卓LOGO界面
26
镜像移除 ​
然后会进入一段黑屏，大概3~5分钟后仍然黑屏的话，宿主机执行qm stop 100，然后开始移除镜像文件
移除已经按照完毕的ISO文件，在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]
ar
然后宿主机再执行qm start 100，然后应该就会进入安卓系统的初始化界面了
系统初始化 ​
初始化界面选择语言，然后点击确定按钮
27
此时回尝试连接WIFI，由于本项目安装的PVE是完全的静态网络配置，直接跳过，稍后再进行设置
31
点击下一步按钮确认设置时间
32
点击取消屏幕保护，确认仍然跳过
33
然后一段时间黑屏后，会出现主屏幕应用的选择，如果等待3~5分钟这个界面仍然没有出现，那么像之前那样重启虚拟机，再进入VNC应该就会显示了
选择Quickstep
34
网络设置 ​
进入桌面，此时需要开始设置网络，左上角点击设置图标
35
出现下拉框，点击按住下拉
36
点击齿轮按钮
37
进入网络和互联网设置
38
左键双击WIFI
39
修改目前识别到的VirtWIFI，右键点击出现选择框后，点击修改网络
40
出现高级选项，点击打开隐藏的选项
41
如图进行对应的网络设置
IP地址 172.16.1.xxx(xxx换成你想绑定的ip，我的vmid是100，为了方便写了100)
子网掩码 24
默认网关 172.16.1.1
DNS 8.8.8.8 或 144.144.144.144
然后点击保存按钮
42
此时出来后可能仍然未应用设置，点击关闭WIFI后，再启用WIFI，应该就会显示已连接
43
然后退出到主界面，点击谷歌浏览器，尝试打开一个网页
44
可以看到打开本指南的网址无问题，证明网络已联通
45
以安卓版本10及以后的新镜像开设Android虚拟机 ​
本指南以
https://psychz.dl.sourceforge.net/project/blissos-x86/Official/BlissOS15/Gapps/Generic/Bliss-v15.9.2-x86_64-OFFICIAL-gapps-20241012.iso?viasf=1
作为示例进行演示
1
模板设置 ​
宿主机需要先执行以下命令安装图形环境依赖
shell
apt install libgl1 libegl1 -y
然后开始创建虚拟机，点击右上角的Create VM按钮，填写VMID、Name、Resource Pool
2
选择安卓镜像，然后Type选择Linux，Version选择含2.6版本的选项
3
如果宿主机本身携带有GPU，那么Graphic card选择VirGL GPU。
如果宿主机本身不携带GPU，那么Graphic card选择VirtIO或Vmware compatible。
Machine选择q35，BIOS选择OVMF (UEFI)启动，EFI Storage选择local。
4
磁盘格式选择SATA，具体需要分配多大的磁盘自选，推荐至少30G
5
CPU数量至少2核
如果你的宿主机支持嵌套虚拟化，CPU的类型请选择host(经验证无问题)
如果你的宿主机不支持嵌套虚拟化，CPU的类型请选择qemu64，同时在模板设置成功后，需要在Options中点击KVM hardware virtualization取消勾选后再启动虚拟机(不保证后面系统初始化无问题)
6
内存至少4G内存，填写至少4096
7
绑定的网桥选择vmbr1，Model选择VirtIO (paravirtualized)，取消Firewall的勾选
8
后续点击continue按钮后，模板成功创建出来，需要手动点击启动并进入VNC界面。
系统安装 ​
进入引导后，选择Installation结尾的选项
9
然后需要创建分区写入，这块如果选择不了的话按键盘按钮c，就能选中了。
10
选择不使用GPT格式，依然使用cfdisk格式。
11
显示格式选择框，选择gpt。
12
显示空白盘后，选择New。
13
因为要划分EFI分区，这个盘需要修改大小，不能使用默认大小，数字改成1就行，分配1G硬盘，然后按回车。
14
然后回到了菜单栏，按方向键选择Type，然后回车，给分区选择格式类型
15
按方向键选择第一个选项EFI System，然后回车
16
此时回到菜单栏，页面上半部分就能看到具体的分区大小和格式
17
然后按下方向键，选择下一行空白的分区
18
菜单栏选择New，然后回车
19
这块需要填写分区大小，此时对照右上角选中的空白分区大小一致即可，然后回车。
20
回到菜单栏，选择Write，回车，写入分区。
21
会提示你输入yes进行确认，输入后回车。
22
然后一段进度条跑过，应该会回到菜单栏，选择Quit退出菜单，一切准备就绪了
23
然后这时候回到了UI界面，使用前面初始化好的1GB大小的盘，选择OK按钮回车。
24
文件系统按方向键选择fat32类型，选择OK按钮回车
25
确认不修改名字，选择OK按钮回车
26
确认进行格式化，选择Yes按钮回车
27
然后回到最初的UI栏，选择第二块不是1GB大小的分区，选择OK按钮回车
28
文件系统按方向键选择ext4类型，选择OK按钮回车
29
确认不修改名字，选择OK按钮回车
30
确认进行格式化，选择Yes按钮回车
31
默认不使用额外空间更新，选择No按钮回车
32
确认GRUB2 EFI BootLoader，选择OK按钮回车
33
跑了一段时间进度条后，显示安装成功，此时选择Reboot，选择OK按钮回车。
34
系统初始化 ​
然后一段时间后进入LOGO界面。
35
再过一段时间，应该就会进入初始的安卓界面了，能看到弹窗和时间，按住左键上划
36
会出现主屏幕应用的选择，选择Quickstep
如果等待3~5分钟这个界面仍然没有出现，那么就重启虚拟机，再进入VNC应该就会显示了
37
镜像移除 ​
出现了安卓的界面后，宿主机执行qm stop 100，然后开始移除镜像文件。
移除已经按照完毕的ISO文件，在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]
br
然后宿主机再执行qm start 100，然后应该就会进入系统的初始界面了。
网络设置 ​
进入桌面，此时需要开始设置网络，图示位置按住左键，上划
38
弹出一堆应用，在里面找到那个叫做Bliss Ethernet Manager的应用，点击并打开
39
IP Assignment点击打开，选择Static类型，点击OK按钮确认
40
IP Address点击打开，填入172.16.1.xxx/24(xxx我写的100，因为这里我的虚拟机VMID是100方便区分)，点击OK按钮确认
41
Gateway Address点击打开，填入172.16.1.1，点击OK按钮确认
42
DNS Address点击打开，填入8.8.8.8，点击OK按钮确认
43
然后在应用界面中，点击Interface Up和Refresh，然后键盘按exit键退出程序
44
主界面中打开浏览器，验证网络是否畅通
45
可以看到打开本指南无问题，网络畅通
46
',227),Ls=[Rs];function Ts(Ws,zs,js,Qs,$s,Ys){return p(),e("div",null,Ls)}const Xs=s(Ms,[["render",Ts]]);export{Js as __pageData,Xs as default};
+import{_ as s,v as p,b as e,R as o}from"./chunks/framework.70afa331.js";const a="/assets/a1.662d9415.png",t="/assets/a2.1d7d86db.png",c="/assets/a3.178777a1.png",d="/assets/a4.65c15963.png",r="/assets/a5.01b8514f.png",i="/assets/a6.67efded0.png",n="/assets/a7.b8de9a6c.png",l="/assets/a8.69056d9a.png",m="/assets/a9.d4cc5fc0.png",g="/assets/a10.36860678.png",_="/assets/a11.bbc20080.png",b="/assets/a12.da46fe54.png",h="/assets/a13.b49276aa.png",f="/assets/a14.908480a6.png",u="/assets/a15.9533f30d.png",x="/assets/a16.2257f2d8.png",q="/assets/a17.b57c7755.png",I="/assets/a18.c3a22602.png",O="/assets/a19.1eefd81d.png",P="/assets/a20.24042237.png",C="/assets/a21.2bb37c9a.png",A="/assets/a22.44ab6d75.png",v="/assets/a23.191de0ca.png",k="/assets/a24.d2a9c729.png",G="/assets/a25.3e24d99b.png",V="/assets/a26.2fce6332.png",w="/assets/ar.0d8bb8f3.png",y="/assets/a27.dd61884c.png",F="/assets/a31.6d3a9d85.png",K="/assets/a32.d9973307.png",U="/assets/a33.8b54ce3f.png",D="/assets/a34.07f5cc75.png",B="/assets/a35.78be61d4.png",E="/assets/a36.a36765c2.png",S="/assets/a37.e6740eaa.png",N="/assets/a38.999b4ffb.png",M="/assets/a39.9dac95e1.png",R="/assets/a40.7f5ad4ea.png",L="/assets/a41.bbc5e317.png",T="/assets/a42.de7d1da7.png",W="/assets/a43.e713599d.png",z="/assets/a44.5c4e5e0a.png",j="/assets/a45.2c32612e.png",Q="/assets/b1.c1fdb506.png",$="/assets/b2.519a9bf0.png",Y="/assets/b3.42fd37a2.png",H="/assets/b4.b6d283a7.png",J="/assets/b5.4cd5361f.png",X="/assets/b6.36f0470d.png",Z="/assets/b7.9714bb16.png",ss="/assets/b8.2eb373bf.png",ps="/assets/b9.3f01ffdc.png",es="/assets/b10.52a93636.png",os="/assets/b11.2e525d8d.png",as="/assets/b12.54c3189d.png",ts="/assets/b13.3b3ae784.png",cs="/assets/b14.662b1a1b.png",ds="/assets/b15.0c5536d8.png",rs="/assets/b16.0fbcfcb1.png",is="/assets/b17.4e7429fe.png",ns="/assets/b18.8211f293.png",ls="/assets/b19.2128d0fa.png",ms="/assets/b20.8a62698b.png",gs="/assets/b21.dfe1e8f0.png",_s="/assets/b22.13e3438c.png",bs="/assets/b23.e293a560.png",hs="/assets/b24.23cbc29a.png",fs="/assets/b25.f2c2ebd7.png",us="/assets/b26.b7136167.png",xs="/assets/b27.cc8f8644.png",qs="/assets/b28.2bf4d8b9.png",Is="/assets/b29.8d301c10.png",Os="/assets/b30.a50bc8f3.png",Ps="/assets/b31.4881ca1d.png",Cs="/assets/b32.b857654b.png",As="/assets/b33.1125a81c.png",vs="/assets/b34.2101ce9a.png",ks="/assets/b35.83c5a766.png",Gs="/assets/b36.ea1f048c.png",Vs="/assets/b37.b60405a9.png",ws="/assets/br.bb3418b4.png",ys="/assets/b38.4d73fbe3.png",Fs="/assets/b39.c59ccabe.png",Ks="/assets/b40.c1d0ee00.png",Us="/assets/b41.0c6d7432.png",Ds="/assets/b42.66cc353b.png",Bs="/assets/b43.a775b641.png",Es="/assets/b44.2d540844.png",Ss="/assets/b45.fe0240c6.png",Ns="/assets/b46.f6b9da14.png",Js=JSON.parse('{"title":"Android 虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_android.md","filePath":"guide/pve/pve_android.md","lastUpdated":1747730955000}'),Ms={name:"guide/pve/pve_android.md"},Rs=o('
Android 虚拟机 ​
安卓系统镜像下载 ​
Android系统版本9及以前的镜像下载地址：
国际
https://www.fosshub.com/Android-x86.html
https://sourceforge.net/projects/android-x86/files/
国内
https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/
Android系统版本10及以后的新镜像下载地址：
https://blissos.org/index.html#download
虚拟机开设 ​
以安卓版本9及以前的镜像开设Android虚拟机 ​
本指南以
https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/71931/android-x86_64-9.0-rc2.iso
作为示例进行演示
1
模板设置 ​
开设VMID为100的虚拟机选择对应的存储盘
2
选择安卓镜像，然后Type选择Linux，Version选择含2.6版本的选项
3
Graphic card选择Vmware compatible，其他选项选择默认如图所示
4
磁盘格式选择SATA，具体需要分配多大的磁盘自选，推荐至少30G
5
CPU数量至少2核
如果你的宿主机支持嵌套虚拟化，CPU的类型请选择host(经验证无问题)
如果你的宿主机不支持嵌套虚拟化，CPU的类型请选择qemu64，同时在模板设置成功后，需要在Options中点击KVM hardware virtualization取消勾选后再启动虚拟机(不保证后面系统初始化无问题)
6
内存至少4G内存，填写至少4096
7
绑定的网桥选择vmbr1，Model选择VirtIO (paravirtualized)，取消Firewall的勾选
8
后续点击continue按钮后，模板成功创建出来，需要手动点击启动并进入VNC界面
9
系统安装 ​
进入引导后，选择Installation开头的选项
10
然后需要创建分区写入，这块如果选择不了的话按键盘按钮c，就能选中了
11
选择不使用GPT格式
12
显示空白盘后，选择New
13
选择分区类型Primary
14
然后会提示划分多大的空间，默认回车就行，使用全部的空间
15
然后是选择Flags，移动到Bootable后，按回车，直到Flags下方显示Boot
16
然后移动到Write，回车，进行写入
17
这时候会让你确认是否继续，输入yes后回车继续
18
一段进度条跑过后，回到了最初的菜单，选择Quit退出菜单，一切准备就绪了
19
然后这时候回到了UI界面，使用前面初始化好的盘，选择OK按钮回车
20
文件系统按方向键选择ext4类型，选择OK按钮回车
21
确认进行格式化，选择Yes按钮回车
22
确认GRUB引导安装，选择OK按钮回车
23
确认文件系统可读写，选择OK按钮回车
24
跑了一段时间进度条后，显示安装成功，此时选择Reboot，选择OK按钮回车
25
然后一段时间后进入安卓LOGO界面
26
镜像移除 ​
然后会进入一段黑屏，大概3~5分钟后仍然黑屏的话，宿主机执行qm stop 100，然后开始移除镜像文件
移除已经按照完毕的ISO文件，在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]
ar
然后宿主机再执行qm start 100，然后应该就会进入安卓系统的初始化界面了
系统初始化 ​
初始化界面选择语言，然后点击确定按钮
27
此时回尝试连接WIFI，由于本项目安装的PVE是完全的静态网络配置，直接跳过，稍后再进行设置
31
点击下一步按钮确认设置时间
32
点击取消屏幕保护，确认仍然跳过
33
然后一段时间黑屏后，会出现主屏幕应用的选择，如果等待3~5分钟这个界面仍然没有出现，那么像之前那样重启虚拟机，再进入VNC应该就会显示了
选择Quickstep
34
网络设置 ​
进入桌面，此时需要开始设置网络，左上角点击设置图标
35
出现下拉框，点击按住下拉
36
点击齿轮按钮
37
进入网络和互联网设置
38
左键双击WIFI
39
修改目前识别到的VirtWIFI，右键点击出现选择框后，点击修改网络
40
出现高级选项，点击打开隐藏的选项
41
如图进行对应的网络设置
IP地址 172.16.1.xxx(xxx换成你想绑定的ip，我的vmid是100，为了方便写了100)
子网掩码 24
默认网关 172.16.1.1
DNS 8.8.8.8 或 144.144.144.144
然后点击保存按钮
42
此时出来后可能仍然未应用设置，点击关闭WIFI后，再启用WIFI，应该就会显示已连接
43
然后退出到主界面，点击谷歌浏览器，尝试打开一个网页
44
可以看到打开本指南的网址无问题，证明网络已联通
45
以安卓版本10及以后的新镜像开设Android虚拟机 ​
本指南以
https://psychz.dl.sourceforge.net/project/blissos-x86/Official/BlissOS15/Gapps/Generic/Bliss-v15.9.2-x86_64-OFFICIAL-gapps-20241012.iso?viasf=1
作为示例进行演示
1
模板设置 ​
宿主机需要先执行以下命令安装图形环境依赖
shell
apt install libgl1 libegl1 -y
然后开始创建虚拟机，点击右上角的Create VM按钮，填写VMID、Name、Resource Pool
2
选择安卓镜像，然后Type选择Linux，Version选择含2.6版本的选项
3
如果宿主机本身携带有GPU，那么Graphic card选择VirGL GPU。
如果宿主机本身不携带GPU，那么Graphic card选择VirtIO或Vmware compatible。
Machine选择q35，BIOS选择OVMF (UEFI)启动，EFI Storage选择local。
4
磁盘格式选择SATA，具体需要分配多大的磁盘自选，推荐至少30G
5
CPU数量至少2核
如果你的宿主机支持嵌套虚拟化，CPU的类型请选择host(经验证无问题)
如果你的宿主机不支持嵌套虚拟化，CPU的类型请选择qemu64，同时在模板设置成功后，需要在Options中点击KVM hardware virtualization取消勾选后再启动虚拟机(不保证后面系统初始化无问题)
6
内存至少4G内存，填写至少4096
7
绑定的网桥选择vmbr1，Model选择VirtIO (paravirtualized)，取消Firewall的勾选
8
后续点击continue按钮后，模板成功创建出来，需要手动点击启动并进入VNC界面。
系统安装 ​
进入引导后，选择Installation结尾的选项
9
然后需要创建分区写入，这块如果选择不了的话按键盘按钮c，就能选中了。
10
选择不使用GPT格式，依然使用cfdisk格式。
11
显示格式选择框，选择gpt。
12
显示空白盘后，选择New。
13
因为要划分EFI分区，这个盘需要修改大小，不能使用默认大小，数字改成1就行，分配1G硬盘，然后按回车。
14
然后回到了菜单栏，按方向键选择Type，然后回车，给分区选择格式类型
15
按方向键选择第一个选项EFI System，然后回车
16
此时回到菜单栏，页面上半部分就能看到具体的分区大小和格式
17
然后按下方向键，选择下一行空白的分区
18
菜单栏选择New，然后回车
19
这块需要填写分区大小，此时对照右上角选中的空白分区大小一致即可，然后回车。
20
回到菜单栏，选择Write，回车，写入分区。
21
会提示你输入yes进行确认，输入后回车。
22
然后一段进度条跑过，应该会回到菜单栏，选择Quit退出菜单，一切准备就绪了
23
然后这时候回到了UI界面，使用前面初始化好的1GB大小的盘，选择OK按钮回车。
24
文件系统按方向键选择fat32类型，选择OK按钮回车
25
确认不修改名字，选择OK按钮回车
26
确认进行格式化，选择Yes按钮回车
27
然后回到最初的UI栏，选择第二块不是1GB大小的分区，选择OK按钮回车
28
文件系统按方向键选择ext4类型，选择OK按钮回车
29
确认不修改名字，选择OK按钮回车
30
确认进行格式化，选择Yes按钮回车
31
默认不使用额外空间更新，选择No按钮回车
32
确认GRUB2 EFI BootLoader，选择OK按钮回车
33
跑了一段时间进度条后，显示安装成功，此时选择Reboot，选择OK按钮回车。
34
系统初始化 ​
然后一段时间后进入LOGO界面。
35
再过一段时间，应该就会进入初始的安卓界面了，能看到弹窗和时间，按住左键上划
36
会出现主屏幕应用的选择，选择Quickstep
如果等待3~5分钟这个界面仍然没有出现，那么就重启虚拟机，再进入VNC应该就会显示了
37
镜像移除 ​
出现了安卓的界面后，宿主机执行qm stop 100，然后开始移除镜像文件。
移除已经按照完毕的ISO文件，在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]
br
然后宿主机再执行qm start 100，然后应该就会进入系统的初始界面了。
网络设置 ​
进入桌面，此时需要开始设置网络，图示位置按住左键，上划
38
弹出一堆应用，在里面找到那个叫做Bliss Ethernet Manager的应用，点击并打开
39
IP Assignment点击打开，选择Static类型，点击OK按钮确认
40
IP Address点击打开，填入172.16.1.xxx/24(xxx我写的100，因为这里我的虚拟机VMID是100方便区分)，点击OK按钮确认
41
Gateway Address点击打开，填入172.16.1.1，点击OK按钮确认
42
DNS Address点击打开，填入8.8.8.8，点击OK按钮确认
43
然后在应用界面中，点击Interface Up和Refresh，然后键盘按exit键退出程序
44
主界面中打开浏览器，验证网络是否畅通
45
可以看到打开本指南无问题，网络畅通
46
',227),Ls=[Rs];function Ts(Ws,zs,js,Qs,$s,Ys){return p(),e("div",null,Ls)}const Xs=s(Ms,[["render",Ts]]);export{Js as __pageData,Xs as default};
diff --git a/assets/guide_pve_pve_android.md.541a2bf0.lean.js b/assets/guide_pve_pve_android.md.579cbfc0.lean.js
similarity index 99%
rename from assets/guide_pve_pve_android.md.541a2bf0.lean.js
rename to assets/guide_pve_pve_android.md.579cbfc0.lean.js
index 12709408c0..dbf854f65e 100644
--- a/assets/guide_pve_pve_android.md.541a2bf0.lean.js
+++ b/assets/guide_pve_pve_android.md.579cbfc0.lean.js
@@ -1 +1 @@
-import{_ as s,v as p,b as e,R as o}from"./chunks/framework.70afa331.js";const a="/assets/a1.662d9415.png",t="/assets/a2.1d7d86db.png",c="/assets/a3.178777a1.png",d="/assets/a4.65c15963.png",r="/assets/a5.01b8514f.png",i="/assets/a6.67efded0.png",n="/assets/a7.b8de9a6c.png",l="/assets/a8.69056d9a.png",m="/assets/a9.d4cc5fc0.png",g="/assets/a10.36860678.png",_="/assets/a11.bbc20080.png",b="/assets/a12.da46fe54.png",h="/assets/a13.b49276aa.png",f="/assets/a14.908480a6.png",u="/assets/a15.9533f30d.png",x="/assets/a16.2257f2d8.png",q="/assets/a17.b57c7755.png",I="/assets/a18.c3a22602.png",O="/assets/a19.1eefd81d.png",P="/assets/a20.24042237.png",C="/assets/a21.2bb37c9a.png",A="/assets/a22.44ab6d75.png",v="/assets/a23.191de0ca.png",k="/assets/a24.d2a9c729.png",G="/assets/a25.3e24d99b.png",V="/assets/a26.2fce6332.png",w="/assets/ar.0d8bb8f3.png",y="/assets/a27.dd61884c.png",F="/assets/a31.6d3a9d85.png",K="/assets/a32.d9973307.png",U="/assets/a33.8b54ce3f.png",D="/assets/a34.07f5cc75.png",B="/assets/a35.78be61d4.png",E="/assets/a36.a36765c2.png",S="/assets/a37.e6740eaa.png",N="/assets/a38.999b4ffb.png",M="/assets/a39.9dac95e1.png",R="/assets/a40.7f5ad4ea.png",L="/assets/a41.bbc5e317.png",T="/assets/a42.de7d1da7.png",W="/assets/a43.e713599d.png",z="/assets/a44.5c4e5e0a.png",j="/assets/a45.2c32612e.png",Q="/assets/b1.c1fdb506.png",$="/assets/b2.519a9bf0.png",Y="/assets/b3.42fd37a2.png",H="/assets/b4.b6d283a7.png",J="/assets/b5.4cd5361f.png",X="/assets/b6.36f0470d.png",Z="/assets/b7.9714bb16.png",ss="/assets/b8.2eb373bf.png",ps="/assets/b9.3f01ffdc.png",es="/assets/b10.52a93636.png",os="/assets/b11.2e525d8d.png",as="/assets/b12.54c3189d.png",ts="/assets/b13.3b3ae784.png",cs="/assets/b14.662b1a1b.png",ds="/assets/b15.0c5536d8.png",rs="/assets/b16.0fbcfcb1.png",is="/assets/b17.4e7429fe.png",ns="/assets/b18.8211f293.png",ls="/assets/b19.2128d0fa.png",ms="/assets/b20.8a62698b.png",gs="/assets/b21.dfe1e8f0.png",_s="/assets/b22.13e3438c.png",bs="/assets/b23.e293a560.png",hs="/assets/b24.23cbc29a.png",fs="/assets/b25.f2c2ebd7.png",us="/assets/b26.b7136167.png",xs="/assets/b27.cc8f8644.png",qs="/assets/b28.2bf4d8b9.png",Is="/assets/b29.8d301c10.png",Os="/assets/b30.a50bc8f3.png",Ps="/assets/b31.4881ca1d.png",Cs="/assets/b32.b857654b.png",As="/assets/b33.1125a81c.png",vs="/assets/b34.2101ce9a.png",ks="/assets/b35.83c5a766.png",Gs="/assets/b36.ea1f048c.png",Vs="/assets/b37.b60405a9.png",ws="/assets/br.bb3418b4.png",ys="/assets/b38.4d73fbe3.png",Fs="/assets/b39.c59ccabe.png",Ks="/assets/b40.c1d0ee00.png",Us="/assets/b41.0c6d7432.png",Ds="/assets/b42.66cc353b.png",Bs="/assets/b43.a775b641.png",Es="/assets/b44.2d540844.png",Ss="/assets/b45.fe0240c6.png",Ns="/assets/b46.f6b9da14.png",Js=JSON.parse('{"title":"Android 虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_android.md","filePath":"guide/pve/pve_android.md","lastUpdated":1747726389000}'),Ms={name:"guide/pve/pve_android.md"},Rs=o('
Android 虚拟机 ​
安卓系统镜像下载 ​
Android系统版本9及以前的镜像下载地址：
国际
https://www.fosshub.com/Android-x86.html
https://sourceforge.net/projects/android-x86/files/
国内
https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/
Android系统版本10及以后的新镜像下载地址：
https://blissos.org/index.html#download
虚拟机开设 ​
以安卓版本9及以前的镜像开设Android虚拟机 ​
本指南以
https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/71931/android-x86_64-9.0-rc2.iso
作为示例进行演示
1
模板设置 ​
开设VMID为100的虚拟机选择对应的存储盘
2
选择安卓镜像，然后Type选择Linux，Version选择含2.6版本的选项
3
Graphic card选择Vmware compatible，其他选项选择默认如图所示
4
磁盘格式选择SATA，具体需要分配多大的磁盘自选，推荐至少30G
5
CPU数量至少2核
如果你的宿主机支持嵌套虚拟化，CPU的类型请选择host(经验证无问题)
如果你的宿主机不支持嵌套虚拟化，CPU的类型请选择qemu64，同时在模板设置成功后，需要在Options中点击KVM hardware virtualization取消勾选后再启动虚拟机(不保证后面系统初始化无问题)
6
内存至少4G内存，填写至少4096
7
绑定的网桥选择vmbr1，Model选择VirtIO (paravirtualized)，取消Firewall的勾选
8
后续点击continue按钮后，模板成功创建出来，需要手动点击启动并进入VNC界面
9
系统安装 ​
进入引导后，选择Installation开头的选项
10
然后需要创建分区写入，这块如果选择不了的话按键盘按钮c，就能选中了
11
选择不使用GPT格式
12
显示空白盘后，选择New
13
选择分区类型Primary
14
然后会提示划分多大的空间，默认回车就行，使用全部的空间
15
然后是选择Flags，移动到Bootable后，按回车，直到Flags下方显示Boot
16
然后移动到Write，回车，进行写入
17
这时候会让你确认是否继续，输入yes后回车继续
18
一段进度条跑过后，回到了最初的菜单，选择Quit退出菜单，一切准备就绪了
19
然后这时候回到了UI界面，使用前面初始化好的盘，选择OK按钮回车
20
文件系统按方向键选择ext4类型，选择OK按钮回车
21
确认进行格式化，选择Yes按钮回车
22
确认GRUB引导安装，选择OK按钮回车
23
确认文件系统可读写，选择OK按钮回车
24
跑了一段时间进度条后，显示安装成功，此时选择Reboot，选择OK按钮回车
25
然后一段时间后进入安卓LOGO界面
26
镜像移除 ​
然后会进入一段黑屏，大概3~5分钟后仍然黑屏的话，宿主机执行qm stop 100，然后开始移除镜像文件
移除已经按照完毕的ISO文件，在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]
ar
然后宿主机再执行qm start 100，然后应该就会进入安卓系统的初始化界面了
系统初始化 ​
初始化界面选择语言，然后点击确定按钮
27
此时回尝试连接WIFI，由于本项目安装的PVE是完全的静态网络配置，直接跳过，稍后再进行设置
31
点击下一步按钮确认设置时间
32
点击取消屏幕保护，确认仍然跳过
33
然后一段时间黑屏后，会出现主屏幕应用的选择，如果等待3~5分钟这个界面仍然没有出现，那么像之前那样重启虚拟机，再进入VNC应该就会显示了
选择Quickstep
34
网络设置 ​
进入桌面，此时需要开始设置网络，左上角点击设置图标
35
出现下拉框，点击按住下拉
36
点击齿轮按钮
37
进入网络和互联网设置
38
左键双击WIFI
39
修改目前识别到的VirtWIFI，右键点击出现选择框后，点击修改网络
40
出现高级选项，点击打开隐藏的选项
41
如图进行对应的网络设置
IP地址 172.16.1.xxx(xxx换成你想绑定的ip，我的vmid是100，为了方便写了100)
子网掩码 24
默认网关 172.16.1.1
DNS 8.8.8.8 或 144.144.144.144
然后点击保存按钮
42
此时出来后可能仍然未应用设置，点击关闭WIFI后，再启用WIFI，应该就会显示已连接
43
然后退出到主界面，点击谷歌浏览器，尝试打开一个网页
44
可以看到打开本指南的网址无问题，证明网络已联通
45
以安卓版本10及以后的新镜像开设Android虚拟机 ​
本指南以
https://psychz.dl.sourceforge.net/project/blissos-x86/Official/BlissOS15/Gapps/Generic/Bliss-v15.9.2-x86_64-OFFICIAL-gapps-20241012.iso?viasf=1
作为示例进行演示
1
模板设置 ​
宿主机需要先执行以下命令安装图形环境依赖
shell
apt install libgl1 libegl1 -y
然后开始创建虚拟机，点击右上角的Create VM按钮，填写VMID、Name、Resource Pool
2
选择安卓镜像，然后Type选择Linux，Version选择含2.6版本的选项
3
如果宿主机本身携带有GPU，那么Graphic card选择VirGL GPU。
如果宿主机本身不携带GPU，那么Graphic card选择VirtIO或Vmware compatible。
Machine选择q35，BIOS选择OVMF (UEFI)启动，EFI Storage选择local。
4
磁盘格式选择SATA，具体需要分配多大的磁盘自选，推荐至少30G
5
CPU数量至少2核
如果你的宿主机支持嵌套虚拟化，CPU的类型请选择host(经验证无问题)
如果你的宿主机不支持嵌套虚拟化，CPU的类型请选择qemu64，同时在模板设置成功后，需要在Options中点击KVM hardware virtualization取消勾选后再启动虚拟机(不保证后面系统初始化无问题)
6
内存至少4G内存，填写至少4096
7
绑定的网桥选择vmbr1，Model选择VirtIO (paravirtualized)，取消Firewall的勾选
8
后续点击continue按钮后，模板成功创建出来，需要手动点击启动并进入VNC界面。
系统安装 ​
进入引导后，选择Installation结尾的选项
9
然后需要创建分区写入，这块如果选择不了的话按键盘按钮c，就能选中了。
10
选择不使用GPT格式，依然使用cfdisk格式。
11
显示格式选择框，选择gpt。
12
显示空白盘后，选择New。
13
因为要划分EFI分区，这个盘需要修改大小，不能使用默认大小，数字改成1就行，分配1G硬盘，然后按回车。
14
然后回到了菜单栏，按方向键选择Type，然后回车，给分区选择格式类型
15
按方向键选择第一个选项EFI System，然后回车
16
此时回到菜单栏，页面上半部分就能看到具体的分区大小和格式
17
然后按下方向键，选择下一行空白的分区
18
菜单栏选择New，然后回车
19
这块需要填写分区大小，此时对照右上角选中的空白分区大小一致即可，然后回车。
20
回到菜单栏，选择Write，回车，写入分区。
21
会提示你输入yes进行确认，输入后回车。
22
然后一段进度条跑过，应该会回到菜单栏，选择Quit退出菜单，一切准备就绪了
23
然后这时候回到了UI界面，使用前面初始化好的1GB大小的盘，选择OK按钮回车。
24
文件系统按方向键选择fat32类型，选择OK按钮回车
25
确认不修改名字，选择OK按钮回车
26
确认进行格式化，选择Yes按钮回车
27
然后回到最初的UI栏，选择第二块不是1GB大小的分区，选择OK按钮回车
28
文件系统按方向键选择ext4类型，选择OK按钮回车
29
确认不修改名字，选择OK按钮回车
30
确认进行格式化，选择Yes按钮回车
31
默认不使用额外空间更新，选择No按钮回车
32
确认GRUB2 EFI BootLoader，选择OK按钮回车
33
跑了一段时间进度条后，显示安装成功，此时选择Reboot，选择OK按钮回车。
34
系统初始化 ​
然后一段时间后进入LOGO界面。
35
再过一段时间，应该就会进入初始的安卓界面了，能看到弹窗和时间，按住左键上划
36
会出现主屏幕应用的选择，选择Quickstep
如果等待3~5分钟这个界面仍然没有出现，那么就重启虚拟机，再进入VNC应该就会显示了
37
镜像移除 ​
出现了安卓的界面后，宿主机执行qm stop 100，然后开始移除镜像文件。
移除已经按照完毕的ISO文件，在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]
br
然后宿主机再执行qm start 100，然后应该就会进入系统的初始界面了。
网络设置 ​
进入桌面，此时需要开始设置网络，图示位置按住左键，上划
38
弹出一堆应用，在里面找到那个叫做Bliss Ethernet Manager的应用，点击并打开
39
IP Assignment点击打开，选择Static类型，点击OK按钮确认
40
IP Address点击打开，填入172.16.1.xxx/24(xxx我写的100，因为这里我的虚拟机VMID是100方便区分)，点击OK按钮确认
41
Gateway Address点击打开，填入172.16.1.1，点击OK按钮确认
42
DNS Address点击打开，填入8.8.8.8，点击OK按钮确认
43
然后在应用界面中，点击Interface Up和Refresh，然后键盘按exit键退出程序
44
主界面中打开浏览器，验证网络是否畅通
45
可以看到打开本指南无问题，网络畅通
46
',227),Ls=[Rs];function Ts(Ws,zs,js,Qs,$s,Ys){return p(),e("div",null,Ls)}const Xs=s(Ms,[["render",Ts]]);export{Js as __pageData,Xs as default};
+import{_ as s,v as p,b as e,R as o}from"./chunks/framework.70afa331.js";const a="/assets/a1.662d9415.png",t="/assets/a2.1d7d86db.png",c="/assets/a3.178777a1.png",d="/assets/a4.65c15963.png",r="/assets/a5.01b8514f.png",i="/assets/a6.67efded0.png",n="/assets/a7.b8de9a6c.png",l="/assets/a8.69056d9a.png",m="/assets/a9.d4cc5fc0.png",g="/assets/a10.36860678.png",_="/assets/a11.bbc20080.png",b="/assets/a12.da46fe54.png",h="/assets/a13.b49276aa.png",f="/assets/a14.908480a6.png",u="/assets/a15.9533f30d.png",x="/assets/a16.2257f2d8.png",q="/assets/a17.b57c7755.png",I="/assets/a18.c3a22602.png",O="/assets/a19.1eefd81d.png",P="/assets/a20.24042237.png",C="/assets/a21.2bb37c9a.png",A="/assets/a22.44ab6d75.png",v="/assets/a23.191de0ca.png",k="/assets/a24.d2a9c729.png",G="/assets/a25.3e24d99b.png",V="/assets/a26.2fce6332.png",w="/assets/ar.0d8bb8f3.png",y="/assets/a27.dd61884c.png",F="/assets/a31.6d3a9d85.png",K="/assets/a32.d9973307.png",U="/assets/a33.8b54ce3f.png",D="/assets/a34.07f5cc75.png",B="/assets/a35.78be61d4.png",E="/assets/a36.a36765c2.png",S="/assets/a37.e6740eaa.png",N="/assets/a38.999b4ffb.png",M="/assets/a39.9dac95e1.png",R="/assets/a40.7f5ad4ea.png",L="/assets/a41.bbc5e317.png",T="/assets/a42.de7d1da7.png",W="/assets/a43.e713599d.png",z="/assets/a44.5c4e5e0a.png",j="/assets/a45.2c32612e.png",Q="/assets/b1.c1fdb506.png",$="/assets/b2.519a9bf0.png",Y="/assets/b3.42fd37a2.png",H="/assets/b4.b6d283a7.png",J="/assets/b5.4cd5361f.png",X="/assets/b6.36f0470d.png",Z="/assets/b7.9714bb16.png",ss="/assets/b8.2eb373bf.png",ps="/assets/b9.3f01ffdc.png",es="/assets/b10.52a93636.png",os="/assets/b11.2e525d8d.png",as="/assets/b12.54c3189d.png",ts="/assets/b13.3b3ae784.png",cs="/assets/b14.662b1a1b.png",ds="/assets/b15.0c5536d8.png",rs="/assets/b16.0fbcfcb1.png",is="/assets/b17.4e7429fe.png",ns="/assets/b18.8211f293.png",ls="/assets/b19.2128d0fa.png",ms="/assets/b20.8a62698b.png",gs="/assets/b21.dfe1e8f0.png",_s="/assets/b22.13e3438c.png",bs="/assets/b23.e293a560.png",hs="/assets/b24.23cbc29a.png",fs="/assets/b25.f2c2ebd7.png",us="/assets/b26.b7136167.png",xs="/assets/b27.cc8f8644.png",qs="/assets/b28.2bf4d8b9.png",Is="/assets/b29.8d301c10.png",Os="/assets/b30.a50bc8f3.png",Ps="/assets/b31.4881ca1d.png",Cs="/assets/b32.b857654b.png",As="/assets/b33.1125a81c.png",vs="/assets/b34.2101ce9a.png",ks="/assets/b35.83c5a766.png",Gs="/assets/b36.ea1f048c.png",Vs="/assets/b37.b60405a9.png",ws="/assets/br.bb3418b4.png",ys="/assets/b38.4d73fbe3.png",Fs="/assets/b39.c59ccabe.png",Ks="/assets/b40.c1d0ee00.png",Us="/assets/b41.0c6d7432.png",Ds="/assets/b42.66cc353b.png",Bs="/assets/b43.a775b641.png",Es="/assets/b44.2d540844.png",Ss="/assets/b45.fe0240c6.png",Ns="/assets/b46.f6b9da14.png",Js=JSON.parse('{"title":"Android 虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_android.md","filePath":"guide/pve/pve_android.md","lastUpdated":1747730955000}'),Ms={name:"guide/pve/pve_android.md"},Rs=o('
Android 虚拟机 ​
安卓系统镜像下载 ​
Android系统版本9及以前的镜像下载地址：
国际
https://www.fosshub.com/Android-x86.html
https://sourceforge.net/projects/android-x86/files/
国内
https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/
Android系统版本10及以后的新镜像下载地址：
https://blissos.org/index.html#download
虚拟机开设 ​
以安卓版本9及以前的镜像开设Android虚拟机 ​
本指南以
https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/71931/android-x86_64-9.0-rc2.iso
作为示例进行演示
1
模板设置 ​
开设VMID为100的虚拟机选择对应的存储盘
2
选择安卓镜像，然后Type选择Linux，Version选择含2.6版本的选项
3
Graphic card选择Vmware compatible，其他选项选择默认如图所示
4
磁盘格式选择SATA，具体需要分配多大的磁盘自选，推荐至少30G
5
CPU数量至少2核
如果你的宿主机支持嵌套虚拟化，CPU的类型请选择host(经验证无问题)
如果你的宿主机不支持嵌套虚拟化，CPU的类型请选择qemu64，同时在模板设置成功后，需要在Options中点击KVM hardware virtualization取消勾选后再启动虚拟机(不保证后面系统初始化无问题)
6
内存至少4G内存，填写至少4096
7
绑定的网桥选择vmbr1，Model选择VirtIO (paravirtualized)，取消Firewall的勾选
8
后续点击continue按钮后，模板成功创建出来，需要手动点击启动并进入VNC界面
9
系统安装 ​
进入引导后，选择Installation开头的选项
10
然后需要创建分区写入，这块如果选择不了的话按键盘按钮c，就能选中了
11
选择不使用GPT格式
12
显示空白盘后，选择New
13
选择分区类型Primary
14
然后会提示划分多大的空间，默认回车就行，使用全部的空间
15
然后是选择Flags，移动到Bootable后，按回车，直到Flags下方显示Boot
16
然后移动到Write，回车，进行写入
17
这时候会让你确认是否继续，输入yes后回车继续
18
一段进度条跑过后，回到了最初的菜单，选择Quit退出菜单，一切准备就绪了
19
然后这时候回到了UI界面，使用前面初始化好的盘，选择OK按钮回车
20
文件系统按方向键选择ext4类型，选择OK按钮回车
21
确认进行格式化，选择Yes按钮回车
22
确认GRUB引导安装，选择OK按钮回车
23
确认文件系统可读写，选择OK按钮回车
24
跑了一段时间进度条后，显示安装成功，此时选择Reboot，选择OK按钮回车
25
然后一段时间后进入安卓LOGO界面
26
镜像移除 ​
然后会进入一段黑屏，大概3~5分钟后仍然黑屏的话，宿主机执行qm stop 100，然后开始移除镜像文件
移除已经按照完毕的ISO文件，在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]
ar
然后宿主机再执行qm start 100，然后应该就会进入安卓系统的初始化界面了
系统初始化 ​
初始化界面选择语言，然后点击确定按钮
27
此时回尝试连接WIFI，由于本项目安装的PVE是完全的静态网络配置，直接跳过，稍后再进行设置
31
点击下一步按钮确认设置时间
32
点击取消屏幕保护，确认仍然跳过
33
然后一段时间黑屏后，会出现主屏幕应用的选择，如果等待3~5分钟这个界面仍然没有出现，那么像之前那样重启虚拟机，再进入VNC应该就会显示了
选择Quickstep
34
网络设置 ​
进入桌面，此时需要开始设置网络，左上角点击设置图标
35
出现下拉框，点击按住下拉
36
点击齿轮按钮
37
进入网络和互联网设置
38
左键双击WIFI
39
修改目前识别到的VirtWIFI，右键点击出现选择框后，点击修改网络
40
出现高级选项，点击打开隐藏的选项
41
如图进行对应的网络设置
IP地址 172.16.1.xxx(xxx换成你想绑定的ip，我的vmid是100，为了方便写了100)
子网掩码 24
默认网关 172.16.1.1
DNS 8.8.8.8 或 144.144.144.144
然后点击保存按钮
42
此时出来后可能仍然未应用设置，点击关闭WIFI后，再启用WIFI，应该就会显示已连接
43
然后退出到主界面，点击谷歌浏览器，尝试打开一个网页
44
可以看到打开本指南的网址无问题，证明网络已联通
45
以安卓版本10及以后的新镜像开设Android虚拟机 ​
本指南以
https://psychz.dl.sourceforge.net/project/blissos-x86/Official/BlissOS15/Gapps/Generic/Bliss-v15.9.2-x86_64-OFFICIAL-gapps-20241012.iso?viasf=1
作为示例进行演示
1
模板设置 ​
宿主机需要先执行以下命令安装图形环境依赖
shell
apt install libgl1 libegl1 -y
然后开始创建虚拟机，点击右上角的Create VM按钮，填写VMID、Name、Resource Pool
2
选择安卓镜像，然后Type选择Linux，Version选择含2.6版本的选项
3
如果宿主机本身携带有GPU，那么Graphic card选择VirGL GPU。
如果宿主机本身不携带GPU，那么Graphic card选择VirtIO或Vmware compatible。
Machine选择q35，BIOS选择OVMF (UEFI)启动，EFI Storage选择local。
4
磁盘格式选择SATA，具体需要分配多大的磁盘自选，推荐至少30G
5
CPU数量至少2核
如果你的宿主机支持嵌套虚拟化，CPU的类型请选择host(经验证无问题)
如果你的宿主机不支持嵌套虚拟化，CPU的类型请选择qemu64，同时在模板设置成功后，需要在Options中点击KVM hardware virtualization取消勾选后再启动虚拟机(不保证后面系统初始化无问题)
6
内存至少4G内存，填写至少4096
7
绑定的网桥选择vmbr1，Model选择VirtIO (paravirtualized)，取消Firewall的勾选
8
后续点击continue按钮后，模板成功创建出来，需要手动点击启动并进入VNC界面。
系统安装 ​
进入引导后，选择Installation结尾的选项
9
然后需要创建分区写入，这块如果选择不了的话按键盘按钮c，就能选中了。
10
选择不使用GPT格式，依然使用cfdisk格式。
11
显示格式选择框，选择gpt。
12
显示空白盘后，选择New。
13
因为要划分EFI分区，这个盘需要修改大小，不能使用默认大小，数字改成1就行，分配1G硬盘，然后按回车。
14
然后回到了菜单栏，按方向键选择Type，然后回车，给分区选择格式类型
15
按方向键选择第一个选项EFI System，然后回车
16
此时回到菜单栏，页面上半部分就能看到具体的分区大小和格式
17
然后按下方向键，选择下一行空白的分区
18
菜单栏选择New，然后回车
19
这块需要填写分区大小，此时对照右上角选中的空白分区大小一致即可，然后回车。
20
回到菜单栏，选择Write，回车，写入分区。
21
会提示你输入yes进行确认，输入后回车。
22
然后一段进度条跑过，应该会回到菜单栏，选择Quit退出菜单，一切准备就绪了
23
然后这时候回到了UI界面，使用前面初始化好的1GB大小的盘，选择OK按钮回车。
24
文件系统按方向键选择fat32类型，选择OK按钮回车
25
确认不修改名字，选择OK按钮回车
26
确认进行格式化，选择Yes按钮回车
27
然后回到最初的UI栏，选择第二块不是1GB大小的分区，选择OK按钮回车
28
文件系统按方向键选择ext4类型，选择OK按钮回车
29
确认不修改名字，选择OK按钮回车
30
确认进行格式化，选择Yes按钮回车
31
默认不使用额外空间更新，选择No按钮回车
32
确认GRUB2 EFI BootLoader，选择OK按钮回车
33
跑了一段时间进度条后，显示安装成功，此时选择Reboot，选择OK按钮回车。
34
系统初始化 ​
然后一段时间后进入LOGO界面。
35
再过一段时间，应该就会进入初始的安卓界面了，能看到弹窗和时间，按住左键上划
36
会出现主屏幕应用的选择，选择Quickstep
如果等待3~5分钟这个界面仍然没有出现，那么就重启虚拟机，再进入VNC应该就会显示了
37
镜像移除 ​
出现了安卓的界面后，宿主机执行qm stop 100，然后开始移除镜像文件。
移除已经按照完毕的ISO文件，在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]
br
然后宿主机再执行qm start 100，然后应该就会进入系统的初始界面了。
网络设置 ​
进入桌面，此时需要开始设置网络，图示位置按住左键，上划
38
弹出一堆应用，在里面找到那个叫做Bliss Ethernet Manager的应用，点击并打开
39
IP Assignment点击打开，选择Static类型，点击OK按钮确认
40
IP Address点击打开，填入172.16.1.xxx/24(xxx我写的100，因为这里我的虚拟机VMID是100方便区分)，点击OK按钮确认
41
Gateway Address点击打开，填入172.16.1.1，点击OK按钮确认
42
DNS Address点击打开，填入8.8.8.8，点击OK按钮确认
43
然后在应用界面中，点击Interface Up和Refresh，然后键盘按exit键退出程序
44
主界面中打开浏览器，验证网络是否畅通
45
可以看到打开本指南无问题，网络畅通
46
',227),Ls=[Rs];function Ts(Ws,zs,js,Qs,$s,Ys){return p(),e("div",null,Ls)}const Xs=s(Ms,[["render",Ts]]);export{Js as __pageData,Xs as default};
diff --git a/assets/guide_pve_pve_custom.md.939968ff.js b/assets/guide_pve_pve_custom.md.fd708ffe.js
similarity index 99%
rename from assets/guide_pve_pve_custom.md.939968ff.js
rename to assets/guide_pve_pve_custom.md.fd708ffe.js
index aa22e7e5d3..c49e8388e2 100644
--- a/assets/guide_pve_pve_custom.md.939968ff.js
+++ b/assets/guide_pve_pve_custom.md.fd708ffe.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as p}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"自定义分区","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_custom.md","filePath":"guide/pve/pve_custom.md","lastUpdated":1747726389000}'),n={name:"guide/pve/pve_custom.md"},o=p(`
自定义分区 ​
在非Debian系统上安装 Proxmox VE 7 ​
本机硬件配置的最低要求同先前正常安装的要求一致
需要先安装docker
curl -sSL https://get.docker.com/ | sh
+import{_ as s,v as a,b as e,R as p}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"自定义分区","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_custom.md","filePath":"guide/pve/pve_custom.md","lastUpdated":1747730955000}'),n={name:"guide/pve/pve_custom.md"},o=p(`
自定义分区 ​
在非Debian系统上安装 Proxmox VE 7 ​
本机硬件配置的最低要求同先前正常安装的要求一致
需要先安装docker
curl -sSL https://get.docker.com/ | sh
 curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-linux-$(uname -m)" -o /usr/local/bin/docker-compose
 chmod +x /usr/local/bin/docker-compose
 docker-compose --version
然后使用uname -m查询架构，使用对应架构的命令
开设出的PVE面板信息为：
登录用户名和密码都是root，登录后务必使用web的SSH更改密码以免被爆破
用宿主机SSH时务必登录对应https://IPV4地址:8006在web面板上使用SSH，不要使用宿主机的22端口操控PVE
因为web面板上的SSH是在Docker内的，所以不支持后续的一键配置，请自行配置网关等进行使用
X86架构
bash
docker run -idt --network host \\
diff --git a/assets/guide_pve_pve_custom.md.939968ff.lean.js b/assets/guide_pve_pve_custom.md.fd708ffe.lean.js
similarity index 99%
rename from assets/guide_pve_pve_custom.md.939968ff.lean.js
rename to assets/guide_pve_pve_custom.md.fd708ffe.lean.js
index aa22e7e5d3..c49e8388e2 100644
--- a/assets/guide_pve_pve_custom.md.939968ff.lean.js
+++ b/assets/guide_pve_pve_custom.md.fd708ffe.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as p}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"自定义分区","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_custom.md","filePath":"guide/pve/pve_custom.md","lastUpdated":1747726389000}'),n={name:"guide/pve/pve_custom.md"},o=p(`
自定义分区 ​
在非Debian系统上安装 Proxmox VE 7 ​
本机硬件配置的最低要求同先前正常安装的要求一致
需要先安装docker
curl -sSL https://get.docker.com/ | sh
+import{_ as s,v as a,b as e,R as p}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"自定义分区","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_custom.md","filePath":"guide/pve/pve_custom.md","lastUpdated":1747730955000}'),n={name:"guide/pve/pve_custom.md"},o=p(`
自定义分区 ​
在非Debian系统上安装 Proxmox VE 7 ​
本机硬件配置的最低要求同先前正常安装的要求一致
需要先安装docker
curl -sSL https://get.docker.com/ | sh
 curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-linux-$(uname -m)" -o /usr/local/bin/docker-compose
 chmod +x /usr/local/bin/docker-compose
 docker-compose --version
然后使用uname -m查询架构，使用对应架构的命令
开设出的PVE面板信息为：
登录用户名和密码都是root，登录后务必使用web的SSH更改密码以免被爆破
用宿主机SSH时务必登录对应https://IPV4地址:8006在web面板上使用SSH，不要使用宿主机的22端口操控PVE
因为web面板上的SSH是在Docker内的，所以不支持后续的一键配置，请自行配置网关等进行使用
X86架构
bash
docker run -idt --network host \\
diff --git a/assets/guide_pve_pve_install.md.03f5b3ac.js b/assets/guide_pve_pve_install.md.8e26ca11.js
similarity index 99%
rename from assets/guide_pve_pve_install.md.03f5b3ac.js
rename to assets/guide_pve_pve_install.md.8e26ca11.js
index 5dae7a752c..97120f231a 100644
--- a/assets/guide_pve_pve_install.md.03f5b3ac.js
+++ b/assets/guide_pve_pve_install.md.8e26ca11.js
@@ -1 +1 @@
-import{_ as s,v as l,b as a,R as e}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"PVE主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_install.md","filePath":"guide/pve/pve_install.md","lastUpdated":1747726389000}'),p={name:"guide/pve/pve_install.md"},t=e('
PVE主体安装 ​
安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载
TIP
低配置的宿主机，建议所有内容安装完毕后，查看自定义分区的内容，进行内存调优，减少内存占用。
一键安装PVE ​
TIP
建议debian12，实测部分独立服务器的debian11系统会出现一重启网络就失联的情况，debian12没有这种问题
  • 安装的是当下apt源最新的PVE
  • 比如debian10则是pve6.4，debian11则是pve7.x，debian12则是pve8.x
  • /etc/hosts文件修改(修正商家hostname设置错误以及新增PVE所需的内容)
  • /etc/cloud/cloud.cfg文件修改(避免覆写已修改的hostname等配置)
  • /etc/network/interfaces文件修改(修复auto、dhcp类型为static、增加vmbr0网关)
  • 检测是否为中国IP，如果为中国IP使用清华镜像源，否则使用官方源，同时处理apt的源和对应的nameserver，避免断网
  • 创建vmbr0(独立IP网关)，宿主机允许addr和gateway为内网IP或外网IP，已自动识别
  • vmbr0创建支持开设纯IPV4、纯IPV6、双栈虚拟机，自动识别IPV4地址和IPV6地址，自动识别对应的IP区间
  • 安装PVE开虚拟机需要的必备工具包
  • x86_64的替换apt源中的企业订阅为社区源，arm的使用第三方修复的补丁构建的源
  • 打印查询Linux系统内核和PVE内核是否已安装
  • 设置DNS检测8.8.8.8的开机自启添加DNS的systemd服务
  • 新增PVE的APT源链接后，下载PVE并打印输出登陆信息
所有修改过的文件均已设置为只读模式，避免重启后文件被覆写，如需修改请使用chattr -i 文件路径取消只读锁定，修改完毕请执行chattr +i 文件路径进行只读锁定
执行过程中会提示重启系统一次，重启后务必等待起码20秒确保系统未再次自动重启，因为原始环境可能缺失ifupdown或ifupdown2环境，有加载安装的守护进程进行安装，安装后会再次自动重启系统，等待20秒未自重启确保这个安装已运行完毕.
如果你需要将新安装的PVE纳管进入已有的集群，那么这块安装的时候，名字就不能回车默认使用pve，需要换一个名字避免和集群内的pve本身的hostname冲突.
若宿主机本身存在SLAAC分配的IPV6地址，将可选择是否使用最大的IPV6子网范围，默认回车不使用最大的IPV6子网范围仅使用本机IPV6，若后续需要给虚拟机/容器附加独立的IPV6地址，该选项务必选择y.
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh
或
shell
bash install_pve.sh
TIP
安装成功后打开网页可能提示不安全，点击高级或更多选项，坚持访问即可
登录的信息是你SSH的账户和密码
预配置环境 ​
  • 创建资源池mypool(local)
  • 移除订阅弹窗
  • 尝试开启硬件直通
  • 对AppArmor模块检测和自动安装
  • 重启系统前推荐挂上nezha探针方便在后台不通过SSH使用命令行，避免SSH可能因为商家奇葩的预设可能导致重启后root密码丢失
  • 执行reboot前需要等待后台任务执行完毕，一些宿主机的系统apt命令执行很慢，得等一会才能执行完毕，当然大部分的机器没这么烂，如果很久都起不来ssh无法连接，那么尝试通过控制面板重启一下服务器
国际
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)
自动配置宿主机的网关 ​
WARNING
使用前请保证重启过服务器且此时PVE能正常登录进WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动并可登录成功后至少等1分钟再执行本命令 如果WEB端起不来，执行systemctl status pveproxy查看是否启动，如果卡住未启动，执行systemctl start pveproxy启动WEB端。
TIP
这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行。
TIP
在执行本命令前如果宿主机需要附加IPV6隧道(给没有IPV6地址的宿主机添加IPV6子网)，请查看IPV6免费子网附加部分的内容附加到对应的配置文件中，但请忽略<初始环境修改>的操作，直接进行附加，附加后验证有IPV6地址了再执行下面的一键配置网关的命令。
  • 如果vmbr0未创建，则自动创建，逻辑同主体安装一致
  • 创建vmbr1(NAT网关)，支持开设NAT的IPV6网络的NAT的IPV4的服务器
  • 创建vmbr2(独立IPV6网关)，使用ndppd解决宿主机对IPV6地址进行MAC校验的问题，支持开设带独立IPV6网络的服务器
  • 想查看完整设置可以执行cat /etc/network/interfaces查看，如需修改网关需要修改该文件，web端已经无法修改
  • 加载iptables并设置回源且允许NAT端口转发
简单的说，vmbr0负责v4的独立IP，vmbr1负责复杂v4/v6的NAT，vmbr2负责v6的独立IP
开独立IPV4的虚拟机时使用的vmbr0，gateway同宿主机，IPV4/CIDR使用同一网段的地址和相同的子网掩码，使用宿主机未绑定的IPV4地址做IPV4/CIDR，当然如果后续使用本套脚本无需关注这点细枝末节的东西
开NAT的IPV4的虚拟机时使用vmbr1，gateway使用172.16.1.1，IPV4/CIDR使用172.16.1.x/24，这里的x不能是1，当然如果后续使用本套脚本无需关注这点细枝末节的东西
国际
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)
TIP
这一步是可能需要你执行成功几分钟后重启系统，详见脚本最后执行完毕的提示，但重启可以保证部分隐藏设置加载成功，有条件务必重启一次服务器
',37),o=[t];function n(c,i,r,d,h,C){return l(),a("div",null,o)}const v=s(p,[["render",n]]);export{u as __pageData,v as default};
+import{_ as s,v as l,b as a,R as e}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"PVE主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_install.md","filePath":"guide/pve/pve_install.md","lastUpdated":1747730955000}'),p={name:"guide/pve/pve_install.md"},t=e('
PVE主体安装 ​
安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载
TIP
低配置的宿主机，建议所有内容安装完毕后，查看自定义分区的内容，进行内存调优，减少内存占用。
一键安装PVE ​
TIP
建议debian12，实测部分独立服务器的debian11系统会出现一重启网络就失联的情况，debian12没有这种问题
  • 安装的是当下apt源最新的PVE
  • 比如debian10则是pve6.4，debian11则是pve7.x，debian12则是pve8.x
  • /etc/hosts文件修改(修正商家hostname设置错误以及新增PVE所需的内容)
  • /etc/cloud/cloud.cfg文件修改(避免覆写已修改的hostname等配置)
  • /etc/network/interfaces文件修改(修复auto、dhcp类型为static、增加vmbr0网关)
  • 检测是否为中国IP，如果为中国IP使用清华镜像源，否则使用官方源，同时处理apt的源和对应的nameserver，避免断网
  • 创建vmbr0(独立IP网关)，宿主机允许addr和gateway为内网IP或外网IP，已自动识别
  • vmbr0创建支持开设纯IPV4、纯IPV6、双栈虚拟机，自动识别IPV4地址和IPV6地址，自动识别对应的IP区间
  • 安装PVE开虚拟机需要的必备工具包
  • x86_64的替换apt源中的企业订阅为社区源，arm的使用第三方修复的补丁构建的源
  • 打印查询Linux系统内核和PVE内核是否已安装
  • 设置DNS检测8.8.8.8的开机自启添加DNS的systemd服务
  • 新增PVE的APT源链接后，下载PVE并打印输出登陆信息
所有修改过的文件均已设置为只读模式，避免重启后文件被覆写，如需修改请使用chattr -i 文件路径取消只读锁定，修改完毕请执行chattr +i 文件路径进行只读锁定
执行过程中会提示重启系统一次，重启后务必等待起码20秒确保系统未再次自动重启，因为原始环境可能缺失ifupdown或ifupdown2环境，有加载安装的守护进程进行安装，安装后会再次自动重启系统，等待20秒未自重启确保这个安装已运行完毕.
如果你需要将新安装的PVE纳管进入已有的集群，那么这块安装的时候，名字就不能回车默认使用pve，需要换一个名字避免和集群内的pve本身的hostname冲突.
若宿主机本身存在SLAAC分配的IPV6地址，将可选择是否使用最大的IPV6子网范围，默认回车不使用最大的IPV6子网范围仅使用本机IPV6，若后续需要给虚拟机/容器附加独立的IPV6地址，该选项务必选择y.
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh
或
shell
bash install_pve.sh
TIP
安装成功后打开网页可能提示不安全，点击高级或更多选项，坚持访问即可
登录的信息是你SSH的账户和密码
预配置环境 ​
  • 创建资源池mypool(local)
  • 移除订阅弹窗
  • 尝试开启硬件直通
  • 对AppArmor模块检测和自动安装
  • 重启系统前推荐挂上nezha探针方便在后台不通过SSH使用命令行，避免SSH可能因为商家奇葩的预设可能导致重启后root密码丢失
  • 执行reboot前需要等待后台任务执行完毕，一些宿主机的系统apt命令执行很慢，得等一会才能执行完毕，当然大部分的机器没这么烂，如果很久都起不来ssh无法连接，那么尝试通过控制面板重启一下服务器
国际
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)
自动配置宿主机的网关 ​
WARNING
使用前请保证重启过服务器且此时PVE能正常登录进WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动并可登录成功后至少等1分钟再执行本命令 如果WEB端起不来，执行systemctl status pveproxy查看是否启动，如果卡住未启动，执行systemctl start pveproxy启动WEB端。
TIP
这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行。
TIP
在执行本命令前如果宿主机需要附加IPV6隧道(给没有IPV6地址的宿主机添加IPV6子网)，请查看IPV6免费子网附加部分的内容附加到对应的配置文件中，但请忽略<初始环境修改>的操作，直接进行附加，附加后验证有IPV6地址了再执行下面的一键配置网关的命令。
  • 如果vmbr0未创建，则自动创建，逻辑同主体安装一致
  • 创建vmbr1(NAT网关)，支持开设NAT的IPV6网络的NAT的IPV4的服务器
  • 创建vmbr2(独立IPV6网关)，使用ndppd解决宿主机对IPV6地址进行MAC校验的问题，支持开设带独立IPV6网络的服务器
  • 想查看完整设置可以执行cat /etc/network/interfaces查看，如需修改网关需要修改该文件，web端已经无法修改
  • 加载iptables并设置回源且允许NAT端口转发
简单的说，vmbr0负责v4的独立IP，vmbr1负责复杂v4/v6的NAT，vmbr2负责v6的独立IP
开独立IPV4的虚拟机时使用的vmbr0，gateway同宿主机，IPV4/CIDR使用同一网段的地址和相同的子网掩码，使用宿主机未绑定的IPV4地址做IPV4/CIDR，当然如果后续使用本套脚本无需关注这点细枝末节的东西
开NAT的IPV4的虚拟机时使用vmbr1，gateway使用172.16.1.1，IPV4/CIDR使用172.16.1.x/24，这里的x不能是1，当然如果后续使用本套脚本无需关注这点细枝末节的东西
国际
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)
TIP
这一步是可能需要你执行成功几分钟后重启系统，详见脚本最后执行完毕的提示，但重启可以保证部分隐藏设置加载成功，有条件务必重启一次服务器
',37),o=[t];function n(c,i,r,d,h,C){return l(),a("div",null,o)}const v=s(p,[["render",n]]);export{u as __pageData,v as default};
diff --git a/assets/guide_pve_pve_install.md.03f5b3ac.lean.js b/assets/guide_pve_pve_install.md.8e26ca11.lean.js
similarity index 99%
rename from assets/guide_pve_pve_install.md.03f5b3ac.lean.js
rename to assets/guide_pve_pve_install.md.8e26ca11.lean.js
index 5dae7a752c..97120f231a 100644
--- a/assets/guide_pve_pve_install.md.03f5b3ac.lean.js
+++ b/assets/guide_pve_pve_install.md.8e26ca11.lean.js
@@ -1 +1 @@
-import{_ as s,v as l,b as a,R as e}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"PVE主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_install.md","filePath":"guide/pve/pve_install.md","lastUpdated":1747726389000}'),p={name:"guide/pve/pve_install.md"},t=e('
PVE主体安装 ​
安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载
TIP
低配置的宿主机，建议所有内容安装完毕后，查看自定义分区的内容，进行内存调优，减少内存占用。
一键安装PVE ​
TIP
建议debian12，实测部分独立服务器的debian11系统会出现一重启网络就失联的情况，debian12没有这种问题
  • 安装的是当下apt源最新的PVE
  • 比如debian10则是pve6.4，debian11则是pve7.x，debian12则是pve8.x
  • /etc/hosts文件修改(修正商家hostname设置错误以及新增PVE所需的内容)
  • /etc/cloud/cloud.cfg文件修改(避免覆写已修改的hostname等配置)
  • /etc/network/interfaces文件修改(修复auto、dhcp类型为static、增加vmbr0网关)
  • 检测是否为中国IP，如果为中国IP使用清华镜像源，否则使用官方源，同时处理apt的源和对应的nameserver，避免断网
  • 创建vmbr0(独立IP网关)，宿主机允许addr和gateway为内网IP或外网IP，已自动识别
  • vmbr0创建支持开设纯IPV4、纯IPV6、双栈虚拟机，自动识别IPV4地址和IPV6地址，自动识别对应的IP区间
  • 安装PVE开虚拟机需要的必备工具包
  • x86_64的替换apt源中的企业订阅为社区源，arm的使用第三方修复的补丁构建的源
  • 打印查询Linux系统内核和PVE内核是否已安装
  • 设置DNS检测8.8.8.8的开机自启添加DNS的systemd服务
  • 新增PVE的APT源链接后，下载PVE并打印输出登陆信息
所有修改过的文件均已设置为只读模式，避免重启后文件被覆写，如需修改请使用chattr -i 文件路径取消只读锁定，修改完毕请执行chattr +i 文件路径进行只读锁定
执行过程中会提示重启系统一次，重启后务必等待起码20秒确保系统未再次自动重启，因为原始环境可能缺失ifupdown或ifupdown2环境，有加载安装的守护进程进行安装，安装后会再次自动重启系统，等待20秒未自重启确保这个安装已运行完毕.
如果你需要将新安装的PVE纳管进入已有的集群，那么这块安装的时候，名字就不能回车默认使用pve，需要换一个名字避免和集群内的pve本身的hostname冲突.
若宿主机本身存在SLAAC分配的IPV6地址，将可选择是否使用最大的IPV6子网范围，默认回车不使用最大的IPV6子网范围仅使用本机IPV6，若后续需要给虚拟机/容器附加独立的IPV6地址，该选项务必选择y.
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh
或
shell
bash install_pve.sh
TIP
安装成功后打开网页可能提示不安全，点击高级或更多选项，坚持访问即可
登录的信息是你SSH的账户和密码
预配置环境 ​
  • 创建资源池mypool(local)
  • 移除订阅弹窗
  • 尝试开启硬件直通
  • 对AppArmor模块检测和自动安装
  • 重启系统前推荐挂上nezha探针方便在后台不通过SSH使用命令行，避免SSH可能因为商家奇葩的预设可能导致重启后root密码丢失
  • 执行reboot前需要等待后台任务执行完毕，一些宿主机的系统apt命令执行很慢，得等一会才能执行完毕，当然大部分的机器没这么烂，如果很久都起不来ssh无法连接，那么尝试通过控制面板重启一下服务器
国际
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)
自动配置宿主机的网关 ​
WARNING
使用前请保证重启过服务器且此时PVE能正常登录进WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动并可登录成功后至少等1分钟再执行本命令 如果WEB端起不来，执行systemctl status pveproxy查看是否启动，如果卡住未启动，执行systemctl start pveproxy启动WEB端。
TIP
这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行。
TIP
在执行本命令前如果宿主机需要附加IPV6隧道(给没有IPV6地址的宿主机添加IPV6子网)，请查看IPV6免费子网附加部分的内容附加到对应的配置文件中，但请忽略<初始环境修改>的操作，直接进行附加，附加后验证有IPV6地址了再执行下面的一键配置网关的命令。
  • 如果vmbr0未创建，则自动创建，逻辑同主体安装一致
  • 创建vmbr1(NAT网关)，支持开设NAT的IPV6网络的NAT的IPV4的服务器
  • 创建vmbr2(独立IPV6网关)，使用ndppd解决宿主机对IPV6地址进行MAC校验的问题，支持开设带独立IPV6网络的服务器
  • 想查看完整设置可以执行cat /etc/network/interfaces查看，如需修改网关需要修改该文件，web端已经无法修改
  • 加载iptables并设置回源且允许NAT端口转发
简单的说，vmbr0负责v4的独立IP，vmbr1负责复杂v4/v6的NAT，vmbr2负责v6的独立IP
开独立IPV4的虚拟机时使用的vmbr0，gateway同宿主机，IPV4/CIDR使用同一网段的地址和相同的子网掩码，使用宿主机未绑定的IPV4地址做IPV4/CIDR，当然如果后续使用本套脚本无需关注这点细枝末节的东西
开NAT的IPV4的虚拟机时使用vmbr1，gateway使用172.16.1.1，IPV4/CIDR使用172.16.1.x/24，这里的x不能是1，当然如果后续使用本套脚本无需关注这点细枝末节的东西
国际
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)
TIP
这一步是可能需要你执行成功几分钟后重启系统，详见脚本最后执行完毕的提示，但重启可以保证部分隐藏设置加载成功，有条件务必重启一次服务器
',37),o=[t];function n(c,i,r,d,h,C){return l(),a("div",null,o)}const v=s(p,[["render",n]]);export{u as __pageData,v as default};
+import{_ as s,v as l,b as a,R as e}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"PVE主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_install.md","filePath":"guide/pve/pve_install.md","lastUpdated":1747730955000}'),p={name:"guide/pve/pve_install.md"},t=e('
PVE主体安装 ​
安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载
TIP
低配置的宿主机，建议所有内容安装完毕后，查看自定义分区的内容，进行内存调优，减少内存占用。
一键安装PVE ​
TIP
建议debian12，实测部分独立服务器的debian11系统会出现一重启网络就失联的情况，debian12没有这种问题
  • 安装的是当下apt源最新的PVE
  • 比如debian10则是pve6.4，debian11则是pve7.x，debian12则是pve8.x
  • /etc/hosts文件修改(修正商家hostname设置错误以及新增PVE所需的内容)
  • /etc/cloud/cloud.cfg文件修改(避免覆写已修改的hostname等配置)
  • /etc/network/interfaces文件修改(修复auto、dhcp类型为static、增加vmbr0网关)
  • 检测是否为中国IP，如果为中国IP使用清华镜像源，否则使用官方源，同时处理apt的源和对应的nameserver，避免断网
  • 创建vmbr0(独立IP网关)，宿主机允许addr和gateway为内网IP或外网IP，已自动识别
  • vmbr0创建支持开设纯IPV4、纯IPV6、双栈虚拟机，自动识别IPV4地址和IPV6地址，自动识别对应的IP区间
  • 安装PVE开虚拟机需要的必备工具包
  • x86_64的替换apt源中的企业订阅为社区源，arm的使用第三方修复的补丁构建的源
  • 打印查询Linux系统内核和PVE内核是否已安装
  • 设置DNS检测8.8.8.8的开机自启添加DNS的systemd服务
  • 新增PVE的APT源链接后，下载PVE并打印输出登陆信息
所有修改过的文件均已设置为只读模式，避免重启后文件被覆写，如需修改请使用chattr -i 文件路径取消只读锁定，修改完毕请执行chattr +i 文件路径进行只读锁定
执行过程中会提示重启系统一次，重启后务必等待起码20秒确保系统未再次自动重启，因为原始环境可能缺失ifupdown或ifupdown2环境，有加载安装的守护进程进行安装，安装后会再次自动重启系统，等待20秒未自重启确保这个安装已运行完毕.
如果你需要将新安装的PVE纳管进入已有的集群，那么这块安装的时候，名字就不能回车默认使用pve，需要换一个名字避免和集群内的pve本身的hostname冲突.
若宿主机本身存在SLAAC分配的IPV6地址，将可选择是否使用最大的IPV6子网范围，默认回车不使用最大的IPV6子网范围仅使用本机IPV6，若后续需要给虚拟机/容器附加独立的IPV6地址，该选项务必选择y.
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh
或
shell
bash install_pve.sh
TIP
安装成功后打开网页可能提示不安全，点击高级或更多选项，坚持访问即可
登录的信息是你SSH的账户和密码
预配置环境 ​
  • 创建资源池mypool(local)
  • 移除订阅弹窗
  • 尝试开启硬件直通
  • 对AppArmor模块检测和自动安装
  • 重启系统前推荐挂上nezha探针方便在后台不通过SSH使用命令行，避免SSH可能因为商家奇葩的预设可能导致重启后root密码丢失
  • 执行reboot前需要等待后台任务执行完毕，一些宿主机的系统apt命令执行很慢，得等一会才能执行完毕，当然大部分的机器没这么烂，如果很久都起不来ssh无法连接，那么尝试通过控制面板重启一下服务器
国际
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)
自动配置宿主机的网关 ​
WARNING
使用前请保证重启过服务器且此时PVE能正常登录进WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动并可登录成功后至少等1分钟再执行本命令 如果WEB端起不来，执行systemctl status pveproxy查看是否启动，如果卡住未启动，执行systemctl start pveproxy启动WEB端。
TIP
这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行。
TIP
在执行本命令前如果宿主机需要附加IPV6隧道(给没有IPV6地址的宿主机添加IPV6子网)，请查看IPV6免费子网附加部分的内容附加到对应的配置文件中，但请忽略<初始环境修改>的操作，直接进行附加，附加后验证有IPV6地址了再执行下面的一键配置网关的命令。
  • 如果vmbr0未创建，则自动创建，逻辑同主体安装一致
  • 创建vmbr1(NAT网关)，支持开设NAT的IPV6网络的NAT的IPV4的服务器
  • 创建vmbr2(独立IPV6网关)，使用ndppd解决宿主机对IPV6地址进行MAC校验的问题，支持开设带独立IPV6网络的服务器
  • 想查看完整设置可以执行cat /etc/network/interfaces查看，如需修改网关需要修改该文件，web端已经无法修改
  • 加载iptables并设置回源且允许NAT端口转发
简单的说，vmbr0负责v4的独立IP，vmbr1负责复杂v4/v6的NAT，vmbr2负责v6的独立IP
开独立IPV4的虚拟机时使用的vmbr0，gateway同宿主机，IPV4/CIDR使用同一网段的地址和相同的子网掩码，使用宿主机未绑定的IPV4地址做IPV4/CIDR，当然如果后续使用本套脚本无需关注这点细枝末节的东西
开NAT的IPV4的虚拟机时使用vmbr1，gateway使用172.16.1.1，IPV4/CIDR使用172.16.1.x/24，这里的x不能是1，当然如果后续使用本套脚本无需关注这点细枝末节的东西
国际
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)
TIP
这一步是可能需要你执行成功几分钟后重启系统，详见脚本最后执行完毕的提示，但重启可以保证部分隐藏设置加载成功，有条件务必重启一次服务器
',37),o=[t];function n(c,i,r,d,h,C){return l(),a("div",null,o)}const v=s(p,[["render",n]]);export{u as __pageData,v as default};
diff --git a/assets/guide_pve_pve_kvm.md.9e154693.js b/assets/guide_pve_pve_kvm.md.d4fd9ba3.js
similarity index 99%
rename from assets/guide_pve_pve_kvm.md.9e154693.js
rename to assets/guide_pve_pve_kvm.md.d4fd9ba3.js
index 558b71f667..beb949efe2 100644
--- a/assets/guide_pve_pve_kvm.md.9e154693.js
+++ b/assets/guide_pve_pve_kvm.md.d4fd9ba3.js
@@ -1,4 +1,4 @@
-import{_ as s,v as l,b as a,R as t}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"Linux虚拟机(KVM/TCG)","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_kvm.md","filePath":"guide/pve/pve_kvm.md","lastUpdated":1747726389000}'),o={name:"guide/pve/pve_kvm.md"},n=t(`
Linux虚拟机(KVM/TCG) ​
SSH登录说明 ​
开设出的虚拟机，默认生成的用户名可以不是root，此时你需要执行sudo -i切换为root用户
默认设置的用户名不是root时，未经过设置的默认的root密码是password或oneclickvirt
登录SSH切换为root权限后，一定要修改root密码，可以使用以下命令修改
国际
bash
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
国内
bash
bash <(curl -sSL https://cdn.spiritlhl.net/https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
开设带IPV6地址的虚拟机的注意事项 ​
由于长期闲置IPV6不使用可能导致NDP广播缓存失效重置，一般闲置50分钟左右就会出现IPV6不可用的情况，俗称“IPV6断流”，此时需要设置一个定时任务
shell
echo '*/1 * * * * curl -m 6 -s ipv6.ip.sb || curl -m 6 -s ipv6.ip.sb' | crontab -
在开设出的虚拟机中执行上述命令，可保证IPV6网络一直被使用，不会失效断流
开设虚拟机可使用的镜像 ​
  • 已预安装开启cloudinit
  • 开启SSH登陆
  • 预设置SSH监听V4和V6的22端口
  • 开启允许密码验证登陆
  • 开启允许root登陆
  • 部分预安装Qemu-guest-agent
目前可使用的镜像名字的列表为
https://github.com/oneclickvirt/kvm_images/blob/main/list.text
以及
https://github.com/oneclickvirt/pve_kvm_images
仓库的Release中存储的每日修补镜像
单独开设NAT的虚拟化的虚拟机 ​
  • 自动开设NAT服务器，默认使用Debian10镜像，因为该镜像占用最小
  • 可在命令中自定义需要使用的镜像，这里有给出配置好的镜像，镜像自带空间设置是2~10G硬盘，日常使用至少10G以上即可，除非某些镜像开不起来再增加硬盘大小
  • 可在命令中指定存储盘位置，默认不指定时为local盘即系统盘，可指定为PVE中显示的挂载盘
  • 自定义内存大小推荐512MB内存
  • 自动进行内外网端口映射，含22，80，443端口以及其他25个内外网端口号一样的端口
  • 生成后需要等待一段时间虚拟机内部的cloud-init配置好网络以及登陆信息，大概需要5分钟
  • 虚拟机的相关信息将会存储到WEB端对应VM的NOTES中，可在WEB端查看
  • 如果宿主机自带IPV6子网将自动附加上IPV6网络，但无公网IPV6地址
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是/64的子网
使用方法 ​
  • 系统支持： 
    • x86_64架构的详见 跳转 中列出的系统，使用时只需写文件名字，不需要.qcow2尾缀
    • arm架构的详见 跳转 中列出的系统，使用时只需要写系统名字+系统版本号，如ubuntu20、ubutnu22这种
TIP
注意这里的用户名不能是纯数字，会造成cloudinit出问题，最好是纯英文或英文开头
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
各参数含义
shell
# ./buildvm.sh VMID 用户名 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6地址(留空默认N)
TIP
注意这里的密码最好仅英文与数字混合，且以英文开头，避免密码在设置过程中因为特殊字符被转义而设置失败
测试示例 ​
shell
./buildvm.sh 111 root oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
开设完毕可执行cat vm111查看信息，或到WEB端对应VM的NOTES中查看
以下为开设的示例VM的信息：
属性值
VMID111
SSH登录的用户名root
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小10G
SSH端口40001
80端口40002
443端口40003
内外网映射端口一致的区间50000到50025
系统debian11
宿主机的存储盘local
绑定独立IPV6(留空默认N)N
TIP
注意这里的VMID仅可使用100到256，其他数字不可用
删除指定虚拟机 ​
  • 停止VM
  • 删除VM
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应VMID的虚拟机，这里用上文中的示例111做演示
shell
./pve_delete.sh 111
实际删除数量不固定，空格分隔每个VMID即可，可一次性删除多个
批量开设NAT的虚拟化的虚拟机 ​
WARNING
初次使用前需要保证当前PVE纯净且宿主机未进行过任何端口映射，否则设置冲突可能出现BUG
TIP
开设前请使用screen挂起执行，避免批量开设时间过长，SSH不稳定导致中间执行中断
  • 可多次运行批量生成VM
  • 自动开设NAT服务器，选项留空默认使用debian11镜像，可自定义使用镜像名字，支持的系统名字详见上文支持的镜像列表
  • 自动进行内外网端口映射，含22，80，443端口以及其他25个内外网端口号一样的端口
  • 生成后需要等待一段时间虚拟机内部的cloudinit配置好网络以及登陆信息，大概需要5分钟，每个虚拟机创建之间有间隔等待60秒避免突发性能不足
  • 默认批量开设的虚拟机网络配置为：22，80，443端口及一个25个端口区间的内外网映射
  • 可自定义批量开设的核心数，内存大小，硬盘大小，使用宿主机哪个存储盘，记得自己计算好空闲资源开设
  • 虚拟机的相关信息将会存储到WEB端对应VM的NOTES中，可在WEB端查看
  • 如果宿主机自带IPV6子网将自动附加上IPV6网络，但无公网IPV6地址
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是一个/64子网
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_vm.sh -o create_vm.sh && chmod +x create_vm.sh && bash create_vm.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_vm.sh -o create_vm.sh && chmod +x create_vm.sh && bash create_vm.sh
开设完毕可执行cat vmlog查看信息，或到WEB端对应VM的NOTES中查看
删除所有虚拟机 ​
  • 删除所有VM
  • 删除所有nat的端口映射
  • 重启网络
  • 删除log文件
shell
for vmid in $(qm list | awk '{if(NR>1) print $1}'); do qm stop $vmid; qm destroy $vmid; rm -rf /var/lib/vz/images/$vmid*; done
+import{_ as s,v as l,b as a,R as t}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"Linux虚拟机(KVM/TCG)","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_kvm.md","filePath":"guide/pve/pve_kvm.md","lastUpdated":1747730955000}'),o={name:"guide/pve/pve_kvm.md"},n=t(`
Linux虚拟机(KVM/TCG) ​
SSH登录说明 ​
开设出的虚拟机，默认生成的用户名可以不是root，此时你需要执行sudo -i切换为root用户
默认设置的用户名不是root时，未经过设置的默认的root密码是password或oneclickvirt
登录SSH切换为root权限后，一定要修改root密码，可以使用以下命令修改
国际
bash
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
国内
bash
bash <(curl -sSL https://cdn.spiritlhl.net/https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
开设带IPV6地址的虚拟机的注意事项 ​
由于长期闲置IPV6不使用可能导致NDP广播缓存失效重置，一般闲置50分钟左右就会出现IPV6不可用的情况，俗称“IPV6断流”，此时需要设置一个定时任务
shell
echo '*/1 * * * * curl -m 6 -s ipv6.ip.sb || curl -m 6 -s ipv6.ip.sb' | crontab -
在开设出的虚拟机中执行上述命令，可保证IPV6网络一直被使用，不会失效断流
开设虚拟机可使用的镜像 ​
  • 已预安装开启cloudinit
  • 开启SSH登陆
  • 预设置SSH监听V4和V6的22端口
  • 开启允许密码验证登陆
  • 开启允许root登陆
  • 部分预安装Qemu-guest-agent
目前可使用的镜像名字的列表为
https://github.com/oneclickvirt/kvm_images/blob/main/list.text
以及
https://github.com/oneclickvirt/pve_kvm_images
仓库的Release中存储的每日修补镜像
单独开设NAT的虚拟化的虚拟机 ​
  • 自动开设NAT服务器，默认使用Debian10镜像，因为该镜像占用最小
  • 可在命令中自定义需要使用的镜像，这里有给出配置好的镜像，镜像自带空间设置是2~10G硬盘，日常使用至少10G以上即可，除非某些镜像开不起来再增加硬盘大小
  • 可在命令中指定存储盘位置，默认不指定时为local盘即系统盘，可指定为PVE中显示的挂载盘
  • 自定义内存大小推荐512MB内存
  • 自动进行内外网端口映射，含22，80，443端口以及其他25个内外网端口号一样的端口
  • 生成后需要等待一段时间虚拟机内部的cloud-init配置好网络以及登陆信息，大概需要5分钟
  • 虚拟机的相关信息将会存储到WEB端对应VM的NOTES中，可在WEB端查看
  • 如果宿主机自带IPV6子网将自动附加上IPV6网络，但无公网IPV6地址
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是/64的子网
使用方法 ​
  • 系统支持： 
    • x86_64架构的详见 跳转 中列出的系统，使用时只需写文件名字，不需要.qcow2尾缀
    • arm架构的详见 跳转 中列出的系统，使用时只需要写系统名字+系统版本号，如ubuntu20、ubutnu22这种
TIP
注意这里的用户名不能是纯数字，会造成cloudinit出问题，最好是纯英文或英文开头
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
各参数含义
shell
# ./buildvm.sh VMID 用户名 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6地址(留空默认N)
TIP
注意这里的密码最好仅英文与数字混合，且以英文开头，避免密码在设置过程中因为特殊字符被转义而设置失败
测试示例 ​
shell
./buildvm.sh 111 root oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
开设完毕可执行cat vm111查看信息，或到WEB端对应VM的NOTES中查看
以下为开设的示例VM的信息：
属性值
VMID111
SSH登录的用户名root
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小10G
SSH端口40001
80端口40002
443端口40003
内外网映射端口一致的区间50000到50025
系统debian11
宿主机的存储盘local
绑定独立IPV6(留空默认N)N
TIP
注意这里的VMID仅可使用100到256，其他数字不可用
删除指定虚拟机 ​
  • 停止VM
  • 删除VM
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应VMID的虚拟机，这里用上文中的示例111做演示
shell
./pve_delete.sh 111
实际删除数量不固定，空格分隔每个VMID即可，可一次性删除多个
批量开设NAT的虚拟化的虚拟机 ​
WARNING
初次使用前需要保证当前PVE纯净且宿主机未进行过任何端口映射，否则设置冲突可能出现BUG
TIP
开设前请使用screen挂起执行，避免批量开设时间过长，SSH不稳定导致中间执行中断
  • 可多次运行批量生成VM
  • 自动开设NAT服务器，选项留空默认使用debian11镜像，可自定义使用镜像名字，支持的系统名字详见上文支持的镜像列表
  • 自动进行内外网端口映射，含22，80，443端口以及其他25个内外网端口号一样的端口
  • 生成后需要等待一段时间虚拟机内部的cloudinit配置好网络以及登陆信息，大概需要5分钟，每个虚拟机创建之间有间隔等待60秒避免突发性能不足
  • 默认批量开设的虚拟机网络配置为：22，80，443端口及一个25个端口区间的内外网映射
  • 可自定义批量开设的核心数，内存大小，硬盘大小，使用宿主机哪个存储盘，记得自己计算好空闲资源开设
  • 虚拟机的相关信息将会存储到WEB端对应VM的NOTES中，可在WEB端查看
  • 如果宿主机自带IPV6子网将自动附加上IPV6网络，但无公网IPV6地址
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是一个/64子网
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_vm.sh -o create_vm.sh && chmod +x create_vm.sh && bash create_vm.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_vm.sh -o create_vm.sh && chmod +x create_vm.sh && bash create_vm.sh
开设完毕可执行cat vmlog查看信息，或到WEB端对应VM的NOTES中查看
删除所有虚拟机 ​
  • 删除所有VM
  • 删除所有nat的端口映射
  • 重启网络
  • 删除log文件
shell
for vmid in $(qm list | awk '{if(NR>1) print $1}'); do qm stop $vmid; qm destroy $vmid; rm -rf /var/lib/vz/images/$vmid*; done
 iptables -t nat -F
 iptables -t filter -F
 service networking restart
diff --git a/assets/guide_pve_pve_kvm.md.9e154693.lean.js b/assets/guide_pve_pve_kvm.md.d4fd9ba3.lean.js
similarity index 99%
rename from assets/guide_pve_pve_kvm.md.9e154693.lean.js
rename to assets/guide_pve_pve_kvm.md.d4fd9ba3.lean.js
index 558b71f667..beb949efe2 100644
--- a/assets/guide_pve_pve_kvm.md.9e154693.lean.js
+++ b/assets/guide_pve_pve_kvm.md.d4fd9ba3.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as l,b as a,R as t}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"Linux虚拟机(KVM/TCG)","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_kvm.md","filePath":"guide/pve/pve_kvm.md","lastUpdated":1747726389000}'),o={name:"guide/pve/pve_kvm.md"},n=t(`
Linux虚拟机(KVM/TCG) ​
SSH登录说明 ​
开设出的虚拟机，默认生成的用户名可以不是root，此时你需要执行sudo -i切换为root用户
默认设置的用户名不是root时，未经过设置的默认的root密码是password或oneclickvirt
登录SSH切换为root权限后，一定要修改root密码，可以使用以下命令修改
国际
bash
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
国内
bash
bash <(curl -sSL https://cdn.spiritlhl.net/https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
开设带IPV6地址的虚拟机的注意事项 ​
由于长期闲置IPV6不使用可能导致NDP广播缓存失效重置，一般闲置50分钟左右就会出现IPV6不可用的情况，俗称“IPV6断流”，此时需要设置一个定时任务
shell
echo '*/1 * * * * curl -m 6 -s ipv6.ip.sb || curl -m 6 -s ipv6.ip.sb' | crontab -
在开设出的虚拟机中执行上述命令，可保证IPV6网络一直被使用，不会失效断流
开设虚拟机可使用的镜像 ​
  • 已预安装开启cloudinit
  • 开启SSH登陆
  • 预设置SSH监听V4和V6的22端口
  • 开启允许密码验证登陆
  • 开启允许root登陆
  • 部分预安装Qemu-guest-agent
目前可使用的镜像名字的列表为
https://github.com/oneclickvirt/kvm_images/blob/main/list.text
以及
https://github.com/oneclickvirt/pve_kvm_images
仓库的Release中存储的每日修补镜像
单独开设NAT的虚拟化的虚拟机 ​
  • 自动开设NAT服务器，默认使用Debian10镜像，因为该镜像占用最小
  • 可在命令中自定义需要使用的镜像，这里有给出配置好的镜像，镜像自带空间设置是2~10G硬盘，日常使用至少10G以上即可，除非某些镜像开不起来再增加硬盘大小
  • 可在命令中指定存储盘位置，默认不指定时为local盘即系统盘，可指定为PVE中显示的挂载盘
  • 自定义内存大小推荐512MB内存
  • 自动进行内外网端口映射，含22，80，443端口以及其他25个内外网端口号一样的端口
  • 生成后需要等待一段时间虚拟机内部的cloud-init配置好网络以及登陆信息，大概需要5分钟
  • 虚拟机的相关信息将会存储到WEB端对应VM的NOTES中，可在WEB端查看
  • 如果宿主机自带IPV6子网将自动附加上IPV6网络，但无公网IPV6地址
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是/64的子网
使用方法 ​
  • 系统支持： 
    • x86_64架构的详见 跳转 中列出的系统，使用时只需写文件名字，不需要.qcow2尾缀
    • arm架构的详见 跳转 中列出的系统，使用时只需要写系统名字+系统版本号，如ubuntu20、ubutnu22这种
TIP
注意这里的用户名不能是纯数字，会造成cloudinit出问题，最好是纯英文或英文开头
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
各参数含义
shell
# ./buildvm.sh VMID 用户名 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6地址(留空默认N)
TIP
注意这里的密码最好仅英文与数字混合，且以英文开头，避免密码在设置过程中因为特殊字符被转义而设置失败
测试示例 ​
shell
./buildvm.sh 111 root oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
开设完毕可执行cat vm111查看信息，或到WEB端对应VM的NOTES中查看
以下为开设的示例VM的信息：
属性值
VMID111
SSH登录的用户名root
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小10G
SSH端口40001
80端口40002
443端口40003
内外网映射端口一致的区间50000到50025
系统debian11
宿主机的存储盘local
绑定独立IPV6(留空默认N)N
TIP
注意这里的VMID仅可使用100到256，其他数字不可用
删除指定虚拟机 ​
  • 停止VM
  • 删除VM
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应VMID的虚拟机，这里用上文中的示例111做演示
shell
./pve_delete.sh 111
实际删除数量不固定，空格分隔每个VMID即可，可一次性删除多个
批量开设NAT的虚拟化的虚拟机 ​
WARNING
初次使用前需要保证当前PVE纯净且宿主机未进行过任何端口映射，否则设置冲突可能出现BUG
TIP
开设前请使用screen挂起执行，避免批量开设时间过长，SSH不稳定导致中间执行中断
  • 可多次运行批量生成VM
  • 自动开设NAT服务器，选项留空默认使用debian11镜像，可自定义使用镜像名字，支持的系统名字详见上文支持的镜像列表
  • 自动进行内外网端口映射，含22，80，443端口以及其他25个内外网端口号一样的端口
  • 生成后需要等待一段时间虚拟机内部的cloudinit配置好网络以及登陆信息，大概需要5分钟，每个虚拟机创建之间有间隔等待60秒避免突发性能不足
  • 默认批量开设的虚拟机网络配置为：22，80，443端口及一个25个端口区间的内外网映射
  • 可自定义批量开设的核心数，内存大小，硬盘大小，使用宿主机哪个存储盘，记得自己计算好空闲资源开设
  • 虚拟机的相关信息将会存储到WEB端对应VM的NOTES中，可在WEB端查看
  • 如果宿主机自带IPV6子网将自动附加上IPV6网络，但无公网IPV6地址
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是一个/64子网
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_vm.sh -o create_vm.sh && chmod +x create_vm.sh && bash create_vm.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_vm.sh -o create_vm.sh && chmod +x create_vm.sh && bash create_vm.sh
开设完毕可执行cat vmlog查看信息，或到WEB端对应VM的NOTES中查看
删除所有虚拟机 ​
  • 删除所有VM
  • 删除所有nat的端口映射
  • 重启网络
  • 删除log文件
shell
for vmid in $(qm list | awk '{if(NR>1) print $1}'); do qm stop $vmid; qm destroy $vmid; rm -rf /var/lib/vz/images/$vmid*; done
+import{_ as s,v as l,b as a,R as t}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"Linux虚拟机(KVM/TCG)","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_kvm.md","filePath":"guide/pve/pve_kvm.md","lastUpdated":1747730955000}'),o={name:"guide/pve/pve_kvm.md"},n=t(`
Linux虚拟机(KVM/TCG) ​
SSH登录说明 ​
开设出的虚拟机，默认生成的用户名可以不是root，此时你需要执行sudo -i切换为root用户
默认设置的用户名不是root时，未经过设置的默认的root密码是password或oneclickvirt
登录SSH切换为root权限后，一定要修改root密码，可以使用以下命令修改
国际
bash
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
国内
bash
bash <(curl -sSL https://cdn.spiritlhl.net/https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
开设带IPV6地址的虚拟机的注意事项 ​
由于长期闲置IPV6不使用可能导致NDP广播缓存失效重置，一般闲置50分钟左右就会出现IPV6不可用的情况，俗称“IPV6断流”，此时需要设置一个定时任务
shell
echo '*/1 * * * * curl -m 6 -s ipv6.ip.sb || curl -m 6 -s ipv6.ip.sb' | crontab -
在开设出的虚拟机中执行上述命令，可保证IPV6网络一直被使用，不会失效断流
开设虚拟机可使用的镜像 ​
  • 已预安装开启cloudinit
  • 开启SSH登陆
  • 预设置SSH监听V4和V6的22端口
  • 开启允许密码验证登陆
  • 开启允许root登陆
  • 部分预安装Qemu-guest-agent
目前可使用的镜像名字的列表为
https://github.com/oneclickvirt/kvm_images/blob/main/list.text
以及
https://github.com/oneclickvirt/pve_kvm_images
仓库的Release中存储的每日修补镜像
单独开设NAT的虚拟化的虚拟机 ​
  • 自动开设NAT服务器，默认使用Debian10镜像，因为该镜像占用最小
  • 可在命令中自定义需要使用的镜像，这里有给出配置好的镜像，镜像自带空间设置是2~10G硬盘，日常使用至少10G以上即可，除非某些镜像开不起来再增加硬盘大小
  • 可在命令中指定存储盘位置，默认不指定时为local盘即系统盘，可指定为PVE中显示的挂载盘
  • 自定义内存大小推荐512MB内存
  • 自动进行内外网端口映射，含22，80，443端口以及其他25个内外网端口号一样的端口
  • 生成后需要等待一段时间虚拟机内部的cloud-init配置好网络以及登陆信息，大概需要5分钟
  • 虚拟机的相关信息将会存储到WEB端对应VM的NOTES中，可在WEB端查看
  • 如果宿主机自带IPV6子网将自动附加上IPV6网络，但无公网IPV6地址
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是/64的子网
使用方法 ​
  • 系统支持： 
    • x86_64架构的详见 跳转 中列出的系统，使用时只需写文件名字，不需要.qcow2尾缀
    • arm架构的详见 跳转 中列出的系统，使用时只需要写系统名字+系统版本号，如ubuntu20、ubutnu22这种
TIP
注意这里的用户名不能是纯数字，会造成cloudinit出问题，最好是纯英文或英文开头
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
各参数含义
shell
# ./buildvm.sh VMID 用户名 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6地址(留空默认N)
TIP
注意这里的密码最好仅英文与数字混合，且以英文开头，避免密码在设置过程中因为特殊字符被转义而设置失败
测试示例 ​
shell
./buildvm.sh 111 root oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
开设完毕可执行cat vm111查看信息，或到WEB端对应VM的NOTES中查看
以下为开设的示例VM的信息：
属性值
VMID111
SSH登录的用户名root
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小10G
SSH端口40001
80端口40002
443端口40003
内外网映射端口一致的区间50000到50025
系统debian11
宿主机的存储盘local
绑定独立IPV6(留空默认N)N
TIP
注意这里的VMID仅可使用100到256，其他数字不可用
删除指定虚拟机 ​
  • 停止VM
  • 删除VM
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应VMID的虚拟机，这里用上文中的示例111做演示
shell
./pve_delete.sh 111
实际删除数量不固定，空格分隔每个VMID即可，可一次性删除多个
批量开设NAT的虚拟化的虚拟机 ​
WARNING
初次使用前需要保证当前PVE纯净且宿主机未进行过任何端口映射，否则设置冲突可能出现BUG
TIP
开设前请使用screen挂起执行，避免批量开设时间过长，SSH不稳定导致中间执行中断
  • 可多次运行批量生成VM
  • 自动开设NAT服务器，选项留空默认使用debian11镜像，可自定义使用镜像名字，支持的系统名字详见上文支持的镜像列表
  • 自动进行内外网端口映射，含22，80，443端口以及其他25个内外网端口号一样的端口
  • 生成后需要等待一段时间虚拟机内部的cloudinit配置好网络以及登陆信息，大概需要5分钟，每个虚拟机创建之间有间隔等待60秒避免突发性能不足
  • 默认批量开设的虚拟机网络配置为：22，80，443端口及一个25个端口区间的内外网映射
  • 可自定义批量开设的核心数，内存大小，硬盘大小，使用宿主机哪个存储盘，记得自己计算好空闲资源开设
  • 虚拟机的相关信息将会存储到WEB端对应VM的NOTES中，可在WEB端查看
  • 如果宿主机自带IPV6子网将自动附加上IPV6网络，但无公网IPV6地址
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是一个/64子网
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_vm.sh -o create_vm.sh && chmod +x create_vm.sh && bash create_vm.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_vm.sh -o create_vm.sh && chmod +x create_vm.sh && bash create_vm.sh
开设完毕可执行cat vmlog查看信息，或到WEB端对应VM的NOTES中查看
删除所有虚拟机 ​
  • 删除所有VM
  • 删除所有nat的端口映射
  • 重启网络
  • 删除log文件
shell
for vmid in $(qm list | awk '{if(NR>1) print $1}'); do qm stop $vmid; qm destroy $vmid; rm -rf /var/lib/vz/images/$vmid*; done
 iptables -t nat -F
 iptables -t filter -F
 service networking restart
diff --git a/assets/guide_pve_pve_lxc.md.63c4f147.js b/assets/guide_pve_pve_lxc.md.41c738fa.js
similarity index 99%
rename from assets/guide_pve_pve_lxc.md.63c4f147.js
rename to assets/guide_pve_pve_lxc.md.41c738fa.js
index ae42eaedfd..0ffd25d6b7 100644
--- a/assets/guide_pve_pve_lxc.md.63c4f147.js
+++ b/assets/guide_pve_pve_lxc.md.41c738fa.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"LXC容器","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_lxc.md","filePath":"guide/pve/pve_lxc.md","lastUpdated":1747726389000}'),t={name:"guide/pve/pve_lxc.md"},n=p(`
LXC容器 ​
WARNING
如果你需要在一台服务器上开启超过200个LXC容器，那么不推荐你使用本项目，可能会出现lxcfs访问漂移的问题，产生IO占用无法释放。(系lxc原生问题无法修复)
开设LXC容器可使用的镜像 ​
x86_64：
自动修补镜像：https://github.com/oneclickvirt/lxc_amd64_images/blob/main/fixed_images.txt
TIP
每日自动拉取进行编译和修补
手动修补镜像: https://github.com/oneclickvirt/pve_lxc_images/blob/main/fixed_images.txt
TIP
其中的部分镜像有缺陷，不保证所有PVE可用，名字为 ubuntu16.04、debian6、centos7、opensuse42.2、opensuse42.3 非必要不要使用。
和
执行pveam available --section system查看官方可用的系统名字和版本号
优先级：自修补镜像(Proxmox-VE 5及其以下版本不支持) > 官方默认镜像(都支持)
已通过脚本自动识别版本使用对应镜像
arm：
https://github.com/oneclickvirt/lxc_arm_images/blob/main/fixed_images.txt
可在上面的文件中查看支持的系统，其中列出的debian和ubuntu系统不要使用里面的别名，使用数字代号即可。
TIP
系统参数一律是小写的系统名字拼接版本号，如：debian11，ubuntu22等。 (自修补镜像支持一些偏门系统，如 centos6、centos7、debian8、debian9 等)
所有系统的CT默认用户名是root
TIP
当然有时候会存在特殊情况，version可能是current/base，此时系统参数仅使用英文系统名字即可，如 archlinux、gentoo、kali。
单独开设LXC虚拟化的CT ​
WARNING
初次使用前需要保证当前PVE纯净且宿主机未进行过任何端口映射，否则设置冲突可能出现BUG
TIP
开设前请使用screen挂起执行，避免批量开设时间过长，SSH不稳定导致中间执行中断
  • 自动开设NAT服务器，默认使用Debian11镜像，也可自定义系统
  • 自动进行内外网端口映射，含22，80，443端口以及其他25个内外网端口号一样的端口
  • 生成后需要等待一段时间虚拟机内部配置好网络以及登陆信息，大概需要3分钟
  • 默认开设的网络配置为：22，80，443端口及一个25个端口区间的内外网映射
  • 可自定义开设的核心数，内存大小，硬盘大小，使用宿主机哪个存储盘，记得自己计算好空闲资源开设
  • 可在命令中指定存储盘位置，默认不指定时为local盘即系统盘，可指定为PVE中显示的挂载盘
  • 开设的CT默认已启用SSH且允许root登陆，且已设置支持使用docker的嵌套虚拟化
  • 容器的相关信息将会存储到对应的容器的NOTE中，可在WEB端查看
  • 如果宿主机自带IPV6子网将自动附加上IPV6网络，但无公网IPV6地址
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是一个/64子网
使用方法 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
各参数含义
shell
# ./buildct.sh CTID 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6(默认为N)
测试示例 ​
shell
./buildct.sh 111 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
开设完毕可执行cat ct111查看信息，或在web端的NOTES查看
以下为开设的示例CT的信息：
属性值
CTID111
SSH登录的用户名root
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小5G
SSH端口20001
80端口20002
443端口20003
内外网映射端口一致的区间30000到30025
系统debian11
宿主机的存储盘local
IPV6无
TIP
注意这里的CTID仅可使用100到256，其他数字不可用
删除指定容器 ​
  • 停止CT
  • 删除CT
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应CTID的容器，这里用上文中的示例111做演示
shell
./pve_delete.sh 111
实际删除数量不固定，空格分隔每个CTID即可，可一次性删除多个
批量开设NAT的LXC虚拟化的CT ​
WARNING
初次使用前需要保证当前PVE纯净且宿主机未进行过任何端口映射，否则设置冲突可能出现BUG
TIP
开设前请使用screen挂起执行，避免批量开设时间过长，SSH不稳定导致中间执行中断
  • 可多次运行批量生成CT容器，但需要注意的是宿主机内存记得开点swap免得机器炸了开SWAP点我跳转
  • 每个容器创建之间有间隔等待60秒避免突发性能不足
  • 可自定义批量开设的核心数，内存大小，硬盘大小，使用宿主机哪个存储盘，记得自己计算好空闲资源开设
  • 开设的CT默认已启用SSH且允许root登陆，且已设置支持使用docker的嵌套虚拟化
  • 容器的相关信息将会存储到对应的容器的NOTE中，可在WEB端查看
  • 如果宿主机自带IPV6子网将自动附加上IPV6网络，但无公网IPV6地址
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是一个/64子网
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_ct.sh -o create_ct.sh && chmod +x create_ct.sh && bash create_ct.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_ct.sh -o create_ct.sh && chmod +x create_ct.sh && bash create_ct.sh
开设完毕可执行cat ctlog查看信息，或在web端的NOTES查看
删除所有CT ​
  • 删除所有CT
  • 删除所有nat的端口映射
  • 重启网络
  • 删除log文件
shell
pct list | awk 'NR>1{print $1}' | xargs -I {} sh -c 'pct stop {}; pct destroy {}'
+import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"LXC容器","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_lxc.md","filePath":"guide/pve/pve_lxc.md","lastUpdated":1747730955000}'),t={name:"guide/pve/pve_lxc.md"},n=p(`
LXC容器 ​
WARNING
如果你需要在一台服务器上开启超过200个LXC容器，那么不推荐你使用本项目，可能会出现lxcfs访问漂移的问题，产生IO占用无法释放。(系lxc原生问题无法修复)
开设LXC容器可使用的镜像 ​
x86_64：
自动修补镜像：https://github.com/oneclickvirt/lxc_amd64_images/blob/main/fixed_images.txt
TIP
每日自动拉取进行编译和修补
手动修补镜像: https://github.com/oneclickvirt/pve_lxc_images/blob/main/fixed_images.txt
TIP
其中的部分镜像有缺陷，不保证所有PVE可用，名字为 ubuntu16.04、debian6、centos7、opensuse42.2、opensuse42.3 非必要不要使用。
和
执行pveam available --section system查看官方可用的系统名字和版本号
优先级：自修补镜像(Proxmox-VE 5及其以下版本不支持) > 官方默认镜像(都支持)
已通过脚本自动识别版本使用对应镜像
arm：
https://github.com/oneclickvirt/lxc_arm_images/blob/main/fixed_images.txt
可在上面的文件中查看支持的系统，其中列出的debian和ubuntu系统不要使用里面的别名，使用数字代号即可。
TIP
系统参数一律是小写的系统名字拼接版本号，如：debian11，ubuntu22等。 (自修补镜像支持一些偏门系统，如 centos6、centos7、debian8、debian9 等)
所有系统的CT默认用户名是root
TIP
当然有时候会存在特殊情况，version可能是current/base，此时系统参数仅使用英文系统名字即可，如 archlinux、gentoo、kali。
单独开设LXC虚拟化的CT ​
WARNING
初次使用前需要保证当前PVE纯净且宿主机未进行过任何端口映射，否则设置冲突可能出现BUG
TIP
开设前请使用screen挂起执行，避免批量开设时间过长，SSH不稳定导致中间执行中断
  • 自动开设NAT服务器，默认使用Debian11镜像，也可自定义系统
  • 自动进行内外网端口映射，含22，80，443端口以及其他25个内外网端口号一样的端口
  • 生成后需要等待一段时间虚拟机内部配置好网络以及登陆信息，大概需要3分钟
  • 默认开设的网络配置为：22，80，443端口及一个25个端口区间的内外网映射
  • 可自定义开设的核心数，内存大小，硬盘大小，使用宿主机哪个存储盘，记得自己计算好空闲资源开设
  • 可在命令中指定存储盘位置，默认不指定时为local盘即系统盘，可指定为PVE中显示的挂载盘
  • 开设的CT默认已启用SSH且允许root登陆，且已设置支持使用docker的嵌套虚拟化
  • 容器的相关信息将会存储到对应的容器的NOTE中，可在WEB端查看
  • 如果宿主机自带IPV6子网将自动附加上IPV6网络，但无公网IPV6地址
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是一个/64子网
使用方法 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
各参数含义
shell
# ./buildct.sh CTID 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6(默认为N)
测试示例 ​
shell
./buildct.sh 111 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
开设完毕可执行cat ct111查看信息，或在web端的NOTES查看
以下为开设的示例CT的信息：
属性值
CTID111
SSH登录的用户名root
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小5G
SSH端口20001
80端口20002
443端口20003
内外网映射端口一致的区间30000到30025
系统debian11
宿主机的存储盘local
IPV6无
TIP
注意这里的CTID仅可使用100到256，其他数字不可用
删除指定容器 ​
  • 停止CT
  • 删除CT
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应CTID的容器，这里用上文中的示例111做演示
shell
./pve_delete.sh 111
实际删除数量不固定，空格分隔每个CTID即可，可一次性删除多个
批量开设NAT的LXC虚拟化的CT ​
WARNING
初次使用前需要保证当前PVE纯净且宿主机未进行过任何端口映射，否则设置冲突可能出现BUG
TIP
开设前请使用screen挂起执行，避免批量开设时间过长，SSH不稳定导致中间执行中断
  • 可多次运行批量生成CT容器，但需要注意的是宿主机内存记得开点swap免得机器炸了开SWAP点我跳转
  • 每个容器创建之间有间隔等待60秒避免突发性能不足
  • 可自定义批量开设的核心数，内存大小，硬盘大小，使用宿主机哪个存储盘，记得自己计算好空闲资源开设
  • 开设的CT默认已启用SSH且允许root登陆，且已设置支持使用docker的嵌套虚拟化
  • 容器的相关信息将会存储到对应的容器的NOTE中，可在WEB端查看
  • 如果宿主机自带IPV6子网将自动附加上IPV6网络，但无公网IPV6地址
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是一个/64子网
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_ct.sh -o create_ct.sh && chmod +x create_ct.sh && bash create_ct.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_ct.sh -o create_ct.sh && chmod +x create_ct.sh && bash create_ct.sh
开设完毕可执行cat ctlog查看信息，或在web端的NOTES查看
删除所有CT ​
  • 删除所有CT
  • 删除所有nat的端口映射
  • 重启网络
  • 删除log文件
shell
pct list | awk 'NR>1{print $1}' | xargs -I {} sh -c 'pct stop {}; pct destroy {}'
 rm -rf ct*
 iptables -t nat -F
 iptables -t filter -F
diff --git a/assets/guide_pve_pve_lxc.md.63c4f147.lean.js b/assets/guide_pve_pve_lxc.md.41c738fa.lean.js
similarity index 99%
rename from assets/guide_pve_pve_lxc.md.63c4f147.lean.js
rename to assets/guide_pve_pve_lxc.md.41c738fa.lean.js
index ae42eaedfd..0ffd25d6b7 100644
--- a/assets/guide_pve_pve_lxc.md.63c4f147.lean.js
+++ b/assets/guide_pve_pve_lxc.md.41c738fa.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"LXC容器","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_lxc.md","filePath":"guide/pve/pve_lxc.md","lastUpdated":1747726389000}'),t={name:"guide/pve/pve_lxc.md"},n=p(`
LXC容器 ​
WARNING
如果你需要在一台服务器上开启超过200个LXC容器，那么不推荐你使用本项目，可能会出现lxcfs访问漂移的问题，产生IO占用无法释放。(系lxc原生问题无法修复)
开设LXC容器可使用的镜像 ​
x86_64：
自动修补镜像：https://github.com/oneclickvirt/lxc_amd64_images/blob/main/fixed_images.txt
TIP
每日自动拉取进行编译和修补
手动修补镜像: https://github.com/oneclickvirt/pve_lxc_images/blob/main/fixed_images.txt
TIP
其中的部分镜像有缺陷，不保证所有PVE可用，名字为 ubuntu16.04、debian6、centos7、opensuse42.2、opensuse42.3 非必要不要使用。
和
执行pveam available --section system查看官方可用的系统名字和版本号
优先级：自修补镜像(Proxmox-VE 5及其以下版本不支持) > 官方默认镜像(都支持)
已通过脚本自动识别版本使用对应镜像
arm：
https://github.com/oneclickvirt/lxc_arm_images/blob/main/fixed_images.txt
可在上面的文件中查看支持的系统，其中列出的debian和ubuntu系统不要使用里面的别名，使用数字代号即可。
TIP
系统参数一律是小写的系统名字拼接版本号，如：debian11，ubuntu22等。 (自修补镜像支持一些偏门系统，如 centos6、centos7、debian8、debian9 等)
所有系统的CT默认用户名是root
TIP
当然有时候会存在特殊情况，version可能是current/base，此时系统参数仅使用英文系统名字即可，如 archlinux、gentoo、kali。
单独开设LXC虚拟化的CT ​
WARNING
初次使用前需要保证当前PVE纯净且宿主机未进行过任何端口映射，否则设置冲突可能出现BUG
TIP
开设前请使用screen挂起执行，避免批量开设时间过长，SSH不稳定导致中间执行中断
  • 自动开设NAT服务器，默认使用Debian11镜像，也可自定义系统
  • 自动进行内外网端口映射，含22，80，443端口以及其他25个内外网端口号一样的端口
  • 生成后需要等待一段时间虚拟机内部配置好网络以及登陆信息，大概需要3分钟
  • 默认开设的网络配置为：22，80，443端口及一个25个端口区间的内外网映射
  • 可自定义开设的核心数，内存大小，硬盘大小，使用宿主机哪个存储盘，记得自己计算好空闲资源开设
  • 可在命令中指定存储盘位置，默认不指定时为local盘即系统盘，可指定为PVE中显示的挂载盘
  • 开设的CT默认已启用SSH且允许root登陆，且已设置支持使用docker的嵌套虚拟化
  • 容器的相关信息将会存储到对应的容器的NOTE中，可在WEB端查看
  • 如果宿主机自带IPV6子网将自动附加上IPV6网络，但无公网IPV6地址
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是一个/64子网
使用方法 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
各参数含义
shell
# ./buildct.sh CTID 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6(默认为N)
测试示例 ​
shell
./buildct.sh 111 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
开设完毕可执行cat ct111查看信息，或在web端的NOTES查看
以下为开设的示例CT的信息：
属性值
CTID111
SSH登录的用户名root
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小5G
SSH端口20001
80端口20002
443端口20003
内外网映射端口一致的区间30000到30025
系统debian11
宿主机的存储盘local
IPV6无
TIP
注意这里的CTID仅可使用100到256，其他数字不可用
删除指定容器 ​
  • 停止CT
  • 删除CT
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应CTID的容器，这里用上文中的示例111做演示
shell
./pve_delete.sh 111
实际删除数量不固定，空格分隔每个CTID即可，可一次性删除多个
批量开设NAT的LXC虚拟化的CT ​
WARNING
初次使用前需要保证当前PVE纯净且宿主机未进行过任何端口映射，否则设置冲突可能出现BUG
TIP
开设前请使用screen挂起执行，避免批量开设时间过长，SSH不稳定导致中间执行中断
  • 可多次运行批量生成CT容器，但需要注意的是宿主机内存记得开点swap免得机器炸了开SWAP点我跳转
  • 每个容器创建之间有间隔等待60秒避免突发性能不足
  • 可自定义批量开设的核心数，内存大小，硬盘大小，使用宿主机哪个存储盘，记得自己计算好空闲资源开设
  • 开设的CT默认已启用SSH且允许root登陆，且已设置支持使用docker的嵌套虚拟化
  • 容器的相关信息将会存储到对应的容器的NOTE中，可在WEB端查看
  • 如果宿主机自带IPV6子网将自动附加上IPV6网络，但无公网IPV6地址
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是一个/64子网
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_ct.sh -o create_ct.sh && chmod +x create_ct.sh && bash create_ct.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_ct.sh -o create_ct.sh && chmod +x create_ct.sh && bash create_ct.sh
开设完毕可执行cat ctlog查看信息，或在web端的NOTES查看
删除所有CT ​
  • 删除所有CT
  • 删除所有nat的端口映射
  • 重启网络
  • 删除log文件
shell
pct list | awk 'NR>1{print $1}' | xargs -I {} sh -c 'pct stop {}; pct destroy {}'
+import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"LXC容器","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_lxc.md","filePath":"guide/pve/pve_lxc.md","lastUpdated":1747730955000}'),t={name:"guide/pve/pve_lxc.md"},n=p(`
LXC容器 ​
WARNING
如果你需要在一台服务器上开启超过200个LXC容器，那么不推荐你使用本项目，可能会出现lxcfs访问漂移的问题，产生IO占用无法释放。(系lxc原生问题无法修复)
开设LXC容器可使用的镜像 ​
x86_64：
自动修补镜像：https://github.com/oneclickvirt/lxc_amd64_images/blob/main/fixed_images.txt
TIP
每日自动拉取进行编译和修补
手动修补镜像: https://github.com/oneclickvirt/pve_lxc_images/blob/main/fixed_images.txt
TIP
其中的部分镜像有缺陷，不保证所有PVE可用，名字为 ubuntu16.04、debian6、centos7、opensuse42.2、opensuse42.3 非必要不要使用。
和
执行pveam available --section system查看官方可用的系统名字和版本号
优先级：自修补镜像(Proxmox-VE 5及其以下版本不支持) > 官方默认镜像(都支持)
已通过脚本自动识别版本使用对应镜像
arm：
https://github.com/oneclickvirt/lxc_arm_images/blob/main/fixed_images.txt
可在上面的文件中查看支持的系统，其中列出的debian和ubuntu系统不要使用里面的别名，使用数字代号即可。
TIP
系统参数一律是小写的系统名字拼接版本号，如：debian11，ubuntu22等。 (自修补镜像支持一些偏门系统，如 centos6、centos7、debian8、debian9 等)
所有系统的CT默认用户名是root
TIP
当然有时候会存在特殊情况，version可能是current/base，此时系统参数仅使用英文系统名字即可，如 archlinux、gentoo、kali。
单独开设LXC虚拟化的CT ​
WARNING
初次使用前需要保证当前PVE纯净且宿主机未进行过任何端口映射，否则设置冲突可能出现BUG
TIP
开设前请使用screen挂起执行，避免批量开设时间过长，SSH不稳定导致中间执行中断
  • 自动开设NAT服务器，默认使用Debian11镜像，也可自定义系统
  • 自动进行内外网端口映射，含22，80，443端口以及其他25个内外网端口号一样的端口
  • 生成后需要等待一段时间虚拟机内部配置好网络以及登陆信息，大概需要3分钟
  • 默认开设的网络配置为：22，80，443端口及一个25个端口区间的内外网映射
  • 可自定义开设的核心数，内存大小，硬盘大小，使用宿主机哪个存储盘，记得自己计算好空闲资源开设
  • 可在命令中指定存储盘位置，默认不指定时为local盘即系统盘，可指定为PVE中显示的挂载盘
  • 开设的CT默认已启用SSH且允许root登陆，且已设置支持使用docker的嵌套虚拟化
  • 容器的相关信息将会存储到对应的容器的NOTE中，可在WEB端查看
  • 如果宿主机自带IPV6子网将自动附加上IPV6网络，但无公网IPV6地址
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是一个/64子网
使用方法 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
各参数含义
shell
# ./buildct.sh CTID 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6(默认为N)
测试示例 ​
shell
./buildct.sh 111 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
开设完毕可执行cat ct111查看信息，或在web端的NOTES查看
以下为开设的示例CT的信息：
属性值
CTID111
SSH登录的用户名root
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小5G
SSH端口20001
80端口20002
443端口20003
内外网映射端口一致的区间30000到30025
系统debian11
宿主机的存储盘local
IPV6无
TIP
注意这里的CTID仅可使用100到256，其他数字不可用
删除指定容器 ​
  • 停止CT
  • 删除CT
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应CTID的容器，这里用上文中的示例111做演示
shell
./pve_delete.sh 111
实际删除数量不固定，空格分隔每个CTID即可，可一次性删除多个
批量开设NAT的LXC虚拟化的CT ​
WARNING
初次使用前需要保证当前PVE纯净且宿主机未进行过任何端口映射，否则设置冲突可能出现BUG
TIP
开设前请使用screen挂起执行，避免批量开设时间过长，SSH不稳定导致中间执行中断
  • 可多次运行批量生成CT容器，但需要注意的是宿主机内存记得开点swap免得机器炸了开SWAP点我跳转
  • 每个容器创建之间有间隔等待60秒避免突发性能不足
  • 可自定义批量开设的核心数，内存大小，硬盘大小，使用宿主机哪个存储盘，记得自己计算好空闲资源开设
  • 开设的CT默认已启用SSH且允许root登陆，且已设置支持使用docker的嵌套虚拟化
  • 容器的相关信息将会存储到对应的容器的NOTE中，可在WEB端查看
  • 如果宿主机自带IPV6子网将自动附加上IPV6网络，但无公网IPV6地址
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是一个/64子网
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_ct.sh -o create_ct.sh && chmod +x create_ct.sh && bash create_ct.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_ct.sh -o create_ct.sh && chmod +x create_ct.sh && bash create_ct.sh
开设完毕可执行cat ctlog查看信息，或在web端的NOTES查看
删除所有CT ​
  • 删除所有CT
  • 删除所有nat的端口映射
  • 重启网络
  • 删除log文件
shell
pct list | awk 'NR>1{print $1}' | xargs -I {} sh -c 'pct stop {}; pct destroy {}'
 rm -rf ct*
 iptables -t nat -F
 iptables -t filter -F
diff --git a/assets/guide_pve_pve_macos.md.96eb9a9f.js b/assets/guide_pve_pve_macos.md.bfd0da59.js
similarity index 99%
rename from assets/guide_pve_pve_macos.md.96eb9a9f.js
rename to assets/guide_pve_pve_macos.md.bfd0da59.js
index 002522a7b1..25a25db8e2 100644
--- a/assets/guide_pve_pve_macos.md.96eb9a9f.js
+++ b/assets/guide_pve_pve_macos.md.bfd0da59.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as o,R as p}from"./chunks/framework.70afa331.js";import{_ as l}from"./chunks/wk7.6fe7513d.js";const e="/assets/mac0.935d53f3.png",n="/assets/mac00.4296be7b.png",c="/assets/mac1.3307e401.png",t="/assets/mac2.da6ce0bc.png",r="/assets/mac3.76a50b9f.png",i="/assets/mac4.c341ba50.png",d="/assets/mac5.39e1c9a4.png",C="/assets/mac6.1cc0462b.png",m="/assets/mac7.181275ae.png",y="/assets/mac8.dd556f02.png",h="/assets/mac9.c5d88eba.png",A="/assets/mac10.e9c284db.png",D="/assets/mac11.a7587e0e.png",g="/assets/mac12.06b051d3.png",u="/assets/mac13.7d4e3199.png",_="/assets/mac14.39a58b6a.png",b="/assets/mac15.f151793c.png",v="/assets/mac16.eae177db.png",F="/assets/mac17.be61913a.png",E="/assets/mac18.f9454618.png",B="/assets/mac19.845f5510.png",f="/assets/mac20.49a5800c.png",k="/assets/mac21.2c30b60f.png",z=JSON.parse('{"title":"开设MacOS虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_macos.md","filePath":"guide/pve/pve_macos.md","lastUpdated":1747726389000}'),x={name:"guide/pve/pve_macos.md"},P=p(`
开设MacOS虚拟机 ​
前置需求 ​
系统和硬件配置要求 --> 检测环境
只有检测环境检测出宿主机支持KVM嵌套虚拟化时，才可以开设MACOS虚拟机，否则会被硬件识别无法开设。
前置环境设置 ​
  • 自动识别 CPU 类型（AMD 或 Intel），并根据类型设置嵌套虚拟化参数。
  • 修改 GRUB 启动参数，启用 IOMMU 和禁用默认 framebuffer。
  • 添加 VFIO 模块支持，便于直通硬件设备。
  • 黑名单声卡和显卡驱动模块，避免与 macOS 冲突。
  • 配置 KVM 相关内核参数，忽略 MSR 错误，提高兼容性。
  • 修补 Proxmox 前端状态检测逻辑，绕过状态限制。
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/extra_scripts/configure_macos.sh -o configure_macos.sh && chmod +x configure_macos.sh && bash configure_macos.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/extra_scripts/configure_macos.sh -o configure_macos.sh && chmod +x configure_macos.sh && bash configure_macos.sh
执行成功后会显示15秒后重启本机，这是正常的流程，不重启无法使得内核参数生效。
系统镜像下载 ​
  • 所有镜像已预装组件，体积较大（最小约4.9GB），下载与解压任务将后台挂起执行。
  • 镜像为完整系统含所有组件，无需联网即可引导使用。
  • 若系统盘空闲空间不足镜像大小的2倍，将拒绝下载。
  • 镜像为7z压缩格式，下载后需解压才能使用。
  • 可随时查看当前下载与解压任务状态，完成后方可创建虚拟机。
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_macos_images.sh -o install_macos_images.sh && chmod +x install_macos_images.sh && bash install_macos_images.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_macos_images.sh -o install_macos_images.sh && chmod +x install_macos_images.sh && bash install_macos_images.sh
或
shell
bash install_macos_images.sh
后台下载任务挂起执行后，可关闭SSH窗口，等待半小时到3个小时(具体等待时间取决于你的服务器带宽大小和连通性)，下载iso的7z压缩包。
下载任务执行完毕后，查询显示当前下载任务为空时，就可以选择解压任务执行了，解压挂起执行等待的时间取决于你的服务器CPU性能。
当解压任务执行完毕，查询显示当前解压任务为空时，一切准备工作就算准备好了。
相同类型的任务可以并发，也可以随时取消某个任务，取消时需要输入PID的值。
通过 https://github.com/oneclickvirt/macos 制作的目前支持的镜像压缩包：
# 按系统发布时间从旧到新
+import{_ as s,v as a,b as o,R as p}from"./chunks/framework.70afa331.js";import{_ as l}from"./chunks/wk7.6fe7513d.js";const e="/assets/mac0.935d53f3.png",n="/assets/mac00.4296be7b.png",c="/assets/mac1.3307e401.png",t="/assets/mac2.da6ce0bc.png",r="/assets/mac3.76a50b9f.png",i="/assets/mac4.c341ba50.png",d="/assets/mac5.39e1c9a4.png",C="/assets/mac6.1cc0462b.png",m="/assets/mac7.181275ae.png",y="/assets/mac8.dd556f02.png",h="/assets/mac9.c5d88eba.png",A="/assets/mac10.e9c284db.png",D="/assets/mac11.a7587e0e.png",g="/assets/mac12.06b051d3.png",u="/assets/mac13.7d4e3199.png",_="/assets/mac14.39a58b6a.png",b="/assets/mac15.f151793c.png",v="/assets/mac16.eae177db.png",F="/assets/mac17.be61913a.png",E="/assets/mac18.f9454618.png",B="/assets/mac19.845f5510.png",f="/assets/mac20.49a5800c.png",k="/assets/mac21.2c30b60f.png",z=JSON.parse('{"title":"开设MacOS虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_macos.md","filePath":"guide/pve/pve_macos.md","lastUpdated":1747730955000}'),x={name:"guide/pve/pve_macos.md"},P=p(`
开设MacOS虚拟机 ​
前置需求 ​
系统和硬件配置要求 --> 检测环境
只有检测环境检测出宿主机支持KVM嵌套虚拟化时，才可以开设MACOS虚拟机，否则会被硬件识别无法开设。
前置环境设置 ​
  • 自动识别 CPU 类型（AMD 或 Intel），并根据类型设置嵌套虚拟化参数。
  • 修改 GRUB 启动参数，启用 IOMMU 和禁用默认 framebuffer。
  • 添加 VFIO 模块支持，便于直通硬件设备。
  • 黑名单声卡和显卡驱动模块，避免与 macOS 冲突。
  • 配置 KVM 相关内核参数，忽略 MSR 错误，提高兼容性。
  • 修补 Proxmox 前端状态检测逻辑，绕过状态限制。
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/extra_scripts/configure_macos.sh -o configure_macos.sh && chmod +x configure_macos.sh && bash configure_macos.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/extra_scripts/configure_macos.sh -o configure_macos.sh && chmod +x configure_macos.sh && bash configure_macos.sh
执行成功后会显示15秒后重启本机，这是正常的流程，不重启无法使得内核参数生效。
系统镜像下载 ​
  • 所有镜像已预装组件，体积较大（最小约4.9GB），下载与解压任务将后台挂起执行。
  • 镜像为完整系统含所有组件，无需联网即可引导使用。
  • 若系统盘空闲空间不足镜像大小的2倍，将拒绝下载。
  • 镜像为7z压缩格式，下载后需解压才能使用。
  • 可随时查看当前下载与解压任务状态，完成后方可创建虚拟机。
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_macos_images.sh -o install_macos_images.sh && chmod +x install_macos_images.sh && bash install_macos_images.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_macos_images.sh -o install_macos_images.sh && chmod +x install_macos_images.sh && bash install_macos_images.sh
或
shell
bash install_macos_images.sh
后台下载任务挂起执行后，可关闭SSH窗口，等待半小时到3个小时(具体等待时间取决于你的服务器带宽大小和连通性)，下载iso的7z压缩包。
下载任务执行完毕后，查询显示当前下载任务为空时，就可以选择解压任务执行了，解压挂起执行等待的时间取决于你的服务器CPU性能。
当解压任务执行完毕，查询显示当前解压任务为空时，一切准备工作就算准备好了。
相同类型的任务可以并发，也可以随时取消某个任务，取消时需要输入PID的值。
通过 https://github.com/oneclickvirt/macos 制作的目前支持的镜像压缩包：
# 按系统发布时间从旧到新
 high-sierra.iso.7z (大小: 5.23GB)
 mojave.iso.7z (大小: 6.03GB)
 catalina.iso.7z (大小: 8.33GB)
diff --git a/assets/guide_pve_pve_macos.md.96eb9a9f.lean.js b/assets/guide_pve_pve_macos.md.bfd0da59.lean.js
similarity index 99%
rename from assets/guide_pve_pve_macos.md.96eb9a9f.lean.js
rename to assets/guide_pve_pve_macos.md.bfd0da59.lean.js
index 002522a7b1..25a25db8e2 100644
--- a/assets/guide_pve_pve_macos.md.96eb9a9f.lean.js
+++ b/assets/guide_pve_pve_macos.md.bfd0da59.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as o,R as p}from"./chunks/framework.70afa331.js";import{_ as l}from"./chunks/wk7.6fe7513d.js";const e="/assets/mac0.935d53f3.png",n="/assets/mac00.4296be7b.png",c="/assets/mac1.3307e401.png",t="/assets/mac2.da6ce0bc.png",r="/assets/mac3.76a50b9f.png",i="/assets/mac4.c341ba50.png",d="/assets/mac5.39e1c9a4.png",C="/assets/mac6.1cc0462b.png",m="/assets/mac7.181275ae.png",y="/assets/mac8.dd556f02.png",h="/assets/mac9.c5d88eba.png",A="/assets/mac10.e9c284db.png",D="/assets/mac11.a7587e0e.png",g="/assets/mac12.06b051d3.png",u="/assets/mac13.7d4e3199.png",_="/assets/mac14.39a58b6a.png",b="/assets/mac15.f151793c.png",v="/assets/mac16.eae177db.png",F="/assets/mac17.be61913a.png",E="/assets/mac18.f9454618.png",B="/assets/mac19.845f5510.png",f="/assets/mac20.49a5800c.png",k="/assets/mac21.2c30b60f.png",z=JSON.parse('{"title":"开设MacOS虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_macos.md","filePath":"guide/pve/pve_macos.md","lastUpdated":1747726389000}'),x={name:"guide/pve/pve_macos.md"},P=p(`
开设MacOS虚拟机 ​
前置需求 ​
系统和硬件配置要求 --> 检测环境
只有检测环境检测出宿主机支持KVM嵌套虚拟化时，才可以开设MACOS虚拟机，否则会被硬件识别无法开设。
前置环境设置 ​
  • 自动识别 CPU 类型（AMD 或 Intel），并根据类型设置嵌套虚拟化参数。
  • 修改 GRUB 启动参数，启用 IOMMU 和禁用默认 framebuffer。
  • 添加 VFIO 模块支持，便于直通硬件设备。
  • 黑名单声卡和显卡驱动模块，避免与 macOS 冲突。
  • 配置 KVM 相关内核参数，忽略 MSR 错误，提高兼容性。
  • 修补 Proxmox 前端状态检测逻辑，绕过状态限制。
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/extra_scripts/configure_macos.sh -o configure_macos.sh && chmod +x configure_macos.sh && bash configure_macos.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/extra_scripts/configure_macos.sh -o configure_macos.sh && chmod +x configure_macos.sh && bash configure_macos.sh
执行成功后会显示15秒后重启本机，这是正常的流程，不重启无法使得内核参数生效。
系统镜像下载 ​
  • 所有镜像已预装组件，体积较大（最小约4.9GB），下载与解压任务将后台挂起执行。
  • 镜像为完整系统含所有组件，无需联网即可引导使用。
  • 若系统盘空闲空间不足镜像大小的2倍，将拒绝下载。
  • 镜像为7z压缩格式，下载后需解压才能使用。
  • 可随时查看当前下载与解压任务状态，完成后方可创建虚拟机。
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_macos_images.sh -o install_macos_images.sh && chmod +x install_macos_images.sh && bash install_macos_images.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_macos_images.sh -o install_macos_images.sh && chmod +x install_macos_images.sh && bash install_macos_images.sh
或
shell
bash install_macos_images.sh
后台下载任务挂起执行后，可关闭SSH窗口，等待半小时到3个小时(具体等待时间取决于你的服务器带宽大小和连通性)，下载iso的7z压缩包。
下载任务执行完毕后，查询显示当前下载任务为空时，就可以选择解压任务执行了，解压挂起执行等待的时间取决于你的服务器CPU性能。
当解压任务执行完毕，查询显示当前解压任务为空时，一切准备工作就算准备好了。
相同类型的任务可以并发，也可以随时取消某个任务，取消时需要输入PID的值。
通过 https://github.com/oneclickvirt/macos 制作的目前支持的镜像压缩包：
# 按系统发布时间从旧到新
+import{_ as s,v as a,b as o,R as p}from"./chunks/framework.70afa331.js";import{_ as l}from"./chunks/wk7.6fe7513d.js";const e="/assets/mac0.935d53f3.png",n="/assets/mac00.4296be7b.png",c="/assets/mac1.3307e401.png",t="/assets/mac2.da6ce0bc.png",r="/assets/mac3.76a50b9f.png",i="/assets/mac4.c341ba50.png",d="/assets/mac5.39e1c9a4.png",C="/assets/mac6.1cc0462b.png",m="/assets/mac7.181275ae.png",y="/assets/mac8.dd556f02.png",h="/assets/mac9.c5d88eba.png",A="/assets/mac10.e9c284db.png",D="/assets/mac11.a7587e0e.png",g="/assets/mac12.06b051d3.png",u="/assets/mac13.7d4e3199.png",_="/assets/mac14.39a58b6a.png",b="/assets/mac15.f151793c.png",v="/assets/mac16.eae177db.png",F="/assets/mac17.be61913a.png",E="/assets/mac18.f9454618.png",B="/assets/mac19.845f5510.png",f="/assets/mac20.49a5800c.png",k="/assets/mac21.2c30b60f.png",z=JSON.parse('{"title":"开设MacOS虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_macos.md","filePath":"guide/pve/pve_macos.md","lastUpdated":1747730955000}'),x={name:"guide/pve/pve_macos.md"},P=p(`
开设MacOS虚拟机 ​
前置需求 ​
系统和硬件配置要求 --> 检测环境
只有检测环境检测出宿主机支持KVM嵌套虚拟化时，才可以开设MACOS虚拟机，否则会被硬件识别无法开设。
前置环境设置 ​
  • 自动识别 CPU 类型（AMD 或 Intel），并根据类型设置嵌套虚拟化参数。
  • 修改 GRUB 启动参数，启用 IOMMU 和禁用默认 framebuffer。
  • 添加 VFIO 模块支持，便于直通硬件设备。
  • 黑名单声卡和显卡驱动模块，避免与 macOS 冲突。
  • 配置 KVM 相关内核参数，忽略 MSR 错误，提高兼容性。
  • 修补 Proxmox 前端状态检测逻辑，绕过状态限制。
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/extra_scripts/configure_macos.sh -o configure_macos.sh && chmod +x configure_macos.sh && bash configure_macos.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/extra_scripts/configure_macos.sh -o configure_macos.sh && chmod +x configure_macos.sh && bash configure_macos.sh
执行成功后会显示15秒后重启本机，这是正常的流程，不重启无法使得内核参数生效。
系统镜像下载 ​
  • 所有镜像已预装组件，体积较大（最小约4.9GB），下载与解压任务将后台挂起执行。
  • 镜像为完整系统含所有组件，无需联网即可引导使用。
  • 若系统盘空闲空间不足镜像大小的2倍，将拒绝下载。
  • 镜像为7z压缩格式，下载后需解压才能使用。
  • 可随时查看当前下载与解压任务状态，完成后方可创建虚拟机。
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_macos_images.sh -o install_macos_images.sh && chmod +x install_macos_images.sh && bash install_macos_images.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_macos_images.sh -o install_macos_images.sh && chmod +x install_macos_images.sh && bash install_macos_images.sh
或
shell
bash install_macos_images.sh
后台下载任务挂起执行后，可关闭SSH窗口，等待半小时到3个小时(具体等待时间取决于你的服务器带宽大小和连通性)，下载iso的7z压缩包。
下载任务执行完毕后，查询显示当前下载任务为空时，就可以选择解压任务执行了，解压挂起执行等待的时间取决于你的服务器CPU性能。
当解压任务执行完毕，查询显示当前解压任务为空时，一切准备工作就算准备好了。
相同类型的任务可以并发，也可以随时取消某个任务，取消时需要输入PID的值。
通过 https://github.com/oneclickvirt/macos 制作的目前支持的镜像压缩包：
# 按系统发布时间从旧到新
 high-sierra.iso.7z (大小: 5.23GB)
 mojave.iso.7z (大小: 6.03GB)
 catalina.iso.7z (大小: 8.33GB)
diff --git a/assets/guide_pve_pve_precheck.md.dc29dc3e.js b/assets/guide_pve_pve_precheck.md.2b124758.js
similarity index 99%
rename from assets/guide_pve_pve_precheck.md.dc29dc3e.js
rename to assets/guide_pve_pve_precheck.md.2b124758.js
index 7fa3a2b315..158896c5d1 100644
--- a/assets/guide_pve_pve_precheck.md.dc29dc3e.js
+++ b/assets/guide_pve_pve_precheck.md.2b124758.js
@@ -1,3 +1,3 @@
-import{_ as s,v as a,b as p,R as l}from"./chunks/framework.70afa331.js";const n="/assets/pve_kvm_1.0f7e84f0.png",e="/assets/pve_kvm_2.cefb9578.png",o="/assets/pve_kvm_3.1d307586.png",b=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_precheck.md","filePath":"guide/pve/pve_precheck.md","lastUpdated":1747726389000}'),t={name:"guide/pve/pve_precheck.md"},c=l(`
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果有未适配的商家或机器欢迎联系@spiritlhl_bot，有空会尝试支持一下
WARNING
会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/pve
各种要求 ​
建议debian在使用前尽量使用最新的稳定版本的系统
不要在动态IP的服务器上使用本套脚本(重启机器后自动切换本机IP的服务器暂不支持，重启机器后IP不自动切换的支持)
本项目的一键安装脚本只适配Debian系统，非Debian无法通过APT源安装，官方只给了Debian的镜像，其他系统只能使用ISO安装，或使用自定义分区和常见问题分区中的其他方式解决问题。
  • 系统要求：Debian 8+
TIP
建议debian12而不是debian11，debian11在部分独立服务器上有网络重启的BUG。
  • 硬件要求：2核2G内存x86_64或arm架构服务器硬盘至少20G
  • 可开KVM的硬件要求：VM-X或AMD-V支持 (部分VPS和全部独服支持)
  • 如果硬件或系统需求不满足，可使用incus批量开LXC容器跳转
如果使用IPV6隧道进行宿主机的IPV6子网附加，务必在PVE安装成功但网关未自动设置时在对应文件添加内容，不要在一开始(未安装PVE)就进行IPV6隧道的添加。
开设虚拟内存(SWAP)(非必须的可选项) ​
TIP
内存开点swap免得机器炸了，如果你的宿主机内存不够用硬盘又很多空闲的话
单位换算：输入 1024 产生 1G SWAP-虚拟内存，虚拟内存占用硬盘空间，当实际内存不够用时将自动使用虚拟内存做内存使用，但随之带来IO高占用以及CPU性能占用
建议只开实际内存大小两倍大小的虚拟内存
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
检测环境 ​
  • 本项目相关脚本执行前务必执行本脚本检测环境，如果不符合安装PVE的要求则无法使用后续的脚本
  • 检测本机IPV6的网络配置情况(有无IPV6都可安装，只是查询一下罢了)
  • 检测硬件配置是否满足最低要求
  • 检测硬件环境是否可嵌套虚拟化KVM类型的服务器，不可嵌套虚拟化KVM的也可以开QEMU的TCG的服务器，性能较差
  • 检测系统环境是否可嵌套虚拟化KVM类型的服务器，不可嵌套虚拟化KVM的也可以开QEMU的TCG的服务器，性能较差
  • 不可嵌套虚拟化KVM的服务器不推荐安装PVE，不如使用incus性能更好
国际
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh)
国内
bash
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh)
如果你需要更新IPV6信息再查询，那么执行以下命令后再查询
bash
rm -rf /usr/local/bin/pve_ipv6*
+import{_ as s,v as a,b as p,R as l}from"./chunks/framework.70afa331.js";const n="/assets/pve_kvm_1.0f7e84f0.png",e="/assets/pve_kvm_2.cefb9578.png",o="/assets/pve_kvm_3.1d307586.png",b=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_precheck.md","filePath":"guide/pve/pve_precheck.md","lastUpdated":1747730955000}'),t={name:"guide/pve/pve_precheck.md"},c=l(`
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果有未适配的商家或机器欢迎联系@spiritlhl_bot，有空会尝试支持一下
WARNING
会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/pve
各种要求 ​
建议debian在使用前尽量使用最新的稳定版本的系统
不要在动态IP的服务器上使用本套脚本(重启机器后自动切换本机IP的服务器暂不支持，重启机器后IP不自动切换的支持)
本项目的一键安装脚本只适配Debian系统，非Debian无法通过APT源安装，官方只给了Debian的镜像，其他系统只能使用ISO安装，或使用自定义分区和常见问题分区中的其他方式解决问题。
  • 系统要求：Debian 8+
TIP
建议debian12而不是debian11，debian11在部分独立服务器上有网络重启的BUG。
  • 硬件要求：2核2G内存x86_64或arm架构服务器硬盘至少20G
  • 可开KVM的硬件要求：VM-X或AMD-V支持 (部分VPS和全部独服支持)
  • 如果硬件或系统需求不满足，可使用incus批量开LXC容器跳转
如果使用IPV6隧道进行宿主机的IPV6子网附加，务必在PVE安装成功但网关未自动设置时在对应文件添加内容，不要在一开始(未安装PVE)就进行IPV6隧道的添加。
开设虚拟内存(SWAP)(非必须的可选项) ​
TIP
内存开点swap免得机器炸了，如果你的宿主机内存不够用硬盘又很多空闲的话
单位换算：输入 1024 产生 1G SWAP-虚拟内存，虚拟内存占用硬盘空间，当实际内存不够用时将自动使用虚拟内存做内存使用，但随之带来IO高占用以及CPU性能占用
建议只开实际内存大小两倍大小的虚拟内存
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
检测环境 ​
  • 本项目相关脚本执行前务必执行本脚本检测环境，如果不符合安装PVE的要求则无法使用后续的脚本
  • 检测本机IPV6的网络配置情况(有无IPV6都可安装，只是查询一下罢了)
  • 检测硬件配置是否满足最低要求
  • 检测硬件环境是否可嵌套虚拟化KVM类型的服务器，不可嵌套虚拟化KVM的也可以开QEMU的TCG的服务器，性能较差
  • 检测系统环境是否可嵌套虚拟化KVM类型的服务器，不可嵌套虚拟化KVM的也可以开QEMU的TCG的服务器，性能较差
  • 不可嵌套虚拟化KVM的服务器不推荐安装PVE，不如使用incus性能更好
国际
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh)
国内
bash
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh)
如果你需要更新IPV6信息再查询，那么执行以下命令后再查询
bash
rm -rf /usr/local/bin/pve_ipv6*
 rm -rf /usr/local/bin/pve_check_ipv6*
 rm -rf /usr/local/bin/pve_last_ipv6*
执行本项目的检测环境的命令，展示如下
图片
查询如上的只需使用下面的一键脚本自动创建虚拟机即可，无需手动再修改WEB端设置
图片
查询如上的在使用后续脚本创建了虚拟机后，可能需要手动修改WEB端设置，需要关闭对应每个虚拟机的硬件嵌套虚拟化，如下图
图片
先停止虚拟机再修改，修改完后再开机才能使用NOVNC，不关闭可能导致这个虚拟机有BUG无法使用
如果强行安装PVE开KVM，启动不了的也可以关闭这个选项试试能不能启动虚拟机，导致这些问题的原因就是上面说的，宿主机不支持嵌套虚拟化KVM进行加速
TIP
开设虚拟机前请使用screen挂起执行，避免开设时间过长，SSH不稳定导致中间执行中断


',40),r=[c];function i(C,h,d,y,D,A){return a(),p("div",null,r)}const m=s(t,[["render",i]]);export{b as __pageData,m as default};
diff --git a/assets/guide_pve_pve_precheck.md.dc29dc3e.lean.js b/assets/guide_pve_pve_precheck.md.2b124758.lean.js
similarity index 99%
rename from assets/guide_pve_pve_precheck.md.dc29dc3e.lean.js
rename to assets/guide_pve_pve_precheck.md.2b124758.lean.js
index 7fa3a2b315..158896c5d1 100644
--- a/assets/guide_pve_pve_precheck.md.dc29dc3e.lean.js
+++ b/assets/guide_pve_pve_precheck.md.2b124758.lean.js
@@ -1,3 +1,3 @@
-import{_ as s,v as a,b as p,R as l}from"./chunks/framework.70afa331.js";const n="/assets/pve_kvm_1.0f7e84f0.png",e="/assets/pve_kvm_2.cefb9578.png",o="/assets/pve_kvm_3.1d307586.png",b=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_precheck.md","filePath":"guide/pve/pve_precheck.md","lastUpdated":1747726389000}'),t={name:"guide/pve/pve_precheck.md"},c=l(`
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果有未适配的商家或机器欢迎联系@spiritlhl_bot，有空会尝试支持一下
WARNING
会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/pve
各种要求 ​
建议debian在使用前尽量使用最新的稳定版本的系统
不要在动态IP的服务器上使用本套脚本(重启机器后自动切换本机IP的服务器暂不支持，重启机器后IP不自动切换的支持)
本项目的一键安装脚本只适配Debian系统，非Debian无法通过APT源安装，官方只给了Debian的镜像，其他系统只能使用ISO安装，或使用自定义分区和常见问题分区中的其他方式解决问题。
  • 系统要求：Debian 8+
TIP
建议debian12而不是debian11，debian11在部分独立服务器上有网络重启的BUG。
  • 硬件要求：2核2G内存x86_64或arm架构服务器硬盘至少20G
  • 可开KVM的硬件要求：VM-X或AMD-V支持 (部分VPS和全部独服支持)
  • 如果硬件或系统需求不满足，可使用incus批量开LXC容器跳转
如果使用IPV6隧道进行宿主机的IPV6子网附加，务必在PVE安装成功但网关未自动设置时在对应文件添加内容，不要在一开始(未安装PVE)就进行IPV6隧道的添加。
开设虚拟内存(SWAP)(非必须的可选项) ​
TIP
内存开点swap免得机器炸了，如果你的宿主机内存不够用硬盘又很多空闲的话
单位换算：输入 1024 产生 1G SWAP-虚拟内存，虚拟内存占用硬盘空间，当实际内存不够用时将自动使用虚拟内存做内存使用，但随之带来IO高占用以及CPU性能占用
建议只开实际内存大小两倍大小的虚拟内存
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
检测环境 ​
  • 本项目相关脚本执行前务必执行本脚本检测环境，如果不符合安装PVE的要求则无法使用后续的脚本
  • 检测本机IPV6的网络配置情况(有无IPV6都可安装，只是查询一下罢了)
  • 检测硬件配置是否满足最低要求
  • 检测硬件环境是否可嵌套虚拟化KVM类型的服务器，不可嵌套虚拟化KVM的也可以开QEMU的TCG的服务器，性能较差
  • 检测系统环境是否可嵌套虚拟化KVM类型的服务器，不可嵌套虚拟化KVM的也可以开QEMU的TCG的服务器，性能较差
  • 不可嵌套虚拟化KVM的服务器不推荐安装PVE，不如使用incus性能更好
国际
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh)
国内
bash
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh)
如果你需要更新IPV6信息再查询，那么执行以下命令后再查询
bash
rm -rf /usr/local/bin/pve_ipv6*
+import{_ as s,v as a,b as p,R as l}from"./chunks/framework.70afa331.js";const n="/assets/pve_kvm_1.0f7e84f0.png",e="/assets/pve_kvm_2.cefb9578.png",o="/assets/pve_kvm_3.1d307586.png",b=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_precheck.md","filePath":"guide/pve/pve_precheck.md","lastUpdated":1747730955000}'),t={name:"guide/pve/pve_precheck.md"},c=l(`
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果有未适配的商家或机器欢迎联系@spiritlhl_bot，有空会尝试支持一下
WARNING
会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/pve
各种要求 ​
建议debian在使用前尽量使用最新的稳定版本的系统
不要在动态IP的服务器上使用本套脚本(重启机器后自动切换本机IP的服务器暂不支持，重启机器后IP不自动切换的支持)
本项目的一键安装脚本只适配Debian系统，非Debian无法通过APT源安装，官方只给了Debian的镜像，其他系统只能使用ISO安装，或使用自定义分区和常见问题分区中的其他方式解决问题。
  • 系统要求：Debian 8+
TIP
建议debian12而不是debian11，debian11在部分独立服务器上有网络重启的BUG。
  • 硬件要求：2核2G内存x86_64或arm架构服务器硬盘至少20G
  • 可开KVM的硬件要求：VM-X或AMD-V支持 (部分VPS和全部独服支持)
  • 如果硬件或系统需求不满足，可使用incus批量开LXC容器跳转
如果使用IPV6隧道进行宿主机的IPV6子网附加，务必在PVE安装成功但网关未自动设置时在对应文件添加内容，不要在一开始(未安装PVE)就进行IPV6隧道的添加。
开设虚拟内存(SWAP)(非必须的可选项) ​
TIP
内存开点swap免得机器炸了，如果你的宿主机内存不够用硬盘又很多空闲的话
单位换算：输入 1024 产生 1G SWAP-虚拟内存，虚拟内存占用硬盘空间，当实际内存不够用时将自动使用虚拟内存做内存使用，但随之带来IO高占用以及CPU性能占用
建议只开实际内存大小两倍大小的虚拟内存
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
检测环境 ​
  • 本项目相关脚本执行前务必执行本脚本检测环境，如果不符合安装PVE的要求则无法使用后续的脚本
  • 检测本机IPV6的网络配置情况(有无IPV6都可安装，只是查询一下罢了)
  • 检测硬件配置是否满足最低要求
  • 检测硬件环境是否可嵌套虚拟化KVM类型的服务器，不可嵌套虚拟化KVM的也可以开QEMU的TCG的服务器，性能较差
  • 检测系统环境是否可嵌套虚拟化KVM类型的服务器，不可嵌套虚拟化KVM的也可以开QEMU的TCG的服务器，性能较差
  • 不可嵌套虚拟化KVM的服务器不推荐安装PVE，不如使用incus性能更好
国际
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh)
国内
bash
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh)
如果你需要更新IPV6信息再查询，那么执行以下命令后再查询
bash
rm -rf /usr/local/bin/pve_ipv6*
 rm -rf /usr/local/bin/pve_check_ipv6*
 rm -rf /usr/local/bin/pve_last_ipv6*
执行本项目的检测环境的命令，展示如下
图片
查询如上的只需使用下面的一键脚本自动创建虚拟机即可，无需手动再修改WEB端设置
图片
查询如上的在使用后续脚本创建了虚拟机后，可能需要手动修改WEB端设置，需要关闭对应每个虚拟机的硬件嵌套虚拟化，如下图
图片
先停止虚拟机再修改，修改完后再开机才能使用NOVNC，不关闭可能导致这个虚拟机有BUG无法使用
如果强行安装PVE开KVM，启动不了的也可以关闭这个选项试试能不能启动虚拟机，导致这些问题的原因就是上面说的，宿主机不支持嵌套虚拟化KVM进行加速
TIP
开设虚拟机前请使用screen挂起执行，避免开设时间过长，SSH不稳定导致中间执行中断


',40),r=[c];function i(C,h,d,y,D,A){return a(),p("div",null,r)}const m=s(t,[["render",i]]);export{b as __pageData,m as default};
diff --git a/assets/guide_pve_pve_qa.md.f01cd6dc.js b/assets/guide_pve_pve_qa.md.93e38573.js
similarity index 99%
rename from assets/guide_pve_pve_qa.md.f01cd6dc.js
rename to assets/guide_pve_pve_qa.md.93e38573.js
index c3395727d2..9adb464d58 100644
--- a/assets/guide_pve_pve_qa.md.f01cd6dc.js
+++ b/assets/guide_pve_pve_qa.md.93e38573.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as l}from"./chunks/framework.70afa331.js";const o="/assets/onlinepkg.30da8d76.png",n="/assets/dns0.1beb9fa7.png",u=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_qa.md","filePath":"guide/pve/pve_qa.md","lastUpdated":1747726389000}'),p={name:"guide/pve/pve_qa.md"},t=l(`
解惑 ​
执行脚本不到30秒机器就掉线了 ​
原装系统执行
systemctl restart networking
看看是不是直接掉线，如果是那就是机器原生有问题，热插拔或者dhcp导致的网络无法自重启，此时建议更换宿主机的系统或DD一个新系统尝试
一般来说这种情况都是出现在独服的Debian11系统上，切换为Debian12系统就没问题了
安装PVE失败且报错显示某些安装包不存在 ​
执行下述命令查询apt的源
shell
grep -r "deb " /etc/apt/sources.list /etc/apt/sources.list.d/
如果看到
deb file://
+import{_ as s,v as a,b as e,R as l}from"./chunks/framework.70afa331.js";const o="/assets/onlinepkg.30da8d76.png",n="/assets/dns0.1beb9fa7.png",u=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_qa.md","filePath":"guide/pve/pve_qa.md","lastUpdated":1747730955000}'),p={name:"guide/pve/pve_qa.md"},t=l(`
解惑 ​
执行脚本不到30秒机器就掉线了 ​
原装系统执行
systemctl restart networking
看看是不是直接掉线，如果是那就是机器原生有问题，热插拔或者dhcp导致的网络无法自重启，此时建议更换宿主机的系统或DD一个新系统尝试
一般来说这种情况都是出现在独服的Debian11系统上，切换为Debian12系统就没问题了
安装PVE失败且报错显示某些安装包不存在 ​
执行下述命令查询apt的源
shell
grep -r "deb " /etc/apt/sources.list /etc/apt/sources.list.d/
如果看到
deb file://
 deb cdrom:[
这种开头的行，那么证明宿主机使用的是本地源而不是网络源，需要替换/etc/apt/sources.list的源，如
图片
一样替换为网络源才可使用PVE一键安装脚本进行安装。
替换网络源
国内服务器可使用
bash <(curl -sSL https://gitee.com/SuperManito/LinuxMirrors/raw/main/ChangeMirrors.sh)
国外服务器可使用
bash <(curl -sSL https://raw.githubusercontent.com/SuperManito/LinuxMirrors/main/ChangeMirrors.sh) --abroad
进行apt源的替换
安装PVE成功但重启后失联 ​
如果什么机器安装PVE成功后WEB可用，但重启失联，请安装成功PVE后，重启前执行以下命令再重启
bash
auto_interface=$(grep '^auto ' /etc/network/interfaces | grep -v '^auto lo' | awk '{print $2}' | head -n 1)
 if ! grep -q "^post-up /sbin/ethtool" /etc/network/interfaces; then
     chattr -i /etc/network/interfaces
diff --git a/assets/guide_pve_pve_qa.md.f01cd6dc.lean.js b/assets/guide_pve_pve_qa.md.93e38573.lean.js
similarity index 99%
rename from assets/guide_pve_pve_qa.md.f01cd6dc.lean.js
rename to assets/guide_pve_pve_qa.md.93e38573.lean.js
index c3395727d2..9adb464d58 100644
--- a/assets/guide_pve_pve_qa.md.f01cd6dc.lean.js
+++ b/assets/guide_pve_pve_qa.md.93e38573.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as l}from"./chunks/framework.70afa331.js";const o="/assets/onlinepkg.30da8d76.png",n="/assets/dns0.1beb9fa7.png",u=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_qa.md","filePath":"guide/pve/pve_qa.md","lastUpdated":1747726389000}'),p={name:"guide/pve/pve_qa.md"},t=l(`
解惑 ​
执行脚本不到30秒机器就掉线了 ​
原装系统执行
systemctl restart networking
看看是不是直接掉线，如果是那就是机器原生有问题，热插拔或者dhcp导致的网络无法自重启，此时建议更换宿主机的系统或DD一个新系统尝试
一般来说这种情况都是出现在独服的Debian11系统上，切换为Debian12系统就没问题了
安装PVE失败且报错显示某些安装包不存在 ​
执行下述命令查询apt的源
shell
grep -r "deb " /etc/apt/sources.list /etc/apt/sources.list.d/
如果看到
deb file://
+import{_ as s,v as a,b as e,R as l}from"./chunks/framework.70afa331.js";const o="/assets/onlinepkg.30da8d76.png",n="/assets/dns0.1beb9fa7.png",u=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_qa.md","filePath":"guide/pve/pve_qa.md","lastUpdated":1747730955000}'),p={name:"guide/pve/pve_qa.md"},t=l(`
解惑 ​
执行脚本不到30秒机器就掉线了 ​
原装系统执行
systemctl restart networking
看看是不是直接掉线，如果是那就是机器原生有问题，热插拔或者dhcp导致的网络无法自重启，此时建议更换宿主机的系统或DD一个新系统尝试
一般来说这种情况都是出现在独服的Debian11系统上，切换为Debian12系统就没问题了
安装PVE失败且报错显示某些安装包不存在 ​
执行下述命令查询apt的源
shell
grep -r "deb " /etc/apt/sources.list /etc/apt/sources.list.d/
如果看到
deb file://
 deb cdrom:[
这种开头的行，那么证明宿主机使用的是本地源而不是网络源，需要替换/etc/apt/sources.list的源，如
图片
一样替换为网络源才可使用PVE一键安装脚本进行安装。
替换网络源
国内服务器可使用
bash <(curl -sSL https://gitee.com/SuperManito/LinuxMirrors/raw/main/ChangeMirrors.sh)
国外服务器可使用
bash <(curl -sSL https://raw.githubusercontent.com/SuperManito/LinuxMirrors/main/ChangeMirrors.sh) --abroad
进行apt源的替换
安装PVE成功但重启后失联 ​
如果什么机器安装PVE成功后WEB可用，但重启失联，请安装成功PVE后，重启前执行以下命令再重启
bash
auto_interface=$(grep '^auto ' /etc/network/interfaces | grep -v '^auto lo' | awk '{print $2}' | head -n 1)
 if ! grep -q "^post-up /sbin/ethtool" /etc/network/interfaces; then
     chattr -i /etc/network/interfaces
diff --git a/assets/guide_pve_pve_thanks.md.a04e54b5.js b/assets/guide_pve_pve_thanks.md.a2dddf32.js
similarity index 97%
rename from assets/guide_pve_pve_thanks.md.a04e54b5.js
rename to assets/guide_pve_pve_thanks.md.a2dddf32.js
index b519b81afb..8857edb26f 100644
--- a/assets/guide_pve_pve_thanks.md.a04e54b5.js
+++ b/assets/guide_pve_pve_thanks.md.a2dddf32.js
@@ -1 +1 @@
-import{_ as r,v as e,b as t,R as o}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/pve/pve_thanks.md","filePath":"guide/pve/pve_thanks.md","lastUpdated":1747726389000}'),a={name:"guide/pve/pve_thanks.md"},p=o('
致谢 ​
https://forum.proxmox.com/
https://blog.ilolicon.com/archives/615
https://github.com/Ella-Alinda/somescripts/blob/main/nat.sh
https://pve.proxmox.com/pve-docs/qm.1.html
https://down.idc.wiki/Image/realServer-Template/
https://mirrors.tuna.tsinghua.edu.cn/proxmox/
https://github.com/roacn/pve/blob/main/pve.sh
https://github.com/spiritLHLS/lxc
https://github.com/leitbogioro/Tools
https://github.com/jiangcuo/Proxmox-Port
https://gitlab.com/minkebox/pimox
https://github.com/jiangcuo/run_proxmox_in_docker
https://github.com/yoursunny/ndpresponder
https://github.com/SuperManito/LinuxMirrors
感谢 @Ella-Alinda 提供的PVE指导
',16),n=[p];function i(s,h,l,m,c,b){return e(),t("div",null,n)}const f=r(a,[["render",i]]);export{u as __pageData,f as default};
+import{_ as r,v as e,b as t,R as o}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/pve/pve_thanks.md","filePath":"guide/pve/pve_thanks.md","lastUpdated":1747730955000}'),a={name:"guide/pve/pve_thanks.md"},p=o('
致谢 ​
https://forum.proxmox.com/
https://blog.ilolicon.com/archives/615
https://github.com/Ella-Alinda/somescripts/blob/main/nat.sh
https://pve.proxmox.com/pve-docs/qm.1.html
https://down.idc.wiki/Image/realServer-Template/
https://mirrors.tuna.tsinghua.edu.cn/proxmox/
https://github.com/roacn/pve/blob/main/pve.sh
https://github.com/spiritLHLS/lxc
https://github.com/leitbogioro/Tools
https://github.com/jiangcuo/Proxmox-Port
https://gitlab.com/minkebox/pimox
https://github.com/jiangcuo/run_proxmox_in_docker
https://github.com/yoursunny/ndpresponder
https://github.com/SuperManito/LinuxMirrors
感谢 @Ella-Alinda 提供的PVE指导
',16),n=[p];function i(s,h,l,m,c,b){return e(),t("div",null,n)}const f=r(a,[["render",i]]);export{u as __pageData,f as default};
diff --git a/assets/guide_pve_pve_thanks.md.a04e54b5.lean.js b/assets/guide_pve_pve_thanks.md.a2dddf32.lean.js
similarity index 97%
rename from assets/guide_pve_pve_thanks.md.a04e54b5.lean.js
rename to assets/guide_pve_pve_thanks.md.a2dddf32.lean.js
index b519b81afb..8857edb26f 100644
--- a/assets/guide_pve_pve_thanks.md.a04e54b5.lean.js
+++ b/assets/guide_pve_pve_thanks.md.a2dddf32.lean.js
@@ -1 +1 @@
-import{_ as r,v as e,b as t,R as o}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/pve/pve_thanks.md","filePath":"guide/pve/pve_thanks.md","lastUpdated":1747726389000}'),a={name:"guide/pve/pve_thanks.md"},p=o('
致谢 ​
https://forum.proxmox.com/
https://blog.ilolicon.com/archives/615
https://github.com/Ella-Alinda/somescripts/blob/main/nat.sh
https://pve.proxmox.com/pve-docs/qm.1.html
https://down.idc.wiki/Image/realServer-Template/
https://mirrors.tuna.tsinghua.edu.cn/proxmox/
https://github.com/roacn/pve/blob/main/pve.sh
https://github.com/spiritLHLS/lxc
https://github.com/leitbogioro/Tools
https://github.com/jiangcuo/Proxmox-Port
https://gitlab.com/minkebox/pimox
https://github.com/jiangcuo/run_proxmox_in_docker
https://github.com/yoursunny/ndpresponder
https://github.com/SuperManito/LinuxMirrors
感谢 @Ella-Alinda 提供的PVE指导
',16),n=[p];function i(s,h,l,m,c,b){return e(),t("div",null,n)}const f=r(a,[["render",i]]);export{u as __pageData,f as default};
+import{_ as r,v as e,b as t,R as o}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/pve/pve_thanks.md","filePath":"guide/pve/pve_thanks.md","lastUpdated":1747730955000}'),a={name:"guide/pve/pve_thanks.md"},p=o('
致谢 ​
https://forum.proxmox.com/
https://blog.ilolicon.com/archives/615
https://github.com/Ella-Alinda/somescripts/blob/main/nat.sh
https://pve.proxmox.com/pve-docs/qm.1.html
https://down.idc.wiki/Image/realServer-Template/
https://mirrors.tuna.tsinghua.edu.cn/proxmox/
https://github.com/roacn/pve/blob/main/pve.sh
https://github.com/spiritLHLS/lxc
https://github.com/leitbogioro/Tools
https://github.com/jiangcuo/Proxmox-Port
https://gitlab.com/minkebox/pimox
https://github.com/jiangcuo/run_proxmox_in_docker
https://github.com/yoursunny/ndpresponder
https://github.com/SuperManito/LinuxMirrors
感谢 @Ella-Alinda 提供的PVE指导
',16),n=[p];function i(s,h,l,m,c,b){return e(),t("div",null,n)}const f=r(a,[["render",i]]);export{u as __pageData,f as default};
diff --git a/assets/guide_pve_pve_windows.md.12c35287.js b/assets/guide_pve_pve_windows.md.538cb762.js
similarity index 99%
rename from assets/guide_pve_pve_windows.md.12c35287.js
rename to assets/guide_pve_pve_windows.md.538cb762.js
index 30c107a105..2a01098b0b 100644
--- a/assets/guide_pve_pve_windows.md.12c35287.js
+++ b/assets/guide_pve_pve_windows.md.538cb762.js
@@ -1,2 +1,2 @@
-import{_ as e,v as c,b as s,R as t}from"./chunks/framework.70afa331.js";import{_ as o}from"./chunks/wk7.6fe7513d.js";const d="/assets/kvm.d81063e5.png",i="/assets/dlwiniso.a2c0c1ef.png",p="/assets/dlwiniso1.4fa2fea0.png",a="/assets/general.ea03923c.png",r="/assets/os.b2be1a5c.png",n="/assets/system.8e69987e.png",l="/assets/disks.8065a143.png",m="/assets/cpu.4618bc7b.png",g="/assets/memory.c4992870.png",_="/assets/network.48037353.png",h="/assets/finish.0c3eac87.png",w="/assets/start.3aebbfd4.png",k="/assets/gic1.42bfd260.png",v="/assets/gic2.ff78c941.png",u="/assets/gic3.4a04cf3d.png",b="/assets/gic4.e2343160.png",f="/assets/gic5.54522dff.png",x="/assets/gic6.97561122.png",q="/assets/gic7.a8679083.png",C="/assets/gic8.fe7d0b3c.png",P="/assets/gic9.4cdf4daa.png",I="/assets/net1.4f166207.png",S="/assets/net2.e2773ada.png",O="/assets/net3.40e8a226.png",V="/assets/net4.a81e777c.png",D="/assets/virtio.b42d8275.png",N="/assets/lower2.e782a20a.png",M="/assets/lower1.28498396.png",y="/assets/nodisk.5ec86f3b.png",U="/assets/nodisk1.671c1309.png",E="/assets/nodisk2.ff20bb76.png",W="/assets/nodisk3.71534a11.png",B="/assets/nodisk4.b08d75e3.png",R="/assets/wk4.004be17f.png",G="/assets/wk5.6cdba880.png",K="/assets/wk6.667c5c95.png",A="/assets/wk1.7d9f24d7.png",L="/assets/wk2.2e88d91a.png",T="/assets/wk3.975bc38e.png",co=JSON.parse('{"title":"开设Windows虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_windows.md","filePath":"guide/pve/pve_windows.md","lastUpdated":1747726389000}'),H={name:"guide/pve/pve_windows.md"},$=t('
开设Windows虚拟机 ​
开设时选择KVM虚拟化还是QEMU的TCG仿真 ​
宿主机本身如果支持嵌套虚拟化，那么就可用host或kvm64或qemu64类型的CPU
从性能上来说，host > kvm64 > qemu64
qemu类型虚拟化性能损耗很多
如果本身不支持嵌套虚拟化，那么只能用qemu64类型的CPU，且需要在启动虚拟机前修改Options[选项]中的KVM hardware virtualization[KVM硬件虚拟化]
设置为no取消Enabled[启用]的勾选
kvm
如果你实在不清楚本机是否支持嵌套虚拟化，那么查看 系统与硬件配置要求 --> 检测环境 检测确保可用(含尝试性启用功能)
它的主体逻辑在
https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh
这块的逻辑中，主要检测
egrep -c '(vmx|svm)' /proc/cpuinfo 检测是否为1
cat /sys/module/kvm_intel/parameters/nested是否存在且为1
lsmod | grep -q kvm检测是否已加载
这些都支持的时候，才可选host类型。
使用带virtio的iso镜像文件开设 ​
1.下载镜像 ​
安装需要提前下载镜像文件local(pve) --> ISO images --> Download from URL
下载链接URL:可使用
https://github.com/ILLKX/Windows-VirtIO
中的文件链接，文件名字File Name:填win.iso
download
点击下载Download，下载完成后当前的页面可见win.iso的文件大小，可见格式为iso。
downloaded
2.设置模板 ​
页面顶部右上角点击Create VM
General窗口中，Resource Pool:勾选mypool，Name填写win，然后点击Next。
general
OS窗口中，ISO image勾选win.iso，Guest OS勾选Type为Microsoft Windows类型，Version选择当前ISO的win的版本，示例下载是2022，就选11/2022类型，然后点击Next。
OS
System窗口中，Graphic card勾选VirtIO-GPU类型，Machine勾选q35类型，SCSI Controller勾选VirtIO SCSI类型，BIOS勾选Default (SeaBIOS)类型，然后点击Next。
system
Disk窗口中，Cache勾选Write Back类型，Disk size (GiB)填写你要分配的硬盘大小，一般不小于20，Storage选择存储在哪个盘，示例只有系统盘local所以就选loacl，然后点击Next。
disk
CPU窗口中，Cores填写所需核数，CPU类型按照前面描述的方法选择，然后点击Next。
cpu
Memory窗口中，Memory (MiB)填写所需内存大小，然后点击Next。
memory
Network窗口中，Bridge勾选vmbr1类型，Model勾选VirtIO (paravirtualized)类型，Firewall取消勾选，然后点击Next。
Network
Confirm窗口中，点击Finish。
finish
3.图形化配置安装 ​
左侧点击设置好的模板，右上角点击Start启动虚拟机，然后点击Console进入VNC界面，等待操作系统启动。
console
然后在VNC中点击下一页，然后点击现在安装，然后点击我没有产品密钥，然后勾选接受许可，点击下一页，然后勾选自定义安装。
win0
win1
win2
win3
win4
然后如果镜像本身带virtio，那么应该可见可选系统存储的硬盘及其大小，选中后点击下一页。
win5
win6
然后等待系统安装，应该会自动重启几次，大概耗时10分钟以上。
win7
安装完成后首次登录会要求设置密码，正常设置即可
win8
设置完成后，NOVNC页面左侧有一个弹出框，点击第一个按钮，然后根据登录提示，点击Ctrl+Alt+最后一个按钮，进入登录页面。
4.初始化网络 ​
由于通过本项目设置的PVE是静态网络，所以登陆后需要手动修改绑定的IP地址，不通过DHCP
在桌面右下角右击点出打开 网络和Internet设置，点击后，在弹出的设置页面中点击更改适配器设置
win9
然后在网络链接中勾选以太网，点击更改此连接的设置
win10
在弹出框中点击Internet协议版本4(TCP/IPV4)选中后点击属性
win11
在新弹出的弹出框中，选择并点击使用下面的IP地址(s)，然后分别填入
IP地址(I)：172.16.1.xxx(xxx换成你想绑定的ip，我的vmid是100，为了方便写了100)
子网掩码(U)：255.255.255.0
默认网关(D)：172.16.1.1
然后选择点击使用下面的DNS服务器地址(E)，分别填入
8.8.8.8
+import{_ as e,v as c,b as s,R as t}from"./chunks/framework.70afa331.js";import{_ as o}from"./chunks/wk7.6fe7513d.js";const d="/assets/kvm.d81063e5.png",i="/assets/dlwiniso.a2c0c1ef.png",p="/assets/dlwiniso1.4fa2fea0.png",a="/assets/general.ea03923c.png",r="/assets/os.b2be1a5c.png",n="/assets/system.8e69987e.png",l="/assets/disks.8065a143.png",m="/assets/cpu.4618bc7b.png",g="/assets/memory.c4992870.png",_="/assets/network.48037353.png",h="/assets/finish.0c3eac87.png",w="/assets/start.3aebbfd4.png",k="/assets/gic1.42bfd260.png",v="/assets/gic2.ff78c941.png",u="/assets/gic3.4a04cf3d.png",b="/assets/gic4.e2343160.png",f="/assets/gic5.54522dff.png",x="/assets/gic6.97561122.png",q="/assets/gic7.a8679083.png",C="/assets/gic8.fe7d0b3c.png",P="/assets/gic9.4cdf4daa.png",I="/assets/net1.4f166207.png",S="/assets/net2.e2773ada.png",O="/assets/net3.40e8a226.png",V="/assets/net4.a81e777c.png",D="/assets/virtio.b42d8275.png",N="/assets/lower2.e782a20a.png",M="/assets/lower1.28498396.png",y="/assets/nodisk.5ec86f3b.png",U="/assets/nodisk1.671c1309.png",E="/assets/nodisk2.ff20bb76.png",W="/assets/nodisk3.71534a11.png",B="/assets/nodisk4.b08d75e3.png",R="/assets/wk4.004be17f.png",G="/assets/wk5.6cdba880.png",K="/assets/wk6.667c5c95.png",A="/assets/wk1.7d9f24d7.png",L="/assets/wk2.2e88d91a.png",T="/assets/wk3.975bc38e.png",co=JSON.parse('{"title":"开设Windows虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_windows.md","filePath":"guide/pve/pve_windows.md","lastUpdated":1747730955000}'),H={name:"guide/pve/pve_windows.md"},$=t('
开设Windows虚拟机 ​
开设时选择KVM虚拟化还是QEMU的TCG仿真 ​
宿主机本身如果支持嵌套虚拟化，那么就可用host或kvm64或qemu64类型的CPU
从性能上来说，host > kvm64 > qemu64
qemu类型虚拟化性能损耗很多
如果本身不支持嵌套虚拟化，那么只能用qemu64类型的CPU，且需要在启动虚拟机前修改Options[选项]中的KVM hardware virtualization[KVM硬件虚拟化]
设置为no取消Enabled[启用]的勾选
kvm
如果你实在不清楚本机是否支持嵌套虚拟化，那么查看 系统与硬件配置要求 --> 检测环境 检测确保可用(含尝试性启用功能)
它的主体逻辑在
https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh
这块的逻辑中，主要检测
egrep -c '(vmx|svm)' /proc/cpuinfo 检测是否为1
cat /sys/module/kvm_intel/parameters/nested是否存在且为1
lsmod | grep -q kvm检测是否已加载
这些都支持的时候，才可选host类型。
使用带virtio的iso镜像文件开设 ​
1.下载镜像 ​
安装需要提前下载镜像文件local(pve) --> ISO images --> Download from URL
下载链接URL:可使用
https://github.com/ILLKX/Windows-VirtIO
中的文件链接，文件名字File Name:填win.iso
download
点击下载Download，下载完成后当前的页面可见win.iso的文件大小，可见格式为iso。
downloaded
2.设置模板 ​
页面顶部右上角点击Create VM
General窗口中，Resource Pool:勾选mypool，Name填写win，然后点击Next。
general
OS窗口中，ISO image勾选win.iso，Guest OS勾选Type为Microsoft Windows类型，Version选择当前ISO的win的版本，示例下载是2022，就选11/2022类型，然后点击Next。
OS
System窗口中，Graphic card勾选VirtIO-GPU类型，Machine勾选q35类型，SCSI Controller勾选VirtIO SCSI类型，BIOS勾选Default (SeaBIOS)类型，然后点击Next。
system
Disk窗口中，Cache勾选Write Back类型，Disk size (GiB)填写你要分配的硬盘大小，一般不小于20，Storage选择存储在哪个盘，示例只有系统盘local所以就选loacl，然后点击Next。
disk
CPU窗口中，Cores填写所需核数，CPU类型按照前面描述的方法选择，然后点击Next。
cpu
Memory窗口中，Memory (MiB)填写所需内存大小，然后点击Next。
memory
Network窗口中，Bridge勾选vmbr1类型，Model勾选VirtIO (paravirtualized)类型，Firewall取消勾选，然后点击Next。
Network
Confirm窗口中，点击Finish。
finish
3.图形化配置安装 ​
左侧点击设置好的模板，右上角点击Start启动虚拟机，然后点击Console进入VNC界面，等待操作系统启动。
console
然后在VNC中点击下一页，然后点击现在安装，然后点击我没有产品密钥，然后勾选接受许可，点击下一页，然后勾选自定义安装。
win0
win1
win2
win3
win4
然后如果镜像本身带virtio，那么应该可见可选系统存储的硬盘及其大小，选中后点击下一页。
win5
win6
然后等待系统安装，应该会自动重启几次，大概耗时10分钟以上。
win7
安装完成后首次登录会要求设置密码，正常设置即可
win8
设置完成后，NOVNC页面左侧有一个弹出框，点击第一个按钮，然后根据登录提示，点击Ctrl+Alt+最后一个按钮，进入登录页面。
4.初始化网络 ​
由于通过本项目设置的PVE是静态网络，所以登陆后需要手动修改绑定的IP地址，不通过DHCP
在桌面右下角右击点出打开 网络和Internet设置，点击后，在弹出的设置页面中点击更改适配器设置
win9
然后在网络链接中勾选以太网，点击更改此连接的设置
win10
在弹出框中点击Internet协议版本4(TCP/IPV4)选中后点击属性
win11
在新弹出的弹出框中，选择并点击使用下面的IP地址(s)，然后分别填入
IP地址(I)：172.16.1.xxx(xxx换成你想绑定的ip，我的vmid是100，为了方便写了100)
子网掩码(U)：255.255.255.0
默认网关(D)：172.16.1.1
然后选择点击使用下面的DNS服务器地址(E)，分别填入
8.8.8.8
 144.144.144.144
然后右下角点击确定，注意不要勾选退出时验证
win12
然后其他弹出框都选确定和是就行了，然后本虚拟机就有网络了。
5.取消CD盘挂载 ​
在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]然后再重启虚拟机，这样就能直接使用了
wk
使用不带virtio的iso镜像开设 ​
1.下载镜像 ​
无virtio的win镜像下载可使用
https://down.idc.wiki/ISOS/Windows/
这块的镜像
virtio的iso镜像可使用
https://down.idc.wiki/ISOS/Toolkit/
或者
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/
下载
virtio也可以只下载msi包，本地用软件打包成iso压缩格式再本地上传到ProxmoxVE中也可以
这样的话包小一些，前者官方的是包含所有WIN镜像支持的包总计500MB左右，后者自己打包5MB左右
2.virtio导入 ​
注意这里的导入在ProxmoxVE的8.x及之后的版本中，OS这一栏默认可选择virtio启动加载，如图所示
virtio
而在更低版本的ProxmoxVE中，比如7.x和6.x的版本，OS这一栏默认无法选择virtio启动加载
lower
需要手动在Hardware[硬件]中点击Add[添加]添加CD/DVD Drive选择下载好的virtio的ISO文件
lower
然后其他的一切照常，直到
nodisk
这块找不到硬盘，需要选择加载驱动程序
nodisk
然后选择驱动盘是virtio的，点击打开，从amd64那导入对应系统名字的驱动
nodisk
我的是windows server 2019的镜像所以导入的是2k19的驱动，导入完毕后选择导入的驱动，点击下一页
nodisk
nodisk
这样就能看得到硬盘了，选中后继续后续的安装步骤，选中后继续后续的安装步骤如同前面的教程，直到系统安装完毕，进入桌面。
3.通过virtio-win-guest-tools安装驱动 ​
此时安装成功，出现桌面后，还需要手动安装驱动
打开VirtIO驱动所在的CD光驱目录，最下面有一个virtio-win-guest-tools程序，会安装用到的virtio驱动，这个驱动也会包含virtio的网卡驱动
wk
wk
wk
点击安装完毕后就安装上网卡驱动了，后续网络设置参考前面的初始化网络的教程
4.安装网卡驱动(备选) ​
此时安装成功，出现桌面后，还需要手动安装网卡驱动才能连通网络：
  1. 打开 控制面板 → 设备管理器
  2. 找到 以太网控制器，右键选择 更新驱动程序
  3. 选择 浏览我的计算机以查找驱动程序软件 (R)
  4. 浏览到VirtIO驱动所在的CD光驱目录
  5. 打开其中的 NetKVM 文件夹
  6. 根据当前系统版本选择对应的驱动文件夹(和上面相同的操作，我会选择2k19文件夹，里面的amd64驱动)
  7. 确认安装，完成后即可成功加载VirtIO的网卡驱动
wk
wk
wk
后续网络设置参考前面的初始化网络的教程
5.取消CD盘挂载 ​
在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]然后再重启虚拟机，这样就能直接使用了
wk
',126),z=[$];function F(Q,X,J,j,Y,Z){return c(),s("div",null,z)}const so=e(H,[["render",F]]);export{co as __pageData,so as default};
diff --git a/assets/guide_pve_pve_windows.md.12c35287.lean.js b/assets/guide_pve_pve_windows.md.538cb762.lean.js
similarity index 99%
rename from assets/guide_pve_pve_windows.md.12c35287.lean.js
rename to assets/guide_pve_pve_windows.md.538cb762.lean.js
index 30c107a105..2a01098b0b 100644
--- a/assets/guide_pve_pve_windows.md.12c35287.lean.js
+++ b/assets/guide_pve_pve_windows.md.538cb762.lean.js
@@ -1,2 +1,2 @@
-import{_ as e,v as c,b as s,R as t}from"./chunks/framework.70afa331.js";import{_ as o}from"./chunks/wk7.6fe7513d.js";const d="/assets/kvm.d81063e5.png",i="/assets/dlwiniso.a2c0c1ef.png",p="/assets/dlwiniso1.4fa2fea0.png",a="/assets/general.ea03923c.png",r="/assets/os.b2be1a5c.png",n="/assets/system.8e69987e.png",l="/assets/disks.8065a143.png",m="/assets/cpu.4618bc7b.png",g="/assets/memory.c4992870.png",_="/assets/network.48037353.png",h="/assets/finish.0c3eac87.png",w="/assets/start.3aebbfd4.png",k="/assets/gic1.42bfd260.png",v="/assets/gic2.ff78c941.png",u="/assets/gic3.4a04cf3d.png",b="/assets/gic4.e2343160.png",f="/assets/gic5.54522dff.png",x="/assets/gic6.97561122.png",q="/assets/gic7.a8679083.png",C="/assets/gic8.fe7d0b3c.png",P="/assets/gic9.4cdf4daa.png",I="/assets/net1.4f166207.png",S="/assets/net2.e2773ada.png",O="/assets/net3.40e8a226.png",V="/assets/net4.a81e777c.png",D="/assets/virtio.b42d8275.png",N="/assets/lower2.e782a20a.png",M="/assets/lower1.28498396.png",y="/assets/nodisk.5ec86f3b.png",U="/assets/nodisk1.671c1309.png",E="/assets/nodisk2.ff20bb76.png",W="/assets/nodisk3.71534a11.png",B="/assets/nodisk4.b08d75e3.png",R="/assets/wk4.004be17f.png",G="/assets/wk5.6cdba880.png",K="/assets/wk6.667c5c95.png",A="/assets/wk1.7d9f24d7.png",L="/assets/wk2.2e88d91a.png",T="/assets/wk3.975bc38e.png",co=JSON.parse('{"title":"开设Windows虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_windows.md","filePath":"guide/pve/pve_windows.md","lastUpdated":1747726389000}'),H={name:"guide/pve/pve_windows.md"},$=t('
开设Windows虚拟机 ​
开设时选择KVM虚拟化还是QEMU的TCG仿真 ​
宿主机本身如果支持嵌套虚拟化，那么就可用host或kvm64或qemu64类型的CPU
从性能上来说，host > kvm64 > qemu64
qemu类型虚拟化性能损耗很多
如果本身不支持嵌套虚拟化，那么只能用qemu64类型的CPU，且需要在启动虚拟机前修改Options[选项]中的KVM hardware virtualization[KVM硬件虚拟化]
设置为no取消Enabled[启用]的勾选
kvm
如果你实在不清楚本机是否支持嵌套虚拟化，那么查看 系统与硬件配置要求 --> 检测环境 检测确保可用(含尝试性启用功能)
它的主体逻辑在
https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh
这块的逻辑中，主要检测
egrep -c '(vmx|svm)' /proc/cpuinfo 检测是否为1
cat /sys/module/kvm_intel/parameters/nested是否存在且为1
lsmod | grep -q kvm检测是否已加载
这些都支持的时候，才可选host类型。
使用带virtio的iso镜像文件开设 ​
1.下载镜像 ​
安装需要提前下载镜像文件local(pve) --> ISO images --> Download from URL
下载链接URL:可使用
https://github.com/ILLKX/Windows-VirtIO
中的文件链接，文件名字File Name:填win.iso
download
点击下载Download，下载完成后当前的页面可见win.iso的文件大小，可见格式为iso。
downloaded
2.设置模板 ​
页面顶部右上角点击Create VM
General窗口中，Resource Pool:勾选mypool，Name填写win，然后点击Next。
general
OS窗口中，ISO image勾选win.iso，Guest OS勾选Type为Microsoft Windows类型，Version选择当前ISO的win的版本，示例下载是2022，就选11/2022类型，然后点击Next。
OS
System窗口中，Graphic card勾选VirtIO-GPU类型，Machine勾选q35类型，SCSI Controller勾选VirtIO SCSI类型，BIOS勾选Default (SeaBIOS)类型，然后点击Next。
system
Disk窗口中，Cache勾选Write Back类型，Disk size (GiB)填写你要分配的硬盘大小，一般不小于20，Storage选择存储在哪个盘，示例只有系统盘local所以就选loacl，然后点击Next。
disk
CPU窗口中，Cores填写所需核数，CPU类型按照前面描述的方法选择，然后点击Next。
cpu
Memory窗口中，Memory (MiB)填写所需内存大小，然后点击Next。
memory
Network窗口中，Bridge勾选vmbr1类型，Model勾选VirtIO (paravirtualized)类型，Firewall取消勾选，然后点击Next。
Network
Confirm窗口中，点击Finish。
finish
3.图形化配置安装 ​
左侧点击设置好的模板，右上角点击Start启动虚拟机，然后点击Console进入VNC界面，等待操作系统启动。
console
然后在VNC中点击下一页，然后点击现在安装，然后点击我没有产品密钥，然后勾选接受许可，点击下一页，然后勾选自定义安装。
win0
win1
win2
win3
win4
然后如果镜像本身带virtio，那么应该可见可选系统存储的硬盘及其大小，选中后点击下一页。
win5
win6
然后等待系统安装，应该会自动重启几次，大概耗时10分钟以上。
win7
安装完成后首次登录会要求设置密码，正常设置即可
win8
设置完成后，NOVNC页面左侧有一个弹出框，点击第一个按钮，然后根据登录提示，点击Ctrl+Alt+最后一个按钮，进入登录页面。
4.初始化网络 ​
由于通过本项目设置的PVE是静态网络，所以登陆后需要手动修改绑定的IP地址，不通过DHCP
在桌面右下角右击点出打开 网络和Internet设置，点击后，在弹出的设置页面中点击更改适配器设置
win9
然后在网络链接中勾选以太网，点击更改此连接的设置
win10
在弹出框中点击Internet协议版本4(TCP/IPV4)选中后点击属性
win11
在新弹出的弹出框中，选择并点击使用下面的IP地址(s)，然后分别填入
IP地址(I)：172.16.1.xxx(xxx换成你想绑定的ip，我的vmid是100，为了方便写了100)
子网掩码(U)：255.255.255.0
默认网关(D)：172.16.1.1
然后选择点击使用下面的DNS服务器地址(E)，分别填入
8.8.8.8
+import{_ as e,v as c,b as s,R as t}from"./chunks/framework.70afa331.js";import{_ as o}from"./chunks/wk7.6fe7513d.js";const d="/assets/kvm.d81063e5.png",i="/assets/dlwiniso.a2c0c1ef.png",p="/assets/dlwiniso1.4fa2fea0.png",a="/assets/general.ea03923c.png",r="/assets/os.b2be1a5c.png",n="/assets/system.8e69987e.png",l="/assets/disks.8065a143.png",m="/assets/cpu.4618bc7b.png",g="/assets/memory.c4992870.png",_="/assets/network.48037353.png",h="/assets/finish.0c3eac87.png",w="/assets/start.3aebbfd4.png",k="/assets/gic1.42bfd260.png",v="/assets/gic2.ff78c941.png",u="/assets/gic3.4a04cf3d.png",b="/assets/gic4.e2343160.png",f="/assets/gic5.54522dff.png",x="/assets/gic6.97561122.png",q="/assets/gic7.a8679083.png",C="/assets/gic8.fe7d0b3c.png",P="/assets/gic9.4cdf4daa.png",I="/assets/net1.4f166207.png",S="/assets/net2.e2773ada.png",O="/assets/net3.40e8a226.png",V="/assets/net4.a81e777c.png",D="/assets/virtio.b42d8275.png",N="/assets/lower2.e782a20a.png",M="/assets/lower1.28498396.png",y="/assets/nodisk.5ec86f3b.png",U="/assets/nodisk1.671c1309.png",E="/assets/nodisk2.ff20bb76.png",W="/assets/nodisk3.71534a11.png",B="/assets/nodisk4.b08d75e3.png",R="/assets/wk4.004be17f.png",G="/assets/wk5.6cdba880.png",K="/assets/wk6.667c5c95.png",A="/assets/wk1.7d9f24d7.png",L="/assets/wk2.2e88d91a.png",T="/assets/wk3.975bc38e.png",co=JSON.parse('{"title":"开设Windows虚拟机","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_windows.md","filePath":"guide/pve/pve_windows.md","lastUpdated":1747730955000}'),H={name:"guide/pve/pve_windows.md"},$=t('
开设Windows虚拟机 ​
开设时选择KVM虚拟化还是QEMU的TCG仿真 ​
宿主机本身如果支持嵌套虚拟化，那么就可用host或kvm64或qemu64类型的CPU
从性能上来说，host > kvm64 > qemu64
qemu类型虚拟化性能损耗很多
如果本身不支持嵌套虚拟化，那么只能用qemu64类型的CPU，且需要在启动虚拟机前修改Options[选项]中的KVM hardware virtualization[KVM硬件虚拟化]
设置为no取消Enabled[启用]的勾选
kvm
如果你实在不清楚本机是否支持嵌套虚拟化，那么查看 系统与硬件配置要求 --> 检测环境 检测确保可用(含尝试性启用功能)
它的主体逻辑在
https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh
这块的逻辑中，主要检测
egrep -c '(vmx|svm)' /proc/cpuinfo 检测是否为1
cat /sys/module/kvm_intel/parameters/nested是否存在且为1
lsmod | grep -q kvm检测是否已加载
这些都支持的时候，才可选host类型。
使用带virtio的iso镜像文件开设 ​
1.下载镜像 ​
安装需要提前下载镜像文件local(pve) --> ISO images --> Download from URL
下载链接URL:可使用
https://github.com/ILLKX/Windows-VirtIO
中的文件链接，文件名字File Name:填win.iso
download
点击下载Download，下载完成后当前的页面可见win.iso的文件大小，可见格式为iso。
downloaded
2.设置模板 ​
页面顶部右上角点击Create VM
General窗口中，Resource Pool:勾选mypool，Name填写win，然后点击Next。
general
OS窗口中，ISO image勾选win.iso，Guest OS勾选Type为Microsoft Windows类型，Version选择当前ISO的win的版本，示例下载是2022，就选11/2022类型，然后点击Next。
OS
System窗口中，Graphic card勾选VirtIO-GPU类型，Machine勾选q35类型，SCSI Controller勾选VirtIO SCSI类型，BIOS勾选Default (SeaBIOS)类型，然后点击Next。
system
Disk窗口中，Cache勾选Write Back类型，Disk size (GiB)填写你要分配的硬盘大小，一般不小于20，Storage选择存储在哪个盘，示例只有系统盘local所以就选loacl，然后点击Next。
disk
CPU窗口中，Cores填写所需核数，CPU类型按照前面描述的方法选择，然后点击Next。
cpu
Memory窗口中，Memory (MiB)填写所需内存大小，然后点击Next。
memory
Network窗口中，Bridge勾选vmbr1类型，Model勾选VirtIO (paravirtualized)类型，Firewall取消勾选，然后点击Next。
Network
Confirm窗口中，点击Finish。
finish
3.图形化配置安装 ​
左侧点击设置好的模板，右上角点击Start启动虚拟机，然后点击Console进入VNC界面，等待操作系统启动。
console
然后在VNC中点击下一页，然后点击现在安装，然后点击我没有产品密钥，然后勾选接受许可，点击下一页，然后勾选自定义安装。
win0
win1
win2
win3
win4
然后如果镜像本身带virtio，那么应该可见可选系统存储的硬盘及其大小，选中后点击下一页。
win5
win6
然后等待系统安装，应该会自动重启几次，大概耗时10分钟以上。
win7
安装完成后首次登录会要求设置密码，正常设置即可
win8
设置完成后，NOVNC页面左侧有一个弹出框，点击第一个按钮，然后根据登录提示，点击Ctrl+Alt+最后一个按钮，进入登录页面。
4.初始化网络 ​
由于通过本项目设置的PVE是静态网络，所以登陆后需要手动修改绑定的IP地址，不通过DHCP
在桌面右下角右击点出打开 网络和Internet设置，点击后，在弹出的设置页面中点击更改适配器设置
win9
然后在网络链接中勾选以太网，点击更改此连接的设置
win10
在弹出框中点击Internet协议版本4(TCP/IPV4)选中后点击属性
win11
在新弹出的弹出框中，选择并点击使用下面的IP地址(s)，然后分别填入
IP地址(I)：172.16.1.xxx(xxx换成你想绑定的ip，我的vmid是100，为了方便写了100)
子网掩码(U)：255.255.255.0
默认网关(D)：172.16.1.1
然后选择点击使用下面的DNS服务器地址(E)，分别填入
8.8.8.8
 144.144.144.144
然后右下角点击确定，注意不要勾选退出时验证
win12
然后其他弹出框都选确定和是就行了，然后本虚拟机就有网络了。
5.取消CD盘挂载 ​
在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]然后再重启虚拟机，这样就能直接使用了
wk
使用不带virtio的iso镜像开设 ​
1.下载镜像 ​
无virtio的win镜像下载可使用
https://down.idc.wiki/ISOS/Windows/
这块的镜像
virtio的iso镜像可使用
https://down.idc.wiki/ISOS/Toolkit/
或者
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/
下载
virtio也可以只下载msi包，本地用软件打包成iso压缩格式再本地上传到ProxmoxVE中也可以
这样的话包小一些，前者官方的是包含所有WIN镜像支持的包总计500MB左右，后者自己打包5MB左右
2.virtio导入 ​
注意这里的导入在ProxmoxVE的8.x及之后的版本中，OS这一栏默认可选择virtio启动加载，如图所示
virtio
而在更低版本的ProxmoxVE中，比如7.x和6.x的版本，OS这一栏默认无法选择virtio启动加载
lower
需要手动在Hardware[硬件]中点击Add[添加]添加CD/DVD Drive选择下载好的virtio的ISO文件
lower
然后其他的一切照常，直到
nodisk
这块找不到硬盘，需要选择加载驱动程序
nodisk
然后选择驱动盘是virtio的，点击打开，从amd64那导入对应系统名字的驱动
nodisk
我的是windows server 2019的镜像所以导入的是2k19的驱动，导入完毕后选择导入的驱动，点击下一页
nodisk
nodisk
这样就能看得到硬盘了，选中后继续后续的安装步骤，选中后继续后续的安装步骤如同前面的教程，直到系统安装完毕，进入桌面。
3.通过virtio-win-guest-tools安装驱动 ​
此时安装成功，出现桌面后，还需要手动安装驱动
打开VirtIO驱动所在的CD光驱目录，最下面有一个virtio-win-guest-tools程序，会安装用到的virtio驱动，这个驱动也会包含virtio的网卡驱动
wk
wk
wk
点击安装完毕后就安装上网卡驱动了，后续网络设置参考前面的初始化网络的教程
4.安装网卡驱动(备选) ​
此时安装成功，出现桌面后，还需要手动安装网卡驱动才能连通网络：
  1. 打开 控制面板 → 设备管理器
  2. 找到 以太网控制器，右键选择 更新驱动程序
  3. 选择 浏览我的计算机以查找驱动程序软件 (R)
  4. 浏览到VirtIO驱动所在的CD光驱目录
  5. 打开其中的 NetKVM 文件夹
  6. 根据当前系统版本选择对应的驱动文件夹(和上面相同的操作，我会选择2k19文件夹，里面的amd64驱动)
  7. 确认安装，完成后即可成功加载VirtIO的网卡驱动
wk
wk
wk
后续网络设置参考前面的初始化网络的教程
5.取消CD盘挂载 ​
在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]然后再重启虚拟机，这样就能直接使用了
wk
',126),z=[$];function F(Q,X,J,j,Y,Z){return c(),s("div",null,z)}const so=e(H,[["render",F]]);export{co as __pageData,so as default};
diff --git a/assets/incomplete_bashvm.md.1a8e809b.js b/assets/incomplete_bashvm.md.17d16c32.js
similarity index 95%
rename from assets/incomplete_bashvm.md.1a8e809b.js
rename to assets/incomplete_bashvm.md.17d16c32.js
index 9abb9665d6..0623eee948 100644
--- a/assets/incomplete_bashvm.md.1a8e809b.js
+++ b/assets/incomplete_bashvm.md.17d16c32.js
@@ -1 +1 @@
-import{_ as a,v as e,b as t,R as r}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/bashvm.md","filePath":"incomplete/bashvm.md","lastUpdated":1747726389000}'),s={name:"incomplete/bashvm.md"},h=r('
仓库 ​
https://github.com/babywhale321/bashvm
https://bashvm.com/
说明 ​
如果你想深入了解怎么开设一个虚拟机，怎么转发端口，那么这个项目将完全从底层开始，一步步教你如何开设虚拟机
缺点 ​
非常的繁琐，非常的耗时，不如别的项目快速设置网络和开设
',7),o=[h];function n(i,l,p,c,m,b){return e(),t("div",null,o)}const f=a(s,[["render",n]]);export{_ as __pageData,f as default};
+import{_ as a,v as e,b as t,R as r}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/bashvm.md","filePath":"incomplete/bashvm.md","lastUpdated":1747730955000}'),s={name:"incomplete/bashvm.md"},h=r('
仓库 ​
https://github.com/babywhale321/bashvm
https://bashvm.com/
说明 ​
如果你想深入了解怎么开设一个虚拟机，怎么转发端口，那么这个项目将完全从底层开始，一步步教你如何开设虚拟机
缺点 ​
非常的繁琐，非常的耗时，不如别的项目快速设置网络和开设
',7),o=[h];function n(i,l,p,c,m,b){return e(),t("div",null,o)}const f=a(s,[["render",n]]);export{_ as __pageData,f as default};
diff --git a/assets/incomplete_bashvm.md.1a8e809b.lean.js b/assets/incomplete_bashvm.md.17d16c32.lean.js
similarity index 95%
rename from assets/incomplete_bashvm.md.1a8e809b.lean.js
rename to assets/incomplete_bashvm.md.17d16c32.lean.js
index 9abb9665d6..0623eee948 100644
--- a/assets/incomplete_bashvm.md.1a8e809b.lean.js
+++ b/assets/incomplete_bashvm.md.17d16c32.lean.js
@@ -1 +1 @@
-import{_ as a,v as e,b as t,R as r}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/bashvm.md","filePath":"incomplete/bashvm.md","lastUpdated":1747726389000}'),s={name:"incomplete/bashvm.md"},h=r('
仓库 ​
https://github.com/babywhale321/bashvm
https://bashvm.com/
说明 ​
如果你想深入了解怎么开设一个虚拟机，怎么转发端口，那么这个项目将完全从底层开始，一步步教你如何开设虚拟机
缺点 ​
非常的繁琐，非常的耗时，不如别的项目快速设置网络和开设
',7),o=[h];function n(i,l,p,c,m,b){return e(),t("div",null,o)}const f=a(s,[["render",n]]);export{_ as __pageData,f as default};
+import{_ as a,v as e,b as t,R as r}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/bashvm.md","filePath":"incomplete/bashvm.md","lastUpdated":1747730955000}'),s={name:"incomplete/bashvm.md"},h=r('
仓库 ​
https://github.com/babywhale321/bashvm
https://bashvm.com/
说明 ​
如果你想深入了解怎么开设一个虚拟机，怎么转发端口，那么这个项目将完全从底层开始，一步步教你如何开设虚拟机
缺点 ​
非常的繁琐，非常的耗时，不如别的项目快速设置网络和开设
',7),o=[h];function n(i,l,p,c,m,b){return e(),t("div",null,o)}const f=a(s,[["render",n]]);export{_ as __pageData,f as default};
diff --git a/assets/incomplete_cockpit.md.5b533bd1.js b/assets/incomplete_cockpit.md.520f225b.js
similarity index 98%
rename from assets/incomplete_cockpit.md.5b533bd1.js
rename to assets/incomplete_cockpit.md.520f225b.js
index 9f091cbe38..5249287290 100644
--- a/assets/incomplete_cockpit.md.5b533bd1.js
+++ b/assets/incomplete_cockpit.md.520f225b.js
@@ -1 +1 @@
-import{_ as s,v as a,b as l,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/cockpit.md","filePath":"incomplete/cockpit.md","lastUpdated":1747726389000}'),e={name:"incomplete/cockpit.md"},n=t('
仓库 ​
hits
https://github.com/oneclickvirt/cockpit
安装 ​
支持的系统：Debian，Ubuntu，Almalinux，Rockylinux，Fedora，Centos，Arch
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh
只安装带容器的
shell
bash install.sh --ct
只安装带虚拟机的
shell
bash install.sh --vm
仅安装面板
shell
bash install.sh
容器和虚拟机依赖都进行安装
shell
bash install.sh --all
缺点 ​
网络自行配置，镜像自行导入，端口自行映射，只是比纯命令行多了一个GUI界面罢了
致谢 ​
https://cockpit-project.org/running.html
',21),p=[n];function o(c,r,i,h,C,y){return a(),l("div",null,p)}const A=s(e,[["render",o]]);export{m as __pageData,A as default};
+import{_ as s,v as a,b as l,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/cockpit.md","filePath":"incomplete/cockpit.md","lastUpdated":1747730955000}'),e={name:"incomplete/cockpit.md"},n=t('
仓库 ​
hits
https://github.com/oneclickvirt/cockpit
安装 ​
支持的系统：Debian，Ubuntu，Almalinux，Rockylinux，Fedora，Centos，Arch
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh
只安装带容器的
shell
bash install.sh --ct
只安装带虚拟机的
shell
bash install.sh --vm
仅安装面板
shell
bash install.sh
容器和虚拟机依赖都进行安装
shell
bash install.sh --all
缺点 ​
网络自行配置，镜像自行导入，端口自行映射，只是比纯命令行多了一个GUI界面罢了
致谢 ​
https://cockpit-project.org/running.html
',21),p=[n];function o(c,r,i,h,C,y){return a(),l("div",null,p)}const A=s(e,[["render",o]]);export{m as __pageData,A as default};
diff --git a/assets/incomplete_cockpit.md.5b533bd1.lean.js b/assets/incomplete_cockpit.md.520f225b.lean.js
similarity index 98%
rename from assets/incomplete_cockpit.md.5b533bd1.lean.js
rename to assets/incomplete_cockpit.md.520f225b.lean.js
index 9f091cbe38..5249287290 100644
--- a/assets/incomplete_cockpit.md.5b533bd1.lean.js
+++ b/assets/incomplete_cockpit.md.520f225b.lean.js
@@ -1 +1 @@
-import{_ as s,v as a,b as l,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/cockpit.md","filePath":"incomplete/cockpit.md","lastUpdated":1747726389000}'),e={name:"incomplete/cockpit.md"},n=t('
仓库 ​
hits
https://github.com/oneclickvirt/cockpit
安装 ​
支持的系统：Debian，Ubuntu，Almalinux，Rockylinux，Fedora，Centos，Arch
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh
只安装带容器的
shell
bash install.sh --ct
只安装带虚拟机的
shell
bash install.sh --vm
仅安装面板
shell
bash install.sh
容器和虚拟机依赖都进行安装
shell
bash install.sh --all
缺点 ​
网络自行配置，镜像自行导入，端口自行映射，只是比纯命令行多了一个GUI界面罢了
致谢 ​
https://cockpit-project.org/running.html
',21),p=[n];function o(c,r,i,h,C,y){return a(),l("div",null,p)}const A=s(e,[["render",o]]);export{m as __pageData,A as default};
+import{_ as s,v as a,b as l,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/cockpit.md","filePath":"incomplete/cockpit.md","lastUpdated":1747730955000}'),e={name:"incomplete/cockpit.md"},n=t('
仓库 ​
hits
https://github.com/oneclickvirt/cockpit
安装 ​
支持的系统：Debian，Ubuntu，Almalinux，Rockylinux，Fedora，Centos，Arch
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh
只安装带容器的
shell
bash install.sh --ct
只安装带虚拟机的
shell
bash install.sh --vm
仅安装面板
shell
bash install.sh
容器和虚拟机依赖都进行安装
shell
bash install.sh --all
缺点 ​
网络自行配置，镜像自行导入，端口自行映射，只是比纯命令行多了一个GUI界面罢了
致谢 ​
https://cockpit-project.org/running.html
',21),p=[n];function o(c,r,i,h,C,y){return a(),l("div",null,p)}const A=s(e,[["render",o]]);export{m as __pageData,A as default};
diff --git a/assets/incomplete_convoy.md.f0491c7c.js b/assets/incomplete_convoy.md.94729ba2.js
similarity index 98%
rename from assets/incomplete_convoy.md.f0491c7c.js
rename to assets/incomplete_convoy.md.94729ba2.js
index 4ec898fdb7..bb09516fb1 100644
--- a/assets/incomplete_convoy.md.f0491c7c.js
+++ b/assets/incomplete_convoy.md.94729ba2.js
@@ -1 +1 @@
-import{_ as s,v as a,b as o,R as n}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/convoy.md","filePath":"incomplete/convoy.md","lastUpdated":1747726389000}'),l={name:"incomplete/convoy.md"},t=n('
Repo ​
https://github.com/oneclickvirt/convoypanel-scripts
hits
convoypanel-scripts ​
安装前提条件：
  • 已安装 PVE，但不能是同一节点（不能是同一台机器）
  • 系统为 Debian 11
  • CPU 至少 2 核，硬盘至少 20G，内存至少 4G（内存包含 swap）
我不保证这个脚本没有错误，本项目未完整
国际
shell
curl -L https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
Thanks ​
Base on https://github.com/oneclickvirt/pve
Base on https://docs.convoypanel.com/guide/deployment/#installation
Base on https://github.com/ConvoyPanel/panel
',15),e=[t];function p(c,r,i,h,y,C){return a(),o("div",null,e)}const d=s(l,[["render",p]]);export{D as __pageData,d as default};
+import{_ as s,v as a,b as o,R as n}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/convoy.md","filePath":"incomplete/convoy.md","lastUpdated":1747730955000}'),l={name:"incomplete/convoy.md"},t=n('
Repo ​
https://github.com/oneclickvirt/convoypanel-scripts
hits
convoypanel-scripts ​
安装前提条件：
  • 已安装 PVE，但不能是同一节点（不能是同一台机器）
  • 系统为 Debian 11
  • CPU 至少 2 核，硬盘至少 20G，内存至少 4G（内存包含 swap）
我不保证这个脚本没有错误，本项目未完整
国际
shell
curl -L https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
Thanks ​
Base on https://github.com/oneclickvirt/pve
Base on https://docs.convoypanel.com/guide/deployment/#installation
Base on https://github.com/ConvoyPanel/panel
',15),e=[t];function p(c,r,i,h,y,C){return a(),o("div",null,e)}const d=s(l,[["render",p]]);export{D as __pageData,d as default};
diff --git a/assets/incomplete_convoy.md.f0491c7c.lean.js b/assets/incomplete_convoy.md.94729ba2.lean.js
similarity index 98%
rename from assets/incomplete_convoy.md.f0491c7c.lean.js
rename to assets/incomplete_convoy.md.94729ba2.lean.js
index 4ec898fdb7..bb09516fb1 100644
--- a/assets/incomplete_convoy.md.f0491c7c.lean.js
+++ b/assets/incomplete_convoy.md.94729ba2.lean.js
@@ -1 +1 @@
-import{_ as s,v as a,b as o,R as n}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/convoy.md","filePath":"incomplete/convoy.md","lastUpdated":1747726389000}'),l={name:"incomplete/convoy.md"},t=n('
Repo ​
https://github.com/oneclickvirt/convoypanel-scripts
hits
convoypanel-scripts ​
安装前提条件：
  • 已安装 PVE，但不能是同一节点（不能是同一台机器）
  • 系统为 Debian 11
  • CPU 至少 2 核，硬盘至少 20G，内存至少 4G（内存包含 swap）
我不保证这个脚本没有错误，本项目未完整
国际
shell
curl -L https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
Thanks ​
Base on https://github.com/oneclickvirt/pve
Base on https://docs.convoypanel.com/guide/deployment/#installation
Base on https://github.com/ConvoyPanel/panel
',15),e=[t];function p(c,r,i,h,y,C){return a(),o("div",null,e)}const d=s(l,[["render",p]]);export{D as __pageData,d as default};
+import{_ as s,v as a,b as o,R as n}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/convoy.md","filePath":"incomplete/convoy.md","lastUpdated":1747730955000}'),l={name:"incomplete/convoy.md"},t=n('
Repo ​
https://github.com/oneclickvirt/convoypanel-scripts
hits
convoypanel-scripts ​
安装前提条件：
  • 已安装 PVE，但不能是同一节点（不能是同一台机器）
  • 系统为 Debian 11
  • CPU 至少 2 核，硬盘至少 20G，内存至少 4G（内存包含 swap）
我不保证这个脚本没有错误，本项目未完整
国际
shell
curl -L https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
Thanks ​
Base on https://github.com/oneclickvirt/pve
Base on https://docs.convoypanel.com/guide/deployment/#installation
Base on https://github.com/ConvoyPanel/panel
',15),e=[t];function p(c,r,i,h,y,C){return a(),o("div",null,e)}const d=s(l,[["render",p]]);export{D as __pageData,d as default};
diff --git a/assets/incomplete_index.md.4aab6741.js b/assets/incomplete_index.md.4ba82ff7.js
similarity index 95%
rename from assets/incomplete_index.md.4aab6741.js
rename to assets/incomplete_index.md.4ba82ff7.js
index 11b015b22b..ea6761b2fb 100644
--- a/assets/incomplete_index.md.4aab6741.js
+++ b/assets/incomplete_index.md.4ba82ff7.js
@@ -1 +1 @@
-import{_ as t,v as e,b as i}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"其他虚拟化项目","titleTemplate":"其他不完整的虚拟化项目","description":"","frontmatter":{"layout":"home","title":"其他虚拟化项目","titleTemplate":"其他不完整的虚拟化项目","hero":{"name":"其他虚拟化项目","text":"一些不完整的虚拟化项目","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"查看项目 →","link":"/incomplete/webvirtcloud"}]},"features":[{"title":"注意事项","details":"这块每个项目都有对应的缺点，每个项目都不像之前的项目一样简单好用，有一定的学习成本。"},{"title":"难易程度","details":"基于项目本身的使用难度，由易到难排序，越往后你能得到本指南的引导越少。"},{"title":"项目缺点","details":"每个项目都有部分缺点导致不被认为是完整的一键项目，有一些操作需要手动执行命令无法一键化。"}]},"headers":[],"relativePath":"incomplete/index.md","filePath":"incomplete/index.md","lastUpdated":1747726389000}'),a={name:"incomplete/index.md"};function n(s,l,o,r,p,d){return e(),i("div")}const h=t(a,[["render",n]]);export{m as __pageData,h as default};
+import{_ as t,v as e,b as i}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"其他虚拟化项目","titleTemplate":"其他不完整的虚拟化项目","description":"","frontmatter":{"layout":"home","title":"其他虚拟化项目","titleTemplate":"其他不完整的虚拟化项目","hero":{"name":"其他虚拟化项目","text":"一些不完整的虚拟化项目","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"查看项目 →","link":"/incomplete/webvirtcloud"}]},"features":[{"title":"注意事项","details":"这块每个项目都有对应的缺点，每个项目都不像之前的项目一样简单好用，有一定的学习成本。"},{"title":"难易程度","details":"基于项目本身的使用难度，由易到难排序，越往后你能得到本指南的引导越少。"},{"title":"项目缺点","details":"每个项目都有部分缺点导致不被认为是完整的一键项目，有一些操作需要手动执行命令无法一键化。"}]},"headers":[],"relativePath":"incomplete/index.md","filePath":"incomplete/index.md","lastUpdated":1747730955000}'),a={name:"incomplete/index.md"};function n(s,l,o,r,p,d){return e(),i("div")}const h=t(a,[["render",n]]);export{m as __pageData,h as default};
diff --git a/assets/incomplete_index.md.4aab6741.lean.js b/assets/incomplete_index.md.4ba82ff7.lean.js
similarity index 95%
rename from assets/incomplete_index.md.4aab6741.lean.js
rename to assets/incomplete_index.md.4ba82ff7.lean.js
index 11b015b22b..ea6761b2fb 100644
--- a/assets/incomplete_index.md.4aab6741.lean.js
+++ b/assets/incomplete_index.md.4ba82ff7.lean.js
@@ -1 +1 @@
-import{_ as t,v as e,b as i}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"其他虚拟化项目","titleTemplate":"其他不完整的虚拟化项目","description":"","frontmatter":{"layout":"home","title":"其他虚拟化项目","titleTemplate":"其他不完整的虚拟化项目","hero":{"name":"其他虚拟化项目","text":"一些不完整的虚拟化项目","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"查看项目 →","link":"/incomplete/webvirtcloud"}]},"features":[{"title":"注意事项","details":"这块每个项目都有对应的缺点，每个项目都不像之前的项目一样简单好用，有一定的学习成本。"},{"title":"难易程度","details":"基于项目本身的使用难度，由易到难排序，越往后你能得到本指南的引导越少。"},{"title":"项目缺点","details":"每个项目都有部分缺点导致不被认为是完整的一键项目，有一些操作需要手动执行命令无法一键化。"}]},"headers":[],"relativePath":"incomplete/index.md","filePath":"incomplete/index.md","lastUpdated":1747726389000}'),a={name:"incomplete/index.md"};function n(s,l,o,r,p,d){return e(),i("div")}const h=t(a,[["render",n]]);export{m as __pageData,h as default};
+import{_ as t,v as e,b as i}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"其他虚拟化项目","titleTemplate":"其他不完整的虚拟化项目","description":"","frontmatter":{"layout":"home","title":"其他虚拟化项目","titleTemplate":"其他不完整的虚拟化项目","hero":{"name":"其他虚拟化项目","text":"一些不完整的虚拟化项目","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"查看项目 →","link":"/incomplete/webvirtcloud"}]},"features":[{"title":"注意事项","details":"这块每个项目都有对应的缺点，每个项目都不像之前的项目一样简单好用，有一定的学习成本。"},{"title":"难易程度","details":"基于项目本身的使用难度，由易到难排序，越往后你能得到本指南的引导越少。"},{"title":"项目缺点","details":"每个项目都有部分缺点导致不被认为是完整的一键项目，有一些操作需要手动执行命令无法一键化。"}]},"headers":[],"relativePath":"incomplete/index.md","filePath":"incomplete/index.md","lastUpdated":1747730955000}'),a={name:"incomplete/index.md"};function n(s,l,o,r,p,d){return e(),i("div")}const h=t(a,[["render",n]]);export{m as __pageData,h as default};
diff --git a/assets/incomplete_pterodactyl.md.ec35dbae.js b/assets/incomplete_pterodactyl.md.10b58889.js
similarity index 99%
rename from assets/incomplete_pterodactyl.md.ec35dbae.js
rename to assets/incomplete_pterodactyl.md.10b58889.js
index 63520eff41..d875db66b2 100644
--- a/assets/incomplete_pterodactyl.md.ec35dbae.js
+++ b/assets/incomplete_pterodactyl.md.10b58889.js
@@ -1 +1 @@
-import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/pterodactyl.md","filePath":"incomplete/pterodactyl.md","lastUpdated":1747726389000}'),n={name:"incomplete/pterodactyl.md"},o=p('
Repo ​
https://github.com/oneclickvirt/pterodactyl
hits
pterodactyl-scripts ​
进一步调研发现开设servers和绑定用户极麻烦，不如原生直接docker方便，故而暂不做后续开发了
说明 ​
目前支持的系统
系统类型版本范围备注
Ubuntu20.04(推荐), 22.04, 24.04已支持
Debian11(Bullseye), 12(Bookworm)已支持
Panel ​
panel端执行：
国际
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh
国内
shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh
Wings ​
wings端执行：
国际
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh
国内
shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh
Import ​
panel端执行：
国际
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh
国内
shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh
会生成需要在wings端执行的命令
生成的命令执行完毕后等待20秒以上，避免一些初始化流程未走完，然后wings端再执行：
shell
bash install_wings.sh
然后在http://<your_ip>/admin/nodes就能看到你的节点已经被自动添加纳管，心跳是绿色的
Thanks ​
https://pterodactyl.io/
',32),t=[o];function e(r,c,C,i,y,h){return a(),l("div",null,t)}const D=s(n,[["render",e]]);export{A as __pageData,D as default};
+import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/pterodactyl.md","filePath":"incomplete/pterodactyl.md","lastUpdated":1747730955000}'),n={name:"incomplete/pterodactyl.md"},o=p('
Repo ​
https://github.com/oneclickvirt/pterodactyl
hits
pterodactyl-scripts ​
进一步调研发现开设servers和绑定用户极麻烦，不如原生直接docker方便，故而暂不做后续开发了
说明 ​
目前支持的系统
系统类型版本范围备注
Ubuntu20.04(推荐), 22.04, 24.04已支持
Debian11(Bullseye), 12(Bookworm)已支持
Panel ​
panel端执行：
国际
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh
国内
shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh
Wings ​
wings端执行：
国际
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh
国内
shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh
Import ​
panel端执行：
国际
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh
国内
shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh
会生成需要在wings端执行的命令
生成的命令执行完毕后等待20秒以上，避免一些初始化流程未走完，然后wings端再执行：
shell
bash install_wings.sh
然后在http://<your_ip>/admin/nodes就能看到你的节点已经被自动添加纳管，心跳是绿色的
Thanks ​
https://pterodactyl.io/
',32),t=[o];function e(r,c,C,i,y,h){return a(),l("div",null,t)}const D=s(n,[["render",e]]);export{A as __pageData,D as default};
diff --git a/assets/incomplete_pterodactyl.md.ec35dbae.lean.js b/assets/incomplete_pterodactyl.md.10b58889.lean.js
similarity index 99%
rename from assets/incomplete_pterodactyl.md.ec35dbae.lean.js
rename to assets/incomplete_pterodactyl.md.10b58889.lean.js
index 63520eff41..d875db66b2 100644
--- a/assets/incomplete_pterodactyl.md.ec35dbae.lean.js
+++ b/assets/incomplete_pterodactyl.md.10b58889.lean.js
@@ -1 +1 @@
-import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/pterodactyl.md","filePath":"incomplete/pterodactyl.md","lastUpdated":1747726389000}'),n={name:"incomplete/pterodactyl.md"},o=p('
Repo ​
https://github.com/oneclickvirt/pterodactyl
hits
pterodactyl-scripts ​
进一步调研发现开设servers和绑定用户极麻烦，不如原生直接docker方便，故而暂不做后续开发了
说明 ​
目前支持的系统
系统类型版本范围备注
Ubuntu20.04(推荐), 22.04, 24.04已支持
Debian11(Bullseye), 12(Bookworm)已支持
Panel ​
panel端执行：
国际
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh
国内
shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh
Wings ​
wings端执行：
国际
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh
国内
shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh
Import ​
panel端执行：
国际
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh
国内
shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh
会生成需要在wings端执行的命令
生成的命令执行完毕后等待20秒以上，避免一些初始化流程未走完，然后wings端再执行：
shell
bash install_wings.sh
然后在http://<your_ip>/admin/nodes就能看到你的节点已经被自动添加纳管，心跳是绿色的
Thanks ​
https://pterodactyl.io/
',32),t=[o];function e(r,c,C,i,y,h){return a(),l("div",null,t)}const D=s(n,[["render",e]]);export{A as __pageData,D as default};
+import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/pterodactyl.md","filePath":"incomplete/pterodactyl.md","lastUpdated":1747730955000}'),n={name:"incomplete/pterodactyl.md"},o=p('
Repo ​
https://github.com/oneclickvirt/pterodactyl
hits
pterodactyl-scripts ​
进一步调研发现开设servers和绑定用户极麻烦，不如原生直接docker方便，故而暂不做后续开发了
说明 ​
目前支持的系统
系统类型版本范围备注
Ubuntu20.04(推荐), 22.04, 24.04已支持
Debian11(Bullseye), 12(Bookworm)已支持
Panel ​
panel端执行：
国际
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh
国内
shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh
Wings ​
wings端执行：
国际
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh
国内
shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh
Import ​
panel端执行：
国际
shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh
国内
shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh
会生成需要在wings端执行的命令
生成的命令执行完毕后等待20秒以上，避免一些初始化流程未走完，然后wings端再执行：
shell
bash install_wings.sh
然后在http://<your_ip>/admin/nodes就能看到你的节点已经被自动添加纳管，心跳是绿色的
Thanks ​
https://pterodactyl.io/
',32),t=[o];function e(r,c,C,i,y,h){return a(),l("div",null,t)}const D=s(n,[["render",e]]);export{A as __pageData,D as default};
diff --git a/assets/incomplete_virtfusion.md.f0ae5001.js b/assets/incomplete_virtfusion.md.ce2e2114.js
similarity index 99%
rename from assets/incomplete_virtfusion.md.f0ae5001.js
rename to assets/incomplete_virtfusion.md.ce2e2114.js
index 62fb6c12fd..4d45be35a8 100644
--- a/assets/incomplete_virtfusion.md.f0ae5001.js
+++ b/assets/incomplete_virtfusion.md.ce2e2114.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/virtfusion.md","filePath":"incomplete/virtfusion.md","lastUpdated":1747726389000}'),o={name:"incomplete/virtfusion.md"},p=n(`
官方文档 ​
https://docs.virtfusion.com/next/installation/control-server/#activating-a-license
一键安装 ​
debian11
shell
apt install curl -y
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/virtfusion.md","filePath":"incomplete/virtfusion.md","lastUpdated":1747730955000}'),o={name:"incomplete/virtfusion.md"},p=n(`
官方文档 ​
https://docs.virtfusion.com/next/installation/control-server/#activating-a-license
一键安装 ​
debian11
shell
apt install curl -y
 curl https://install.virtfusion.net/install-control-debian-11.sh | sh -s -- --verbose
debian12
shell
apt install curl -y
 curl https://install.virtfusion.net/install-control-debian-12.sh | sh -s -- --verbose
RHEL8
shell
dnf install curl -y
 curl https://install.virtfusion.net/install-control-rhel-8.sh | sh -s -- --verbose
RHEL9
shell
dnf install curl -y
diff --git a/assets/incomplete_virtfusion.md.f0ae5001.lean.js b/assets/incomplete_virtfusion.md.ce2e2114.lean.js
similarity index 99%
rename from assets/incomplete_virtfusion.md.f0ae5001.lean.js
rename to assets/incomplete_virtfusion.md.ce2e2114.lean.js
index 62fb6c12fd..4d45be35a8 100644
--- a/assets/incomplete_virtfusion.md.f0ae5001.lean.js
+++ b/assets/incomplete_virtfusion.md.ce2e2114.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/virtfusion.md","filePath":"incomplete/virtfusion.md","lastUpdated":1747726389000}'),o={name:"incomplete/virtfusion.md"},p=n(`
官方文档 ​
https://docs.virtfusion.com/next/installation/control-server/#activating-a-license
一键安装 ​
debian11
shell
apt install curl -y
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/virtfusion.md","filePath":"incomplete/virtfusion.md","lastUpdated":1747730955000}'),o={name:"incomplete/virtfusion.md"},p=n(`
官方文档 ​
https://docs.virtfusion.com/next/installation/control-server/#activating-a-license
一键安装 ​
debian11
shell
apt install curl -y
 curl https://install.virtfusion.net/install-control-debian-11.sh | sh -s -- --verbose
debian12
shell
apt install curl -y
 curl https://install.virtfusion.net/install-control-debian-12.sh | sh -s -- --verbose
RHEL8
shell
dnf install curl -y
 curl https://install.virtfusion.net/install-control-rhel-8.sh | sh -s -- --verbose
RHEL9
shell
dnf install curl -y
diff --git a/assets/incomplete_virtualizor-docker.md.c2bfdb7a.js b/assets/incomplete_virtualizor-docker.md.a4432ceb.js
similarity index 95%
rename from assets/incomplete_virtualizor-docker.md.c2bfdb7a.js
rename to assets/incomplete_virtualizor-docker.md.a4432ceb.js
index efc076222b..9ba72c8fe5 100644
--- a/assets/incomplete_virtualizor-docker.md.c2bfdb7a.js
+++ b/assets/incomplete_virtualizor-docker.md.a4432ceb.js
@@ -1 +1 @@
-import{_ as e,v as a,b as t,R as r}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/virtualizor-docker.md","filePath":"incomplete/virtualizor-docker.md","lastUpdated":1747726389000}'),o={name:"incomplete/virtualizor-docker.md"},i=r('
仓库 ​
https://github.com/ivstiv/virtualizor-docker
说明 ​
在docker中开设的 virtualizor
证书用的是试用的证书，有效期一天，且默认只安装了OpenVZ的虚拟化方式
缺点 ​
毫无社区，一切自行摸索
admin面板的端口不要看脚本的提示信息，以仓库说明为准。
',8),s=[i];function n(l,c,d,p,h,u){return a(),t("div",null,s)}const v=e(o,[["render",n]]);export{_ as __pageData,v as default};
+import{_ as e,v as a,b as t,R as r}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/virtualizor-docker.md","filePath":"incomplete/virtualizor-docker.md","lastUpdated":1747730955000}'),o={name:"incomplete/virtualizor-docker.md"},i=r('
仓库 ​
https://github.com/ivstiv/virtualizor-docker
说明 ​
在docker中开设的 virtualizor
证书用的是试用的证书，有效期一天，且默认只安装了OpenVZ的虚拟化方式
缺点 ​
毫无社区，一切自行摸索
admin面板的端口不要看脚本的提示信息，以仓库说明为准。
',8),s=[i];function n(l,c,d,p,h,u){return a(),t("div",null,s)}const v=e(o,[["render",n]]);export{_ as __pageData,v as default};
diff --git a/assets/incomplete_virtualizor-docker.md.c2bfdb7a.lean.js b/assets/incomplete_virtualizor-docker.md.a4432ceb.lean.js
similarity index 95%
rename from assets/incomplete_virtualizor-docker.md.c2bfdb7a.lean.js
rename to assets/incomplete_virtualizor-docker.md.a4432ceb.lean.js
index efc076222b..9ba72c8fe5 100644
--- a/assets/incomplete_virtualizor-docker.md.c2bfdb7a.lean.js
+++ b/assets/incomplete_virtualizor-docker.md.a4432ceb.lean.js
@@ -1 +1 @@
-import{_ as e,v as a,b as t,R as r}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/virtualizor-docker.md","filePath":"incomplete/virtualizor-docker.md","lastUpdated":1747726389000}'),o={name:"incomplete/virtualizor-docker.md"},i=r('
仓库 ​
https://github.com/ivstiv/virtualizor-docker
说明 ​
在docker中开设的 virtualizor
证书用的是试用的证书，有效期一天，且默认只安装了OpenVZ的虚拟化方式
缺点 ​
毫无社区，一切自行摸索
admin面板的端口不要看脚本的提示信息，以仓库说明为准。
',8),s=[i];function n(l,c,d,p,h,u){return a(),t("div",null,s)}const v=e(o,[["render",n]]);export{_ as __pageData,v as default};
+import{_ as e,v as a,b as t,R as r}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/virtualizor-docker.md","filePath":"incomplete/virtualizor-docker.md","lastUpdated":1747730955000}'),o={name:"incomplete/virtualizor-docker.md"},i=r('
仓库 ​
https://github.com/ivstiv/virtualizor-docker
说明 ​
在docker中开设的 virtualizor
证书用的是试用的证书，有效期一天，且默认只安装了OpenVZ的虚拟化方式
缺点 ​
毫无社区，一切自行摸索
admin面板的端口不要看脚本的提示信息，以仓库说明为准。
',8),s=[i];function n(l,c,d,p,h,u){return a(),t("div",null,s)}const v=e(o,[["render",n]]);export{_ as __pageData,v as default};
diff --git a/assets/incomplete_webvirtcloud.md.945a6b84.js b/assets/incomplete_webvirtcloud.md.225601ed.js
similarity index 99%
rename from assets/incomplete_webvirtcloud.md.945a6b84.js
rename to assets/incomplete_webvirtcloud.md.225601ed.js
index 345d49e0a4..a901c80e0a 100644
--- a/assets/incomplete_webvirtcloud.md.945a6b84.js
+++ b/assets/incomplete_webvirtcloud.md.225601ed.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const o="/assets/wv1.5ac4a026.png",h=JSON.parse('{"title":"WebVirtCloud 安装指南","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/webvirtcloud.md","filePath":"incomplete/webvirtcloud.md","lastUpdated":1747726389000}'),p={name:"incomplete/webvirtcloud.md"},e=n(`
WebVirtCloud 安装指南 ​
hits
仓库地址: https://github.com/oneclickvirt/webvirtcloud
原项目对应仓库：https://github.com/webvirtcloud/webvirtcloud
应该算是全网中文第一份完整的部署指南，官方的指南实际上有很多地方是和本项目部署的方式有出入的。
1. 控制端安装 ​
系统要求 ​
最低配置要求:
  • CPU: 1 核
  • 内存: 1 GB RAM
  • 硬盘: 空余 10 GB
  • 系统：Debian11+，Ubuntu20.04+, Centos8+, AlmaLinux8+, RockyLinux8+
默认登录信息 ​
  • 用户名: admin@webvirt.cloud
  • 密码: admin
面板地址 ​
  • 用户面板: https://192-168-0-114.nip.io
  • 管理后台: https://192-168-0-114.nip.io/admin
注意: 请将 192.168.0.114 替换为你的公网 IP，以获取真实可访问地址。
安装命令 ​
国际版本：
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud.sh -o install_webvirt_cloud.sh \\
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const o="/assets/wv1.5ac4a026.png",h=JSON.parse('{"title":"WebVirtCloud 安装指南","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/webvirtcloud.md","filePath":"incomplete/webvirtcloud.md","lastUpdated":1747730955000}'),p={name:"incomplete/webvirtcloud.md"},e=n(`
WebVirtCloud 安装指南 ​
hits
仓库地址: https://github.com/oneclickvirt/webvirtcloud
原项目对应仓库：https://github.com/webvirtcloud/webvirtcloud
应该算是全网中文第一份完整的部署指南，官方的指南实际上有很多地方是和本项目部署的方式有出入的。
1. 控制端安装 ​
系统要求 ​
最低配置要求:
  • CPU: 1 核
  • 内存: 1 GB RAM
  • 硬盘: 空余 10 GB
  • 系统：Debian11+，Ubuntu20.04+, Centos8+, AlmaLinux8+, RockyLinux8+
默认登录信息 ​
  • 用户名: admin@webvirt.cloud
  • 密码: admin
面板地址 ​
  • 用户面板: https://192-168-0-114.nip.io
  • 管理后台: https://192-168-0-114.nip.io/admin
注意: 请将 192.168.0.114 替换为你的公网 IP，以获取真实可访问地址。
安装命令 ​
国际版本：
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud.sh -o install_webvirt_cloud.sh \\
 && chmod +x install_webvirt_cloud.sh \\
 && bash install_webvirt_cloud.sh
国内版本：
bash
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud.sh -o install_webvirt_cloud.sh \\
 && chmod +x install_webvirt_cloud.sh \\
diff --git a/assets/incomplete_webvirtcloud.md.945a6b84.lean.js b/assets/incomplete_webvirtcloud.md.225601ed.lean.js
similarity index 99%
rename from assets/incomplete_webvirtcloud.md.945a6b84.lean.js
rename to assets/incomplete_webvirtcloud.md.225601ed.lean.js
index 345d49e0a4..a901c80e0a 100644
--- a/assets/incomplete_webvirtcloud.md.945a6b84.lean.js
+++ b/assets/incomplete_webvirtcloud.md.225601ed.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const o="/assets/wv1.5ac4a026.png",h=JSON.parse('{"title":"WebVirtCloud 安装指南","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/webvirtcloud.md","filePath":"incomplete/webvirtcloud.md","lastUpdated":1747726389000}'),p={name:"incomplete/webvirtcloud.md"},e=n(`
WebVirtCloud 安装指南 ​
hits
仓库地址: https://github.com/oneclickvirt/webvirtcloud
原项目对应仓库：https://github.com/webvirtcloud/webvirtcloud
应该算是全网中文第一份完整的部署指南，官方的指南实际上有很多地方是和本项目部署的方式有出入的。
1. 控制端安装 ​
系统要求 ​
最低配置要求:
  • CPU: 1 核
  • 内存: 1 GB RAM
  • 硬盘: 空余 10 GB
  • 系统：Debian11+，Ubuntu20.04+, Centos8+, AlmaLinux8+, RockyLinux8+
默认登录信息 ​
  • 用户名: admin@webvirt.cloud
  • 密码: admin
面板地址 ​
  • 用户面板: https://192-168-0-114.nip.io
  • 管理后台: https://192-168-0-114.nip.io/admin
注意: 请将 192.168.0.114 替换为你的公网 IP，以获取真实可访问地址。
安装命令 ​
国际版本：
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud.sh -o install_webvirt_cloud.sh \\
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const o="/assets/wv1.5ac4a026.png",h=JSON.parse('{"title":"WebVirtCloud 安装指南","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/webvirtcloud.md","filePath":"incomplete/webvirtcloud.md","lastUpdated":1747730955000}'),p={name:"incomplete/webvirtcloud.md"},e=n(`
WebVirtCloud 安装指南 ​
hits
仓库地址: https://github.com/oneclickvirt/webvirtcloud
原项目对应仓库：https://github.com/webvirtcloud/webvirtcloud
应该算是全网中文第一份完整的部署指南，官方的指南实际上有很多地方是和本项目部署的方式有出入的。
1. 控制端安装 ​
系统要求 ​
最低配置要求:
  • CPU: 1 核
  • 内存: 1 GB RAM
  • 硬盘: 空余 10 GB
  • 系统：Debian11+，Ubuntu20.04+, Centos8+, AlmaLinux8+, RockyLinux8+
默认登录信息 ​
  • 用户名: admin@webvirt.cloud
  • 密码: admin
面板地址 ​
  • 用户面板: https://192-168-0-114.nip.io
  • 管理后台: https://192-168-0-114.nip.io/admin
注意: 请将 192.168.0.114 替换为你的公网 IP，以获取真实可访问地址。
安装命令 ​
国际版本：
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud.sh -o install_webvirt_cloud.sh \\
 && chmod +x install_webvirt_cloud.sh \\
 && bash install_webvirt_cloud.sh
国内版本：
bash
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud.sh -o install_webvirt_cloud.sh \\
 && chmod +x install_webvirt_cloud.sh \\
diff --git a/assets/incomplete_webvirtcloud_retspen.md.f23e0ec1.js b/assets/incomplete_webvirtcloud_retspen.md.c02acb84.js
similarity index 99%
rename from assets/incomplete_webvirtcloud_retspen.md.f23e0ec1.js
rename to assets/incomplete_webvirtcloud_retspen.md.c02acb84.js
index 33bc788731..04780f65e2 100644
--- a/assets/incomplete_webvirtcloud_retspen.md.f23e0ec1.js
+++ b/assets/incomplete_webvirtcloud_retspen.md.c02acb84.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as p}from"./chunks/framework.70afa331.js";const t="/assets/vcr1.30d933ab.jpg",l="/assets/vcr2.9b30a319.jpg",o="/assets/vcr3.0aa5a564.jpg",n="/assets/vcr4.18a1487e.jpg",c="/assets/vcr5.97deb479.jpg",r="/assets/vcr6.e706123b.jpg",i="/assets/vcr7.43c60335.jpg",d="/assets/vcr8.1bf1f353.jpg",m="/assets/vcr9.b5afa4b4.jpg",h="/assets/vcr10.548c566e.jpg",C="/assets/vcr11.58ce8ace.jpg",_="/assets/vcr12.3aa69b2a.jpg",b="/assets/vcr13.fcbcc557.jpg",v="/assets/vcr14.7009c833.jpg",q=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/webvirtcloud_retspen.md","filePath":"incomplete/webvirtcloud_retspen.md","lastUpdated":1747726389000}'),u={name:"incomplete/webvirtcloud_retspen.md"},g=p(`
WebVirtCloud 安装指南 ​
hits
仓库地址: https://github.com/oneclickvirt/webvirtcloud
原项目对应仓库：https://github.com/retspen/webvirtcloud
控制节点和计算节点同时安装 ​
  • 支持系统：Debian10+, Ubuntu18.04+, Centos8+, AlmaLinux8+, RockyLinux8+
  • 推荐系统：Debian12+，Ubuntu22.04+
  • 低版本系统会自动编译python新版本的安装包后再进行部署，所以推荐使用新系统不必编译直接安装
国际
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud_retspen.sh -o install_webvirt_cloud_retspen.sh \\
+import{_ as s,v as a,b as e,R as p}from"./chunks/framework.70afa331.js";const t="/assets/vcr1.30d933ab.jpg",l="/assets/vcr2.9b30a319.jpg",o="/assets/vcr3.0aa5a564.jpg",n="/assets/vcr4.18a1487e.jpg",c="/assets/vcr5.97deb479.jpg",r="/assets/vcr6.e706123b.jpg",i="/assets/vcr7.43c60335.jpg",d="/assets/vcr8.1bf1f353.jpg",m="/assets/vcr9.b5afa4b4.jpg",h="/assets/vcr10.548c566e.jpg",C="/assets/vcr11.58ce8ace.jpg",_="/assets/vcr12.3aa69b2a.jpg",b="/assets/vcr13.fcbcc557.jpg",v="/assets/vcr14.7009c833.jpg",q=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/webvirtcloud_retspen.md","filePath":"incomplete/webvirtcloud_retspen.md","lastUpdated":1747730955000}'),u={name:"incomplete/webvirtcloud_retspen.md"},g=p(`
WebVirtCloud 安装指南 ​
hits
仓库地址: https://github.com/oneclickvirt/webvirtcloud
原项目对应仓库：https://github.com/retspen/webvirtcloud
控制节点和计算节点同时安装 ​
  • 支持系统：Debian10+, Ubuntu18.04+, Centos8+, AlmaLinux8+, RockyLinux8+
  • 推荐系统：Debian12+，Ubuntu22.04+
  • 低版本系统会自动编译python新版本的安装包后再进行部署，所以推荐使用新系统不必编译直接安装
国际
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud_retspen.sh -o install_webvirt_cloud_retspen.sh \\
 && chmod +x install_webvirt_cloud_retspen.sh \\
 && bash install_webvirt_cloud_retspen.sh
国内
bash
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud_retspen.sh -o install_webvirt_cloud_retspen.sh \\
 && chmod +x install_webvirt_cloud_retspen.sh \\
diff --git a/assets/incomplete_webvirtcloud_retspen.md.f23e0ec1.lean.js b/assets/incomplete_webvirtcloud_retspen.md.c02acb84.lean.js
similarity index 99%
rename from assets/incomplete_webvirtcloud_retspen.md.f23e0ec1.lean.js
rename to assets/incomplete_webvirtcloud_retspen.md.c02acb84.lean.js
index 33bc788731..04780f65e2 100644
--- a/assets/incomplete_webvirtcloud_retspen.md.f23e0ec1.lean.js
+++ b/assets/incomplete_webvirtcloud_retspen.md.c02acb84.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as p}from"./chunks/framework.70afa331.js";const t="/assets/vcr1.30d933ab.jpg",l="/assets/vcr2.9b30a319.jpg",o="/assets/vcr3.0aa5a564.jpg",n="/assets/vcr4.18a1487e.jpg",c="/assets/vcr5.97deb479.jpg",r="/assets/vcr6.e706123b.jpg",i="/assets/vcr7.43c60335.jpg",d="/assets/vcr8.1bf1f353.jpg",m="/assets/vcr9.b5afa4b4.jpg",h="/assets/vcr10.548c566e.jpg",C="/assets/vcr11.58ce8ace.jpg",_="/assets/vcr12.3aa69b2a.jpg",b="/assets/vcr13.fcbcc557.jpg",v="/assets/vcr14.7009c833.jpg",q=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/webvirtcloud_retspen.md","filePath":"incomplete/webvirtcloud_retspen.md","lastUpdated":1747726389000}'),u={name:"incomplete/webvirtcloud_retspen.md"},g=p(`
WebVirtCloud 安装指南 ​
hits
仓库地址: https://github.com/oneclickvirt/webvirtcloud
原项目对应仓库：https://github.com/retspen/webvirtcloud
控制节点和计算节点同时安装 ​
  • 支持系统：Debian10+, Ubuntu18.04+, Centos8+, AlmaLinux8+, RockyLinux8+
  • 推荐系统：Debian12+，Ubuntu22.04+
  • 低版本系统会自动编译python新版本的安装包后再进行部署，所以推荐使用新系统不必编译直接安装
国际
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud_retspen.sh -o install_webvirt_cloud_retspen.sh \\
+import{_ as s,v as a,b as e,R as p}from"./chunks/framework.70afa331.js";const t="/assets/vcr1.30d933ab.jpg",l="/assets/vcr2.9b30a319.jpg",o="/assets/vcr3.0aa5a564.jpg",n="/assets/vcr4.18a1487e.jpg",c="/assets/vcr5.97deb479.jpg",r="/assets/vcr6.e706123b.jpg",i="/assets/vcr7.43c60335.jpg",d="/assets/vcr8.1bf1f353.jpg",m="/assets/vcr9.b5afa4b4.jpg",h="/assets/vcr10.548c566e.jpg",C="/assets/vcr11.58ce8ace.jpg",_="/assets/vcr12.3aa69b2a.jpg",b="/assets/vcr13.fcbcc557.jpg",v="/assets/vcr14.7009c833.jpg",q=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/webvirtcloud_retspen.md","filePath":"incomplete/webvirtcloud_retspen.md","lastUpdated":1747730955000}'),u={name:"incomplete/webvirtcloud_retspen.md"},g=p(`
WebVirtCloud 安装指南 ​
hits
仓库地址: https://github.com/oneclickvirt/webvirtcloud
原项目对应仓库：https://github.com/retspen/webvirtcloud
控制节点和计算节点同时安装 ​
  • 支持系统：Debian10+, Ubuntu18.04+, Centos8+, AlmaLinux8+, RockyLinux8+
  • 推荐系统：Debian12+，Ubuntu22.04+
  • 低版本系统会自动编译python新版本的安装包后再进行部署，所以推荐使用新系统不必编译直接安装
国际
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud_retspen.sh -o install_webvirt_cloud_retspen.sh \\
 && chmod +x install_webvirt_cloud_retspen.sh \\
 && bash install_webvirt_cloud_retspen.sh
国内
bash
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirt_cloud_retspen.sh -o install_webvirt_cloud_retspen.sh \\
 && chmod +x install_webvirt_cloud_retspen.sh \\
diff --git a/assets/incomplete_webvirtmgr.md.6d1a23e0.js b/assets/incomplete_webvirtmgr.md.509f8d4b.js
similarity index 98%
rename from assets/incomplete_webvirtmgr.md.6d1a23e0.js
rename to assets/incomplete_webvirtmgr.md.509f8d4b.js
index 24cfde4b5e..66fe895f20 100644
--- a/assets/incomplete_webvirtmgr.md.6d1a23e0.js
+++ b/assets/incomplete_webvirtmgr.md.509f8d4b.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as t,R as l}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/webvirtmgr.md","filePath":"incomplete/webvirtmgr.md","lastUpdated":1747726389000}'),n={name:"incomplete/webvirtmgr.md"},e=l(`
WebVirtMgr 安装指南 ​
hits
仓库地址: https://github.com/oneclickvirt/webvirtcloud
原项目对应仓库：https://github.com/retspen/webvirtmgr
控制节点和计算节点同时安装 ​
  • 支持系统：Debian[8,9,10]，Ubuntu[16.04,18.04,20.04]
  • 系统会自动编译python的2.7的安装包后再进行部署，编译过程中会有报错提示但不用理会，只要脚本还在跑就说明一切正常
国际
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirtmgr.sh -o install_webvirtmgr.sh \\
+import{_ as s,v as a,b as t,R as l}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/webvirtmgr.md","filePath":"incomplete/webvirtmgr.md","lastUpdated":1747730955000}'),n={name:"incomplete/webvirtmgr.md"},e=l(`
WebVirtMgr 安装指南 ​
hits
仓库地址: https://github.com/oneclickvirt/webvirtcloud
原项目对应仓库：https://github.com/retspen/webvirtmgr
控制节点和计算节点同时安装 ​
  • 支持系统：Debian[8,9,10]，Ubuntu[16.04,18.04,20.04]
  • 系统会自动编译python的2.7的安装包后再进行部署，编译过程中会有报错提示但不用理会，只要脚本还在跑就说明一切正常
国际
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirtmgr.sh -o install_webvirtmgr.sh \\
 && chmod +x install_webvirtmgr.sh \\
 && bash install_webvirtmgr.sh
国内
bash
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirtmgr.sh -o install_webvirtmgr.sh \\
 && chmod +x install_webvirtmgr.sh \\
diff --git a/assets/incomplete_webvirtmgr.md.6d1a23e0.lean.js b/assets/incomplete_webvirtmgr.md.509f8d4b.lean.js
similarity index 98%
rename from assets/incomplete_webvirtmgr.md.6d1a23e0.lean.js
rename to assets/incomplete_webvirtmgr.md.509f8d4b.lean.js
index 24cfde4b5e..66fe895f20 100644
--- a/assets/incomplete_webvirtmgr.md.6d1a23e0.lean.js
+++ b/assets/incomplete_webvirtmgr.md.509f8d4b.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as t,R as l}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/webvirtmgr.md","filePath":"incomplete/webvirtmgr.md","lastUpdated":1747726389000}'),n={name:"incomplete/webvirtmgr.md"},e=l(`
WebVirtMgr 安装指南 ​
hits
仓库地址: https://github.com/oneclickvirt/webvirtcloud
原项目对应仓库：https://github.com/retspen/webvirtmgr
控制节点和计算节点同时安装 ​
  • 支持系统：Debian[8,9,10]，Ubuntu[16.04,18.04,20.04]
  • 系统会自动编译python的2.7的安装包后再进行部署，编译过程中会有报错提示但不用理会，只要脚本还在跑就说明一切正常
国际
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirtmgr.sh -o install_webvirtmgr.sh \\
+import{_ as s,v as a,b as t,R as l}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"incomplete/webvirtmgr.md","filePath":"incomplete/webvirtmgr.md","lastUpdated":1747730955000}'),n={name:"incomplete/webvirtmgr.md"},e=l(`
WebVirtMgr 安装指南 ​
hits
仓库地址: https://github.com/oneclickvirt/webvirtcloud
原项目对应仓库：https://github.com/retspen/webvirtmgr
控制节点和计算节点同时安装 ​
  • 支持系统：Debian[8,9,10]，Ubuntu[16.04,18.04,20.04]
  • 系统会自动编译python的2.7的安装包后再进行部署，编译过程中会有报错提示但不用理会，只要脚本还在跑就说明一切正常
国际
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirtmgr.sh -o install_webvirtmgr.sh \\
 && chmod +x install_webvirtmgr.sh \\
 && bash install_webvirtmgr.sh
国内
bash
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirtmgr.sh -o install_webvirtmgr.sh \\
 && chmod +x install_webvirtmgr.sh \\
diff --git a/assets/index.md.6d09fb06.js b/assets/index.md.ee7c4885.js
similarity index 96%
rename from assets/index.md.6d09fb06.js
rename to assets/index.md.ee7c4885.js
index 57b0d86164..dafca87fe1 100644
--- a/assets/index.md.6d09fb06.js
+++ b/assets/index.md.ee7c4885.js
@@ -1 +1 @@
-import{_ as t,v as e,b as i}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"库苏恩","titleTemplate":"一键虚拟化项目","description":"","frontmatter":{"layout":"home","title":"库苏恩","titleTemplate":"一键虚拟化项目","tagline":"开源、易于使用的服务器虚拟化项目","hero":{"name":"一键虚拟化项目","text":"开源、易于使用的服务器虚拟化项目","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"开始使用 →","link":"/guide/dashboard"}]},"features":[{"title":"一键使用","details":"支持一键命令安装使用，轻松在X86_64和ARM架构的服务器上创建虚拟机或容器"},{"title":"基于主流系统开发","details":"基于 Debian、Ubuntu、Centos 等系统的长期维护版本开发，无论是什么系统总有一个方法能让你虚拟化出容器或虚拟机"},{"title":"端口转发和IP分配自动化","details":"自带内外网端口转发和IP地址自动分配(含IPV6、IPV4)，支持TCP/UDP、VNC/RDP等协议，无需人工管理"},{"title":"批量虚拟化","details":"支持使用 QEMU、KVM、LXC、Docker 虚拟化批量开设容器或虚拟机"},{"title":"多系统多环境支持","details":"开设出的容器或虚拟机已支持主流系统，涵盖 Linux、Windows、MacOS、Android 系统，也支持纯粹的浏览器环境或桌面环境"},{"title":"自限制滥用","details":"部分虚拟化开设的容器或虚拟机支持设置屏蔽和装载限制，避免被用于滥用"}]},"headers":[],"relativePath":"index.md","filePath":"index.md","lastUpdated":1747726389000}'),a={name:"index.md"};function s(n,d,l,r,o,p){return e(),i("div")}const h=t(a,[["render",s]]);export{m as __pageData,h as default};
+import{_ as t,v as e,b as i}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"库苏恩","titleTemplate":"一键虚拟化项目","description":"","frontmatter":{"layout":"home","title":"库苏恩","titleTemplate":"一键虚拟化项目","tagline":"开源、易于使用的服务器虚拟化项目","hero":{"name":"一键虚拟化项目","text":"开源、易于使用的服务器虚拟化项目","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"开始使用 →","link":"/guide/dashboard"}]},"features":[{"title":"一键使用","details":"支持一键命令安装使用，轻松在X86_64和ARM架构的服务器上创建虚拟机或容器"},{"title":"基于主流系统开发","details":"基于 Debian、Ubuntu、Centos 等系统的长期维护版本开发，无论是什么系统总有一个方法能让你虚拟化出容器或虚拟机"},{"title":"端口转发和IP分配自动化","details":"自带内外网端口转发和IP地址自动分配(含IPV6、IPV4)，支持TCP/UDP、VNC/RDP等协议，无需人工管理"},{"title":"批量虚拟化","details":"支持使用 QEMU、KVM、LXC、Docker 虚拟化批量开设容器或虚拟机"},{"title":"多系统多环境支持","details":"开设出的容器或虚拟机已支持主流系统，涵盖 Linux、Windows、MacOS、Android 系统，也支持纯粹的浏览器环境或桌面环境"},{"title":"自限制滥用","details":"部分虚拟化开设的容器或虚拟机支持设置屏蔽和装载限制，避免被用于滥用"}]},"headers":[],"relativePath":"index.md","filePath":"index.md","lastUpdated":1747730955000}'),a={name:"index.md"};function s(n,d,l,r,o,p){return e(),i("div")}const h=t(a,[["render",s]]);export{m as __pageData,h as default};
diff --git a/assets/index.md.6d09fb06.lean.js b/assets/index.md.ee7c4885.lean.js
similarity index 96%
rename from assets/index.md.6d09fb06.lean.js
rename to assets/index.md.ee7c4885.lean.js
index 57b0d86164..dafca87fe1 100644
--- a/assets/index.md.6d09fb06.lean.js
+++ b/assets/index.md.ee7c4885.lean.js
@@ -1 +1 @@
-import{_ as t,v as e,b as i}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"库苏恩","titleTemplate":"一键虚拟化项目","description":"","frontmatter":{"layout":"home","title":"库苏恩","titleTemplate":"一键虚拟化项目","tagline":"开源、易于使用的服务器虚拟化项目","hero":{"name":"一键虚拟化项目","text":"开源、易于使用的服务器虚拟化项目","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"开始使用 →","link":"/guide/dashboard"}]},"features":[{"title":"一键使用","details":"支持一键命令安装使用，轻松在X86_64和ARM架构的服务器上创建虚拟机或容器"},{"title":"基于主流系统开发","details":"基于 Debian、Ubuntu、Centos 等系统的长期维护版本开发，无论是什么系统总有一个方法能让你虚拟化出容器或虚拟机"},{"title":"端口转发和IP分配自动化","details":"自带内外网端口转发和IP地址自动分配(含IPV6、IPV4)，支持TCP/UDP、VNC/RDP等协议，无需人工管理"},{"title":"批量虚拟化","details":"支持使用 QEMU、KVM、LXC、Docker 虚拟化批量开设容器或虚拟机"},{"title":"多系统多环境支持","details":"开设出的容器或虚拟机已支持主流系统，涵盖 Linux、Windows、MacOS、Android 系统，也支持纯粹的浏览器环境或桌面环境"},{"title":"自限制滥用","details":"部分虚拟化开设的容器或虚拟机支持设置屏蔽和装载限制，避免被用于滥用"}]},"headers":[],"relativePath":"index.md","filePath":"index.md","lastUpdated":1747726389000}'),a={name:"index.md"};function s(n,d,l,r,o,p){return e(),i("div")}const h=t(a,[["render",s]]);export{m as __pageData,h as default};
+import{_ as t,v as e,b as i}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"库苏恩","titleTemplate":"一键虚拟化项目","description":"","frontmatter":{"layout":"home","title":"库苏恩","titleTemplate":"一键虚拟化项目","tagline":"开源、易于使用的服务器虚拟化项目","hero":{"name":"一键虚拟化项目","text":"开源、易于使用的服务器虚拟化项目","image":"https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritlhls/pages/main/logo.png","actions":[{"theme":"brand","text":"开始使用 →","link":"/guide/dashboard"}]},"features":[{"title":"一键使用","details":"支持一键命令安装使用，轻松在X86_64和ARM架构的服务器上创建虚拟机或容器"},{"title":"基于主流系统开发","details":"基于 Debian、Ubuntu、Centos 等系统的长期维护版本开发，无论是什么系统总有一个方法能让你虚拟化出容器或虚拟机"},{"title":"端口转发和IP分配自动化","details":"自带内外网端口转发和IP地址自动分配(含IPV6、IPV4)，支持TCP/UDP、VNC/RDP等协议，无需人工管理"},{"title":"批量虚拟化","details":"支持使用 QEMU、KVM、LXC、Docker 虚拟化批量开设容器或虚拟机"},{"title":"多系统多环境支持","details":"开设出的容器或虚拟机已支持主流系统，涵盖 Linux、Windows、MacOS、Android 系统，也支持纯粹的浏览器环境或桌面环境"},{"title":"自限制滥用","details":"部分虚拟化开设的容器或虚拟机支持设置屏蔽和装载限制，避免被用于滥用"}]},"headers":[],"relativePath":"index.md","filePath":"index.md","lastUpdated":1747730955000}'),a={name:"index.md"};function s(n,d,l,r,o,p){return e(),i("div")}const h=t(a,[["render",s]]);export{m as __pageData,h as default};
diff --git a/case/case1.html b/case/case1.html
index 81188c7a8d..314d62d9c3 100644
--- a/case/case1.html
+++ b/case/case1.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -76,8 +76,8 @@
 export PATH=$PATH:/usr/local/go/bin
  1. 编译
bash
go build -o goecs
  1. 运行测试
bash
./goecs -menu=false -l zh
支持的编译参数：
  • GOOS：支持 linux、windows、darwin、freebsd、openbsd
  • GOARCH：支持 amd64、arm、arm64、386、mips、mipsle、s390x、riscv64
跨平台编译示例：
bash
# 编译 Windows 版本
 GOOS=windows GOARCH=amd64 go build -o goecs.exe
 # 编译 MacOS 版本
-GOOS=darwin GOARCH=amd64 go build -o goecs_darwin
QA ​
Q: 为什么默认使用sysbench而不是geekbench ​
A: 比较二者特点 ​
比较项sysbenchgeekbench
适用范围轻量级，几乎可在任何服务器上运行重量级，小型机器无法运行
测试要求无需网络，无特殊硬件需求需联网，IPV4环境，至少1G内存
开源情况基于LUA，开源，可自行编译各架构版本官方二进制闭源代码，不支持自行编译
测试稳定性核心测试组件10年以上未变每个大版本更新测试项，分数不同版本间难以对比(每个版本对标当前最好的CPU)
测试内容仅测试计算性能覆盖多种性能测试，分数加权计算，但部分测试实际不常用
适用场景适合快速测试，仅测试计算性能适合综合全面的测试
且goecs测试使用何种CPU测试方式可使用参数指定，默认只是为了更多用户快速测试的需求
Q: 为什么使用Golang而不是Rust重构 ​
A: 因为网络相关的项目目前以Golang语言为趋势，大多组件有开源生态维护，Rust很多得自己手搓，我懒得搞我没那个技术力 ​
Q: 为什么不继续开发Shell版本而是选择重构 ​
A: 因为太多千奇百怪的环境问题了，还是提前编译好测试的二进制文件比较容易解决环境问题(泛化性更好) ​
Q: 每个测试项目的说明有吗？ ​
A: 每个测试项目有对应的维护仓库，自行点击查看仓库说明 ​
Q: 测试进行到一半如何手动终止？ ​
A: 按ctrl键和c键终止程序，终止后依然会在当前目录下生成goecs.txt文件和分享链接，里面是已经测试到的信息。 ​
Q: 非Root环境如何进行测试？ ​
A: 手动执行安装命令，实在装不上也没问题，直接在release中下载对应架构的压缩包解压后执行即可，只要你能执行的了文件。或者你能使用docker的话用docker执行。 ​
致谢 ​
感谢 he.net bgp.tools ipinfo.io ip.sb cheervision.co scamalytics.com abuseipdb.com virustotal.com ip2location.com ip-api.com ipregistry.co ipdata.co ipgeolocation.io ipwhois.io ipapi.com ipapi.is ipqualityscore.com bigdatacloud.com 等网站提供的API进行检测，感谢互联网各网站提供的查询资源
感谢
h501
提供的免费托管支持本开源项目的共享测试结果存储
同时感谢以下平台提供编辑和测试支持
golandibm

-    
+GOOS=darwin GOARCH=amd64 go build -o goecs_darwin
QA ​
Q: 为什么默认使用sysbench而不是geekbench ​
A: 比较二者特点 ​
比较项sysbenchgeekbench
适用范围轻量级，几乎可在任何服务器上运行重量级，小型机器无法运行
测试要求无需网络，无特殊硬件需求需联网，IPV4环境，至少1G内存
开源情况基于LUA，开源，可自行编译各架构版本官方二进制闭源代码，不支持自行编译
测试稳定性核心测试组件10年以上未变每个大版本更新测试项，分数不同版本间难以对比(每个版本对标当前最好的CPU)
测试内容仅测试计算性能覆盖多种性能测试，分数加权计算，但部分测试实际不常用
适用场景适合快速测试，仅测试计算性能适合综合全面的测试
且goecs测试使用何种CPU测试方式可使用参数指定，默认只是为了更多用户快速测试的需求
Q: 为什么使用Golang而不是Rust重构 ​
A: 因为网络相关的项目目前以Golang语言为趋势，大多组件有开源生态维护，Rust很多得自己手搓，我懒得搞我没那个技术力 ​
Q: 为什么不继续开发Shell版本而是选择重构 ​
A: 因为太多千奇百怪的环境问题了，还是提前编译好测试的二进制文件比较容易解决环境问题(泛化性更好) ​
Q: 每个测试项目的说明有吗？ ​
A: 每个测试项目有对应的维护仓库，自行点击查看仓库说明 ​
Q: 测试进行到一半如何手动终止？ ​
A: 按ctrl键和c键终止程序，终止后依然会在当前目录下生成goecs.txt文件和分享链接，里面是已经测试到的信息。 ​
Q: 非Root环境如何进行测试？ ​
A: 手动执行安装命令，实在装不上也没问题，直接在release中下载对应架构的压缩包解压后执行即可，只要你能执行的了文件。或者你能使用docker的话用docker执行。 ​
致谢 ​
感谢 he.net bgp.tools ipinfo.io ip.sb cheervision.co scamalytics.com abuseipdb.com virustotal.com ip2location.com ip-api.com ipregistry.co ipdata.co ipgeolocation.io ipwhois.io ipapi.com ipapi.is ipqualityscore.com bigdatacloud.com 等网站提供的API进行检测，感谢互联网各网站提供的查询资源
感谢
h501
提供的免费托管支持本开源项目的共享测试结果存储
同时感谢以下平台提供编辑和测试支持
golandibm

+    
     
   
 
\ No newline at end of file
diff --git a/case/case2.html b/case/case2.html
index f2d2722eb2..7fe6701609 100644
--- a/case/case2.html
+++ b/case/case2.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -54,8 +54,8 @@
 cat .config/code-server/config.yaml
卸载需要
sudo systemctl stop code-server@root
 sudo systemctl disable code-server@root
 rm -rf ~/.cache/coder
-sudo apt remove coder -y

-    
+sudo apt remove coder -y

+    
     
   
 
\ No newline at end of file
diff --git a/case/case3.html b/case/case3.html
index 8832f8ae14..c2e409afda 100644
--- a/case/case3.html
+++ b/case/case3.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
仓库 ​
https://github.com/spiritLHLS/ecsspeed
Hits
ecsspeed ​
自动更新测速服务器节点列表的网络基准测试脚本
Network benchmarking script that automatically updates the list of speed measurement server nodes
说明 ​
所有组件以及数据均来源于平台或已有的开源项目，无非开源部分，放心食用
对应 speedtest.net 的自动更新测速服务器ID的测速脚本 ​
日常推荐使用
bash <(wget -qO- bash.spiritlhl.net/ecs-net)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-net.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-net.sh)
支持测速的架构：i386, x86_64, amd64, arm64, s390x, riscv64, ppc64le, ppc64
涵盖中国三大运营商、香港、台湾的测速节点，默认的三网测速每个运营商选择本机ping值最低的两个节点测速，详情三网测速才是全测，节点列表大概每7天自动更新一次。
支持国内服务器测试(有判断是否为国内机器)，但由于国内服务器带宽过小，会很慢，详见初次运行的显示
当官方CLI安装失败(如罕见的架构或者官方网站访问失败时)自动使用 speedtest-go 作为替代品测速
对应 speedtest.cn 的自动更新测速服务器ID的测速脚本 ​
单线程测速
bash <(wget -qO- bash.spiritlhl.net/ecs-cn)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-cn.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-cn.sh)
支持测速的架构：i386, x86_64, amd64, arm64, s390x, riscv64, ppc64le, ppc64
涵盖中国三大运营商、香港、台湾的测速节点，默认的三网测速每个运营商选择本机ping值最低的两个节点测速，详情三网测速才是全测，节点列表每天自动更新一次。
支持国内服务器测试(有判断是否为国内机器)，但由于国内服务器带宽过小，会很慢，详见初次运行的显示
自动更新测试服务器列表的三网延迟测试脚本 ​
平均耗时10~15秒
bash <(wget -qO- bash.spiritlhl.net/ecs-ping)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-ping.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-ping.sh)
效果图
图片
功能 ​
  • [x] 自动抓取 speedtest.cn 节点信息结合已有信息去重并更新列表数据
  • [x] 自动抓取 speedtest.net 节点信息结合已有信息去重并更新列表数据
  • [x] 对应 speedtest.net 的自动更新测速服务器列表的测速脚本
  • [x] 对应 speedtest.cn 的自动更新测速服务器列表的测速脚本
  • [x] 自动更新测试服务器列表的三网Ping值测试脚本
.cn数据 ​
仓库：https://github.com/spiritLHLS/speedtest.cn-CN-ID
.net数据 ​
仓库：https://github.com/spiritLHLS/speedtest.net-CN-ID

-    
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
仓库 ​
https://github.com/spiritLHLS/ecsspeed
Hits
ecsspeed ​
自动更新测速服务器节点列表的网络基准测试脚本
Network benchmarking script that automatically updates the list of speed measurement server nodes
说明 ​
所有组件以及数据均来源于平台或已有的开源项目，无非开源部分，放心食用
对应 speedtest.net 的自动更新测速服务器ID的测速脚本 ​
日常推荐使用
bash <(wget -qO- bash.spiritlhl.net/ecs-net)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-net.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-net.sh)
支持测速的架构：i386, x86_64, amd64, arm64, s390x, riscv64, ppc64le, ppc64
涵盖中国三大运营商、香港、台湾的测速节点，默认的三网测速每个运营商选择本机ping值最低的两个节点测速，详情三网测速才是全测，节点列表大概每7天自动更新一次。
支持国内服务器测试(有判断是否为国内机器)，但由于国内服务器带宽过小，会很慢，详见初次运行的显示
当官方CLI安装失败(如罕见的架构或者官方网站访问失败时)自动使用 speedtest-go 作为替代品测速
对应 speedtest.cn 的自动更新测速服务器ID的测速脚本 ​
单线程测速
bash <(wget -qO- bash.spiritlhl.net/ecs-cn)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-cn.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-cn.sh)
支持测速的架构：i386, x86_64, amd64, arm64, s390x, riscv64, ppc64le, ppc64
涵盖中国三大运营商、香港、台湾的测速节点，默认的三网测速每个运营商选择本机ping值最低的两个节点测速，详情三网测速才是全测，节点列表每天自动更新一次。
支持国内服务器测试(有判断是否为国内机器)，但由于国内服务器带宽过小，会很慢，详见初次运行的显示
自动更新测试服务器列表的三网延迟测试脚本 ​
平均耗时10~15秒
bash <(wget -qO- bash.spiritlhl.net/ecs-ping)
或
bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecsspeed/raw/main/script/ecsspeed-ping.sh)
或国内用
bash <(wget -qO- --no-check-certificate https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/ecsspeed/main/script/ecsspeed-ping.sh)
效果图
图片
功能 ​
  • [x] 自动抓取 speedtest.cn 节点信息结合已有信息去重并更新列表数据
  • [x] 自动抓取 speedtest.net 节点信息结合已有信息去重并更新列表数据
  • [x] 对应 speedtest.net 的自动更新测速服务器列表的测速脚本
  • [x] 对应 speedtest.cn 的自动更新测速服务器列表的测速脚本
  • [x] 自动更新测试服务器列表的三网Ping值测试脚本
.cn数据 ​
仓库：https://github.com/spiritLHLS/speedtest.cn-CN-ID
.net数据 ​
仓库：https://github.com/spiritLHLS/speedtest.net-CN-ID

+    
     
   
 
\ No newline at end of file
diff --git a/case/case4.html b/case/case4.html
index 245993ef2e..eb66b7ecb9 100644
--- a/case/case4.html
+++ b/case/case4.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
仓库 ​
https://github.com/oneclickvirt/backtrace
Hits
backtrace ​
三网回程路由线路测试
基于 https://github.com/zhanghanyun/backtrace 的重构和优化，与原版存在很大不同
路由的线路判断最终还是得人工判断的才准确，本项目测试结果仅供参考
功能 ​
  • [x] 检测回程显示IPV4地址时的线路，不显示IP地址时显示ASN检测不到，原版backtrace也支持
  • [x] 支持对4837、9929和163线路的判断，原版backtrace也支持
  • [x] 支持对CN2GT和CN2GIA线路的判断，原版backtrace不支持
  • [x] 支持对CMIN2和CMI线路的判断，原版backtrace不支持
  • [x] 支持对整个回程路由进行线路分析，与原版backtrace仅进行一次判断不同
  • [x] 修复原版backtrace对IPV4地址信息获取时json解析失败依然打印信息的问题
  • [x] 增加对全平台的编译支持，原版backtrace仅支持linux平台的amd64和arm64架构
使用 ​
shell
curl https://raw.githubusercontent.com/oneclickvirt/backtrace/main/backtrace_install.sh -sSf | sh
更多架构请查看 https://github.com/oneclickvirt/backtrace/releases/tag/output
概览图 ​
图片
图片
图片

-    
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
仓库 ​
https://github.com/oneclickvirt/backtrace
Hits
backtrace ​
三网回程路由线路测试
基于 https://github.com/zhanghanyun/backtrace 的重构和优化，与原版存在很大不同
路由的线路判断最终还是得人工判断的才准确，本项目测试结果仅供参考
功能 ​
  • [x] 检测回程显示IPV4地址时的线路，不显示IP地址时显示ASN检测不到，原版backtrace也支持
  • [x] 支持对4837、9929和163线路的判断，原版backtrace也支持
  • [x] 支持对CN2GT和CN2GIA线路的判断，原版backtrace不支持
  • [x] 支持对CMIN2和CMI线路的判断，原版backtrace不支持
  • [x] 支持对整个回程路由进行线路分析，与原版backtrace仅进行一次判断不同
  • [x] 修复原版backtrace对IPV4地址信息获取时json解析失败依然打印信息的问题
  • [x] 增加对全平台的编译支持，原版backtrace仅支持linux平台的amd64和arm64架构
使用 ​
shell
curl https://raw.githubusercontent.com/oneclickvirt/backtrace/main/backtrace_install.sh -sSf | sh
更多架构请查看 https://github.com/oneclickvirt/backtrace/releases/tag/output
概览图 ​
图片
图片
图片

+    
     
   
 
\ No newline at end of file
diff --git a/case/case5.html b/case/case5.html
index 0bbf5878a6..451bf5c4b4 100644
--- a/case/case5.html
+++ b/case/case5.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
仓库 ​
https://github.com/spiritLHLS/Oracle-server-keep-alive-script
Hits
Oracle-server-keep-alive-script ​
实际不止可以在甲骨文服务器上使用，也可以使用在任意ARM或X86_64架构的系统，用作资源占用
甲骨文服务器保活脚本 ​
适配系统：已在Ubuntu 20+，Debian 10+, Centos 7+, Oracle linux 8+，AlmaLinux 8.5+
上述系统验证无问题，别的主流系统应该也没有问题
可选占用：CPU，内存，带宽
安装完毕后如果有问题请卸载脚本反馈问题(重复卸载也没问题)
所有资源(除了CPU)可选默认配置则动态占用，实时调整，避免服务器有别的任何资源已经超过限额了仍然再占用资源
为避免GitHub的CDN抽风加载不了新内容，所有新更新已使用Gitlab仓库
由于speedtest-go的release依赖于GitHub，所以请检查 www.githubstatus.com ,有问题时无法安装带宽占用
基础开发完毕，测试中，有问题请在issues中反馈 ​
选项1安装，选项2卸载，选项3更新安装引导脚本，选项4退出脚本
安装过程中无脑回车则全部可选的占用都占用，不需要什么占用输入n再回车
如果选择带宽占用，会询问使用speedtest-go占用还是使用wget占用，按照提示进行选择即可
有询问是否需要带宽占用的参数自定义，这时候默认选项就是n，回车就使用默认配置，输入y再回车则需要按照提示自定义参数
curl -L https://gitlab.com/spiritysdx/Oracle-server-keep-alive-script/-/raw/main/oalive.sh -o oalive.sh && chmod +x oalive.sh && bash oalive.sh
或
bash oalive.sh
或
bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/Oracle-server-keep-alive-script/-/raw/main/oalive.sh)
说明 ​
  • 提供两种CPU占用模式：DD模拟占用和科学计算模式，用户可以自由选择，占用范围设置在15%至25%之间，更推荐DD模拟占用
  • DD模拟占用在守护进程中设置了CPU占用的最高限制
  • 默认情况下，CPU占用设置为25%最高值，计算方法是核数乘以12%，如果计算结果低于25%，则设置为该值；如果计算结果高于25%，则按照计算结果的比例进行设置。
  • 内存占用设置为占用总内存的20%，占用时间为300秒，休息时间为300秒。
  • 每300秒检测一次内存占用情况，并根据需要动态调整占用大小。如果内存占用已经大于20%，则不增加占用。
  • 在占用过程中，使用守护进程和开机自启服务，以确保占用任务持续且有效。
  • 默认选项的带宽占用每45分钟下载一次大小在1G至10G之间的文件，只进行下载而不保存。在下载过程中会占用硬盘空间，但在下载完成后会自动释放。
  • 默认选项的带宽占用动态调整实际下载的带宽/速率，限制每次下载的最长时长为6分钟。在每次下载之前，会测试最大可用带宽，并根据实时结果将下载速率设置为30%的带宽。
  • 带宽占用测试使用了speedtest-cli和speedtest-go两种工具，以防其中之一不可用时使用第二种工具，用户可以自定义设置带宽占用，此时详见设置提示。
  • 提供一键卸载所有占用服务的选项，卸载将删除所有脚本、服务、任务、守护进程和开机自启设置。
  • 提供一键检查更新的功能，更新范围仅限于脚本更新。请在更新后重新设置占用服务
  • 对所有进程执行增加唯一性检测，避免重复运行，使用PID文件进行判断。
如若不希望一键的，希望自定义设置时间的，请查看README_CRON.md自行设置定时任务

-    
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
仓库 ​
https://github.com/spiritLHLS/Oracle-server-keep-alive-script
Hits
Oracle-server-keep-alive-script ​
实际不止可以在甲骨文服务器上使用，也可以使用在任意ARM或X86_64架构的系统，用作资源占用
甲骨文服务器保活脚本 ​
适配系统：已在Ubuntu 20+，Debian 10+, Centos 7+, Oracle linux 8+，AlmaLinux 8.5+
上述系统验证无问题，别的主流系统应该也没有问题
可选占用：CPU，内存，带宽
安装完毕后如果有问题请卸载脚本反馈问题(重复卸载也没问题)
所有资源(除了CPU)可选默认配置则动态占用，实时调整，避免服务器有别的任何资源已经超过限额了仍然再占用资源
为避免GitHub的CDN抽风加载不了新内容，所有新更新已使用Gitlab仓库
由于speedtest-go的release依赖于GitHub，所以请检查 www.githubstatus.com ,有问题时无法安装带宽占用
基础开发完毕，测试中，有问题请在issues中反馈 ​
选项1安装，选项2卸载，选项3更新安装引导脚本，选项4退出脚本
安装过程中无脑回车则全部可选的占用都占用，不需要什么占用输入n再回车
如果选择带宽占用，会询问使用speedtest-go占用还是使用wget占用，按照提示进行选择即可
有询问是否需要带宽占用的参数自定义，这时候默认选项就是n，回车就使用默认配置，输入y再回车则需要按照提示自定义参数
curl -L https://gitlab.com/spiritysdx/Oracle-server-keep-alive-script/-/raw/main/oalive.sh -o oalive.sh && chmod +x oalive.sh && bash oalive.sh
或
bash oalive.sh
或
bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/Oracle-server-keep-alive-script/-/raw/main/oalive.sh)
说明 ​
  • 提供两种CPU占用模式：DD模拟占用和科学计算模式，用户可以自由选择，占用范围设置在15%至25%之间，更推荐DD模拟占用
  • DD模拟占用在守护进程中设置了CPU占用的最高限制
  • 默认情况下，CPU占用设置为25%最高值，计算方法是核数乘以12%，如果计算结果低于25%，则设置为该值；如果计算结果高于25%，则按照计算结果的比例进行设置。
  • 内存占用设置为占用总内存的20%，占用时间为300秒，休息时间为300秒。
  • 每300秒检测一次内存占用情况，并根据需要动态调整占用大小。如果内存占用已经大于20%，则不增加占用。
  • 在占用过程中，使用守护进程和开机自启服务，以确保占用任务持续且有效。
  • 默认选项的带宽占用每45分钟下载一次大小在1G至10G之间的文件，只进行下载而不保存。在下载过程中会占用硬盘空间，但在下载完成后会自动释放。
  • 默认选项的带宽占用动态调整实际下载的带宽/速率，限制每次下载的最长时长为6分钟。在每次下载之前，会测试最大可用带宽，并根据实时结果将下载速率设置为30%的带宽。
  • 带宽占用测试使用了speedtest-cli和speedtest-go两种工具，以防其中之一不可用时使用第二种工具，用户可以自定义设置带宽占用，此时详见设置提示。
  • 提供一键卸载所有占用服务的选项，卸载将删除所有脚本、服务、任务、守护进程和开机自启设置。
  • 提供一键检查更新的功能，更新范围仅限于脚本更新。请在更新后重新设置占用服务
  • 对所有进程执行增加唯一性检测，避免重复运行，使用PID文件进行判断。
如若不希望一键的，希望自定义设置时间的，请查看README_CRON.md自行设置定时任务

+    
     
   
 
\ No newline at end of file
diff --git a/case/case6.html b/case/case6.html
index cf17f8eb47..4311e9b6b7 100644
--- a/case/case6.html
+++ b/case/case6.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
仓库 ​
https://github.com/spiritLHLS/addswap
addswap ​
为openvz、kvm虚拟化的linux服务器增加swap分区(虚拟内存)
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
已增加openvz架构重启swap自动添加的
openvz这个添加=掩耳盗铃，实际受到虚拟化限制应该是无法添加的，只能由虚拟化的宿主机控制，同理LXC虚拟化的也只能由宿主机控制，都无法自主添加虚拟内存SWAP
因此，该项目不再更新，除非另有需求
单位换算：输入 1024 产生 1G SWAP内存
致谢 ​
kvm分区原版脚本源自 https://www.moerats.com/
bash
curl -L https://www.moerats.com/usr/shell/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
openVZ分区原版脚本源自
http://linux-problem-solver.blogspot.com/2013/08/create-fake-swap-in-openvz-vps-if-you-get-swapon-failed-operation-not-permitted-error.html
感谢 @fscarmen 提供优化建议

-    
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
仓库 ​
https://github.com/spiritLHLS/addswap
addswap ​
为openvz、kvm虚拟化的linux服务器增加swap分区(虚拟内存)
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
已增加openvz架构重启swap自动添加的
openvz这个添加=掩耳盗铃，实际受到虚拟化限制应该是无法添加的，只能由虚拟化的宿主机控制，同理LXC虚拟化的也只能由宿主机控制，都无法自主添加虚拟内存SWAP
因此，该项目不再更新，除非另有需求
单位换算：输入 1024 产生 1G SWAP内存
致谢 ​
kvm分区原版脚本源自 https://www.moerats.com/
bash
curl -L https://www.moerats.com/usr/shell/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
openVZ分区原版脚本源自
http://linux-problem-solver.blogspot.com/2013/08/create-fake-swap-in-openvz-vps-if-you-get-swapon-failed-operation-not-permitted-error.html
感谢 @fscarmen 提供优化建议

+    
     
   
 
\ No newline at end of file
diff --git a/case/case7.html b/case/case7.html
index acaa10b813..1ad3eb70d7 100644
--- a/case/case7.html
+++ b/case/case7.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
仓库 ​
https://github.com/spiritLHLS/addzram
addzram ​
为linux服务器启用zram(压缩内存)
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addzram/main/addzram.sh -o addzram.sh && chmod +x addzram.sh && bash addzram.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addzram/main/addzram.sh -o addzram.sh && chmod +x addzram.sh && bash addzram.sh
类同前面的addswap项目
同样是给机器优化内存占用的东西，只不过zram是压缩内存占用，swap是附加虚拟内存增加内存空间，二者都会占用CPU资源，zram在CPU性能冗余的机器上使用更优
(理论上zram会比swap的性能占用低，但未实际测试过)
单位换算：输入 1024 产生 1G 的 zram 设备压缩内存，zram 设备大小不能大于实际内存大小
致谢 ​
感谢 @Ella-Alinda 提供优化建议

-    
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
仓库 ​
https://github.com/spiritLHLS/addzram
addzram ​
为linux服务器启用zram(压缩内存)
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addzram/main/addzram.sh -o addzram.sh && chmod +x addzram.sh && bash addzram.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addzram/main/addzram.sh -o addzram.sh && chmod +x addzram.sh && bash addzram.sh
类同前面的addswap项目
同样是给机器优化内存占用的东西，只不过zram是压缩内存占用，swap是附加虚拟内存增加内存空间，二者都会占用CPU资源，zram在CPU性能冗余的机器上使用更优
(理论上zram会比swap的性能占用低，但未实际测试过)
单位换算：输入 1024 产生 1G 的 zram 设备压缩内存，zram 设备大小不能大于实际内存大小
致谢 ​
感谢 @Ella-Alinda 提供优化建议

+    
     
   
 
\ No newline at end of file
diff --git a/case/index.html b/case/index.html
index 621f3a77e3..e32badad7c 100644
--- a/case/index.html
+++ b/case/index.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -20,7 +20,7 @@
   
   
     
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
其他实用项目
与Linux相关的其他实用项目
查看项目 →
实用性
仁者见仁智者见智。

-    
+    
     
   
 
\ No newline at end of file
diff --git a/developer/index.html b/developer/index.html
index 15c8bb8756..8a80fdf935 100644
--- a/developer/index.html
+++ b/developer/index.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -20,7 +20,7 @@
   
   
     
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
开发手册
开发手册
开始使用 →

-    
+    
     
   
 
\ No newline at end of file
diff --git a/developer/l10n.html b/developer/l10n.html
index 61405c6da4..1516bebcf7 100644
--- a/developer/l10n.html
+++ b/developer/l10n.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
你可以在开发新功能时遵循以下步骤来支持本地化
介绍 ​
  1. 你可以直接使用 /resource/l10n/zh-CN.toml 中已有的文本配置来替换新功能中的文本
  2. 如果新功能中有新增文本，请参考 zh-CN.toml 的配置文本，将新文本拉取到 zh-CN.toml 等其他语言的配置文件中，并添加翻译
新本地化文本的添加 ​
  1. 在 /resource/l10n/ 中添加新的语言文本配置
  2. 在新的语言文本配置中拉取其他语言已有的文本配置
  3. 为新的语言文本配置添加翻译

-    
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
你可以在开发新功能时遵循以下步骤来支持本地化
介绍 ​
  1. 你可以直接使用 /resource/l10n/zh-CN.toml 中已有的文本配置来替换新功能中的文本
  2. 如果新功能中有新增文本，请参考 zh-CN.toml 的配置文本，将新文本拉取到 zh-CN.toml 等其他语言的配置文件中，并添加翻译
新本地化文本的添加 ​
  1. 在 /resource/l10n/ 中添加新的语言文本配置
  2. 在新的语言文本配置中拉取其他语言已有的文本配置
  3. 为新的语言文本配置添加翻译

+    
     
   
 
\ No newline at end of file
diff --git a/en/developer/index.html b/en/developer/index.html
index ae5bac415b..8853b6ebb7 100644
--- a/en/developer/index.html
+++ b/en/developer/index.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -20,7 +20,7 @@
   
   
     
One Click Virtualization
English
简体中文
English
简体中文
Appearance
Development Manual
Welcome to the oneclickvirt Development Manual.
Start Now →

-    
+    
     
   
 
\ No newline at end of file
diff --git a/en/developer/l10n.html b/en/developer/l10n.html
index a08a446794..425d33e1d1 100644
--- a/en/developer/l10n.html
+++ b/en/developer/l10n.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
You can follow these steps to support localization when developing new features
Introduction ​
  1. You can directly use the text configuration already available in /resource/l10n/en-US.toml to replace the text in the new feature.
  2. If there is new text in the new feature, please refer to the configuration text in en-US.toml, pull the new text into the configuration files of other languages such as en-US.toml, and add translations.
Adding a new localized text file ​
  1. Add a new language text configuration in /resource/l10n/.
  2. Pull existing text configurations from other languages in the new language text configuration.
  3. Add translations for the new language text configuration.

-    
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
You can follow these steps to support localization when developing new features
Introduction ​
  1. You can directly use the text configuration already available in /resource/l10n/en-US.toml to replace the text in the new feature.
  2. If there is new text in the new feature, please refer to the configuration text in en-US.toml, pull the new text into the configuration files of other languages such as en-US.toml, and add translations.
Adding a new localized text file ​
  1. Add a new language text configuration in /resource/l10n/.
  2. Pull existing text configurations from other languages in the new language text configuration.
  3. Add translations for the new language text configuration.

+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/block/block_docker.html b/en/guide/block/block_docker.html
index 1716c50d96..b1fb6bd5f2 100644
--- a/en/guide/block/block_docker.html
+++ b/en/guide/block/block_docker.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
-    
+    
+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/block/block_incus.html b/en/guide/block/block_incus.html
index e17f19b9c2..c6c9c093d8 100644
--- a/en/guide/block/block_incus.html
+++ b/en/guide/block/block_incus.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Blocking Abusive Behavior via Shell Scripts ​
Blocking Ingress/Egress Traffic on Easily Abused Ports and Filtering Out Port Scanning and Exploitation Toolkits ​
  • (Optional, this script is solely for preventing container abuse and is not mandatory to install.)
  • Precautionary Measures
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
Use the 'screen' command to configure monitoring and blocking of certain processes' commands: terminate containers immediately upon the appearance of specific processes. ​
  • To stop monitoring, you can use the 'screen' command to stop the window named 'lxc_monitor' and delete it.
  • (Optional, this script is only for preventing misuse of containers; it's fine not to install it.)
  • Shutdown afterwards.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh

-    
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Blocking Abusive Behavior via Shell Scripts ​
Blocking Ingress/Egress Traffic on Easily Abused Ports and Filtering Out Port Scanning and Exploitation Toolkits ​
  • (Optional, this script is solely for preventing container abuse and is not mandatory to install.)
  • Precautionary Measures
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
Use the 'screen' command to configure monitoring and blocking of certain processes' commands: terminate containers immediately upon the appearance of specific processes. ​
  • To stop monitoring, you can use the 'screen' command to stop the window named 'lxc_monitor' and delete it.
  • (Optional, this script is only for preventing misuse of containers; it's fine not to install it.)
  • Shutdown afterwards.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh

+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/block/block_iptables.html b/en/guide/block/block_iptables.html
index 2250bec984..5d78dd9add 100644
--- a/en/guide/block/block_iptables.html
+++ b/en/guide/block/block_iptables.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -72,8 +72,8 @@
 
 for str in "${strings[@]}"; do
     iptables -A OUTPUT -m string --string "$str" --algo bm -j DROP
-done

-    
+done

+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/block/block_lxd.html b/en/guide/block/block_lxd.html
index fd36edfd07..7c589bccae 100644
--- a/en/guide/block/block_lxd.html
+++ b/en/guide/block/block_lxd.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Blocking Abusive Behavior via Shell Scripts ​
Blocking Ingress/Egress Traffic on Easily Abused Ports and Filtering Out Port Scanning and Exploitation Toolkits ​
  • (Optional, this script is solely for preventing container abuse and is not mandatory to install.)
  • Precautionary Measures
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
Use the 'screen' command to configure monitoring and blocking of certain processes' commands: terminate containers immediately upon the appearance of specific processes. ​
  • To stop monitoring, you can use the 'screen' command to stop the window named 'lxc_monitor' and delete it.
  • (Optional, this script is only for preventing misuse of containers; it's fine not to install it.)
  • Shutdown afterwards.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh

-    
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Blocking Abusive Behavior via Shell Scripts ​
Blocking Ingress/Egress Traffic on Easily Abused Ports and Filtering Out Port Scanning and Exploitation Toolkits ​
  • (Optional, this script is solely for preventing container abuse and is not mandatory to install.)
  • Precautionary Measures
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh
Use the 'screen' command to configure monitoring and blocking of certain processes' commands: terminate containers immediately upon the appearance of specific processes. ​
  • To stop monitoring, you can use the 'screen' command to stop the window named 'lxc_monitor' and delete it.
  • (Optional, this script is only for preventing misuse of containers; it's fine not to install it.)
  • Shutdown afterwards.
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh

+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/block/block_pve.html b/en/guide/block/block_pve.html
index 7748a687a1..2398cfefd3 100644
--- a/en/guide/block/block_pve.html
+++ b/en/guide/block/block_pve.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -21,8 +21,8 @@
   
     
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Avoid theft by setting up a firewall to limit the IPs used by the VMs ​
Create the following file under the PVE's host machine
shell
/etc/pve/firewall/<VMID>.fw
 [IPSET ipfilter-<net0>]
-xxx.xxx.xxx.xxx
<VMID> is replaced with the VMID number of the virtual machine, <net0> is replaced with the corresponding alias in the network device (which generally doesn't need to be changed unless you're restricted to IPV6), and xxx.xxx.xxx.xxx is replaced with the public IP address, noting that this IP corresponds to the network device in front of it.
The idea here is that net0 can only use the IP xxx.xxx.xxx.xxx, if you use any other IP the data will be dropped, thus restricting the VM to only use this IP.
There can be more than one IP, once this rule is enabled the VM can't use any other IP, if you don't write an IPv6 address it means the VM can't use an IPv6 address.
TIP
This setting is only recommended when opening VMs with separate IPs that are not NAT full port mapped, otherwise it may cause strange issues resulting in the server being without a network.
This method is not suitable for use on PVEs that open any NAT VMs/containers.

-    
+xxx.xxx.xxx.xxx
<VMID> is replaced with the VMID number of the virtual machine, <net0> is replaced with the corresponding alias in the network device (which generally doesn't need to be changed unless you're restricted to IPV6), and xxx.xxx.xxx.xxx is replaced with the public IP address, noting that this IP corresponds to the network device in front of it.
The idea here is that net0 can only use the IP xxx.xxx.xxx.xxx, if you use any other IP the data will be dropped, thus restricting the VM to only use this IP.
There can be more than one IP, once this rule is enabled the VM can't use any other IP, if you don't write an IPv6 address it means the VM can't use an IPv6 address.
TIP
This setting is only recommended when opening VMs with separate IPs that are not NAT full port mapped, otherwise it may cause strange issues resulting in the server being without a network.
This method is not suitable for use on PVEs that open any NAT VMs/containers.

+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/dashboard.html b/en/guide/dashboard.html
index bc8df6d06d..7f02e54741 100644
--- a/en/guide/dashboard.html
+++ b/en/guide/dashboard.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Preparation Work ​
To virtualize a server, you will need:
  1. A server (VPS or Dedicated Server) that can connect to the public internet. It's preferable if this server can access GitHub's RAW pages perfectly, as some projects and components might not use CDN acceleration.
  2. A stable SSH connection from your local machine. If the connection isn't stable, you can use the screen command to create a window and execute commands within that window.
TIP
If you're unfamiliar with the screen command, please search for relevant tutorials to learn it, or you can use tmux as an alternative.
  1. Ensure that the server's system and hardware meet the requirements specified by the corresponding project. Refer to the project's documentation for detailed information.
This document will use a VPS as an example, and the VPS should be clean without any native environment issues. If necessary, reinstall the system to ensure the initial environment's cleanliness.
WARNING
The PVE project might cause problems on the host machine. If you're not familiar with debugging bugs and fixing system issues, it's not recommended to use PVE in a production environment. When using PVE-related scripts, make sure the host machine can be reinstalled at any time.
Project Repository ​
Welcome Star and Fork, all resources are open source, no non-open source parts, reproduced as well as the use of please write on the source of this site, thank you!
PVE ​
https://github.com/oneclickvirt/pve
Hits
incus ​
https://github.com/oneclickvirt/incus
Hits
Docker ​
https://github.com/oneclickvirt/docker
Hits
LXD ​
https://github.com/oneclickvirt/lxd
Hits

-    
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Preparation Work ​
To virtualize a server, you will need:
  1. A server (VPS or Dedicated Server) that can connect to the public internet. It's preferable if this server can access GitHub's RAW pages perfectly, as some projects and components might not use CDN acceleration.
  2. A stable SSH connection from your local machine. If the connection isn't stable, you can use the screen command to create a window and execute commands within that window.
TIP
If you're unfamiliar with the screen command, please search for relevant tutorials to learn it, or you can use tmux as an alternative.
  1. Ensure that the server's system and hardware meet the requirements specified by the corresponding project. Refer to the project's documentation for detailed information.
This document will use a VPS as an example, and the VPS should be clean without any native environment issues. If necessary, reinstall the system to ensure the initial environment's cleanliness.
WARNING
The PVE project might cause problems on the host machine. If you're not familiar with debugging bugs and fixing system issues, it's not recommended to use PVE in a production environment. When using PVE-related scripts, make sure the host machine can be reinstalled at any time.
Project Repository ​
Welcome Star and Fork, all resources are open source, no non-open source parts, reproduced as well as the use of please write on the source of this site, thank you!
PVE ​
https://github.com/oneclickvirt/pve
Hits
incus ​
https://github.com/oneclickvirt/incus
Hits
Docker ​
https://github.com/oneclickvirt/docker
Hits
LXD ​
https://github.com/oneclickvirt/lxd
Hits

+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/dashboardq.html b/en/guide/dashboardq.html
index 525e186cee..4f773e473b 100644
--- a/en/guide/dashboardq.html
+++ b/en/guide/dashboardq.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
-    
+    
+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/docker/docker_android.html b/en/guide/docker/docker_android.html
index de1ba3873c..732e3103a4 100644
--- a/en/guide/docker/docker_android.html
+++ b/en/guide/docker/docker_android.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -24,8 +24,8 @@
 rm -rf /etc/nginx/sites-enabled/reverse-proxy
 rm -rf /etc/nginx/sites-available/reverse-proxy
 rm -rf /etc/nginx/passwd_scrcpy_web
-rm -rf /root/android_info

-    
+rm -rf /root/android_info

+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/docker/docker_build.html b/en/guide/docker/docker_build.html
index 84b715ab96..b13d190cd2 100644
--- a/en/guide/docker/docker_build.html
+++ b/en/guide/docker/docker_build.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -42,8 +42,8 @@
     docker exec -it $container_id bash -c "service sshd restart"
     docker exec -it $container_id sh -c "service ssh start"
     docker exec -it $container_id sh -c "/usr/sbin/sshd"
-done

-    
+done

+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/docker/docker_custom.html b/en/guide/docker/docker_custom.html
index 8baa6013a7..8cf8930055 100644
--- a/en/guide/docker/docker_custom.html
+++ b/en/guide/docker/docker_custom.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -28,8 +28,8 @@
 docker rm -f chromium_${PORT}
 rm -rf /usr/local/bin/config_${PORT}
 rm -rf /usr/local/bin/password_${PORT}
-docker rmi lscr.io/linuxserver/chromium
One-Click Setup of Desktop Container ​
  • Crashes automatically restart have been configured.
  • Chinese fonts are included in the setup.
  • Built-in web validation with the ability to set your own username and password.
  • Customizable maximum memory usage for the container.
  • No need to consider nested virtualization support and server architecture.
  • Sound mapping is supported, and sound can be transmitted via the web interface.
A complete Linux desktop on which you can use a browser
The host system requires at least 1 core, 2 GB of RAM, and 5 GB of hard disk space. The created container will occupy a minimum of 3.2 GB of hard disk space.
Setup Instructions:
After setup, the default username is onew and the password is oneclick. The default maximum memory usage is 2 GB.
The default web port for HTTP protocol is 3004, and for HTTPS protocol is 3005. After setup, open the corresponding protocol with localhost's IPV4:port in your web browser.
Run the following command to download and execute the setup script:
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onewebtop.sh -o onewebtop.sh && chmod +x onewebtop.sh && bash onewebtop.sh
Deletion
Command:
shell
docker ps -a
Query for containers with a prefix of 'webtop' in their names, and record the IDs of these containers.
shell
docker rm -f container_ID
To remove the corresponding image, you can use the following command after deleting all associated containers:
shell
docker rmi lscr.io/linuxserver/webtop
One-Click Installation of Guacamole ​
A web-based tool for controlling servers using protocols like SSH or RDP.
Website: http://your_IPV4_address:80/guacamole
Default Username: guacadmin
Default Password: guacadmin
After installation, remember to change the password upon login.
The host machine should have at least 1 core, 2GB RAM, and 10GB of disk space; otherwise, launching might lead to host machine freezing!
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/extra_scripts/guacamole.sh -o guacamole.sh && chmod +x guacamole.sh && bash guacamole.sh

-    
+docker rmi lscr.io/linuxserver/chromium
One-Click Setup of Desktop Container ​
  • Crashes automatically restart have been configured.
  • Chinese fonts are included in the setup.
  • Built-in web validation with the ability to set your own username and password.
  • Customizable maximum memory usage for the container.
  • No need to consider nested virtualization support and server architecture.
  • Sound mapping is supported, and sound can be transmitted via the web interface.
A complete Linux desktop on which you can use a browser
The host system requires at least 1 core, 2 GB of RAM, and 5 GB of hard disk space. The created container will occupy a minimum of 3.2 GB of hard disk space.
Setup Instructions:
After setup, the default username is onew and the password is oneclick. The default maximum memory usage is 2 GB.
The default web port for HTTP protocol is 3004, and for HTTPS protocol is 3005. After setup, open the corresponding protocol with localhost's IPV4:port in your web browser.
Run the following command to download and execute the setup script:
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onewebtop.sh -o onewebtop.sh && chmod +x onewebtop.sh && bash onewebtop.sh
Deletion
Command:
shell
docker ps -a
Query for containers with a prefix of 'webtop' in their names, and record the IDs of these containers.
shell
docker rm -f container_ID
To remove the corresponding image, you can use the following command after deleting all associated containers:
shell
docker rmi lscr.io/linuxserver/webtop
One-Click Installation of Guacamole ​
A web-based tool for controlling servers using protocols like SSH or RDP.
Website: http://your_IPV4_address:80/guacamole
Default Username: guacadmin
Default Password: guacadmin
After installation, remember to change the password upon login.
The host machine should have at least 1 core, 2GB RAM, and 10GB of disk space; otherwise, launching might lead to host machine freezing!
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/extra_scripts/guacamole.sh -o guacamole.sh && chmod +x guacamole.sh && bash guacamole.sh

+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/docker/docker_install.html b/en/guide/docker/docker_install.html
index 74176290ac..28a43f3137 100644
--- a/en/guide/docker/docker_install.html
+++ b/en/guide/docker/docker_install.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Preface ​
Support for running Docker virtualization on various systems, including Linux, Android, and Windows.
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the LXD module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
Setting Up Virtual Memory ​
TIP
Allocate some swap space to prevent your machine from crashing.
Unit conversion: Inputting 1024 results in 1G of SWAP - virtual memory. Virtual memory occupies disk space and is automatically utilized when the physical memory is insufficient. However, this leads to high IO usage and CPU performance overhead.
It is recommended to allocate virtual memory twice the size of your physical memory.
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
Environment Setup ​
  • Detect the system environment and install the corresponding components
  • Install docker and docker-compose.
  • Download some configuration scripts required by default
  • Detect if there is an IPV6 address, check if it is greater than or equal to /112, and if so, configure the docker's ipv6 network.
  • If all the above conditions are met, create ndpresponder docker and radvd so that IPV6 allocation supports ndp broadcasting and auto-allocation.
  • Support for x86_64 and ARM architecture servers
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
OR
bash dockerinstall.sh
TIP
The environment installation process may require you to reboot the server and then execute the script again, see the instructions after the script is run for more details

-    
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Preface ​
Support for running Docker virtualization on various systems, including Linux, Android, and Windows.
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the LXD module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
Setting Up Virtual Memory ​
TIP
Allocate some swap space to prevent your machine from crashing.
Unit conversion: Inputting 1024 results in 1G of SWAP - virtual memory. Virtual memory occupies disk space and is automatically utilized when the physical memory is insufficient. However, this leads to high IO usage and CPU performance overhead.
It is recommended to allocate virtual memory twice the size of your physical memory.
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
Environment Setup ​
  • Detect the system environment and install the corresponding components
  • Install docker and docker-compose.
  • Download some configuration scripts required by default
  • Detect if there is an IPV6 address, check if it is greater than or equal to /112, and if so, configure the docker's ipv6 network.
  • If all the above conditions are met, create ndpresponder docker and radvd so that IPV6 allocation supports ndp broadcasting and auto-allocation.
  • Support for x86_64 and ARM architecture servers
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
OR
bash dockerinstall.sh
TIP
The environment installation process may require you to reboot the server and then execute the script again, see the instructions after the script is run for more details

+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/docker/docker_macos.html b/en/guide/docker/docker_macos.html
index af3a66af1f..96fd141a6a 100644
--- a/en/guide/docker/docker_macos.html
+++ b/en/guide/docker/docker_macos.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Running macOS Virtual Machines in Docker ​
Using Dockur ​
Original Project:
https://github.com/dockur/macos
Using Docker-OSX ​
Original Project:
https://github.com/sickcodes/Docker-OSX

-    
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Running macOS Virtual Machines in Docker ​
Using Dockur ​
Original Project:
https://github.com/dockur/macos
Using Docker-OSX ​
Original Project:
https://github.com/sickcodes/Docker-OSX

+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/docker/docker_precheck.html b/en/guide/docker/docker_precheck.html
index 697f937bb0..797fe9554e 100644
--- a/en/guide/docker/docker_precheck.html
+++ b/en/guide/docker/docker_precheck.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Introduction ​
The following is an introduction to the non-customized sections. Please ensure that you don't confuse them with the customized parts.
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the incus module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
WARNING
If the host has an IPV6 network, the installation will change the network structure of the host, please make sure that the host can reset the system at any time and that there is no important data on the host before running.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/docker
Project Features ​
Bulk or individual NAT server provisioning via docker
Default use of debian system optional alpine system, each container comes with 1 external ssh port, 25 internal and external network ports, you can choose whether to bind IPV6 address
The default creation of unprivileged containers, and does not mount and host docker daemon communication, so ** host created docker virtualization NAT servers can not be nested within the virtualization docker **
By default, lxcfs is installed and enabled, so that when querying resources within a container, CPU and memory use the configured view instead of the host's view.
Since most cloud servers have ext4 filesystems, even xfs filesystems do not enable the pquota option, so sharing the host's hard disk by default does not limit the disk size of each container.
Configuration requirements ​
The system can be installed docker can be used, the network can connect to the Github raw interface can be used, hardware configuration as long as not pull across the line, free hard disk has 3G on it!
(If you need to bind an IPV6 address, then please make sure to use the installation script of this set of scripts for docker installation, you need it to automatically preset some of the settings)
If the hardware resources are just a little bit better, need to limit more things and need to limit the size of the hard disk, you can use the incus partition of the script batch open LXC virtualization containers
If the hardware is very good and you have a lot of resources, you can use the PVE partition script to batch open KVM virtualized VMs.

-    
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Introduction ​
The following is an introduction to the non-customized sections. Please ensure that you don't confuse them with the customized parts.
If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the incus module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.
WARNING
If the host has an IPV6 network, the installation will change the network structure of the host, please make sure that the host can reset the system at any time and that there is no important data on the host before running.
Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/docker
Project Features ​
Bulk or individual NAT server provisioning via docker
Default use of debian system optional alpine system, each container comes with 1 external ssh port, 25 internal and external network ports, you can choose whether to bind IPV6 address
The default creation of unprivileged containers, and does not mount and host docker daemon communication, so ** host created docker virtualization NAT servers can not be nested within the virtualization docker **
By default, lxcfs is installed and enabled, so that when querying resources within a container, CPU and memory use the configured view instead of the host's view.
Since most cloud servers have ext4 filesystems, even xfs filesystems do not enable the pquota option, so sharing the host's hard disk by default does not limit the disk size of each container.
Configuration requirements ​
The system can be installed docker can be used, the network can connect to the Github raw interface can be used, hardware configuration as long as not pull across the line, free hard disk has 3G on it!
(If you need to bind an IPV6 address, then please make sure to use the installation script of this set of scripts for docker installation, you need it to automatically preset some of the settings)
If the hardware resources are just a little bit better, need to limit more things and need to limit the size of the hard disk, you can use the incus partition of the script batch open LXC virtualization containers
If the hardware is very good and you have a lot of resources, you can use the PVE partition script to batch open KVM virtualized VMs.

+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/docker/docker_qa.html b/en/guide/docker/docker_qa.html
index 491b7e5a1f..79335dace3 100644
--- a/en/guide/docker/docker_qa.html
+++ b/en/guide/docker/docker_qa.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Solve the puzzle ​
Common Docker Commands ​
Check real-time resource usage of a specific container
docker stats <container_name>
Enter a specific container
docker exec -it <container_name> /bin/bash
Clean Docker cache, remove unused resources including images, containers, networks, etc.
docker system prune -a
Uninstall all Docker images and containers
docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)
View logs of a specific container
docker logs <container_name_or_ID>
View overall disk usage of Docker
docker system df
List all containers
docker ps -a
List all images
docker images
Remove a specific container
docker rm -f <container_name_or_ID>
Remove a specific image
docker rmi <image_name_or_ID>

-    
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Solve the puzzle ​
Common Docker Commands ​
Check real-time resource usage of a specific container
docker stats <container_name>
Enter a specific container
docker exec -it <container_name> /bin/bash
Clean Docker cache, remove unused resources including images, containers, networks, etc.
docker system prune -a
Uninstall all Docker images and containers
docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)
View logs of a specific container
docker logs <container_name_or_ID>
View overall disk usage of Docker
docker system df
List all containers
docker ps -a
List all images
docker images
Remove a specific container
docker rm -f <container_name_or_ID>
Remove a specific image
docker rmi <image_name_or_ID>

+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/docker/docker_thanks.html b/en/guide/docker/docker_thanks.html
index fad378346d..6b3f9a36f7 100644
--- a/en/guide/docker/docker_thanks.html
+++ b/en/guide/docker/docker_thanks.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance

-    
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance

+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/docker/docker_windows.html b/en/guide/docker/docker_windows.html
index 3ca143a7e8..1e099f25fa 100644
--- a/en/guide/docker/docker_windows.html
+++ b/en/guide/docker/docker_windows.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -44,8 +44,8 @@
   --device=/dev/net/tun \
   --cap-add NET_ADMIN \
   --stop-timeout 120 \
-  windows:2022
Important Notes ​
It is not recommended to use docker commit to save changes to this image, as repeated layer stacking may cause the image size to exceed 40 GB.
For personalized configuration or additional software integration, always start from the builder image to ensure a clean and maintainable result.

-    
+  windows:2022
Important Notes ​
It is not recommended to use docker commit to save changes to this image, as repeated layer stacking may cause the image size to exceed 40 GB.
For personalized configuration or additional software integration, always start from the builder image to ensure a clean and maintainable result.

+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/incus/incus_custom.html b/en/guide/incus/incus_custom.html
index b9d9981f31..7ef3f30b72 100644
--- a/en/guide/incus/incus_custom.html
+++ b/en/guide/incus/incus_custom.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -98,8 +98,8 @@
 
 # Reconnect and set process daemon to take effect automatically after reboot.
 systemctl enable --now wg-quick@warp
3: Autorun: fscarmen's one-click scripts ​
Finally, the one-click script for fscarmen is introduced. The script is mentioned as a handy tool to simplify the configuration process. It also automatically handles advanced parameters such as Optimal MTU, Optimal Endpoint, etc.
Project: https://github.com/fscarmen/warp-sh
# Run one-key script
-wget -N https://gitlab.com/fscarmen/warp/-/raw/main/menu.sh && bash menu.sh
image.png

-    
+wget -N https://gitlab.com/fscarmen/warp/-/raw/main/menu.sh && bash menu.sh
image.png

+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/incus/incus_extra_config.html b/en/guide/incus/incus_extra_config.html
index 5dbcd18064..36de2eb507 100644
--- a/en/guide/incus/incus_extra_config.html
+++ b/en/guide/incus/incus_extra_config.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -29,8 +29,8 @@
 rm /etc/systemd/system/add-ipv6.service
 systemctl daemon-reload
 rm /usr/local/bin/add-ipv6.sh
One-click Installation of Common Pre-configured Environment for incus Hosts with vnstat Integration ​
  • (Optional, this script is only for easy monitoring integration with the site, it's fine if you choose not to install)
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/backend.sh -o backend.sh && chmod +x backend.sh && bash backend.sh
One-Click Installation of the official incus Visualization Dashboard ​
  • (Optional, this panel is just for convenient visualization operations, it's okay if not present)
shell
apt-get install -y incus-ui-canonical
-incus config set core.https_address [::]
Then you can type in your browser
https://your_public_ipv4_address:8443
You can enter the official visualization panel, subsequent operation configuration in accordance with the UI prompts can be operated.

-    
+incus config set core.https_address [::]
Then you can type in your browser
https://your_public_ipv4_address:8443
You can enter the official visualization panel, subsequent operation configuration in accordance with the UI prompts can be operated.

+    
     
   
 
\ No newline at end of file
diff --git a/en/guide/incus/incus_install.html b/en/guide/incus/incus_install.html
index e0d39ae8b5..debbed2cad 100644
--- a/en/guide/incus/incus_install.html
+++ b/en/guide/incus/incus_install.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -35,8 +35,8 @@
 EOF'
 apt-get update
 apt-get install incus -y
-incus -h
If there are no exceptions, continue execution
incus admin init
Just enter the default for the normal options
Choose the size of the physical disk (hint: select the default option with a minimum of 1GB). Generally, I fill in the available disk space minus the memory size, then multiply by 0.95 and round down. Here, I entered 10GB.
Remember to select 'no' for options containing 'auto' when prompted to update the image, in order to avoid occupying the system.
- +incus -h

If there are no exceptions, continue execution

incus admin init

Just enter the default for the normal options

Choose the size of the physical disk (hint: select the default option with a minimum of 1GB). Generally, I fill in the available disk space minus the memory size, then multiply by 0.95 and round down. Here, I entered 10GB.

Remember to select 'no' for options containing 'auto' when prompted to update the image, in order to avoid occupying the system.

+ \ No newline at end of file diff --git a/en/guide/incus/incus_lxc.html b/en/guide/incus/incus_lxc.html index f3eb8dd4d9..e619a6aa34 100644 --- a/en/guide/incus/incus_lxc.html +++ b/en/guide/incus/incus_lxc.html @@ -11,7 +11,7 @@ - + @@ -43,8 +43,8 @@ wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/ssh_bash.sh -O /usr/local/bin/ssh_bash.sh && chmod +x /usr/local/bin/ssh_bash.sh wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/ssh_sh.sh -O /usr/local/bin/ssh_sh.sh && chmod +x /usr/local/bin/ssh_sh.sh wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_ipv6_network.sh -O /root/build_ipv6_network.sh && chmod +x /root/build_ipv6_network.sh -wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/buildone.sh -O /root/buildone.sh && chmod +x /root/buildone.sh

Just download the other one-click scripts yourself.

- +wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/buildone.sh -O /root/buildone.sh && chmod +x /root/buildone.sh

Just download the other one-click scripts yourself.

+ \ No newline at end of file diff --git a/en/guide/incus/incus_precheck.html b/en/guide/incus/incus_precheck.html index 2f267ffa2f..11dbf9260c 100644 --- a/en/guide/incus/incus_precheck.html +++ b/en/guide/incus/incus_precheck.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Preface ​

The following is the introduction of the non-customized part, the customized part has its own corresponding introduction, do not get confused!

If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the incus module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.

Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/incus

Requirements ​

Hardware requirements.

  • System: Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • Virtualization: KVM, VMWARE recommended.
  • Memory: At least 512MB of RAM
  • Hard disk: hard disk (system disk) at least 10G
  • Network: Independent IPV4 address, IPV6 is optional, bandwidth can download scripts on the line, the network can connect to the Github raw page on the line

PS: If the hardware is very good and has a lot of resources, you can use PVE to batch open KVM virtualized VMs Jump

PS: If the hardware resources are even worse, virtualization is not supported, you can use the docker version, the adaption surface is wider Jump

Project Features ​

  • This set of script development using Ubuntu24 and Debian12, other long-term maintenance version should also be no problem, automatically switch to another storage type if btrfs not supported

  • Set up both TCP and UDP forwarding, in addition to SSH ports, other mapping intranet and extranet ports are the same.

  • Support for docker nested virtualization of open incus containers has been set up, and the default normal version and pure probe version use the debian11 system.

  • lxcfs has been set to be enabled by default, so that querying resources within a container uses the configured view rather than the host's view

  • Have blocked the container may be used to abuse the toolkit and IPV4 network TCP/UDP protocol ports ( 3389 8888 54321 65432 ), to prevent the container is used for scanning and blasting, and can be external process checking for problems automatically shut down

  • Has supported one-click configuration of IPV6 addresses for incus containers (provided that the mother hen has an IPV6 subnet, no IPV6 address is not configured), automatically adapted to the size of the subnet

  • Ensure that the disk you want to open is the default system disk (sda or sda1) and not the mounted disk (sdb and so on), if you are not sure, use fdisk -l and df to check.

  • See Other notes for details on mounting other disks.

  • One-click scripts support custom restrictions on all content, the normal version supports multiple runs of the batch generation does not overwrite the previously generated configuration

Detecting the environment ​

Use the subsequent script must execute this command to detect the hen whether it meets the requirements

Command:

bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)
- +
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Preface ​

The following is the introduction of the non-customized part, the customized part has its own corresponding introduction, do not get confused!

If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the incus module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.

Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/incus

Requirements ​

Hardware requirements.

  • System: Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • Virtualization: KVM, VMWARE recommended.
  • Memory: At least 512MB of RAM
  • Hard disk: hard disk (system disk) at least 10G
  • Network: Independent IPV4 address, IPV6 is optional, bandwidth can download scripts on the line, the network can connect to the Github raw page on the line

PS: If the hardware is very good and has a lot of resources, you can use PVE to batch open KVM virtualized VMs Jump

PS: If the hardware resources are even worse, virtualization is not supported, you can use the docker version, the adaption surface is wider Jump

Project Features ​

  • This set of script development using Ubuntu24 and Debian12, other long-term maintenance version should also be no problem, automatically switch to another storage type if btrfs not supported

  • Set up both TCP and UDP forwarding, in addition to SSH ports, other mapping intranet and extranet ports are the same.

  • Support for docker nested virtualization of open incus containers has been set up, and the default normal version and pure probe version use the debian11 system.

  • lxcfs has been set to be enabled by default, so that querying resources within a container uses the configured view rather than the host's view

  • Have blocked the container may be used to abuse the toolkit and IPV4 network TCP/UDP protocol ports ( 3389 8888 54321 65432 ), to prevent the container is used for scanning and blasting, and can be external process checking for problems automatically shut down

  • Has supported one-click configuration of IPV6 addresses for incus containers (provided that the mother hen has an IPV6 subnet, no IPV6 address is not configured), automatically adapted to the size of the subnet

  • Ensure that the disk you want to open is the default system disk (sda or sda1) and not the mounted disk (sdb and so on), if you are not sure, use fdisk -l and df to check.

  • See Other notes for details on mounting other disks.

  • One-click scripts support custom restrictions on all content, the normal version supports multiple runs of the batch generation does not overwrite the previously generated configuration

Detecting the environment ​

Use the subsequent script must execute this command to detect the hen whether it meets the requirements

Command:

bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)
+ \ No newline at end of file diff --git a/en/guide/incus/incus_qa.html b/en/guide/incus/incus_qa.html index e48729027b..8da52059ff 100644 --- a/en/guide/incus/incus_qa.html +++ b/en/guide/incus/incus_qa.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Solve the puzzle ​

What to do if you open centos7 and find that CGroupV1 is not supported? ​

Enable CGroup V1: To enable CGroup V1 on an Ubuntu system, you need to edit the kernel boot parameters.

Please note that before changing kernel boot parameters, make sure to backup important data and settings to prevent unexpected problems.

Edit the ```/etc/default/grubfile and addsystemd.unified_cgroup_hierarchy=0to the end of the parameters inGRUB_CMDLINE_LINUX_DEFAULT``, just like:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"

Save the file and run the following command to update the GRUB boot.

bash
sudo update-grub

Reboot the system for the changes to take effect

If the above changes still do not support the opening of centos7, try using a different host system.

Currently verified VPS vendors that can open containers with separate IPV6 addresses. ​

kuroit Phoenix, USA regular

datalix German AMD Promotions

- +
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Solve the puzzle ​

What to do if you open centos7 and find that CGroupV1 is not supported? ​

Enable CGroup V1: To enable CGroup V1 on an Ubuntu system, you need to edit the kernel boot parameters.

Please note that before changing kernel boot parameters, make sure to backup important data and settings to prevent unexpected problems.

Edit the ```/etc/default/grubfile and addsystemd.unified_cgroup_hierarchy=0to the end of the parameters inGRUB_CMDLINE_LINUX_DEFAULT``, just like:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"

Save the file and run the following command to update the GRUB boot.

bash
sudo update-grub

Reboot the system for the changes to take effect

If the above changes still do not support the opening of centos7, try using a different host system.

Currently verified VPS vendors that can open containers with separate IPV6 addresses. ​

kuroit Phoenix, USA regular

datalix German AMD Promotions

+ \ No newline at end of file diff --git a/en/guide/incus/incus_thanks.html b/en/guide/incus/incus_thanks.html index 48d0b9c147..97a9583641 100644 --- a/en/guide/incus/incus_thanks.html +++ b/en/guide/incus/incus_thanks.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
One Click Virtualization

English

简体中文

English

简体中文

Appearance

- +
One Click Virtualization

English

简体中文

English

简体中文

Appearance

+ \ No newline at end of file diff --git a/en/guide/incus/incus_windows.html b/en/guide/incus/incus_windows.html index e43ebca496..ac8e131323 100644 --- a/en/guide/incus/incus_windows.html +++ b/en/guide/incus/incus_windows.html @@ -11,7 +11,7 @@ - + @@ -68,8 +68,8 @@ > /var/log/websockify-winvm.log 2>&1 & echo "SPICE HTML5 console on http://${SERVER_IP}:6080/spice_auto.html"

At the first boot, you'll need to press the Ctrl+Alt+Delete button in the upper left corner of the browser page. After restarting, follow the prompts on the default interface. You'll need to wait 5-10 minutes for the ISO to be loaded for the actual installation.

Eventually, the Zabbly icon will appear and spin for at least 10 minutes. Please be patient.

Once the spinning stops, you'll enter the normal Windows VM installation process, similar to PVE operations.

If you need to delete the VM and recreate it due to resource limitations or other reasons, use pkill -f websockify to terminate all SPICE signal forwarding, then incus delete -f winvm to forcibly delete the VM.

shell
lsof -i :6080

Check if the PID for the corresponding port still exists to ensure it has completely stopped (if you have signal forwarding for multiple VMs, it's better not to use pkill to delete all of them; use kill -9 to delete the PID for the specific port).

If the installation is complete, first shut down/exit Windows (from the browser), then remove the ISO device to ensure it boots from the hard disk next time:

shell
incus stop winvm
 incus config device remove winvm install
-incus start winvm

Disadvantages ​

The frontend lacks authentication, so you can't set user passwords.

If you need frontend authentication, you'll need to use Guacamole with additional settings to implement it, which won't be covered in detail here.

- +incus start winvm

Disadvantages ​

The frontend lacks authentication, so you can't set user passwords.

If you need frontend authentication, you'll need to use Guacamole with additional settings to implement it, which won't be covered in detail here.

+ \ No newline at end of file diff --git a/en/guide/lxd/lxd_custom.html b/en/guide/lxd/lxd_custom.html index c8cd503e75..eac69d1d2d 100644 --- a/en/guide/lxd/lxd_custom.html +++ b/en/guide/lxd/lxd_custom.html @@ -11,7 +11,7 @@ - + @@ -98,8 +98,8 @@ # Reconnect and set process daemon to take effect automatically after reboot. systemctl enable --now wg-quick@warp

3: Autorun: fscarmen's one-click scripts ​

Finally, the one-click script for fscarmen is introduced. The script is mentioned as a handy tool to simplify the configuration process. It also automatically handles advanced parameters such as Optimal MTU, Optimal Endpoint, etc.

Project: https://github.com/fscarmen/warp-sh

# Run one-key script
-wget -N https://gitlab.com/fscarmen/warp/-/raw/main/menu.sh && bash menu.sh

image.png

- +wget -N https://gitlab.com/fscarmen/warp/-/raw/main/menu.sh && bash menu.sh

image.png

+ \ No newline at end of file diff --git a/en/guide/lxd/lxd_extra_config.html b/en/guide/lxd/lxd_extra_config.html index c89e74586e..6fece5d2dd 100644 --- a/en/guide/lxd/lxd_extra_config.html +++ b/en/guide/lxd/lxd_extra_config.html @@ -11,7 +11,7 @@ - + @@ -34,8 +34,8 @@ systemctl reload snap.lxd.daemon snap restart --reload lxd

Then you can type in your browser

https://your_public_ipv4_address:8443

You can enter the official visualization panel, subsequent operation configuration in accordance with the UI prompts can be operated.

One-Click Installation of Hosted Third-Party Visualization Dashboard ​

shell
lxc config set core.https_address [::]
 lxc config set core.trust_password your_password
-snap install lxdmosaic

After the installation is complete, open the hen IP address, follow the prompts to set the password for admin, other all the way to the default will be able to use the panel!

- +snap install lxdmosaic

After the installation is complete, open the hen IP address, follow the prompts to set the password for admin, other all the way to the default will be able to use the panel!

+ \ No newline at end of file diff --git a/en/guide/lxd/lxd_install.html b/en/guide/lxd/lxd_install.html index e8ea6a3f16..560a019860 100644 --- a/en/guide/lxd/lxd_install.html +++ b/en/guide/lxd/lxd_install.html @@ -11,7 +11,7 @@ - + @@ -24,8 +24,8 @@ ufw disable

Enabling Virtual Memory SWAP ​

The amount of memory depends on how many instances you want to run. If you want to run 8 instances and calculate, you'll need 2GB of memory. If your actual physical memory is 512MB, you'll need an additional 1.5GB. To be cautious, allocate 2GB of virtual memory.

Execute the following commands: Enter '1', then enter '2048'. This signifies allocating 2GB of virtual memory.

Command:

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh

Installing LXD ​

Actually, the virtual memory allocated for swap should be twice the size of the actual memory. So, it's reasonable to allocate 1GB if the actual memory is 500MB. The scenario I described above is an excessive allocation.

apt install snapd -y
 snap install lxd
 /snap/bin/lxd init

If the following error occurs in the above command

(snap "lxd" assumes unsupported features: snapd2.39 (try to update snapd and refresh the core snap))

Use the command patch before installing lxd

snap install core

If there are no exceptions, the results of the above three lines of commands are as follows

Just enter the default for the normal options

Choose the size of the physical disk (hint: select the default option with a minimum of 1GB). Generally, I fill in the available disk space minus the memory size, then multiply by 0.95 and round down. Here, I entered 10GB.

Remember to select 'no' for options containing 'auto' when prompted to update the image, in order to avoid occupying the system.

Test whether symbolic links are functioning in LXC.

lxc -h

If an error is reported then execute the following command to soft connect the lxc command

bash
! lxc -h >/dev/null 2>&1 && echo 'alias lxc="/snap/bin/lxc"' >> /root/.bashrc && source /root/.bashrc
-export PATH=$PATH:/snap/bin

After connecting, test the lxc command again to see if there is an error about not being able to find it

- +export PATH=$PATH:/snap/bin

After connecting, test the lxc command again to see if there is an error about not being able to find it

+ \ No newline at end of file diff --git a/en/guide/lxd/lxd_lxc.html b/en/guide/lxd/lxd_lxc.html index 8e7564da67..d38786936e 100644 --- a/en/guide/lxd/lxd_lxc.html +++ b/en/guide/lxd/lxd_lxc.html @@ -11,7 +11,7 @@ - + @@ -43,8 +43,8 @@ wget https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/ssh_bash.sh -O /usr/local/bin/ssh_bash.sh && chmod +x /usr/local/bin/ssh_bash.sh wget https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/ssh_sh.sh -O /usr/local/bin/ssh_sh.sh && chmod +x /usr/local/bin/ssh_sh.sh wget https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_ipv6_network.sh -O /root/build_ipv6_network.sh && chmod +x /root/build_ipv6_network.sh -wget https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/buildone.sh -O /root/buildone.sh && chmod +x /root/buildone.sh

Just download the other one-click scripts yourself.

- +wget https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/buildone.sh -O /root/buildone.sh && chmod +x /root/buildone.sh

Just download the other one-click scripts yourself.

+ \ No newline at end of file diff --git a/en/guide/lxd/lxd_precheck.html b/en/guide/lxd/lxd_precheck.html index 6aae95e397..53ff384335 100644 --- a/en/guide/lxd/lxd_precheck.html +++ b/en/guide/lxd/lxd_precheck.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Preface ​

The following is the introduction of the non-customized part, the customized part has its own corresponding introduction, do not get confused!

If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the LXD module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.

Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/lxd

Requirements ​

Hardware requirements.

  • System: Debian 8+, Ubuntu 18+ (20.04 recommended).
  • Virtualization: KVM, VMWARE recommended.
  • Memory: At least 512MB of RAM
  • Hard disk: hard disk (system disk) at least 10G
  • Network: Independent IPV4 address, IPV6 is optional, bandwidth can download scripts on the line, the network can connect to the Github raw page on the line

PS: If the hardware is very good and has a lot of resources, you can use PVE to batch open KVM virtualized VMs Jump

PS: If the hardware resources are even worse, virtualization is not supported, you can use the docker version, the adaption surface is wider Jump

Project Features ​

  • This set of script development using Ubuntu20, Ubuntu other long-term maintenance version should also be no problem, automatically switch to another storage type if btrfs not supported

  • Set up both TCP and UDP forwarding, in addition to SSH ports, other mapping intranet and extranet ports are the same.

  • Support for docker nested virtualization of open LXC containers has been set up, and the default normal version and pure probe version use the debian11 system.

  • lxcfs has been set to be enabled by default, so that querying resources within a container uses the configured view rather than the host's view

  • Have blocked the container may be used to abuse the toolkit and IPV4 network TCP/UDP protocol ports ( 3389 8888 54321 65432 ), to prevent the container is used for scanning and blasting, and can be external process checking for problems automatically shut down

  • Has supported one-click configuration of IPV6 addresses for LXC containers (provided that the mother hen has an IPV6 subnet, no IPV6 address is not configured), automatically adapted to the size of the subnet

  • Ensure that the disk you want to open is the default system disk (sda or sda1) and not the mounted disk (sdb and so on), if you are not sure, use fdisk -l and df to check.

  • See Other notes for details on mounting other disks.

  • One-click scripts support custom restrictions on all content, the normal version supports multiple runs of the batch generation does not overwrite the previously generated configuration

Detecting the environment ​

Use the subsequent script must execute this command to detect the hen whether it meets the requirements

Command:

bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)
- +
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Preface ​

The following is the introduction of the non-customized part, the customized part has its own corresponding introduction, do not get confused!

If your host does not have an IPV6 subnet and you want to assign IPV6 addresses to containers, then please check the Customize partition in the LXD module for the Attach a free IPV6 address segment to the host, and attach an IPV6 subnet to the host before installing the environment.

Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/lxd

Requirements ​

Hardware requirements.

  • System: Debian 8+, Ubuntu 18+ (20.04 recommended).
  • Virtualization: KVM, VMWARE recommended.
  • Memory: At least 512MB of RAM
  • Hard disk: hard disk (system disk) at least 10G
  • Network: Independent IPV4 address, IPV6 is optional, bandwidth can download scripts on the line, the network can connect to the Github raw page on the line

PS: If the hardware is very good and has a lot of resources, you can use PVE to batch open KVM virtualized VMs Jump

PS: If the hardware resources are even worse, virtualization is not supported, you can use the docker version, the adaption surface is wider Jump

Project Features ​

  • This set of script development using Ubuntu20, Ubuntu other long-term maintenance version should also be no problem, automatically switch to another storage type if btrfs not supported

  • Set up both TCP and UDP forwarding, in addition to SSH ports, other mapping intranet and extranet ports are the same.

  • Support for docker nested virtualization of open LXC containers has been set up, and the default normal version and pure probe version use the debian11 system.

  • lxcfs has been set to be enabled by default, so that querying resources within a container uses the configured view rather than the host's view

  • Have blocked the container may be used to abuse the toolkit and IPV4 network TCP/UDP protocol ports ( 3389 8888 54321 65432 ), to prevent the container is used for scanning and blasting, and can be external process checking for problems automatically shut down

  • Has supported one-click configuration of IPV6 addresses for LXC containers (provided that the mother hen has an IPV6 subnet, no IPV6 address is not configured), automatically adapted to the size of the subnet

  • Ensure that the disk you want to open is the default system disk (sda or sda1) and not the mounted disk (sdb and so on), if you are not sure, use fdisk -l and df to check.

  • See Other notes for details on mounting other disks.

  • One-click scripts support custom restrictions on all content, the normal version supports multiple runs of the batch generation does not overwrite the previously generated configuration

Detecting the environment ​

Use the subsequent script must execute this command to detect the hen whether it meets the requirements

Command:

bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)
+ \ No newline at end of file diff --git a/en/guide/lxd/lxd_qa.html b/en/guide/lxd/lxd_qa.html index ca5d1c4f45..c7942ba43a 100644 --- a/en/guide/lxd/lxd_qa.html +++ b/en/guide/lxd/lxd_qa.html @@ -11,7 +11,7 @@ - + @@ -20,8 +20,8 @@
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Solve the puzzle ​

What if the lxc command says it can't be found after LXD is installed? ​

! lxc -h >/dev/null 2>&1 && echo 'alias lxc="/snap/bin/lxc"' >> /root/.bashrc && source /root/.bashrc
-export PATH=$PATH:/snap/bin

After executing this command try

lxc -h

to see if the lxc command is fixed.

What to do if you open centos7 and find that CGroupV1 is not supported? ​

Enable CGroup V1: To enable CGroup V1 on an Ubuntu system, you need to edit the kernel boot parameters.

Please note that before changing kernel boot parameters, make sure to backup important data and settings to prevent unexpected problems.

Edit the ```/etc/default/grubfile and addsystemd.unified_cgroup_hierarchy=0to the end of the parameters inGRUB_CMDLINE_LINUX_DEFAULT``, just like:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"

Save the file and run the following command to update the GRUB boot.

bash
sudo update-grub

Reboot the system for the changes to take effect

If the above changes still do not support the opening of centos7, try using a different host system.

Currently verified VPS vendors that can open containers with separate IPV6 addresses. ​

kuroit Phoenix, USA regular

datalix German AMD Promotions

- +export PATH=$PATH:/snap/bin

After executing this command try

lxc -h

to see if the lxc command is fixed.

What to do if you open centos7 and find that CGroupV1 is not supported? ​

Enable CGroup V1: To enable CGroup V1 on an Ubuntu system, you need to edit the kernel boot parameters.

Please note that before changing kernel boot parameters, make sure to backup important data and settings to prevent unexpected problems.

Edit the ```/etc/default/grubfile and addsystemd.unified_cgroup_hierarchy=0to the end of the parameters inGRUB_CMDLINE_LINUX_DEFAULT``, just like:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"

Save the file and run the following command to update the GRUB boot.

bash
sudo update-grub

Reboot the system for the changes to take effect

If the above changes still do not support the opening of centos7, try using a different host system.

Currently verified VPS vendors that can open containers with separate IPV6 addresses. ​

kuroit Phoenix, USA regular

datalix German AMD Promotions

+ \ No newline at end of file diff --git a/en/guide/lxd/lxd_thanks.html b/en/guide/lxd/lxd_thanks.html index dffd300d4c..e9458bc00b 100644 --- a/en/guide/lxd/lxd_thanks.html +++ b/en/guide/lxd/lxd_thanks.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
One Click Virtualization

English

简体中文

English

简体中文

Appearance

- +
One Click Virtualization

English

简体中文

English

简体中文

Appearance

+ \ No newline at end of file diff --git a/en/guide/pve/images/readme.html b/en/guide/pve/images/readme.html index 9622cb3bad..85d68865de 100644 --- a/en/guide/pve/images/readme.html +++ b/en/guide/pve/images/readme.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

暂存图片

- +
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

暂存图片

+ \ No newline at end of file diff --git a/en/guide/pve/pve_android.html b/en/guide/pve/pve_android.html index 02c01b7311..96a50aec13 100644 --- a/en/guide/pve/pve_android.html +++ b/en/guide/pve/pve_android.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Android Virtual Machine ​

Android System Image Download ​

Download links for Android system version 9 and earlier:

International

https://www.fosshub.com/Android-x86.html

https://sourceforge.net/projects/android-x86/files/

Domestic (China)

https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/

Download links for Android system version 10 and later:

https://blissos.org/index.html#download

Virtual Machine Setup ​

Setting up an Android Virtual Machine with version 9 and earlier images ​

This guide demonstrates using:

https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/71931/android-x86_64-9.0-rc2.iso

as an example

1

Template Configuration ​

Create a virtual machine with VMID 100 and select the corresponding storage disk

2

Select the Android image, then choose Linux for Type and choose an option with version 2.6 for Version

3

Select Vmware compatible for Graphic card, other options are default as shown

4

Choose SATA for disk format, allocate at least 30GB of disk space (size can be chosen based on your needs)

5

CPU count should be at least 2 cores

If your host machine supports nested virtualization, choose host for CPU type (verified to work)

If your host machine doesn't support nested virtualization, choose qemu64 for CPU type, and after creating the template, go to Options and uncheck KVM hardware virtualization before starting the virtual machine (no guarantee that system initialization will work properly)

6

Memory should be at least 4GB, enter at least 4096

7

Select vmbr1 for the network bridge, choose VirtIO (paravirtualized) for Model, and uncheck Firewall

8

After clicking the continue button, the template is successfully created. You need to manually start it and enter the VNC interface

9

System Installation ​

After entering the boot menu, select the option starting with Installation

10

Then you need to create disk partitions. If you can't select it, press the keyboard button 'c' to select it

11

Choose not to use GPT format

12

When the empty disk is displayed, select New

13

Select partition type Primary

14

Then you'll be prompted to specify the size of the space. Just press Enter to use all available space

15

Then select Flags, move to Bootable, press Enter until Boot appears under Flags

16

Then move to Write and press Enter to write changes

17

You'll be asked to confirm whether to continue. Type yes and press Enter to continue

18

After a progress bar completes, you'll return to the initial menu. Select Quit to exit the menu, everything is now ready

19

Then you'll return to the UI interface. Use the previously initialized disk and select the OK button

20

Use the arrow keys to select ext4 file system type, then select the OK button

21

Confirm formatting by selecting the Yes button

22

Confirm GRUB boot installation by selecting the OK button

23

Confirm the file system is readable and writable by selecting the OK button

24

After a progress bar runs for some time, it will show that installation was successful. Select Reboot and the OK button

25

After a while, you'll enter the Android logo screen

26

Removing the Image ​

Then there will be a black screen. If it's still black after 3-5 minutes, execute qm stop 100 on the host machine, then start removing the image file.

Remove the installed ISO file by manually clicking on the corresponding CD in the Hardware section of the ProxmoxVE web interface and selecting Remove

ar

Then execute qm start 100 on the host machine again, and you should enter the Android system initialization interface

System Initialization ​

In the initialization interface, select the language and click the confirm button

27

It will try to connect to WiFi. Since our PVE installation uses a completely static network configuration, just skip this and set it up later

31

Click the next button to confirm the time settings

32

Click to cancel screen protection, confirm to skip again

33

After a period of black screen, the main screen application selection will appear. If this interface doesn't appear after waiting 3-5 minutes, restart the virtual machine as before, and it should display after entering VNC

Select Quickstep

34

Network Settings ​

After entering the desktop, you need to set up the network. Click the settings icon in the upper left corner

35

A dropdown appears, click and hold to pull down

36

Click the gear button

37

Enter Network & Internet settings

38

Double-click WIFI with the left mouse button

39

Modify the detected VirtWIFI. Right-click to bring up the selection box, then click Modify network

40

Advanced options appear, click to open hidden options

41

Configure the network settings as shown

IP address 172.16.1.xxx (replace xxx with your desired IP, I used 100 because my vmid is 100 for convenience)

Subnet mask 24

Default gateway 172.16.1.1

DNS 8.8.8.8 or 144.144.144.144

Then click the save button

42

At this point, the settings may still not be applied. Turn off WiFi and then turn it back on, it should then show as connected

43

Then exit to the main interface, click on Google Chrome, and try to open a webpage

44

You can see that opening this guide's URL works without problems, proving that the network is connected

45

Setting up an Android Virtual Machine with version 10 and later images ​

This guide demonstrates using:

https://psychz.dl.sourceforge.net/project/blissos-x86/Official/BlissOS15/Gapps/Generic/Bliss-v15.9.2-x86_64-OFFICIAL-gapps-20241012.iso?viasf=1

as an example

1

Template Configuration ​

The host machine needs to execute the following command to install graphics environment dependencies

shell
apt install libgl1 libegl1 -y

Then start creating the virtual machine by clicking the Create VM button in the upper right corner. Fill in VMID, Name, Resource Pool

2

Select the Android image, then choose Linux for Type and an option with version 2.6 for Version

3

If the host machine has a GPU, select VirGL GPU for Graphic card.

If the host machine doesn't have a GPU, select VirtIO or Vmware compatible for Graphic card.

Select q35 for Machine, select OVMF (UEFI) for BIOS, and select local for EFI Storage.

4

Choose SATA for disk format. How much disk space to allocate is up to you, but at least 30GB is recommended

5

CPU count should be at least 2 cores

If your host machine supports nested virtualization, choose host for CPU type (verified to work)

If your host machine doesn't support nested virtualization, choose qemu64 for CPU type, and after creating the template, go to Options and uncheck KVM hardware virtualization before starting the virtual machine (no guarantee that system initialization will work properly)

6

Memory should be at least 4GB, enter at least 4096

7

Select vmbr1 for the network bridge, choose VirtIO (paravirtualized) for Model, and uncheck Firewall

8

After clicking the continue button, the template is successfully created. You need to manually start it and enter the VNC interface.

System Installation ​

After entering the boot menu, select the option ending with Installation

9

Then you need to create disk partitions. If you can't select it, press the keyboard button 'c' to select it.

10

Choose not to use GPT format, continue using cfdisk format.

11

When the format selection box appears, select gpt.

12

When the empty disk is displayed, select New.

13

Because you need to create an EFI partition, you need to change the size rather than using the default. Change the number to 1 to allocate 1GB of disk space, then press Enter.

14

Then you'll return to the menu bar. Use the arrow keys to select Type, then press Enter to choose the format type for the partition

15

Use the arrow keys to select the first option EFI System, then press Enter

16

Now you're back at the menu bar. In the upper half of the page, you can see the specific partition size and format

17

Then press the down arrow key to select the next empty partition line

18

Select New from the menu bar, then press Enter

19

Here you need to fill in the partition size. Match it with the empty partition size shown in the upper right corner, then press Enter.

20

Return to the menu bar, select Write, press Enter to write the partition.

21

You'll be prompted to enter yes to confirm. Enter it and press Enter.

22

After a progress bar runs, you should return to the menu bar. Select Quit to exit the menu, everything is now ready

23

Then you'll return to the UI interface. Use the previously initialized 1GB disk and select the OK button

24

Use the arrow keys to select fat32 file system type, then select the OK button

25

Confirm not to modify the name by selecting the OK button

26

Confirm formatting by selecting the Yes button

27

Then you'll return to the initial UI bar. Select the second partition that is not 1GB in size and select the OK button

28

Use the arrow keys to select ext4 file system type, then select the OK button

29

Confirm not to modify the name by selecting the OK button

30

Confirm formatting by selecting the Yes button

31

Choose not to use extra space for updates by selecting the No button

32

Confirm GRUB2 EFI BootLoader by selecting the OK button

33

After a progress bar runs for some time, it will show that installation was successful. Select Reboot and the OK button.

34

System Initialization ​

After a while, you'll enter the logo screen.

35

After some more time, you should enter the initial Android interface. You'll see a popup and the time. Hold the left mouse button and swipe up

36

The main screen application selection will appear. Select Quickstep

If this interface doesn't appear after waiting 3-5 minutes, restart the virtual machine, and it should display after entering VNC

37

Removing the Image ​

After the Android interface appears, execute qm stop 100 on the host machine, then start removing the image file.

Remove the installed ISO file by manually clicking on the corresponding CD in the Hardware section of the ProxmoxVE web interface and selecting Remove

br

Then execute qm start 100 on the host machine again, and you should enter the system's initial interface.

Network Settings ​

After entering the desktop, you need to set up the network. Hold the left mouse button in the indicated position and swipe up

38

A bunch of applications will pop up. Find the one called Bliss Ethernet Manager and click to open it

39

Click to open IP Assignment, select Static type, click the OK button to confirm

40

Click to open IP Address, enter 172.16.1.xxx/24 (I used 100 for xxx because my virtual machine VMID is 100 for easy identification), click the OK button to confirm

41

Click to open Gateway Address, enter 172.16.1.1, click the OK button to confirm

42

Click to open DNS Address, enter 8.8.8.8, click the OK button to confirm

43

Then in the application interface, click Interface Up and Refresh, then press the exit key on the keyboard to exit the program

44

Open the browser in the main interface to verify that the network is working properly

45

You can see that opening this guide works without problems, the network is functioning

46

- +
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Android Virtual Machine ​

Android System Image Download ​

Download links for Android system version 9 and earlier:

International

https://www.fosshub.com/Android-x86.html

https://sourceforge.net/projects/android-x86/files/

Domestic (China)

https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/

Download links for Android system version 10 and later:

https://blissos.org/index.html#download

Virtual Machine Setup ​

Setting up an Android Virtual Machine with version 9 and earlier images ​

This guide demonstrates using:

https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/71931/android-x86_64-9.0-rc2.iso

as an example

1

Template Configuration ​

Create a virtual machine with VMID 100 and select the corresponding storage disk

2

Select the Android image, then choose Linux for Type and choose an option with version 2.6 for Version

3

Select Vmware compatible for Graphic card, other options are default as shown

4

Choose SATA for disk format, allocate at least 30GB of disk space (size can be chosen based on your needs)

5

CPU count should be at least 2 cores

If your host machine supports nested virtualization, choose host for CPU type (verified to work)

If your host machine doesn't support nested virtualization, choose qemu64 for CPU type, and after creating the template, go to Options and uncheck KVM hardware virtualization before starting the virtual machine (no guarantee that system initialization will work properly)

6

Memory should be at least 4GB, enter at least 4096

7

Select vmbr1 for the network bridge, choose VirtIO (paravirtualized) for Model, and uncheck Firewall

8

After clicking the continue button, the template is successfully created. You need to manually start it and enter the VNC interface

9

System Installation ​

After entering the boot menu, select the option starting with Installation

10

Then you need to create disk partitions. If you can't select it, press the keyboard button 'c' to select it

11

Choose not to use GPT format

12

When the empty disk is displayed, select New

13

Select partition type Primary

14

Then you'll be prompted to specify the size of the space. Just press Enter to use all available space

15

Then select Flags, move to Bootable, press Enter until Boot appears under Flags

16

Then move to Write and press Enter to write changes

17

You'll be asked to confirm whether to continue. Type yes and press Enter to continue

18

After a progress bar completes, you'll return to the initial menu. Select Quit to exit the menu, everything is now ready

19

Then you'll return to the UI interface. Use the previously initialized disk and select the OK button

20

Use the arrow keys to select ext4 file system type, then select the OK button

21

Confirm formatting by selecting the Yes button

22

Confirm GRUB boot installation by selecting the OK button

23

Confirm the file system is readable and writable by selecting the OK button

24

After a progress bar runs for some time, it will show that installation was successful. Select Reboot and the OK button

25

After a while, you'll enter the Android logo screen

26

Removing the Image ​

Then there will be a black screen. If it's still black after 3-5 minutes, execute qm stop 100 on the host machine, then start removing the image file.

Remove the installed ISO file by manually clicking on the corresponding CD in the Hardware section of the ProxmoxVE web interface and selecting Remove

ar

Then execute qm start 100 on the host machine again, and you should enter the Android system initialization interface

System Initialization ​

In the initialization interface, select the language and click the confirm button

27

It will try to connect to WiFi. Since our PVE installation uses a completely static network configuration, just skip this and set it up later

31

Click the next button to confirm the time settings

32

Click to cancel screen protection, confirm to skip again

33

After a period of black screen, the main screen application selection will appear. If this interface doesn't appear after waiting 3-5 minutes, restart the virtual machine as before, and it should display after entering VNC

Select Quickstep

34

Network Settings ​

After entering the desktop, you need to set up the network. Click the settings icon in the upper left corner

35

A dropdown appears, click and hold to pull down

36

Click the gear button

37

Enter Network & Internet settings

38

Double-click WIFI with the left mouse button

39

Modify the detected VirtWIFI. Right-click to bring up the selection box, then click Modify network

40

Advanced options appear, click to open hidden options

41

Configure the network settings as shown

IP address 172.16.1.xxx (replace xxx with your desired IP, I used 100 because my vmid is 100 for convenience)

Subnet mask 24

Default gateway 172.16.1.1

DNS 8.8.8.8 or 144.144.144.144

Then click the save button

42

At this point, the settings may still not be applied. Turn off WiFi and then turn it back on, it should then show as connected

43

Then exit to the main interface, click on Google Chrome, and try to open a webpage

44

You can see that opening this guide's URL works without problems, proving that the network is connected

45

Setting up an Android Virtual Machine with version 10 and later images ​

This guide demonstrates using:

https://psychz.dl.sourceforge.net/project/blissos-x86/Official/BlissOS15/Gapps/Generic/Bliss-v15.9.2-x86_64-OFFICIAL-gapps-20241012.iso?viasf=1

as an example

1

Template Configuration ​

The host machine needs to execute the following command to install graphics environment dependencies

shell
apt install libgl1 libegl1 -y

Then start creating the virtual machine by clicking the Create VM button in the upper right corner. Fill in VMID, Name, Resource Pool

2

Select the Android image, then choose Linux for Type and an option with version 2.6 for Version

3

If the host machine has a GPU, select VirGL GPU for Graphic card.

If the host machine doesn't have a GPU, select VirtIO or Vmware compatible for Graphic card.

Select q35 for Machine, select OVMF (UEFI) for BIOS, and select local for EFI Storage.

4

Choose SATA for disk format. How much disk space to allocate is up to you, but at least 30GB is recommended

5

CPU count should be at least 2 cores

If your host machine supports nested virtualization, choose host for CPU type (verified to work)

If your host machine doesn't support nested virtualization, choose qemu64 for CPU type, and after creating the template, go to Options and uncheck KVM hardware virtualization before starting the virtual machine (no guarantee that system initialization will work properly)

6

Memory should be at least 4GB, enter at least 4096

7

Select vmbr1 for the network bridge, choose VirtIO (paravirtualized) for Model, and uncheck Firewall

8

After clicking the continue button, the template is successfully created. You need to manually start it and enter the VNC interface.

System Installation ​

After entering the boot menu, select the option ending with Installation

9

Then you need to create disk partitions. If you can't select it, press the keyboard button 'c' to select it.

10

Choose not to use GPT format, continue using cfdisk format.

11

When the format selection box appears, select gpt.

12

When the empty disk is displayed, select New.

13

Because you need to create an EFI partition, you need to change the size rather than using the default. Change the number to 1 to allocate 1GB of disk space, then press Enter.

14

Then you'll return to the menu bar. Use the arrow keys to select Type, then press Enter to choose the format type for the partition

15

Use the arrow keys to select the first option EFI System, then press Enter

16

Now you're back at the menu bar. In the upper half of the page, you can see the specific partition size and format

17

Then press the down arrow key to select the next empty partition line

18

Select New from the menu bar, then press Enter

19

Here you need to fill in the partition size. Match it with the empty partition size shown in the upper right corner, then press Enter.

20

Return to the menu bar, select Write, press Enter to write the partition.

21

You'll be prompted to enter yes to confirm. Enter it and press Enter.

22

After a progress bar runs, you should return to the menu bar. Select Quit to exit the menu, everything is now ready

23

Then you'll return to the UI interface. Use the previously initialized 1GB disk and select the OK button

24

Use the arrow keys to select fat32 file system type, then select the OK button

25

Confirm not to modify the name by selecting the OK button

26

Confirm formatting by selecting the Yes button

27

Then you'll return to the initial UI bar. Select the second partition that is not 1GB in size and select the OK button

28

Use the arrow keys to select ext4 file system type, then select the OK button

29

Confirm not to modify the name by selecting the OK button

30

Confirm formatting by selecting the Yes button

31

Choose not to use extra space for updates by selecting the No button

32

Confirm GRUB2 EFI BootLoader by selecting the OK button

33

After a progress bar runs for some time, it will show that installation was successful. Select Reboot and the OK button.

34

System Initialization ​

After a while, you'll enter the logo screen.

35

After some more time, you should enter the initial Android interface. You'll see a popup and the time. Hold the left mouse button and swipe up

36

The main screen application selection will appear. Select Quickstep

If this interface doesn't appear after waiting 3-5 minutes, restart the virtual machine, and it should display after entering VNC

37

Removing the Image ​

After the Android interface appears, execute qm stop 100 on the host machine, then start removing the image file.

Remove the installed ISO file by manually clicking on the corresponding CD in the Hardware section of the ProxmoxVE web interface and selecting Remove

br

Then execute qm start 100 on the host machine again, and you should enter the system's initial interface.

Network Settings ​

After entering the desktop, you need to set up the network. Hold the left mouse button in the indicated position and swipe up

38

A bunch of applications will pop up. Find the one called Bliss Ethernet Manager and click to open it

39

Click to open IP Assignment, select Static type, click the OK button to confirm

40

Click to open IP Address, enter 172.16.1.xxx/24 (I used 100 for xxx because my virtual machine VMID is 100 for easy identification), click the OK button to confirm

41

Click to open Gateway Address, enter 172.16.1.1, click the OK button to confirm

42

Click to open DNS Address, enter 8.8.8.8, click the OK button to confirm

43

Then in the application interface, click Interface Up and Refresh, then press the exit key on the keyboard to exit the program

44

Open the browser in the main interface to verify that the network is working properly

45

You can see that opening this guide works without problems, the network is functioning

46

+ \ No newline at end of file diff --git a/en/guide/pve/pve_custom.html b/en/guide/pve/pve_custom.html index 2c18b37667..3dcbc74201 100644 --- a/en/guide/pve/pve_custom.html +++ b/en/guide/pve/pve_custom.html @@ -11,7 +11,7 @@ - + @@ -48,8 +48,8 @@ echo "*/5 * * * * sleep 120; echo 3 > /proc/sys/vm/drop_caches" >> $TEMP_CRON echo "*/5 * * * * sleep 180; fstrim -av" >> $TEMP_CRON sudo crontab $TEMP_CRON -rm $TEMP_CRON

The above commands require the sudo and crontab commands to be available on the host itself.

Self-mapping of public ports on KVM VMs with open NATs ​

Use the nano or vim command to modify the file to add port mapping:

/etc/iptables/rules.v4

For example, if I have a KVM VM with an intranet IP of 172.16.1.152, and MYSQL has been set up to listen to 3306, and I need to use the tcp protocol to map out to the 33306 port on the host IP, I would add the following line to the COMMIT line in the file above, then add the following line

-A PREROUTING -i vmbr0 -p tcp -m tcp -dport 33306 -j DNAT --to-destination 172.16.1.152:3306

Save the file and exit file editing and then execute:

service netfilter-persistent restart

Reload Port Mapping

At this point, on the host machine, execute the

lsof -i:33306

To see if the port mapping rule is in effect

Customizing the CPU TYPE when opening a Linux virtual machine ​

On the host computer, use something like

shell
echo "kvm64" > /usr/local/bin/cpu_type

Specifying the default CPU TYPE in this way allows you to replace kvm64 with the type you want

- +rm $TEMP_CRON

The above commands require the sudo and crontab commands to be available on the host itself.

Self-mapping of public ports on KVM VMs with open NATs ​

Use the nano or vim command to modify the file to add port mapping:

/etc/iptables/rules.v4

For example, if I have a KVM VM with an intranet IP of 172.16.1.152, and MYSQL has been set up to listen to 3306, and I need to use the tcp protocol to map out to the 33306 port on the host IP, I would add the following line to the COMMIT line in the file above, then add the following line

-A PREROUTING -i vmbr0 -p tcp -m tcp -dport 33306 -j DNAT --to-destination 172.16.1.152:3306

Save the file and exit file editing and then execute:

service netfilter-persistent restart

Reload Port Mapping

At this point, on the host machine, execute the

lsof -i:33306

To see if the port mapping rule is in effect

Customizing the CPU TYPE when opening a Linux virtual machine ​

On the host computer, use something like

shell
echo "kvm64" > /usr/local/bin/cpu_type

Specifying the default CPU TYPE in this way allows you to replace kvm64 with the type you want

+ \ No newline at end of file diff --git a/en/guide/pve/pve_install.html b/en/guide/pve/pve_install.html index 1840cdfb57..ccaafe8c7b 100644 --- a/en/guide/pve/pve_install.html +++ b/en/guide/pve/pve_install.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

PVE Body Installation ​

If you don't know how to choose an option during installation, just press enter.

TIP

For low-configuration hosts, it is recommended to check the contents of the Custom partition after all the content has been installed to perform memory tuning and reduce the memory footprint.

One-click PVE installation ​

TIP

Suggest debian12, the actual test part of the independent server debian11 system will appear a reboot network will be lost, debian12 does not have such a problem!

  • The installation is the latest PVE from the apt source at the moment.
  • For example, debian10 is pve6.4, debian11 is pve7.x, debian12 is pve8.x
  • Changes to the /etc/hosts file (to fix the wrong hostname setting for merchants and to add the required content for PVE)
  • /etc/cloud/cloud.cfg file modification (to avoid overwriting modified hostname etc.)
  • /etc/network/interfaces file modification (fix auto, dhcp type to static, add vmbr0 gateway)
  • Detect whether it is China IP, if it is China IP use Tsinghua mirror source, otherwise use the official source, and at the same time deal with the source of apt and the corresponding nameserver, to avoid disconnections
  • Create vmbr0 (independent IP gateway), the host allows addr and gateway for intranet IP or extranet IP, has been automatically recognized
  • vmbr0 creation support to open pure IPV4, pure IPV6, dual-stack virtual machine, automatic identification of IPV4 address and IPV6 address, automatic identification of the corresponding IP interval
  • Installation of the necessary toolkit for PVE to open a virtual machine
  • x86_64 replace enterprise subscriptions in apt sources with community sources, arm sources built using third-party patches for fixes
  • Print query Linux system kernel and PVE kernel installed or not
  • Setting up DNS detection 8.8.8.8.8 for boot add DNS systemd service
  • Download PVE and printout of login information after adding APT source link for PVE

All modified files have been set to read-only mode to avoid overwriting after reboot.

If you want to modify the file, please use chattr -i file path to cancel the read-only lock, and run chattr +i file path to lock the read-only lock when you finish modifying the file.

You will be prompted to reboot your system once during the execution process, After rebooting, be sure to wait at least 20 seconds to make sure the system does not reboot automatically again.

Because the original environment may be missing ifupdown or ifupdown2 environment, there is a self-installation daemon loaded for the installation, after the installation of the system will automatically reboot the system again, wait for 20 seconds without reboot to ensure that the installation has been run.

If the host itself exists SLAAC assigned IPV6 address, will be able to choose whether to use the largest IPV6 subnet range, the default carriage return does not use the largest IPV6 subnet range only use the local IPV6, if you subsequently need to attach a separate IPV6 address to the virtual machine/container, the option must be selected y.

Command:

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh

or

shell
bash install_pve.sh

TIP

After successful installation, the web page may not be safe to open, click on Advanced or More Options and insist on accessing it!

The login information is your SSH account and password.

Pre-configure the environment ​

  • Creating a resource pool mypool
  • Remove the subscription popup
  • Attempt to enable hardware passthrough
  • Detect and auto-install AppArmor modules.
  • Before rebooting the system, it is recommended to hook up nezha probe to facilitate the use of the command line in the background without SSH, to avoid the possibility that SSH may lead to the loss of the root password after the reboot due to the merchant's strange presets.
  • Before executing reboot, you need to wait for the background task to finish executing, some host system apt command execution is very slow, you have to wait for a while to finish executing, of course, most of the machines are not so bad!

Command:

shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)

Automatically configure the host's gateway ​

WARNING

Before using this command, please make sure that you have restarted the server and that PVE can use the WEB terminal normally before executing this command. Do not execute this command immediately after restarting the machine, wait for at least 1 minute after the WEB terminal is successfully started before executing this command. If the WEB side doesn't start, run systemctl status pveproxy to see if it starts, if it's stuck, run systemctl start pveproxy to start the WEB side.

TIP

This step is most likely to cause SSH disconnections, the reason is to modify the network without waiting for the PVE kernel to start, which will result in setting conflicts, so wait at least a few minutes until the kernel is started, that is, the WEB side is started successfully before execution.

TIP

If the host needs to attach an IPV6 tunnel (add an IPV6 subnet to a host that does not have an IPV6 address) before executing this command, please check the IPV6 free subnet attachment section to attach to the corresponding configuration file, but please ignore 'initial environment modifications' and attach directly, and then execute the following one-click gateway configuration commands after verifying that you have an IPV6 address.

  • If vmbr0 is not created, it is automatically created with the same logic as the main installation
  • Create vmbr1 (NAT gateway) to support IPV4 servers that open NAT for IPV6 networks with NAT.
  • Create vmbr2 (standalone IPV6 gateway), use ndppd to solve the problem of MAC verification of IPV6 addresses by the host, support the opening of servers with standalone IPV6 networks.
  • If you want to see the complete settings, you can execute cat /etc/network/interfaces to see, if you need to modify the gateway you need to modify the file, the web site can not be modified!
  • Load iptables and set back to source and allow NAT port forwarding.

In short, vmbr0 is responsible for v4 standalone IPs, and vmbr1 is responsible for complex v4/v6 NATs, vmbr2 is responsible for v6 standalone IPs.

Open independent IPV4 virtual machine using vmbr0, gateway with the host, IPV4/CIDR using the same network segment address and the same subnet mask, using the host's unbound IPV4 address for IPV4/CIDR, of course, if the subsequent use of this script does not need to pay attention to this point of the nuances of the thing

Use vmbr1 for IPV4 VM with NAT, 172.16.1.1 for gateway, 172.16.1.x/24 for IPV4/CIDR, where x can't be 1, but of course you don't need to pay attention to this minutia if you use this script later.

Command:

shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)

TIP

This step may require you to reboot your system after a few minutes of successful execution, see the final execution of the script at the end of the tip. However, a reboot will ensure that some of the hidden settings are loaded successfully, so be sure to reboot the server once if you are in a position to do so.

- +
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

PVE Body Installation ​

If you don't know how to choose an option during installation, just press enter.

TIP

For low-configuration hosts, it is recommended to check the contents of the Custom partition after all the content has been installed to perform memory tuning and reduce the memory footprint.

One-click PVE installation ​

TIP

Suggest debian12, the actual test part of the independent server debian11 system will appear a reboot network will be lost, debian12 does not have such a problem!

  • The installation is the latest PVE from the apt source at the moment.
  • For example, debian10 is pve6.4, debian11 is pve7.x, debian12 is pve8.x
  • Changes to the /etc/hosts file (to fix the wrong hostname setting for merchants and to add the required content for PVE)
  • /etc/cloud/cloud.cfg file modification (to avoid overwriting modified hostname etc.)
  • /etc/network/interfaces file modification (fix auto, dhcp type to static, add vmbr0 gateway)
  • Detect whether it is China IP, if it is China IP use Tsinghua mirror source, otherwise use the official source, and at the same time deal with the source of apt and the corresponding nameserver, to avoid disconnections
  • Create vmbr0 (independent IP gateway), the host allows addr and gateway for intranet IP or extranet IP, has been automatically recognized
  • vmbr0 creation support to open pure IPV4, pure IPV6, dual-stack virtual machine, automatic identification of IPV4 address and IPV6 address, automatic identification of the corresponding IP interval
  • Installation of the necessary toolkit for PVE to open a virtual machine
  • x86_64 replace enterprise subscriptions in apt sources with community sources, arm sources built using third-party patches for fixes
  • Print query Linux system kernel and PVE kernel installed or not
  • Setting up DNS detection 8.8.8.8.8 for boot add DNS systemd service
  • Download PVE and printout of login information after adding APT source link for PVE

All modified files have been set to read-only mode to avoid overwriting after reboot.

If you want to modify the file, please use chattr -i file path to cancel the read-only lock, and run chattr +i file path to lock the read-only lock when you finish modifying the file.

You will be prompted to reboot your system once during the execution process, After rebooting, be sure to wait at least 20 seconds to make sure the system does not reboot automatically again.

Because the original environment may be missing ifupdown or ifupdown2 environment, there is a self-installation daemon loaded for the installation, after the installation of the system will automatically reboot the system again, wait for 20 seconds without reboot to ensure that the installation has been run.

If the host itself exists SLAAC assigned IPV6 address, will be able to choose whether to use the largest IPV6 subnet range, the default carriage return does not use the largest IPV6 subnet range only use the local IPV6, if you subsequently need to attach a separate IPV6 address to the virtual machine/container, the option must be selected y.

Command:

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh

or

shell
bash install_pve.sh

TIP

After successful installation, the web page may not be safe to open, click on Advanced or More Options and insist on accessing it!

The login information is your SSH account and password.

Pre-configure the environment ​

  • Creating a resource pool mypool
  • Remove the subscription popup
  • Attempt to enable hardware passthrough
  • Detect and auto-install AppArmor modules.
  • Before rebooting the system, it is recommended to hook up nezha probe to facilitate the use of the command line in the background without SSH, to avoid the possibility that SSH may lead to the loss of the root password after the reboot due to the merchant's strange presets.
  • Before executing reboot, you need to wait for the background task to finish executing, some host system apt command execution is very slow, you have to wait for a while to finish executing, of course, most of the machines are not so bad!

Command:

shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)

Automatically configure the host's gateway ​

WARNING

Before using this command, please make sure that you have restarted the server and that PVE can use the WEB terminal normally before executing this command. Do not execute this command immediately after restarting the machine, wait for at least 1 minute after the WEB terminal is successfully started before executing this command. If the WEB side doesn't start, run systemctl status pveproxy to see if it starts, if it's stuck, run systemctl start pveproxy to start the WEB side.

TIP

This step is most likely to cause SSH disconnections, the reason is to modify the network without waiting for the PVE kernel to start, which will result in setting conflicts, so wait at least a few minutes until the kernel is started, that is, the WEB side is started successfully before execution.

TIP

If the host needs to attach an IPV6 tunnel (add an IPV6 subnet to a host that does not have an IPV6 address) before executing this command, please check the IPV6 free subnet attachment section to attach to the corresponding configuration file, but please ignore 'initial environment modifications' and attach directly, and then execute the following one-click gateway configuration commands after verifying that you have an IPV6 address.

  • If vmbr0 is not created, it is automatically created with the same logic as the main installation
  • Create vmbr1 (NAT gateway) to support IPV4 servers that open NAT for IPV6 networks with NAT.
  • Create vmbr2 (standalone IPV6 gateway), use ndppd to solve the problem of MAC verification of IPV6 addresses by the host, support the opening of servers with standalone IPV6 networks.
  • If you want to see the complete settings, you can execute cat /etc/network/interfaces to see, if you need to modify the gateway you need to modify the file, the web site can not be modified!
  • Load iptables and set back to source and allow NAT port forwarding.

In short, vmbr0 is responsible for v4 standalone IPs, and vmbr1 is responsible for complex v4/v6 NATs, vmbr2 is responsible for v6 standalone IPs.

Open independent IPV4 virtual machine using vmbr0, gateway with the host, IPV4/CIDR using the same network segment address and the same subnet mask, using the host's unbound IPV4 address for IPV4/CIDR, of course, if the subsequent use of this script does not need to pay attention to this point of the nuances of the thing

Use vmbr1 for IPV4 VM with NAT, 172.16.1.1 for gateway, 172.16.1.x/24 for IPV4/CIDR, where x can't be 1, but of course you don't need to pay attention to this minutia if you use this script later.

Command:

shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)

TIP

This step may require you to reboot your system after a few minutes of successful execution, see the final execution of the script at the end of the tip. However, a reboot will ensure that some of the hidden settings are loaded successfully, so be sure to reboot the server once if you are in a position to do so.

+ \ No newline at end of file diff --git a/en/guide/pve/pve_kvm.html b/en/guide/pve/pve_kvm.html index 6984dc69eb..af3a2ad5c2 100644 --- a/en/guide/pve/pve_kvm.html +++ b/en/guide/pve/pve_kvm.html @@ -11,7 +11,7 @@ - + @@ -33,8 +33,8 @@ service netfilter-persistent restart

This will cause the host to lose the ability to open VMs/containers with NAT that do not have a separate IPV4 address, so be careful!

After this, You will only be able to open VMs with separate IPV4 addresses.

Creating Virtual Machines with Pure IPv6 Addresses ​

The prerequisite is that the host provides an IPv6 subnet instead of just a standalone IPv6 address, and the host does not have MAC address verification enabled.

Automatic Selection of IPv6 Addresses without Manual Specification ​

Usage Instructions ​

Download Script

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm_onlyv6.sh -o buildvm_onlyv6.sh && chmod +x buildvm_onlyv6.sh

Meaning of each parameter

shell
# ./buildvm_onlyv6.sh VMID username password CPU_cores memory_GB disk_GB operating_system storage_disk

TIP

Note that the password here should be a mix of English and numbers only, and start with English, so as to avoid failing to set the password due to special characters being escaped during the setup process.

Test Example ​

shell
./buildvm_onlyv6.sh 152 root oneclick123 1 1024 10 debian12 local

The above command is used to create a virtual machine with only IPv6 addresses.

ParameterValue
VMID152
Usernameroot
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
Operating Systemdebian12
Storage Disklocal

TIP

Note that only VMIDs from 100 to 256 can be used here, no other numbers can be used.

Delete Example vm152 ​

shell
qm stop 152
 qm destroy 152
 systemctl restart ndpresponder.service
-rm -rf vm152
- +rm -rf vm152 + \ No newline at end of file diff --git a/en/guide/pve/pve_lxc.html b/en/guide/pve/pve_lxc.html index 9098a75436..c11eef0977 100644 --- a/en/guide/pve/pve_lxc.html +++ b/en/guide/pve/pve_lxc.html @@ -11,7 +11,7 @@ - + @@ -30,8 +30,8 @@ iptables-save > /etc/iptables/rules.v4

Creating Virtual Machines with Pure IPv6 Addresses ​

The premise is that the host provides an IPv6 subnet rather than a standalone IPv6 address, and the host does not have MAC address filtering enabled.

Automatic Selection of IPv6 Addresses, No Manual Configuration Needed ​

Download script ​

Command:

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildct_onlyv6.sh -o buildct_onlyv6.sh && chmod +x buildct_onlyv6.sh

Example Usage ​

shell
./buildct_onlyv6.sh CTID Password Number_of_CPU_Cores Memory_Size_in_MB Disk_Size_in_GB Operating_System Storage_Disk
shell
./buildct_onlyv6.sh 152 oneclick123 1 1024 10 debian12 local

The above command signifies the creation of a container with a pure IPV6 address.

AttributeValue
Container TypeCT
CTID152
Usernameroot
Passwordoneclick123
CPU Cores1
Memory1024MB
Disk10G
Operating Systemdebian12
Storage DiskLocal Disk (System Disk)

TIP

Note that only CTIDs from 100 to 256 can be used here, no other numbers can be used.

Deletion Example ​

shell
rm -rf ct*
 pct stop 152 
 pct destroy 152
-systemctl restart ndpresponder.service
- +systemctl restart ndpresponder.service + \ No newline at end of file diff --git a/en/guide/pve/pve_macos.html b/en/guide/pve/pve_macos.html index 8bb04cb20e..466856d820 100644 --- a/en/guide/pve/pve_macos.html +++ b/en/guide/pve/pve_macos.html @@ -12,7 +12,7 @@ - + @@ -28,8 +28,8 @@ monterey.iso.7z (Size: 12.36GB) ventura.iso.7z (Size: 12.31GB) sonoma.iso.7z (Size: 14.41GB) -sequoia.iso.7z (Size: 15.02GB)

MACOS Virtual Machine Template Setup ​

Download Template Script ​

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm_macos.sh -o buildvm_macos.sh && chmod +x buildvm_macos.sh

Parameter Meanings ​

shell
# ./buildvm_macos.sh VMID CPU_cores Memory Disk SSH_port VNC_port System Storage_disk Independent_IPV6(default_N_if_empty)

TIP

The disk size here is only the size of the virtual machine's disk. During the actual setup process, the program will also mount the boot disk and system image, so the actual disk requirement for setting up a virtual machine is virtual machine disk size + image size + boot disk size (500MB). Always be aware of whether your disk space is sufficient for setting up virtual machines.

Example Command ​

Using the oldest version (high-sierra) as an example, the supported configuration is as follows (very laggy)

shell
./buildvm_macos.sh 100 2 4096 45 44022 45901 high-sierra local N

After the template is set up, you can run cat vm100 to view information, or check the NOTES in the corresponding VM in the WEB interface.

Here is the information for the example VM:

PropertyValue
VMID100
CPU cores2
Memory size4096MB
Disk size45G
SSH port44022
VNC port45901
Systemhigh-sierra
Host storage disklocal
Independent IPV6N

TIP

Note that VMID can only use numbers from 100 to 256, other numbers are not available

MACOS System Boot and Installation ​

After completing the previous steps, you can see a gray virtual machine waiting to be started in the panel.

mac0

After clicking start, enter the VNC panel. The selection box on the left has a full-screen button. It is recommended to operate in full screen to avoid resolution issues.

mac00

After about 3 minutes of boot disk loading, a startup disk will be displayed on the left center of the screen. Click directly or press Enter.

After another 3-5 minutes of startup disk loading, four selection boxes will appear. Select Disk Utility and click to enter.

mac1

After entering, you can see three disks and one image. Find the disk larger than 40G named QEMU HARDDISK Media, and click Erase.

mac2

A pop-up window will appear, requiring you to rename the name to macos for easy identification and use later, then click Erase to continue initialization.

mac3

After initialization is complete, click Done.

mac4

Now you need to exit the Disk Utility interface. Click Disk Utility in the upper right corner and select Quit Disk Utility to exit the current selection box.

mac5

Then you return to the previous four selection boxes. Select Install macOS XXXX (since I am using Big Sur as an example, XXXX is Big Sur), and click continue.

mac6

In the following steps, continue clicking continue, then click Agree, and then Agree again.

mac7

mac8

mac9

Until those three disks appear again, but here you can see the disk larger than 40G named macos. Select it and click continue.

mac10

After a period of file copying and disk loading (about 12 minutes), you will formally enter the system installation phase. Choose your region based on where the host machine is located.

mac11

After selecting the region, continue clicking continue.

mac12

mac13

Until the Migration Assistant data migration option appears, select Not Now in the lower left corner to not import user data.

mac14

Then you will be prompted to create a user. Fill in the username, account name, and login password. After setting up, click continue.

mac15

After that, you will continue clicking continue until the system installation is complete.

Network Configuration ​

Since the system installation was performed in an offline environment, you need to manually configure a static network connection to the host's bridge.

Click the WIFI button in the upper right corner, turn off WIFI, and then click Network Preferences ...

mac16

After entering the settings interface, click the Advanced button to enter the advanced settings interface.

mac17

Fill in the static network configuration in the TCP/IP tab.

Configure IPV4: Manually

IPV4 Address: 172.16.1.xxx (replace xxx with the IP you want to bind, my vmid is 100, so I wrote 100 for convenience)

Subnet Mask: 255.255.255.0

Router: 172.16.1.1

If you need to configure an IPV6 network, similar to the IPV4 settings above, you will need to fill in the public IPV6 address bound to the virtual machine (written in the Note box in the PVE panel), subnet mask 128, and the default gateway obtained by executing cat /usr/local/bin/pve_check_ipv6 on the host.

mac18

Fill in the static network DNS configuration in the DNS tab.

Generally, adding 8.8.8.8 and 1.1.1.1 is sufficient. For use in mainland China, use 114.114.114.114.

mac19

After filling in and applying, the top left of the settings will show that the network is connected.

mac20

Now, opening the default browser and visiting any website will allow you to access public network resources, proving that the network has worked.

Remove ISO ​

Manually click on the corresponding CD in the Hardware on the web side of ProxmoxVE and select Remove, then restart the VM and you can use it directly.

wk

Macos system is to uninstall opencore.iso and xxxx (the system image used for installation).iso, similar to the Windows system uninstallation of win image and virtio image in the example picture above.

- +sequoia.iso.7z (Size: 15.02GB)

MACOS Virtual Machine Template Setup ​

Download Template Script ​

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm_macos.sh -o buildvm_macos.sh && chmod +x buildvm_macos.sh

Parameter Meanings ​

shell
# ./buildvm_macos.sh VMID CPU_cores Memory Disk SSH_port VNC_port System Storage_disk Independent_IPV6(default_N_if_empty)

TIP

The disk size here is only the size of the virtual machine's disk. During the actual setup process, the program will also mount the boot disk and system image, so the actual disk requirement for setting up a virtual machine is virtual machine disk size + image size + boot disk size (500MB). Always be aware of whether your disk space is sufficient for setting up virtual machines.

Example Command ​

Using the oldest version (high-sierra) as an example, the supported configuration is as follows (very laggy)

shell
./buildvm_macos.sh 100 2 4096 45 44022 45901 high-sierra local N

After the template is set up, you can run cat vm100 to view information, or check the NOTES in the corresponding VM in the WEB interface.

Here is the information for the example VM:

PropertyValue
VMID100
CPU cores2
Memory size4096MB
Disk size45G
SSH port44022
VNC port45901
Systemhigh-sierra
Host storage disklocal
Independent IPV6N

TIP

Note that VMID can only use numbers from 100 to 256, other numbers are not available

MACOS System Boot and Installation ​

After completing the previous steps, you can see a gray virtual machine waiting to be started in the panel.

mac0

After clicking start, enter the VNC panel. The selection box on the left has a full-screen button. It is recommended to operate in full screen to avoid resolution issues.

mac00

After about 3 minutes of boot disk loading, a startup disk will be displayed on the left center of the screen. Click directly or press Enter.

After another 3-5 minutes of startup disk loading, four selection boxes will appear. Select Disk Utility and click to enter.

mac1

After entering, you can see three disks and one image. Find the disk larger than 40G named QEMU HARDDISK Media, and click Erase.

mac2

A pop-up window will appear, requiring you to rename the name to macos for easy identification and use later, then click Erase to continue initialization.

mac3

After initialization is complete, click Done.

mac4

Now you need to exit the Disk Utility interface. Click Disk Utility in the upper right corner and select Quit Disk Utility to exit the current selection box.

mac5

Then you return to the previous four selection boxes. Select Install macOS XXXX (since I am using Big Sur as an example, XXXX is Big Sur), and click continue.

mac6

In the following steps, continue clicking continue, then click Agree, and then Agree again.

mac7

mac8

mac9

Until those three disks appear again, but here you can see the disk larger than 40G named macos. Select it and click continue.

mac10

After a period of file copying and disk loading (about 12 minutes), you will formally enter the system installation phase. Choose your region based on where the host machine is located.

mac11

After selecting the region, continue clicking continue.

mac12

mac13

Until the Migration Assistant data migration option appears, select Not Now in the lower left corner to not import user data.

mac14

Then you will be prompted to create a user. Fill in the username, account name, and login password. After setting up, click continue.

mac15

After that, you will continue clicking continue until the system installation is complete.

Network Configuration ​

Since the system installation was performed in an offline environment, you need to manually configure a static network connection to the host's bridge.

Click the WIFI button in the upper right corner, turn off WIFI, and then click Network Preferences ...

mac16

After entering the settings interface, click the Advanced button to enter the advanced settings interface.

mac17

Fill in the static network configuration in the TCP/IP tab.

Configure IPV4: Manually

IPV4 Address: 172.16.1.xxx (replace xxx with the IP you want to bind, my vmid is 100, so I wrote 100 for convenience)

Subnet Mask: 255.255.255.0

Router: 172.16.1.1

If you need to configure an IPV6 network, similar to the IPV4 settings above, you will need to fill in the public IPV6 address bound to the virtual machine (written in the Note box in the PVE panel), subnet mask 128, and the default gateway obtained by executing cat /usr/local/bin/pve_check_ipv6 on the host.

mac18

Fill in the static network DNS configuration in the DNS tab.

Generally, adding 8.8.8.8 and 1.1.1.1 is sufficient. For use in mainland China, use 114.114.114.114.

mac19

After filling in and applying, the top left of the settings will show that the network is connected.

mac20

Now, opening the default browser and visiting any website will allow you to access public network resources, proving that the network has worked.

Remove ISO ​

Manually click on the corresponding CD in the Hardware on the web side of ProxmoxVE and select Remove, then restart the VM and you can use it directly.

wk

Macos system is to uninstall opencore.iso and xxxx (the system image used for installation).iso, similar to the Windows system uninstallation of win image and virtio image in the example picture above.

+ \ No newline at end of file diff --git a/en/guide/pve/pve_precheck.html b/en/guide/pve/pve_precheck.html index e753e29b48..de0715d4b1 100644 --- a/en/guide/pve/pve_precheck.html +++ b/en/guide/pve/pve_precheck.html @@ -11,7 +11,7 @@ - + @@ -21,8 +21,8 @@
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Preface ​

The following is the introduction of the non-customized part, the customized part has its own corresponding introduction, do not get confused!

If there are unadapted merchants or machines welcome to contact @spiritlhl_bot, will try to support it sometime!

WARNING

Will change the network structure of the host, please make sure that the host can reset the system at any time and that there is no important data on the host before running it.

Feel free to give the project a Star for free support!-->https://github.com/oneclickvirt/pve

Various requirements ​

It is recommended that debian try to use the latest stable version of the system before use.

Do not use this set of scripts in the dynamic IP server (reboot the machine automatically switch the local IP server is not supported, reboot the machine after the IP does not automatically switch the support)

The one-click installation script of this project only adapts to Debian systems, non-Debian can not be installed through the APT source, the official only gives the image of Debian, other systems can only use the ISO installation, or use custom partitions and other ways to solve the problem in the FAQ partition.

  • System requirements: Debian 8+

TIP

It is recommended to install debian11 instead of debian12, because the latter is a beta version, and the debian11 installation is the stable version.

  • Hardware requirements: 2 cores 2G RAM x86_64 or arm architecture server hard disk at least 20G
  • Hardware requirements for KVM: VM-X or AMD-V support (some VPS and all Dedicated servers support).
  • If hardware or system requirements are not met, you can use incus to batch open LXC containers Jump

If you use IPV6 tunnels for IPV6 subnet attachment on the host, be sure to add the contents in the corresponding file when PVE is successfully installed but the gateway is not automatically set, and do not add IPV6 tunnels at the very beginning (without installing PVE).

Setting up virtual memory (SWAP) (optional, not required) ​

TIP

Memory to open some swap lest the machine blow up, if your host computer does not have enough memory and a lot of free hard disk.

Unit conversion: Enter 1024 to generate 1G SWAP-virtual memory, virtual memory takes up hard disk space, when the actual memory is not enough to use the virtual memory will automatically use the virtual memory for memory use, but then bring the IO high occupancy and CPU performance occupancy!

It is recommended to use only twice the size of the actual memory as virtual memory.

Command:

shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh

Detecting the environment ​

  • This project related scripts must be executed before the execution of this script to detect the environment, if it does not meet the requirements of the installation of PVE will not be able to use the subsequent scripts
  • Detection of the local IPV6 network configuration (with or without IPV6 can be installed, just query)
  • Detection of the hardware configuration meets the minimum requirements
  • Detection of the hardware environment can be nested virtualization KVM type of servers, can not be nested virtualization KVM can also open QEMU TCG server, performance is poor
  • Detect whether the system environment can be nested virtualization KVM type of server, can not be nested virtualization KVM can also open QEMU TCG server, performance is poor
  • can not be nested virtualization KVM servers do not recommend the installation of the PVE, it is better to use incus for better performance.

Command:

bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh)

If you need to update the IPV6 information before querying, then execute the following command before querying

bash
rm -rf /usr/local/bin/pve_ipv6*
 rm -rf /usr/local/bin/pve_check_ipv6*
-rm -rf /usr/local/bin/pve_last_ipv6*

Commands to set up the testing environment for executing this project are as follows:

图片

To perform the above-mentioned query, you only need to use the one-click script below to automatically create a virtual machine. There is no need to manually modify settings on the web interface.

图片

After creating the virtual machines using the subsequent script as mentioned above, it may be necessary to manually modify the settings on the web interface. You will need to disable hardware nested virtualization for each respective virtual machine, as shown in the following diagram.

图片

Stop the virtual machine before making modifications. After the modifications are done, you can start the machine to use NOVNC. Failure to close it may result in bugs that render this virtual machine unusable.

If you forcibly install PVE to enable KVM, even if the startup fails, you can also disable this option and try to start the virtual machine to see if it works.

The reason for these issues is what was stated above, the host does not support nested virtualized KVMs for acceleration.

TIP

Please use the "screen" command to suspend execution before launching the virtual machine, in order to avoid prolonged startup times. Unstable SSH connections could lead to interruptions during the intermediate execution.



- +rm -rf /usr/local/bin/pve_last_ipv6*

Commands to set up the testing environment for executing this project are as follows:

图片

To perform the above-mentioned query, you only need to use the one-click script below to automatically create a virtual machine. There is no need to manually modify settings on the web interface.

图片

After creating the virtual machines using the subsequent script as mentioned above, it may be necessary to manually modify the settings on the web interface. You will need to disable hardware nested virtualization for each respective virtual machine, as shown in the following diagram.

图片

Stop the virtual machine before making modifications. After the modifications are done, you can start the machine to use NOVNC. Failure to close it may result in bugs that render this virtual machine unusable.

If you forcibly install PVE to enable KVM, even if the startup fails, you can also disable this option and try to start the virtual machine to see if it works.

The reason for these issues is what was stated above, the host does not support nested virtualized KVMs for acceleration.

TIP

Please use the "screen" command to suspend execution before launching the virtual machine, in order to avoid prolonged startup times. Unstable SSH connections could lead to interruptions during the intermediate execution.



+ \ No newline at end of file diff --git a/en/guide/pve/pve_qa.html b/en/guide/pve/pve_qa.html index 7d9246dd2d..83ae09eaf0 100644 --- a/en/guide/pve/pve_qa.html +++ b/en/guide/pve/pve_qa.html @@ -11,7 +11,7 @@ - + @@ -31,8 +31,8 @@ iptables -t filter -F service networking restart systemctl restart networking.service -cat /etc/iptables/rules.v4 | iptables-restore

Adding a New Node to an Existing PVE Cluster (Create / Join Cluster) ​

To form a cluster from two independent Proxmox VE instances, the following prerequisites must be met:

Cluster Prerequisites ​

  1. Unique Hostnames
    The hostname of each node must be unique to avoid conflicts. It is recommended to use names like pve1, pve2, etc.

  2. Unique VMIDs
    There must be no duplicate VMIDs across the two PVE nodes. If conflicts exist, adjust the VMIDs beforehand to prevent issues during cluster merge.

  3. Network Connectivity & Low Latency
    Both nodes must be able to ping each other. A low-latency network (LAN or high-speed public connection) is recommended for reliable cluster communication.

Creating the Cluster (Run on Any Node) ​

  1. Log in to the web interface of the node where the cluster will be created (e.g., pve1).
  2. Navigate to: Datacenter → Cluster → Create Cluster.
  3. Enter a name for the cluster (Cluster Name).
  4. Select the network interface to be used for cluster communication (e.g., public IP if only one interface is available).
  5. Click Create to initialize the cluster.
  6. Once the cluster is created, click Join Information and copy the displayed information for use on the joining node.

Note: The cluster has no "master" or "slave" nodes—any node can be the one that initiates the cluster.

Joining the Cluster (Run on the Second Node) ​

  1. Log in to the web interface of the node to be added (e.g., pve2).
  2. Navigate to: Datacenter → Cluster → Join Cluster.
  3. Paste the Join Information from pve1 into the input field.
  4. Enter the password of root user on pve1 in the Peer Password field.
  5. Click Join to begin the joining process.
  6. Wait until the process completes successfully, then refresh the page or re-login. You should now see both nodes in the same cluster.

Cluster Benefits ​

Verified VPS Providers ​

VPS Providers Offering KVM Virtualization with NAT ​

spartanhost Debian12 on a Dedicated Server (Debian11 has problems)

interserver VPS or dedicated servers

frantech Las Vegas Tier 2

eugamehost US Phoenix Black Friday Special

amhost Testing version

digitalocean Perminu Intel and Regular 4-core versions

skrime Lowest configuration of AMD Ryzen KVM Server

webdock AMD KVM Server

4vps Russian and Greek testing versions

adtaq Storage KVM server with lowest configuration

nocix Dedicated servers

online.net Debian12 on a Dedicated Server (Debian11 has problems)

OVH Public Cloud needs to be installed after dd as a pure system using the following command

shell
bash <(curl -sSL https://raw.githubusercontent.com/leitbogioro/Tools/master/Linux_reinstall/InstallNET.sh) -debian 12 -pwd ' oneclickvirt139' --network "static"

At this point, the system username after dd is root, and the password is oneclickvirt139.

If it doesn't work, please check the issues and instructions in https://github.com/leitbogioro/Tools. A common problem is that OVH standalone servers are dd'd, which requires the source system to be remounted as raid1 on debian12 by default, and then parameterized to specify dd'd as raid0 in order to be successful, using the following command

shell
wget --no-check-certificate -qO InstallNET.sh 'https://raw.githubusercontent.com/leitbogioro/Tools/master/Linux_reinstall/InstallNET.sh' && chmod a+x InstallNET.sh && bash InstallNET.sh -debian 12  -mirror "http://ftp.debian.org/debian/" -pwd oneclickvirt139 -raid 0

VPS Providers Offering NAT with LXC Virtualization ​

Tencent Cloud Worry-Free and Student editions

spectraip KVM servers

Linode Lowest configuration with dedicated CPU

hosthatch Special high-configuration servers

hetzner Cloud servers

rackdog Servers with floating IP

vultr Standard Cloud servers

azure Standard machines

scaleway ARM architecture servers

aws EC2 servers

Google cloud platform - GCP AMD servers

- +cat /etc/iptables/rules.v4 | iptables-restore

Adding a New Node to an Existing PVE Cluster (Create / Join Cluster) ​

To form a cluster from two independent Proxmox VE instances, the following prerequisites must be met:

Cluster Prerequisites ​

  1. Unique Hostnames
    The hostname of each node must be unique to avoid conflicts. It is recommended to use names like pve1, pve2, etc.

  2. Unique VMIDs
    There must be no duplicate VMIDs across the two PVE nodes. If conflicts exist, adjust the VMIDs beforehand to prevent issues during cluster merge.

  3. Network Connectivity & Low Latency
    Both nodes must be able to ping each other. A low-latency network (LAN or high-speed public connection) is recommended for reliable cluster communication.

Creating the Cluster (Run on Any Node) ​

  1. Log in to the web interface of the node where the cluster will be created (e.g., pve1).
  2. Navigate to: Datacenter → Cluster → Create Cluster.
  3. Enter a name for the cluster (Cluster Name).
  4. Select the network interface to be used for cluster communication (e.g., public IP if only one interface is available).
  5. Click Create to initialize the cluster.
  6. Once the cluster is created, click Join Information and copy the displayed information for use on the joining node.

Note: The cluster has no "master" or "slave" nodes—any node can be the one that initiates the cluster.

Joining the Cluster (Run on the Second Node) ​

  1. Log in to the web interface of the node to be added (e.g., pve2).
  2. Navigate to: Datacenter → Cluster → Join Cluster.
  3. Paste the Join Information from pve1 into the input field.
  4. Enter the password of root user on pve1 in the Peer Password field.
  5. Click Join to begin the joining process.
  6. Wait until the process completes successfully, then refresh the page or re-login. You should now see both nodes in the same cluster.

Cluster Benefits ​

Verified VPS Providers ​

VPS Providers Offering KVM Virtualization with NAT ​

spartanhost Debian12 on a Dedicated Server (Debian11 has problems)

interserver VPS or dedicated servers

frantech Las Vegas Tier 2

eugamehost US Phoenix Black Friday Special

amhost Testing version

digitalocean Perminu Intel and Regular 4-core versions

skrime Lowest configuration of AMD Ryzen KVM Server

webdock AMD KVM Server

4vps Russian and Greek testing versions

adtaq Storage KVM server with lowest configuration

nocix Dedicated servers

online.net Debian12 on a Dedicated Server (Debian11 has problems)

OVH Public Cloud needs to be installed after dd as a pure system using the following command

shell
bash <(curl -sSL https://raw.githubusercontent.com/leitbogioro/Tools/master/Linux_reinstall/InstallNET.sh) -debian 12 -pwd ' oneclickvirt139' --network "static"

At this point, the system username after dd is root, and the password is oneclickvirt139.

If it doesn't work, please check the issues and instructions in https://github.com/leitbogioro/Tools. A common problem is that OVH standalone servers are dd'd, which requires the source system to be remounted as raid1 on debian12 by default, and then parameterized to specify dd'd as raid0 in order to be successful, using the following command

shell
wget --no-check-certificate -qO InstallNET.sh 'https://raw.githubusercontent.com/leitbogioro/Tools/master/Linux_reinstall/InstallNET.sh' && chmod a+x InstallNET.sh && bash InstallNET.sh -debian 12  -mirror "http://ftp.debian.org/debian/" -pwd oneclickvirt139 -raid 0

VPS Providers Offering NAT with LXC Virtualization ​

Tencent Cloud Worry-Free and Student editions

spectraip KVM servers

Linode Lowest configuration with dedicated CPU

hosthatch Special high-configuration servers

hetzner Cloud servers

rackdog Servers with floating IP

vultr Standard Cloud servers

azure Standard machines

scaleway ARM architecture servers

aws EC2 servers

Google cloud platform - GCP AMD servers

+ \ No newline at end of file diff --git a/en/guide/pve/pve_thanks.html b/en/guide/pve/pve_thanks.html index 8817a6fdf3..69a38add3a 100644 --- a/en/guide/pve/pve_thanks.html +++ b/en/guide/pve/pve_thanks.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
One Click Virtualization

English

简体中文

English

简体中文

Appearance

- +
One Click Virtualization

English

简体中文

English

简体中文

Appearance

+ \ No newline at end of file diff --git a/en/guide/pve/pve_windows.html b/en/guide/pve/pve_windows.html index 6a10e41cc2..f48d322a5f 100644 --- a/en/guide/pve/pve_windows.html +++ b/en/guide/pve/pve_windows.html @@ -12,7 +12,7 @@ - + @@ -21,8 +21,8 @@
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Setting Up Windows Visual Machine ​

Using ISO Image with VirtIO for VM Setup ​

1. Download the Image ​

Before installation, you need to download the image file via local(pve) --> ISO images --> Download from URL

For the download link (URL:), you can use files from: https://github.com/ILLKX/Windows-VirtIO

Enter win.iso as the File Name:

download

Click Download. After downloading is complete, you can see the file size of win.iso on the current page, confirming it's in ISO format.

downloaded

2. Setting Up the Template ​

Click Create VM in the top right corner of the page.

In the General window, select mypool for Resource Pool:, enter win for Name, then click Next.

general

In the OS window, select win.iso for ISO image. For Guest OS, select Microsoft Windows as the Type and choose the appropriate Version for your ISO. For example, if you downloaded Windows 2022, select 11/2022, then click Next.

OS

In the System window, select VirtIO-GPU for Graphic card, q35 for Machine, VirtIO SCSI for SCSI Controller, and Default (SeaBIOS) for BIOS, then click Next.

system

In the Disk window, select Write Back for Cache, enter your desired disk size in Disk size (GiB) (generally not less than 20), and choose the storage location in Storage. In this example, only the system disk local is available, so local is selected. Then click Next.

disk

In the CPU window, enter the number of cores needed in Cores, then click Next.

cpu

In the Memory window, enter the desired memory size in Memory (MiB), then click Next.

memory

In the Network window, select vmbr1 for Bridge, VirtIO (paravirtualized) for Model, uncheck Firewall, then click Next.

Network

In the Confirm window, click Finish.

finish

3. Graphical Installation Configuration ​

Click on the template you've set up on the left, click Start in the upper right corner to start the virtual machine, then click Console to enter the VNC interface and wait for the operating system to boot.

console

In the VNC, click Next, then Install now, then I don't have a product key, check Accept license, click Next, and then select Custom installation.

win0win1win2win3win4

If the image comes with VirtIO drivers, you should be able to see the available system storage disk and its size. Select it and click Next.

win5win6

Wait for the system to install. It may restart automatically several times and could take more than 10 minutes.

win7

After installation is complete, you'll be asked to set a password during first login.

win8

Once setup is complete, there's a pop-up box on the left side of the NOVNC page. Click the first button, then follow the login prompt by pressing Ctrl+Alt+last button to enter the login page.

4. Network Initialization ​

Since the PVE is set up with a static network through this project, you need to manually modify the bound IP address after logging in, rather than using DHCP.

Right-click in the bottom right corner of the desktop and select Open Network and Internet settings. In the settings page that appears, click Change adapter options. win9

In the Network Connections, select Ethernet and click Change settings of this connection. win10

In the popup window, select Internet Protocol Version 4 (TCP/IPv4) and click Properties. win11

In the new dialog box, select Use the following IP address and enter: IP address(I): 172.16.1.xxx (replace xxx with your desired IP, I used 100 for convenience as my vmid is 100) Subnet mask(U): 255.255.255.0 Default gateway(D): 172.16.1.1

Then select Use the following DNS server addresses and enter:

8.8.8.8
-144.144.144.144

Click OK in the bottom right corner, and make sure Validate settings upon exit is NOT checked.

win12

Click OK and Yes for any other dialog boxes, and your virtual machine will now have network connectivity.

5. Unmounting the CD Drive ​

Manually click on the corresponding CD in the Hardware on the web side of ProxmoxVE and select Remove, then restart the VM and you can use it directly.

wk

Using ISO Images without VirtIO for VM Installation ​

1. Download Images ​

For Windows images without VirtIO, you can use:

https://down.idc.wiki/ISOS/Windows/

For VirtIO ISO images, you can use:

https://down.idc.wiki/ISOS/Toolkit/

or

https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/

Alternatively, you can download just the MSI package, package it into an ISO format locally, and then upload it to ProxmoxVE.

This way, the package is smaller. The official package contains support for all Windows images and is about 500MB, while a self-packaged one is around 5MB.

2. VirtIO Import ​

Note that in ProxmoxVE version 8.x and later, you can select VirtIO boot loading by default in the OS section, as shown in the image:

virtio

In lower versions of ProxmoxVE, such as 7.x and 6.x, you cannot select VirtIO boot loading by default in the OS section:

lower

You need to manually add CD/DVD Drive by clicking Add in the Hardware section and selecting the downloaded VirtIO ISO file:

lower

Then proceed as usual until you reach:

nodisk

At this point, you can't find the hard disk. You need to select Load Driver:

nodisk

Then select the VirtIO as your driver disk, click open, and import the corresponding system driver from the amd64 directory:

nodisk

I'm using a Windows Server 2019 image, so I imported the 2k19 driver. After importing, select the imported driver and click Next:

nodisk

nodisk

Now you should be able to see the hard disk. Select it and continue with the installation steps as in the previous tutorial until the system installation is complete and you reach the desktop.

3. Installing Drivers via virtio-win-guest-tools ​

Once successfully installed and at the desktop, you still need to manually install the drivers.

Open the VirtIO driver's CD drive directory. At the bottom, there's a virtio-win-guest-tools program that will install the required VirtIO drivers, including the VirtIO network card driver:

wk

wk

wk

After clicking install, the network card driver will be installed. For subsequent network settings, refer to the network initialization tutorial mentioned earlier.

4. Installing Network Card Driver (Alternative) ​

After successful installation and reaching the desktop, you may still need to manually install the network card driver to connect to the network:

  1. Open Control Panel → Device Manager
  2. Find the Ethernet Controller, right-click and select Update Driver
  3. Select Browse my computer for driver software (R)
  4. Browse to the VirtIO driver's CD drive directory
  5. Open the NetKVM folder
  6. Select the driver folder corresponding to your current system version (like the above operation, I would choose the 2k19 folder with amd64 drivers)
  7. Confirm the installation, and after completion, the VirtIO network card driver will be successfully loaded

wk

wk

wk

For subsequent network settings, refer to the network initialization tutorial mentioned earlier.

5. Unmounting the CD Drive ​

In the ProxmoxVE web interface, manually click on the corresponding CD in the Hardware section, select Remove, and then restart the virtual machine. This way, you can use it directly:

wk

- +144.144.144.144

Click OK in the bottom right corner, and make sure Validate settings upon exit is NOT checked.

win12

Click OK and Yes for any other dialog boxes, and your virtual machine will now have network connectivity.

5. Unmounting the CD Drive ​

Manually click on the corresponding CD in the Hardware on the web side of ProxmoxVE and select Remove, then restart the VM and you can use it directly.

wk

Using ISO Images without VirtIO for VM Installation ​

1. Download Images ​

For Windows images without VirtIO, you can use:

https://down.idc.wiki/ISOS/Windows/

For VirtIO ISO images, you can use:

https://down.idc.wiki/ISOS/Toolkit/

or

https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/

Alternatively, you can download just the MSI package, package it into an ISO format locally, and then upload it to ProxmoxVE.

This way, the package is smaller. The official package contains support for all Windows images and is about 500MB, while a self-packaged one is around 5MB.

2. VirtIO Import ​

Note that in ProxmoxVE version 8.x and later, you can select VirtIO boot loading by default in the OS section, as shown in the image:

virtio

In lower versions of ProxmoxVE, such as 7.x and 6.x, you cannot select VirtIO boot loading by default in the OS section:

lower

You need to manually add CD/DVD Drive by clicking Add in the Hardware section and selecting the downloaded VirtIO ISO file:

lower

Then proceed as usual until you reach:

nodisk

At this point, you can't find the hard disk. You need to select Load Driver:

nodisk

Then select the VirtIO as your driver disk, click open, and import the corresponding system driver from the amd64 directory:

nodisk

I'm using a Windows Server 2019 image, so I imported the 2k19 driver. After importing, select the imported driver and click Next:

nodisk

nodisk

Now you should be able to see the hard disk. Select it and continue with the installation steps as in the previous tutorial until the system installation is complete and you reach the desktop.

3. Installing Drivers via virtio-win-guest-tools ​

Once successfully installed and at the desktop, you still need to manually install the drivers.

Open the VirtIO driver's CD drive directory. At the bottom, there's a virtio-win-guest-tools program that will install the required VirtIO drivers, including the VirtIO network card driver:

wk

wk

wk

After clicking install, the network card driver will be installed. For subsequent network settings, refer to the network initialization tutorial mentioned earlier.

4. Installing Network Card Driver (Alternative) ​

After successful installation and reaching the desktop, you may still need to manually install the network card driver to connect to the network:

  1. Open Control Panel → Device Manager
  2. Find the Ethernet Controller, right-click and select Update Driver
  3. Select Browse my computer for driver software (R)
  4. Browse to the VirtIO driver's CD drive directory
  5. Open the NetKVM folder
  6. Select the driver folder corresponding to your current system version (like the above operation, I would choose the 2k19 folder with amd64 drivers)
  7. Confirm the installation, and after completion, the VirtIO network card driver will be successfully loaded

wk

wk

wk

For subsequent network settings, refer to the network initialization tutorial mentioned earlier.

5. Unmounting the CD Drive ​

In the ProxmoxVE web interface, manually click on the corresponding CD in the Hardware section, select Remove, and then restart the virtual machine. This way, you can use it directly:

wk

+ \ No newline at end of file diff --git a/en/incomplete/bashvm.html b/en/incomplete/bashvm.html index a34a4435c1..efb75582eb 100644 --- a/en/incomplete/bashvm.html +++ b/en/incomplete/bashvm.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Repo ​

https://github.com/babywhale321/bashvm

https://bashvm.com/

Description ​

If you want to go deeper into how to open a VM and how to forward ports, then this program will start completely from the bottom and teach you step by step how to open a VM!

Disadvantages ​

Very tedious and time consuming, not as fast as other programs to set up a network and open a VM

- +
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Repo ​

https://github.com/babywhale321/bashvm

https://bashvm.com/

Description ​

If you want to go deeper into how to open a VM and how to forward ports, then this program will start completely from the bottom and teach you step by step how to open a VM!

Disadvantages ​

Very tedious and time consuming, not as fast as other programs to set up a network and open a VM

+ \ No newline at end of file diff --git a/en/incomplete/cockpit.html b/en/incomplete/cockpit.html index fe22d7100a..6a73607d45 100644 --- a/en/incomplete/cockpit.html +++ b/en/incomplete/cockpit.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Repo ​

hits

https://github.com/oneclickvirt/cockpit

Installation ​

Supported Systems: Debian，Ubuntu，Almalinux，Rockylinux，Fedora，Centos，Arch

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh

Install only with Podman containers

shell
bash install.sh --ct

Install only with virtual machines

shell
bash install.sh --vm

Panel Mount Only

shell
bash install.sh

Both container and VM dependencies are installed

shell
bash install.sh --all

Disadvantages ​

The network is self-configuring, the mirrors are self-importing, the ports are self-mapped, and there is just one more GUI interface than the command line.

Thanks ​

https://cockpit-project.org/running.html

- +
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Repo ​

hits

https://github.com/oneclickvirt/cockpit

Installation ​

Supported Systems: Debian，Ubuntu，Almalinux，Rockylinux，Fedora，Centos，Arch

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh

Install only with Podman containers

shell
bash install.sh --ct

Install only with virtual machines

shell
bash install.sh --vm

Panel Mount Only

shell
bash install.sh

Both container and VM dependencies are installed

shell
bash install.sh --all

Disadvantages ​

The network is self-configuring, the mirrors are self-importing, the ports are self-mapped, and there is just one more GUI interface than the command line.

Thanks ​

https://cockpit-project.org/running.html

+ \ No newline at end of file diff --git a/en/incomplete/convoy.html b/en/incomplete/convoy.html index eb58a8cf67..cb8b515e86 100644 --- a/en/incomplete/convoy.html +++ b/en/incomplete/convoy.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Repo ​

https://github.com/oneclickvirt/convoypanel-scripts

hits

convoypanel-scripts ​

One-click installation of convoy panel ​

Prerequisites for installation:

  • PVE is installed, but not the same node(not the same machine)
  • System is debian 11
  • CPU at least 2 cores, hard disk at least 20G, memory at least 4G (memory covers swap)

I don't guarantee that this script is error-free, it's just for my own amusement.

shell
curl -L https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh

Thanks ​

Base on https://github.com/oneclickvirt/pve

Base on https://docs.convoypanel.com/guide/deployment/#installation

Base on https://github.com/ConvoyPanel/panel

- +
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Repo ​

https://github.com/oneclickvirt/convoypanel-scripts

hits

convoypanel-scripts ​

One-click installation of convoy panel ​

Prerequisites for installation:

  • PVE is installed, but not the same node(not the same machine)
  • System is debian 11
  • CPU at least 2 cores, hard disk at least 20G, memory at least 4G (memory covers swap)

I don't guarantee that this script is error-free, it's just for my own amusement.

shell
curl -L https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh

Thanks ​

Base on https://github.com/oneclickvirt/pve

Base on https://docs.convoypanel.com/guide/deployment/#installation

Base on https://github.com/ConvoyPanel/panel

+ \ No newline at end of file diff --git a/en/incomplete/index.html b/en/incomplete/index.html index baef2a0284..6a133cfaba 100644 --- a/en/incomplete/index.html +++ b/en/incomplete/index.html @@ -11,7 +11,7 @@ - + @@ -20,7 +20,7 @@
One Click Virtualization

English

简体中文

English

简体中文

Appearance

Other Virtualization Projects

Some incomplete virtualization projects

View Projects →

Notes

Each item in this block has a corresponding drawback, and each item is not as easy to use as the previous ones, and has a certain learning cost.

Degree of difficulty

Based on the difficulty of using the program itself, sorted from easiest to hardest, the further back you go the less guidance you'll get with this guide.

Project disadvantages

Each project has some drawbacks that result in it not being considered a complete one-click project, and there are some operations that require manual execution of commands that cannot be one-clicked.

- + \ No newline at end of file diff --git a/en/incomplete/pterodactyl.html b/en/incomplete/pterodactyl.html index 6d08b5227c..2c73dd2cf5 100644 --- a/en/incomplete/pterodactyl.html +++ b/en/incomplete/pterodactyl.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Repo ​

https://github.com/oneclickvirt/pterodactyl

hits

pterodactyl-scripts ​

After further research, it was found that creating servers and binding users is too cumbersome compared to using native Docker directly, so further development is currently suspended.

Description ​

Currently supported systems:

OS TypeVersion RangeNotes
Ubuntu20.04 (recommended), 22.04, 24.04Supported
Debian11 (Bullseye), 12 (Bookworm)Supported

Panel ​

On the panel side, run:

shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh

Wings ​

On the wings side, run:

shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh

Import ​

On the panel side, run:

shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh

This will generate a command to be executed on the wings side.

After executing the generated command, wait for more than 20 seconds to avoid issues caused by unfinished initialization processes. Then on the wings side, run:

shell
bash install_wings.sh

Then go to http://<your_ip>/admin/nodes and you should see your node has been automatically added and managed, with a green heartbeat.

Thanks ​

https://pterodactyl.io/

- +
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Repo ​

https://github.com/oneclickvirt/pterodactyl

hits

pterodactyl-scripts ​

After further research, it was found that creating servers and binding users is too cumbersome compared to using native Docker directly, so further development is currently suspended.

Description ​

Currently supported systems:

OS TypeVersion RangeNotes
Ubuntu20.04 (recommended), 22.04, 24.04Supported
Debian11 (Bullseye), 12 (Bookworm)Supported

Panel ​

On the panel side, run:

shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh

Wings ​

On the wings side, run:

shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh

Import ​

On the panel side, run:

shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh

This will generate a command to be executed on the wings side.

After executing the generated command, wait for more than 20 seconds to avoid issues caused by unfinished initialization processes. Then on the wings side, run:

shell
bash install_wings.sh

Then go to http://<your_ip>/admin/nodes and you should see your node has been automatically added and managed, with a green heartbeat.

Thanks ​

https://pterodactyl.io/

+ \ No newline at end of file diff --git a/en/incomplete/virtfusion.html b/en/incomplete/virtfusion.html index af195d9919..c918f1faaf 100644 --- a/en/incomplete/virtfusion.html +++ b/en/incomplete/virtfusion.html @@ -11,7 +11,7 @@ - + @@ -25,8 +25,8 @@ curl https://install.virtfusion.net/install-control-rhel-8.sh | sh -s -- --verbose

RHEL9

shell
dnf install curl -y
 curl https://install.virtfusion.net/install-control-rhel-9.sh | sh -s -- --verbose

Ubuntu22.04

shell
apt install curl -y
 curl https://install.virtfusion.net/install-control-ubuntu-22.04.sh | sh -s -- --verbose

Ubuntu24.04

shell
apt install curl -y
-curl https://install.virtfusion.net/install-control-ubuntu-24.04.sh | sh -s -- --verbose

Disadvantages ​

Only one 30-day trial certificate per server per mailbox, no permanent free certificates

- +curl https://install.virtfusion.net/install-control-ubuntu-24.04.sh | sh -s -- --verbose

Disadvantages ​

Only one 30-day trial certificate per server per mailbox, no permanent free certificates

+ \ No newline at end of file diff --git a/en/incomplete/virtualizor-docker.html b/en/incomplete/virtualizor-docker.html index 7818f93f41..a006641cb5 100644 --- a/en/incomplete/virtualizor-docker.html +++ b/en/incomplete/virtualizor-docker.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Repo ​

https://github.com/ivstiv/virtualizor-docker

Description ​

The virtualizor opened in the docker

The certificate used is a trial certificate, valid for one day, and only the OpenVZ virtualization method is installed by default

Disadvantages ​

There is no community, so you have to figure it out on your own.

Ports for admin panel Don't look at the script's prompt messages, go with the repository instructions.

- +
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

Repo ​

https://github.com/ivstiv/virtualizor-docker

Description ​

The virtualizor opened in the docker

The certificate used is a trial certificate, valid for one day, and only the OpenVZ virtualization method is installed by default

Disadvantages ​

There is no community, so you have to figure it out on your own.

Ports for admin panel Don't look at the script's prompt messages, go with the repository instructions.

+ \ No newline at end of file diff --git a/en/incomplete/webvirtcloud.html b/en/incomplete/webvirtcloud.html index 9031cf0aee..c5b0cc2a4f 100644 --- a/en/incomplete/webvirtcloud.html +++ b/en/incomplete/webvirtcloud.html @@ -11,7 +11,7 @@ - + @@ -63,8 +63,8 @@ systemctl status prometheus-libvirt-exporter

If none of the above reveals the problem, then you need to execute on the Controller:

shell
docker exec -it webvirtcloud-backend /bin/sh
 vi webvirtcloud/settings/production.py

Change DEBUG=False to DEBUG=True, save the file, then execute in the container:

shell
UV_PROJECT_ENVIRONMENT=/usr/local uv sync --dev

Then exit the container and execute:

shell
docker restart webvirtcloud-backend
 sleep 3
-docker logs webvirtcloud-backend -f

Then trigger the error in the frontend, and you'll see the corresponding error in the real-time loaded logs.

Docker Containers Not Auto-Restarting After Controller Reboot ​

If Docker containers don't automatically restart after system reboot, execute:

bash
docker start $(docker ps -a -q)

5. Drawbacks ​

System images are hard-coded; you can't use your own custom images, nor export them for use.

This is not the same project as https://github.com/retspen/webvirtcloud, don't confuse them.

Acknowledgements ​

https://webvirt.cloud/

- +docker logs webvirtcloud-backend -f

Then trigger the error in the frontend, and you'll see the corresponding error in the real-time loaded logs.

Docker Containers Not Auto-Restarting After Controller Reboot ​

If Docker containers don't automatically restart after system reboot, execute:

bash
docker start $(docker ps -a -q)

5. Drawbacks ​

System images are hard-coded; you can't use your own custom images, nor export them for use.

This is not the same project as https://github.com/retspen/webvirtcloud, don't confuse them.

Acknowledgements ​

https://webvirt.cloud/

+ \ No newline at end of file diff --git a/en/incomplete/webvirtcloud_retspen.html b/en/incomplete/webvirtcloud_retspen.html index 4fde7c6d4a..4dc732b852 100644 --- a/en/incomplete/webvirtcloud_retspen.html +++ b/en/incomplete/webvirtcloud_retspen.html @@ -11,7 +11,7 @@ - + @@ -23,8 +23,8 @@ && chmod +x install_webvirt_cloud_retspen.sh \ && bash install_webvirt_cloud_retspen.sh

After installation is complete, open the public IP address to access the login page.

The default login username and password are both admin. Make sure to change them after logging in.

Creating a Linux Virtual Machine ​

After entering the control panel and changing the admin password, you need to manually configure a compute node.

vcr1

Select the type as Local, and name it local.

vcr2

After creation, click the eye icon to enter the view.

vcr3

Under the Storage section, add a storage entry. Choose the type Dir and name it local. If you need to use an ISO for system boot, you’ll need to create a storage of type ISO. If not, just follow this guide and create only the Dir type.

vcr4

vcr5

After creation, download the appropriate qcow2 image for the system using the repository below:

https://github.com/oneclickvirt/pve_kvm_images/releases/tag/images

In the example, a Debian 12 qcow2 image is used:

shell
cd /var/lib/libvirt/images
 wget https://github.com/oneclickvirt/pve_kvm_images/releases/download/images/debian12.qcow2
-chmod 777 debian12.qcow2

Return to the instance page to create a new instance.

vcr6

Select local as the compute node.

vcr7

The default chipset is fine; changing it is optional.

vcr8

You can use predefined sizes for the virtual machine or customize it, depending on your preference.

vcr9

Note: the instance name must not duplicate the system name. For example, you cannot use debian12 as the instance name in this case.

vcr10

After successful creation, do not power it on immediately.

vcr11

You need to modify the disk settings first.

vcr12

Change the disk file to debian12.qcow2, which matches the qcow2 image you previously downloaded.

vcr13

Once confirmed and configured correctly, return to the power page and turn on the VM.

vcr14

The default login for the image is:

Disadvantages ​

Networking is not auto-configured — not as smart as the previous project — you still need to configure it manually.

- +chmod 777 debian12.qcow2

Return to the instance page to create a new instance.

vcr6

Select local as the compute node.

vcr7

The default chipset is fine; changing it is optional.

vcr8

You can use predefined sizes for the virtual machine or customize it, depending on your preference.

vcr9

Note: the instance name must not duplicate the system name. For example, you cannot use debian12 as the instance name in this case.

vcr10

After successful creation, do not power it on immediately.

vcr11

You need to modify the disk settings first.

vcr12

Change the disk file to debian12.qcow2, which matches the qcow2 image you previously downloaded.

vcr13

Once confirmed and configured correctly, return to the power page and turn on the VM.

vcr14

The default login for the image is:

Disadvantages ​

Networking is not auto-configured — not as smart as the previous project — you still need to configure it manually.

+ \ No newline at end of file diff --git a/en/incomplete/webvirtmgr.html b/en/incomplete/webvirtmgr.html index 78a8670357..e09d8203b9 100644 --- a/en/incomplete/webvirtmgr.html +++ b/en/incomplete/webvirtmgr.html @@ -11,7 +11,7 @@ - + @@ -21,8 +21,8 @@
One Click Virtualization

English

简体中文

English

简体中文

Appearance

On this page

WebVirtMgr Installation Guide ​

hits

Repository: https://github.com/oneclickvirt/webvirtcloud

Origin Repository: https://github.com/retspen/webvirtmgr

Control nodes and compute nodes installed at the same time ​

  • Supported systems: Debian[8,9,10]，Ubuntu[16.04,18.04,20.04]
  • The system will automatically compile python 2.7 installer and then deployed, there will be an error in the compilation process but do not pay attention to it, as long as the scripts are still running, it means that everything is fine!
bash
curl -slk https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirtmgr.sh -o install_webvirtmgr.sh \
 && chmod +x install_webvirtmgr.sh \
-&& bash install_webvirtmgr.sh

Disadvantages ​

The origin project is no longer maintained and is not recommended at all.

- +&& bash install_webvirtmgr.sh

Disadvantages ​

The origin project is no longer maintained and is not recommended at all.

+ \ No newline at end of file diff --git a/en/index.html b/en/index.html index 572ccc804d..923fe6bb1e 100644 --- a/en/index.html +++ b/en/index.html @@ -11,7 +11,7 @@ - + @@ -20,7 +20,7 @@
One Click Virtualization

English

简体中文

English

简体中文

Appearance

One Click Virtualization

Open source, easy to use server virtualization project

Learn More →

One Click Use

Supports one-click command installation and use, easy to create virtual machines or containers on X86_64 and ARM architecture servers

Based on mainstream systems development

Based on long-term maintenance releases of Debian, Ubuntu, Centos, etc., there is always a way to virtualize containers or virtual machines, no matter what the system is.

Port forwarding and IP assignment automation

Self-contained internal and external port forwarding and automatic IP address allocation (including IPV6、IPV4), including TCP, UDP, VNC, RDP and other protocols, without manual management

Batch Virtualization

Supports batch opening of containers or virtual machines using KVM, LXC, Docker virtualization

Multi-system and multi-environment support

Open containers or virtual machines that support mainstream systems, including Linux, Windows, MacOS, Android as well as pure browser or desktop environments.

Self-limiting abuse

Some virtualized containers or VMs support the setting of masks and loading limits to avoid being used for abuse.

FAQ

All questions and problems that may arise during the program are answered.

Development thanks

Thanks to Evolution Host for supporting us with a DDoS protected VPS

- + \ No newline at end of file diff --git a/guide/block/block_docker.html b/guide/block/block_docker.html index 8bfb68b61b..5d90c3f4d5 100644 --- a/guide/block/block_docker.html +++ b/guide/block/block_docker.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

待开发，敬请期待 ​

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

待开发，敬请期待 ​

+ \ No newline at end of file diff --git a/guide/block/block_incus.html b/guide/block/block_incus.html index 714c0ce33b..603669eddf 100644 --- a/guide/block/block_incus.html +++ b/guide/block/block_incus.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

通过shell脚本屏蔽滥用行为 ​

屏蔽容易被滥用的端口的出入流量以屏蔽端口和屏蔽滥用工具包 ​

  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事前预防

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh

使用screen配置监控屏蔽某些进程的执行遇到某些进程的出现直接关闭容器 ​

  • 如需停止监控可使用screen命令停止lxc_moniter这个名字的窗口并删除
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事后停机

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

通过shell脚本屏蔽滥用行为 ​

屏蔽容易被滥用的端口的出入流量以屏蔽端口和屏蔽滥用工具包 ​

  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事前预防

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh

使用screen配置监控屏蔽某些进程的执行遇到某些进程的出现直接关闭容器 ​

  • 如需停止监控可使用screen命令停止lxc_moniter这个名字的窗口并删除
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事后停机

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
+ \ No newline at end of file diff --git a/guide/block/block_iptables.html b/guide/block/block_iptables.html index 397acf0883..74852d3e96 100644 --- a/guide/block/block_iptables.html +++ b/guide/block/block_iptables.html @@ -11,7 +11,7 @@ - + @@ -72,8 +72,8 @@ for str in "${strings[@]}"; do iptables -A OUTPUT -m string --string "$str" --algo bm -j DROP -done - +done + \ No newline at end of file diff --git a/guide/block/block_lxd.html b/guide/block/block_lxd.html index 31d4fc5089..cedfaef548 100644 --- a/guide/block/block_lxd.html +++ b/guide/block/block_lxd.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

通过shell脚本屏蔽滥用行为 ​

屏蔽容易被滥用的端口的出入流量以屏蔽端口和屏蔽滥用工具包 ​

  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事前预防

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh

使用screen配置监控屏蔽某些进程的执行遇到某些进程的出现直接关闭容器 ​

  • 如需停止监控可使用screen命令停止lxc_moniter这个名字的窗口并删除
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事后停机

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

通过shell脚本屏蔽滥用行为 ​

屏蔽容易被滥用的端口的出入流量以屏蔽端口和屏蔽滥用工具包 ​

  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事前预防

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh

使用screen配置监控屏蔽某些进程的执行遇到某些进程的出现直接关闭容器 ​

  • 如需停止监控可使用screen命令停止lxc_moniter这个名字的窗口并删除
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事后停机

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
+ \ No newline at end of file diff --git a/guide/block/block_pve.html b/guide/block/block_pve.html index 16f1a6b1df..aa64aa6f39 100644 --- a/guide/block/block_pve.html +++ b/guide/block/block_pve.html @@ -11,7 +11,7 @@ - + @@ -22,8 +22,8 @@
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

通过设置防火墙限制虚拟机使用的IP避免盗用 ​

在PVE的宿主机下创建以下文件

shell
/etc/pve/firewall/<VMID>.fw
 
 [IPSET ipfilter-<net0>]
-xxx.xxx.xxx.xxx

<VMID>替换为虚拟机的VMID数字，<net0>替换为网络设备中对应的别名(一般不用修改，除非你限制的IPV6)，xxx.xxx.xxx.xxx替换为公网IP地址，注意此IP对应前面的网络设备。

这里的意思是net0只能使用xxx.xxx.xxx.xxx这个IP，如果使用其他的IP数据将会被丢弃，从而达到限制虚拟机只能使用此IP的目的。

这里可以有多个IP，一旦启用此规则该VM就无法使用除此之外的任何IP，如果你没有写IPv6地址则代表该VM无法使用IPv6地址。

TIP

本设置仅推荐在开设非NAT全端口映射的独立IP的虚拟机时使用，否则可能导致奇奇怪怪的问题造成服务器没网。

该方法不适合开设任何NAT虚拟机/容器的PVE上使用。

- +xxx.xxx.xxx.xxx

<VMID>替换为虚拟机的VMID数字，<net0>替换为网络设备中对应的别名(一般不用修改，除非你限制的IPV6)，xxx.xxx.xxx.xxx替换为公网IP地址，注意此IP对应前面的网络设备。

这里的意思是net0只能使用xxx.xxx.xxx.xxx这个IP，如果使用其他的IP数据将会被丢弃，从而达到限制虚拟机只能使用此IP的目的。

这里可以有多个IP，一旦启用此规则该VM就无法使用除此之外的任何IP，如果你没有写IPv6地址则代表该VM无法使用IPv6地址。

TIP

本设置仅推荐在开设非NAT全端口映射的独立IP的虚拟机时使用，否则可能导致奇奇怪怪的问题造成服务器没网。

该方法不适合开设任何NAT虚拟机/容器的PVE上使用。

+ \ No newline at end of file diff --git a/guide/dashboard.html b/guide/dashboard.html index fd9a1e8b5b..27f03a2e95 100644 --- a/guide/dashboard.html +++ b/guide/dashboard.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

准备工作 ​

需要虚拟化出服务器，你需要：

  1. 一台可以连接公网的服务器( VPS 或 Dedicated Server)，最好能完美访问 Github 的 RAW 页面，部分项目部分组件可能未使用 CDN 加速

TIP

如果您位于中国大陆，访问 Github 有困难，请注意配套脚本和项目是否有说明已使用 CDN 加速

  1. 本地可以稳定连接SSH，如果不能稳定连接，请使用screen命令创建窗口后，在窗口内执行命令

TIP

不会用screen命令的，自行查找相关教程学习，或者用tmux替代也行

  1. 确保服务器的系统和硬件满足对应项目的要求，详见对应项目说明

本文档将以VPS作为范例，且该VPS纯净，无原生环境问题，如有必要请重装系统保证初始环境的纯净

WARNING

PVE项目可能造成宿主机出现问题，如果你不会看Bug和修复系统，那么不建议你在生产环境中使用，使用PVE相关脚本请确保宿主机随时可重装系统

项目仓库 ​

欢迎Star和Fork，所有资源均开源，无非开源部分，转载以及使用请写上来源于本站，谢谢

PVE ​

https://github.com/oneclickvirt/pve

Hits

incus ​

https://github.com/oneclickvirt/incus

Hits

Docker ​

https://github.com/oneclickvirt/docker

Hits

LXD ​

https://github.com/oneclickvirt/lxd

Hits

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

准备工作 ​

需要虚拟化出服务器，你需要：

  1. 一台可以连接公网的服务器( VPS 或 Dedicated Server)，最好能完美访问 Github 的 RAW 页面，部分项目部分组件可能未使用 CDN 加速

TIP

如果您位于中国大陆，访问 Github 有困难，请注意配套脚本和项目是否有说明已使用 CDN 加速

  1. 本地可以稳定连接SSH，如果不能稳定连接，请使用screen命令创建窗口后，在窗口内执行命令

TIP

不会用screen命令的，自行查找相关教程学习，或者用tmux替代也行

  1. 确保服务器的系统和硬件满足对应项目的要求，详见对应项目说明

本文档将以VPS作为范例，且该VPS纯净，无原生环境问题，如有必要请重装系统保证初始环境的纯净

WARNING

PVE项目可能造成宿主机出现问题，如果你不会看Bug和修复系统，那么不建议你在生产环境中使用，使用PVE相关脚本请确保宿主机随时可重装系统

项目仓库 ​

欢迎Star和Fork，所有资源均开源，无非开源部分，转载以及使用请写上来源于本站，谢谢

PVE ​

https://github.com/oneclickvirt/pve

Hits

incus ​

https://github.com/oneclickvirt/incus

Hits

Docker ​

https://github.com/oneclickvirt/docker

Hits

LXD ​

https://github.com/oneclickvirt/lxd

Hits

+ \ No newline at end of file diff --git a/guide/dashboardq.html b/guide/dashboardq.html index 1642a09b53..372db24bb8 100644 --- a/guide/dashboardq.html +++ b/guide/dashboardq.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

Give me a cup of coffee.

https://ko-fi.com/spiritlhl

WeChat

WeChat

USDT-TRC20

bash
TNqjaPYAmDsm9pbpLY79pixE8z1ce3Zj1B

USDT-Polygon/Matic

bash
0xb81b44cb00f9e6e084f85e5da604ec479e7ffab6
- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

Give me a cup of coffee.

https://ko-fi.com/spiritlhl

WeChat

WeChat

USDT-TRC20

bash
TNqjaPYAmDsm9pbpLY79pixE8z1ce3Zj1B

USDT-Polygon/Matic

bash
0xb81b44cb00f9e6e084f85e5da604ec479e7ffab6
+ \ No newline at end of file diff --git a/guide/docker/docker_android.html b/guide/docker/docker_android.html index de718cd494..3ceab9bdd4 100644 --- a/guide/docker/docker_android.html +++ b/guide/docker/docker_android.html @@ -11,7 +11,7 @@ - + @@ -24,8 +24,8 @@ rm -rf /etc/nginx/sites-enabled/reverse-proxy rm -rf /etc/nginx/sites-available/reverse-proxy rm -rf /etc/nginx/passwd_scrcpy_web -rm -rf /root/android_info - +rm -rf /root/android_info + \ No newline at end of file diff --git a/guide/docker/docker_build.html b/guide/docker/docker_build.html index 171a4da004..e0a491f698 100644 --- a/guide/docker/docker_build.html +++ b/guide/docker/docker_build.html @@ -11,7 +11,7 @@ - + @@ -42,8 +42,8 @@ docker exec -it $container_id bash -c "service sshd restart" docker exec -it $container_id sh -c "service ssh start" docker exec -it $container_id sh -c "/usr/sbin/sshd" -done - +done + \ No newline at end of file diff --git a/guide/docker/docker_custom.html b/guide/docker/docker_custom.html index ef17cbf4a0..627a2161cb 100644 --- a/guide/docker/docker_custom.html +++ b/guide/docker/docker_custom.html @@ -11,7 +11,7 @@ - + @@ -29,8 +29,8 @@ rm -rf /usr/local/bin/config_${PORT} rm -rf /usr/local/bin/password_${PORT} docker rmi lscr.io/linuxserver/chromium

注意事项

图片

一键开设Desktop的容器 ​

完整的Linux桌面，可以在上面使用浏览器

宿主机需要至少1核2G内存5G硬盘，开设的容器大小将占用起码3.2G硬盘

开设

开设后默认的用户名是onew，密码是oneclick，默认的内存最大占用是2GB

默认的http协议的web端口是3004，默认的https协议的web端口是3005，开设后打开对应协议的本机IPV4:端口即可

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onewebtop.sh -o onewebtop.sh && chmod +x onewebtop.sh && bash onewebtop.sh

删除

执行

shell
docker ps -a

查询name的前缀是webtop的容器，记录容器的ID用

shell
docker rm -f 容器的ID

删除所有关联的容器后可用

shell
docker rmi lscr.io/linuxserver/webtop

删除对应镜像

一键安装guacamole ​

一个网页端连接SSH或RDP等协议控制服务器的玩意

网址：http://你的IPV4地址:80/guacamole

默认用户： guacadmin

默认密码： guacadmin

安装完毕登录后自行修改

宿主机的配置至少要有1核2G内存10G硬盘，否则开设可能会导致宿主机卡死！

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/extra_scripts/guacamole.sh -o guacamole.sh && chmod +x guacamole.sh && bash guacamole.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/docker/main/extra_scripts/guacamole.sh -o guacamole.sh && chmod +x guacamole.sh && bash guacamole.sh

一键开设RustDesk的容器 ​

一个跨端的远控中继端(非客户端)，支持双向控制

宿主机需要至少1核1G内存10G硬盘，对带宽的需求极低

开设

安装后客户端在这里找 https://github.com/rustdesk/rustdesk/releases/latest

在设置中设置中继服务器的IP即可，支持 Android、Windows、Linux、浏览器 端，支持电脑远控手机

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/onerustdesk.sh -o onerustdesk.sh && chmod +x onerustdesk.sh && bash onerustdesk.sh

删除

删除容器

shell
docker rm -f hbbs
-docker rm -f hbbr

删除对应镜像

shell
docker rmi rustdesk/rustdesk-server
- +docker rm -f hbbr

删除对应镜像

shell
docker rmi rustdesk/rustdesk-server
+ \ No newline at end of file diff --git a/guide/docker/docker_install.html b/guide/docker/docker_install.html index 4c0f5dfea9..df19eee6ff 100644 --- a/guide/docker/docker_install.html +++ b/guide/docker/docker_install.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统

如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装

开设虚拟内存 ​

TIP

内存开点swap免得机器炸了

单位换算：输入 1024 产生 1G SWAP-虚拟内存，虚拟内存占用硬盘空间，当实际内存不够用时将自动使用虚拟内存做内存使用，但随之带来IO高占用以及CPU性能占用

建议只开实际内存大小两倍大小的虚拟内存

国际

shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh

环境预设 ​

  • 检测系统环境，安装对应组件
  • 安装docker和docker-compose，这里有判断为国际服务器还是国内服务器，自动安装对应源的docker
  • 下载默认需要的一些配置脚本
  • 检测如果存在IPV6地址，检测其是否大于或等于/112，如果符合条件，则配置docker的ipv6的网络
  • 如果上述条件都符合，创建ndpresponder的docker和radvd，使得IPV6的分配支持ndp广播和自动分配
  • 支持x86_64和ARM架构的服务器

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh

或

bash dockerinstall.sh

TIP

环境安装过程中可能要求你重启服务器后再次执行脚本，详见脚本运行后的说明

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统

如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装

开设虚拟内存 ​

TIP

内存开点swap免得机器炸了

单位换算：输入 1024 产生 1G SWAP-虚拟内存，虚拟内存占用硬盘空间，当实际内存不够用时将自动使用虚拟内存做内存使用，但随之带来IO高占用以及CPU性能占用

建议只开实际内存大小两倍大小的虚拟内存

国际

shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh

环境预设 ​

  • 检测系统环境，安装对应组件
  • 安装docker和docker-compose，这里有判断为国际服务器还是国内服务器，自动安装对应源的docker
  • 下载默认需要的一些配置脚本
  • 检测如果存在IPV6地址，检测其是否大于或等于/112，如果符合条件，则配置docker的ipv6的网络
  • 如果上述条件都符合，创建ndpresponder的docker和radvd，使得IPV6的分配支持ndp广播和自动分配
  • 支持x86_64和ARM架构的服务器

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh

或

bash dockerinstall.sh

TIP

环境安装过程中可能要求你重启服务器后再次执行脚本，详见脚本运行后的说明

+ \ No newline at end of file diff --git a/guide/docker/docker_macos.html b/guide/docker/docker_macos.html index 4b0ca49f07..804bc3eaad 100644 --- a/guide/docker/docker_macos.html +++ b/guide/docker/docker_macos.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

在Docker中开设Macos虚拟机 ​

通过dockur开设 ​

原始项目

https://github.com/dockur/macos

通过OSX开设 ​

原始项目

https://github.com/sickcodes/Docker-OSX

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

在Docker中开设Macos虚拟机 ​

通过dockur开设 ​

原始项目

https://github.com/dockur/macos

通过OSX开设 ​

原始项目

https://github.com/sickcodes/Docker-OSX

+ \ No newline at end of file diff --git a/guide/docker/docker_precheck.html b/guide/docker/docker_precheck.html index 4971c5b998..915697a0b9 100644 --- a/guide/docker/docker_precheck.html +++ b/guide/docker/docker_precheck.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了

如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装

WARNING

如果宿主机带IPV6网络的话，安装会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上

欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/docker

项目特点 ​

通过docker批量或单独开设NAT服务器(Bulk or individual NAT server provisioning via docker)

默认使用debian系统可选alpine系统，每个容器自带1个外网ssh端口，25个内外网一致端口，可选择是否绑定IPV6地址

默认创建的是非特权容器，且不挂载与宿主机的docker的守护进程之间的通信，所以宿主机创建的docker虚拟化的NAT服务器内无法再嵌套虚拟化docker

默认安装并启用lxcfs，使得在容器内的查询资源时CPU和内存使用的是配置的视图而不是宿主机的视图

由于大部分云服务器是ext4文件系统，docker默认的存储引擎是overlayfs2，即便宿主机的文件系统是xfs，默认也不会启用pquota选项，所以默认共享宿主机硬盘，无法限制每个容器的磁盘大小

配置要求 ​

系统可安装docker即可用，网络能连接Github的raw界面就能用，硬件配置只要不拉跨就行，空闲硬盘有3G就行

(如果需要绑定IPV6地址，那么请保证使用本套脚本的环境预设脚本进行环境安装，需要它自动预设部分设置)

如果硬件资源只是好了一点，需要限制更多东西并需要限制硬盘大小，可使用LXD分区的脚本批量开LXC虚拟化的容器

如果硬件非常好资源很多，可使用PVE分区的脚本批量开KVM虚拟化的虚拟机

推荐在开设NAT服务器前先增加部分SWAP虚拟内存，避免突发的内存占用导致宿主机卡死

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了

如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装

WARNING

如果宿主机带IPV6网络的话，安装会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上

欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/docker

项目特点 ​

通过docker批量或单独开设NAT服务器(Bulk or individual NAT server provisioning via docker)

默认使用debian系统可选alpine系统，每个容器自带1个外网ssh端口，25个内外网一致端口，可选择是否绑定IPV6地址

默认创建的是非特权容器，且不挂载与宿主机的docker的守护进程之间的通信，所以宿主机创建的docker虚拟化的NAT服务器内无法再嵌套虚拟化docker

默认安装并启用lxcfs，使得在容器内的查询资源时CPU和内存使用的是配置的视图而不是宿主机的视图

由于大部分云服务器是ext4文件系统，docker默认的存储引擎是overlayfs2，即便宿主机的文件系统是xfs，默认也不会启用pquota选项，所以默认共享宿主机硬盘，无法限制每个容器的磁盘大小

配置要求 ​

系统可安装docker即可用，网络能连接Github的raw界面就能用，硬件配置只要不拉跨就行，空闲硬盘有3G就行

(如果需要绑定IPV6地址，那么请保证使用本套脚本的环境预设脚本进行环境安装，需要它自动预设部分设置)

如果硬件资源只是好了一点，需要限制更多东西并需要限制硬盘大小，可使用LXD分区的脚本批量开LXC虚拟化的容器

如果硬件非常好资源很多，可使用PVE分区的脚本批量开KVM虚拟化的虚拟机

推荐在开设NAT服务器前先增加部分SWAP虚拟内存，避免突发的内存占用导致宿主机卡死

+ \ No newline at end of file diff --git a/guide/docker/docker_qa.html b/guide/docker/docker_qa.html index 86df10dbbe..25cfc11222 100644 --- a/guide/docker/docker_qa.html +++ b/guide/docker/docker_qa.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

解惑 ​

常见的一些docker命令 ​

查询某个容器的实时占用

docker stats 容器名字

进入某个容器

docker exec -it 容器名字 /bin/bash

清理 Docker 缓存，清理未使用的资源，包括镜像、容器、网络等

docker system prune -a

卸载所有docker的镜像和容器

docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)

查看对应容器日志

docker logs 容器名字或ID

查看docker整体的disk占用

docker system df

查看所有容器

docker ps -a

查看所有镜像

docker images

删除某个特定容器

docker rm -f 容器名字或ID

删除某个特定镜像

docker rmi 镜像名字或ID
- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

解惑 ​

常见的一些docker命令 ​

查询某个容器的实时占用

docker stats 容器名字

进入某个容器

docker exec -it 容器名字 /bin/bash

清理 Docker 缓存，清理未使用的资源，包括镜像、容器、网络等

docker system prune -a

卸载所有docker的镜像和容器

docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)

查看对应容器日志

docker logs 容器名字或ID

查看docker整体的disk占用

docker system df

查看所有容器

docker ps -a

查看所有镜像

docker images

删除某个特定容器

docker rm -f 容器名字或ID

删除某个特定镜像

docker rmi 镜像名字或ID
+ \ No newline at end of file diff --git a/guide/docker/docker_thanks.html b/guide/docker/docker_thanks.html index 5a874c0a21..99065a7751 100644 --- a/guide/docker/docker_thanks.html +++ b/guide/docker/docker_thanks.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

+ \ No newline at end of file diff --git a/guide/docker/docker_windows.html b/guide/docker/docker_windows.html index 06336f3f46..bf1c2f5bb5 100644 --- a/guide/docker/docker_windows.html +++ b/guide/docker/docker_windows.html @@ -11,7 +11,7 @@ - + @@ -44,8 +44,8 @@ --device=/dev/net/tun \ --cap-add NET_ADMIN \ --stop-timeout 120 \ - windows:2022

注意事项 ​

不建议在当前镜像基础上使用 docker commit 保存修改，因为写入层会不断叠加，导致二次生成的镜像体积可能超过 40G。

如需进行个性化配置或集成应用，请从 builder 镜像开始自行构建新镜像，以保持镜像整洁与可维护性。

- + windows:2022

注意事项 ​

不建议在当前镜像基础上使用 docker commit 保存修改，因为写入层会不断叠加，导致二次生成的镜像体积可能超过 40G。

如需进行个性化配置或集成应用，请从 builder 镜像开始自行构建新镜像，以保持镜像整洁与可维护性。

+ \ No newline at end of file diff --git a/guide/incus/incus_custom.html b/guide/incus/incus_custom.html index 3ed1524b71..57a02c383f 100644 --- a/guide/incus/incus_custom.html +++ b/guide/incus/incus_custom.html @@ -11,7 +11,7 @@ - + @@ -98,8 +98,8 @@ # 重新连接并设置进程守护，以便重启后自动生效 systemctl enable --now wg-quick@warp

自动安装和运行(fscarmen的一键脚本) ​

最后，介绍 fscarmen 的一键脚本。提到该脚本是一个方便的工具，可以简化配置过程。并自动处理最优 MTU, 最优 Endpoint 等进阶参数。

项目介绍: https://github.com/fscarmen/warp-sh

# 运动脚本
-wget -N https://gitlab.com/fscarmen/warp/-/raw/main/menu.sh && bash menu.sh

image.png

- +wget -N https://gitlab.com/fscarmen/warp/-/raw/main/menu.sh && bash menu.sh

image.png

+ \ No newline at end of file diff --git a/guide/incus/incus_extra_config.html b/guide/incus/incus_extra_config.html index 391e34041e..24ab99c202 100644 --- a/guide/incus/incus_extra_config.html +++ b/guide/incus/incus_extra_config.html @@ -11,7 +11,7 @@ - + @@ -29,8 +29,8 @@ rm /etc/systemd/system/add-ipv6.service systemctl daemon-reload rm /usr/local/bin/add-ipv6.sh

一键安装开incus宿主机所需要的带vnstat环境的常用预配置环境 ​

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/backend.sh -o backend.sh && chmod +x backend.sh && bash backend.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/backend.sh -o backend.sh && chmod +x backend.sh && bash backend.sh

安装incus的官方可视化控制面板 ​

shell
apt-get install -y incus-ui-canonical
-incus config set core.https_address [::]

然后你可以在浏览器中输入

https://你的公网IPV4地址:8443

即可进入官方可视化操作面板，后续的操作配置按照UI提示操作即可

- +incus config set core.https_address [::]

然后你可以在浏览器中输入

https://你的公网IPV4地址:8443

即可进入官方可视化操作面板，后续的操作配置按照UI提示操作即可

+ \ No newline at end of file diff --git a/guide/incus/incus_install.html b/guide/incus/incus_install.html index f90e4ce52f..430517e3cf 100644 --- a/guide/incus/incus_install.html +++ b/guide/incus/incus_install.html @@ -11,7 +11,7 @@ - + @@ -35,8 +35,8 @@ EOF' apt-get update apt-get install incus -y -incus -h

如果无异常，继续执行

incus admin init

一般的选项回车默认即可

选择配置物理盘大小(提示默认最小1GB那个选项)，一般我填空闲磁盘大小减去内存大小后乘以0.95并向下取整，这里我填了10GB

提示带auto的更新image的选项记得选no，避免更新占用系统

incus -h
- +incus -h

如果无异常，继续执行

incus admin init

一般的选项回车默认即可

选择配置物理盘大小(提示默认最小1GB那个选项)，一般我填空闲磁盘大小减去内存大小后乘以0.95并向下取整，这里我填了10GB

提示带auto的更新image的选项记得选no，避免更新占用系统

incus -h
+ \ No newline at end of file diff --git a/guide/incus/incus_lxc.html b/guide/incus/incus_lxc.html index 9bf8baf9bf..f8e0a6efd7 100644 --- a/guide/incus/incus_lxc.html +++ b/guide/incus/incus_lxc.html @@ -11,7 +11,7 @@ - + @@ -43,8 +43,8 @@ wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/ssh_bash.sh -O /usr/local/bin/ssh_bash.sh && chmod +x /usr/local/bin/ssh_bash.sh wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/ssh_sh.sh -O /usr/local/bin/ssh_sh.sh && chmod +x /usr/local/bin/ssh_sh.sh wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/build_ipv6_network.sh -O /root/build_ipv6_network.sh && chmod +x /root/build_ipv6_network.sh -wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/buildone.sh -O /root/buildone.sh && chmod +x /root/buildone.sh

其他一键脚本自己对应下载回来就行了

- +wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/buildone.sh -O /root/buildone.sh && chmod +x /root/buildone.sh

其他一键脚本自己对应下载回来就行了

+ \ No newline at end of file diff --git a/guide/incus/incus_precheck.html b/guide/incus/incus_precheck.html index 452249a01c..db33a34d54 100644 --- a/guide/incus/incus_precheck.html +++ b/guide/incus/incus_precheck.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了

如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装

欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/incus

要求 ​

硬件要求:

  • 系统：Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行

PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转

PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转

项目特点 ​

  • 本套脚本开发使用的Ubuntu24和Debian12，别的长期维护版本应该也没问题，某个存储类型无法使用时自动切换(优先级: btrfs > lvm > zfs > ceph > dir )

  • 已设置同时进行TCP和UDP转发，除了SSH端口其他的映射内网外网端口一致

  • 已设置支持开出的LXC容器进行docker嵌套虚拟，默认普通版本和纯探针版本使用debian11系统

  • 已设置默认启用lxcfs，使得在容器内的查询资源时使用的是配置的视图而不是宿主机的视图

  • 已屏蔽容器内可能用于滥用的工具包和IPV4网络的TCP/UDP协议的端口( 3389 8888 54321 65432 )，以防止容器被用于扫描和爆破，且可外置进程检查有问题自动停机

  • 已支持一键为LXC容器配置IPV6地址(前提是宿主机有IPV6子网，无IPV6地址则不配置)，自动适配子网大小

  • 已增加各种第三方镜像源，如果官方镜像丢失时，将使用镜像源下载容器镜像(含自修复镜像)

  • 保证你要开的盘为默认的系统盘(sda或者sda1)而不是挂载的盘(sdb之类的)，不确定的使用fdisk -l和df查看

  • 挂载其他盘的详看 其他说明

  • 一键脚本支持自定义限制所有内容，普通版本支持多次运行批量生成不覆盖先前生成的配置

检测环境 ​

使用后续脚本的务必执行本命令检测宿主机是否符合要求

国际

bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)

国内

bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)
- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了

如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装

欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/incus

要求 ​

硬件要求:

  • 系统：Ubuntu 20+, Debian 11+, RockyLinux 9+, AlmaLinux 9+, Centos 9+
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行

PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转

PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转

项目特点 ​

  • 本套脚本开发使用的Ubuntu24和Debian12，别的长期维护版本应该也没问题，某个存储类型无法使用时自动切换(优先级: btrfs > lvm > zfs > ceph > dir )

  • 已设置同时进行TCP和UDP转发，除了SSH端口其他的映射内网外网端口一致

  • 已设置支持开出的LXC容器进行docker嵌套虚拟，默认普通版本和纯探针版本使用debian11系统

  • 已设置默认启用lxcfs，使得在容器内的查询资源时使用的是配置的视图而不是宿主机的视图

  • 已屏蔽容器内可能用于滥用的工具包和IPV4网络的TCP/UDP协议的端口( 3389 8888 54321 65432 )，以防止容器被用于扫描和爆破，且可外置进程检查有问题自动停机

  • 已支持一键为LXC容器配置IPV6地址(前提是宿主机有IPV6子网，无IPV6地址则不配置)，自动适配子网大小

  • 已增加各种第三方镜像源，如果官方镜像丢失时，将使用镜像源下载容器镜像(含自修复镜像)

  • 保证你要开的盘为默认的系统盘(sda或者sda1)而不是挂载的盘(sdb之类的)，不确定的使用fdisk -l和df查看

  • 挂载其他盘的详看 其他说明

  • 一键脚本支持自定义限制所有内容，普通版本支持多次运行批量生成不覆盖先前生成的配置

检测环境 ​

使用后续脚本的务必执行本命令检测宿主机是否符合要求

国际

bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)

国内

bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/pre_check.sh)
+ \ No newline at end of file diff --git a/guide/incus/incus_qa.html b/guide/incus/incus_qa.html index 9c448927c3..ab3377353a 100644 --- a/guide/incus/incus_qa.html +++ b/guide/incus/incus_qa.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

解惑 ​

开设centos7发现报错CGroupV1不支持怎么办 ​

启用CGroup V1：要在Ubuntu系统上启用CGroup V1，需要编辑内核启动参数。

请注意，在更改内核启动参数之前，请务必备份重要的数据和设置，以防止意外的问题。

编辑/etc/default/grub文件，将GRUB_CMDLINE_LINUX_DEFAULT中的参数末尾加上systemd.unified_cgroup_hierarchy=0，如

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"

保存文件并运行以下命令更新GRUB引导。

bash
sudo update-grub

重启系统，使更改生效

如果上述更改仍旧不支持开设centos7，那么请使用别的宿主机系统尝试

目前已验证可开带独立IPV6地址容器的VPS商家 ​

kuroit 中的 美国凤凰城 regular

datalix 中的 德国AMD 促销款

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

解惑 ​

开设centos7发现报错CGroupV1不支持怎么办 ​

启用CGroup V1：要在Ubuntu系统上启用CGroup V1，需要编辑内核启动参数。

请注意，在更改内核启动参数之前，请务必备份重要的数据和设置，以防止意外的问题。

编辑/etc/default/grub文件，将GRUB_CMDLINE_LINUX_DEFAULT中的参数末尾加上systemd.unified_cgroup_hierarchy=0，如

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"

保存文件并运行以下命令更新GRUB引导。

bash
sudo update-grub

重启系统，使更改生效

如果上述更改仍旧不支持开设centos7，那么请使用别的宿主机系统尝试

目前已验证可开带独立IPV6地址容器的VPS商家 ​

kuroit 中的 美国凤凰城 regular

datalix 中的 德国AMD 促销款

+ \ No newline at end of file diff --git a/guide/incus/incus_thanks.html b/guide/incus/incus_thanks.html index 33693a7b63..7076262dcc 100644 --- a/guide/incus/incus_thanks.html +++ b/guide/incus/incus_thanks.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

+ \ No newline at end of file diff --git a/guide/incus/incus_windows.html b/guide/incus/incus_windows.html index 31a4f5ee25..80a4178fa0 100644 --- a/guide/incus/incus_windows.html +++ b/guide/incus/incus_windows.html @@ -11,7 +11,7 @@ - + @@ -68,8 +68,8 @@ > /var/log/websockify-winvm.log 2>&1 & echo "SPICE HTML5 console on http://${SERVER_IP}:6080/spice_auto.html"

首次启动需要按浏览器页面左上角的Ctrl+Alt+Delete按钮，重启后在默认的界面按照提示，按回车等待5~10分钟才会正式装载ISO进行实际的安装

最终会显示Zabbly的图标，这个图标在这里转圈圈需要至少10分钟，请耐心等待。

转圈圈完毕就会进入正常的Win虚拟机安装流程，类比PVE的操作即可。

如果发现资源没给够等原因需要删虚拟机重新开设，那么需要使用pkill -f websockify终止所有的spice信号转发，然后incus delete -f winvm强行删除虚拟机。

shell
lsof -i :6080

查询对应端口的PID号是否还存在，确保已完全停止(如果你有多个虚拟机的信号转发，那么最好不要用pkill删除所有，用kill -9删除对应端口的PID即可)。

如果已经安装完成，先关闭/退出Windows(在浏览器上关机)，然后移除 ISO 设备，保证下次从硬盘启动

shell
incus stop winvm
 incus config device remove winvm install
-incus start winvm

缺点 ​

前端无权限校验，没法设置用户密码

如果需要前端鉴权，那么得使用Guacamole添加一些设置来实现，这里就不赘述了

- +incus start winvm

缺点 ​

前端无权限校验，没法设置用户密码

如果需要前端鉴权，那么得使用Guacamole添加一些设置来实现，这里就不赘述了

+ \ No newline at end of file diff --git a/guide/lxd/lxd_custom.html b/guide/lxd/lxd_custom.html index 2fbb5ea80e..b963dd0386 100644 --- a/guide/lxd/lxd_custom.html +++ b/guide/lxd/lxd_custom.html @@ -11,7 +11,7 @@ - + @@ -98,8 +98,8 @@ # 重新连接并设置进程守护，以便重启后自动生效 systemctl enable --now wg-quick@warp

自动安装和运行(fscarmen的一键脚本) ​

最后，介绍 fscarmen 的一键脚本。提到该脚本是一个方便的工具，可以简化配置过程。并自动处理最优 MTU, 最优 Endpoint 等进阶参数。

项目介绍: https://github.com/fscarmen/warp-sh

# 运动脚本
-wget -N https://gitlab.com/fscarmen/warp/-/raw/main/menu.sh && bash menu.sh

image.png

- +wget -N https://gitlab.com/fscarmen/warp/-/raw/main/menu.sh && bash menu.sh

image.png

+ \ No newline at end of file diff --git a/guide/lxd/lxd_extra_config.html b/guide/lxd/lxd_extra_config.html index abb587207b..8d0b161aa8 100644 --- a/guide/lxd/lxd_extra_config.html +++ b/guide/lxd/lxd_extra_config.html @@ -11,7 +11,7 @@ - + @@ -34,8 +34,8 @@ systemctl reload snap.lxd.daemon snap restart --reload lxd

然后你可以在浏览器中输入

https://你的公网IPV4地址:8443

即可进入官方可视化操作面板，后续的操作配置按照UI提示操作即可

一键安装宿主机第三方可视化操作的面板 ​

shell
lxc config set core.https_address [::]
 lxc config set core.trust_password your_password
-snap install lxdmosaic

安装完毕后打开宿主机IP地址，按照提示设置admin的密码，其他一路默认就能使用面板了

- +snap install lxdmosaic

安装完毕后打开宿主机IP地址，按照提示设置admin的密码，其他一路默认就能使用面板了

+ \ No newline at end of file diff --git a/guide/lxd/lxd_install.html b/guide/lxd/lxd_install.html index 906d0b6c7c..1105b46de4 100644 --- a/guide/lxd/lxd_install.html +++ b/guide/lxd/lxd_install.html @@ -11,7 +11,7 @@ - + @@ -19,13 +19,13 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

LXD ​

如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装

LXD主体安装 ​

WARNING

如果是全新的服务器，务必保证apt update和apt install curl都无问题再执行本脚本。建议预装btrfs-progs以加速后续的安装流程，安装后建议重启系统以加载设置，若未预安装也没问题，只需按照提示执行脚本即可。且自开机起最好等待5分钟后再执行以下命令，避免系统默认设置中就执行了本脚本导致apt源卡死

  • 环境要求：Ubuntu 18+(推荐)，Debian 8+(仅限x86_64架构)
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程后需要重启服务器以加载一些默认配置
  • 默认启用lxd的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh

初始化配置的例子：

如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15

WARNING

如果你需要在一台服务器上开启超过200个LXD容器，那么不推荐你使用本项目，可能会出现lxcfs访问漂移的问题，产生IO占用无法释放。(系lxc原生问题无法修复)

安装WEB控制面板 ​

自定义 教程中有关于官方面板怎么启用的教程，但这里不选择使用官方的面板，因为官方面板为了安全性，牺牲了很多用户体验，这块使用

https://github.com/turtle0x1/LxdMosaic

的第三方面板

shell
sudo snap install lxdmosaic

直接进行一键安装，然后打开当前宿主机的https://<公网IP地址>/，强制访问，就能进入设置页面

lxd

lxd

lxd

这块如果你需要设置网站名字可以改改

lxd

聊胜于无只能说，没有RBAC权限控制进行分用户隔离

手动安装(备选) ​

不推荐，只是为了一些奇葩环境一键脚本跑不动的时候进行安装

关闭防火墙 ​

bash
apt update
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
LXD ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
LXD主体安装 ​
WARNING
如果是全新的服务器，务必保证apt update和apt install curl都无问题再执行本脚本。
  • 环境要求：Ubuntu 18+(推荐)，Debian 8+(仅限x86_64架构)
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程后需要重启服务器以加载一些默认配置
  • 默认启用lxd的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
WARNING
如果你需要在一台服务器上开启超过200个LXD容器，那么不推荐你使用本项目，可能会出现lxcfs访问漂移的问题，产生IO占用无法释放。(系lxc原生问题无法修复)
安装WEB控制面板 ​
自定义 教程中有关于官方面板怎么启用的教程，但这里不选择使用官方的面板，因为官方面板为了安全性，牺牲了很多用户体验，这块使用
https://github.com/turtle0x1/LxdMosaic
的第三方面板
shell
sudo snap install lxdmosaic
直接进行一键安装，然后打开当前宿主机的https://<公网IP地址>/，强制访问，就能进入设置页面
lxd
lxd
lxd
这块如果你需要设置网站名字可以改改
lxd
聊胜于无只能说，没有RBAC权限控制进行分用户隔离
手动安装(备选) ​
不推荐，只是为了一些奇葩环境一键脚本跑不动的时候进行安装
关闭防火墙 ​
bash
apt update
 apt install curl wget sudo dos2unix ufw jq -y
 ufw disable
开设虚拟内存SWAP ​
内存看你开多少服务器，这里如果要开8个，换算需要2G内存，实际内存如果是512MB内存，还需要开1.5G，保守点开2G虚拟内存即可
执行下面命令，输入1，再输入2048，代表开2G虚拟内存
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/swap.sh -o swap.sh && chmod +x swap.sh && bash swap.sh
安装LXD ​
实际swap开的虚拟内存应该是实际内存的2倍，也就是开1G是合理的，上面我描述的情况属于超开了
apt install snapd -y
 snap install lxd
 /snap/bin/lxd init
如果上面的命令中出现下面的错误
(snap "lxd" assumes unsupported features: snapd2.39 (try to update snapd and refresh the core snap))
使用命令修补后再进行lxd的安装
snap install core
如果无异常，上面三行命令执行结果如下
图片
一般的选项回车默认即可
选择配置物理盘大小(提示默认最小1GB那个选项)，一般我填空闲磁盘大小减去内存大小后乘以0.95并向下取整，这里我填了10GB
提示带auto的更新image的选项记得选no，避免更新占用系统
测试lxc有没有软连接上
lxc -h
如果报错则执行以下命令软连接lxc命令
bash
! lxc -h >/dev/null 2>&1 && echo 'alias lxc="/snap/bin/lxc"' >> /root/.bashrc && source /root/.bashrc
-export PATH=$PATH:/snap/bin
连接后再测试lxc命令是否有报错找不到

-    
+export PATH=$PATH:/snap/bin

连接后再测试lxc命令是否有报错找不到

+ \ No newline at end of file diff --git a/guide/lxd/lxd_lxc.html b/guide/lxd/lxd_lxc.html index 27e214c36c..9bd94eb951 100644 --- a/guide/lxd/lxd_lxc.html +++ b/guide/lxd/lxd_lxc.html @@ -11,7 +11,7 @@ - + @@ -43,8 +43,8 @@ wget https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/ssh_bash.sh -O /usr/local/bin/ssh_bash.sh && chmod +x /usr/local/bin/ssh_bash.sh wget https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/ssh_sh.sh -O /usr/local/bin/ssh_sh.sh && chmod +x /usr/local/bin/ssh_sh.sh wget https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/build_ipv6_network.sh -O /root/build_ipv6_network.sh && chmod +x /root/build_ipv6_network.sh -wget https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/buildone.sh -O /root/buildone.sh && chmod +x /root/buildone.sh

其他一键脚本自己对应下载回来就行了

- +wget https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/buildone.sh -O /root/buildone.sh && chmod +x /root/buildone.sh

其他一键脚本自己对应下载回来就行了

+ \ No newline at end of file diff --git a/guide/lxd/lxd_precheck.html b/guide/lxd/lxd_precheck.html index 9472fb57c1..bfacac72e3 100644 --- a/guide/lxd/lxd_precheck.html +++ b/guide/lxd/lxd_precheck.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了

如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装

欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/lxd

要求 ​

硬件要求:

  • 系统：Debian 8+, Ubuntu 18+(推荐20.04)
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行

PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转

PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转

项目特点 ​

  • 本套脚本开发使用的Ubuntu20，Ubuntu别的长期维护版本应该也没问题，某个存储类型无法使用时自动切换

  • 已设置同时进行TCP和UDP转发，除了SSH端口其他的映射内网外网端口一致

  • 已设置支持开出的LXC容器进行docker嵌套虚拟，默认普通版本和纯探针版本使用debian11系统

  • 已设置默认启用lxcfs，使得在容器内的查询资源时使用的是配置的视图而不是宿主机的视图

  • 已屏蔽容器内可能用于滥用的工具包和IPV4网络的TCP/UDP协议的端口( 3389 8888 54321 65432 )，以防止容器被用于扫描和爆破，且可外置进程检查有问题自动停机

  • 已支持一键为LXC容器配置IPV6地址(前提是宿主机有IPV6子网，无IPV6地址则不配置)，自动适配子网大小

  • 已增加清华镜像源，如果官方镜像丢失时，将使用镜像源下载容器镜像

  • 保证你要开的盘为默认的系统盘(sda或者sda1)而不是挂载的盘(sdb之类的)，不确定的使用fdisk -l和df查看

  • 挂载其他盘的详看 其他说明

  • 一键脚本支持自定义限制所有内容，普通版本支持多次运行批量生成不覆盖先前生成的配置

检测环境 ​

使用后续脚本的务必执行本命令检测宿主机是否符合要求

国际

bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)

国内

bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)
- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了

如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装

欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/lxd

要求 ​

硬件要求:

  • 系统：Debian 8+, Ubuntu 18+(推荐20.04)
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行

PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转

PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转

项目特点 ​

  • 本套脚本开发使用的Ubuntu20，Ubuntu别的长期维护版本应该也没问题，某个存储类型无法使用时自动切换

  • 已设置同时进行TCP和UDP转发，除了SSH端口其他的映射内网外网端口一致

  • 已设置支持开出的LXC容器进行docker嵌套虚拟，默认普通版本和纯探针版本使用debian11系统

  • 已设置默认启用lxcfs，使得在容器内的查询资源时使用的是配置的视图而不是宿主机的视图

  • 已屏蔽容器内可能用于滥用的工具包和IPV4网络的TCP/UDP协议的端口( 3389 8888 54321 65432 )，以防止容器被用于扫描和爆破，且可外置进程检查有问题自动停机

  • 已支持一键为LXC容器配置IPV6地址(前提是宿主机有IPV6子网，无IPV6地址则不配置)，自动适配子网大小

  • 已增加清华镜像源，如果官方镜像丢失时，将使用镜像源下载容器镜像

  • 保证你要开的盘为默认的系统盘(sda或者sda1)而不是挂载的盘(sdb之类的)，不确定的使用fdisk -l和df查看

  • 挂载其他盘的详看 其他说明

  • 一键脚本支持自定义限制所有内容，普通版本支持多次运行批量生成不覆盖先前生成的配置

检测环境 ​

使用后续脚本的务必执行本命令检测宿主机是否符合要求

国际

bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)

国内

bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/lxd/main/scripts/pre_check.sh)
+ \ No newline at end of file diff --git a/guide/lxd/lxd_qa.html b/guide/lxd/lxd_qa.html index a4f712f1c6..e272411770 100644 --- a/guide/lxd/lxd_qa.html +++ b/guide/lxd/lxd_qa.html @@ -11,7 +11,7 @@ - + @@ -20,8 +20,8 @@
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

解惑 ​

如果LXD安装后lxc命令显示找不到怎么办 ​

! lxc -h >/dev/null 2>&1 && echo 'alias lxc="/snap/bin/lxc"' >> /root/.bashrc && source /root/.bashrc
-export PATH=$PATH:/snap/bin

执行这个命令后尝试

lxc -h

看看lxc命令是否已修复

开设centos7发现报错CGroupV1不支持怎么办 ​

启用CGroup V1：要在Ubuntu系统上启用CGroup V1，需要编辑内核启动参数。

请注意，在更改内核启动参数之前，请务必备份重要的数据和设置，以防止意外的问题。

编辑/etc/default/grub文件，将GRUB_CMDLINE_LINUX_DEFAULT中的参数末尾加上systemd.unified_cgroup_hierarchy=0，如

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"

保存文件并运行以下命令更新GRUB引导。

bash
sudo update-grub

重启系统，使更改生效

如果上述更改仍旧不支持开设centos7，那么请使用别的宿主机系统尝试

目前已验证可开带独立IPV6地址容器的VPS商家 ​

kuroit 中的 美国凤凰城 regular

datalix 中的 德国AMD 促销

- +export PATH=$PATH:/snap/bin

执行这个命令后尝试

lxc -h

看看lxc命令是否已修复

开设centos7发现报错CGroupV1不支持怎么办 ​

启用CGroup V1：要在Ubuntu系统上启用CGroup V1，需要编辑内核启动参数。

请注意，在更改内核启动参数之前，请务必备份重要的数据和设置，以防止意外的问题。

编辑/etc/default/grub文件，将GRUB_CMDLINE_LINUX_DEFAULT中的参数末尾加上systemd.unified_cgroup_hierarchy=0，如

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"

保存文件并运行以下命令更新GRUB引导。

bash
sudo update-grub

重启系统，使更改生效

如果上述更改仍旧不支持开设centos7，那么请使用别的宿主机系统尝试

目前已验证可开带独立IPV6地址容器的VPS商家 ​

kuroit 中的 美国凤凰城 regular

datalix 中的 德国AMD 促销

+ \ No newline at end of file diff --git a/guide/lxd/lxd_thanks.html b/guide/lxd/lxd_thanks.html index 11c0e61195..f75da21e21 100644 --- a/guide/lxd/lxd_thanks.html +++ b/guide/lxd/lxd_thanks.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

+ \ No newline at end of file diff --git a/guide/pve/images/readme.html b/guide/pve/images/readme.html index 613907a07b..9636b13646 100644 --- a/guide/pve/images/readme.html +++ b/guide/pve/images/readme.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

暂存图片

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

暂存图片

+ \ No newline at end of file diff --git a/guide/pve/pve_android.html b/guide/pve/pve_android.html index 5672a7dd0c..45f0e81238 100644 --- a/guide/pve/pve_android.html +++ b/guide/pve/pve_android.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

Android 虚拟机 ​

安卓系统镜像下载 ​

Android系统版本9及以前的镜像下载地址：

国际

https://www.fosshub.com/Android-x86.html

https://sourceforge.net/projects/android-x86/files/

国内

https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/

Android系统版本10及以后的新镜像下载地址：

https://blissos.org/index.html#download

虚拟机开设 ​

以安卓版本9及以前的镜像开设Android虚拟机 ​

本指南以

https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/71931/android-x86_64-9.0-rc2.iso

作为示例进行演示

1

模板设置 ​

开设VMID为100的虚拟机选择对应的存储盘

2

选择安卓镜像，然后Type选择Linux，Version选择含2.6版本的选项

3

Graphic card选择Vmware compatible，其他选项选择默认如图所示

4

磁盘格式选择SATA，具体需要分配多大的磁盘自选，推荐至少30G

5

CPU数量至少2核

如果你的宿主机支持嵌套虚拟化，CPU的类型请选择host(经验证无问题)

如果你的宿主机不支持嵌套虚拟化，CPU的类型请选择qemu64，同时在模板设置成功后，需要在Options中点击KVM hardware virtualization取消勾选后再启动虚拟机(不保证后面系统初始化无问题)

6

内存至少4G内存，填写至少4096

7

绑定的网桥选择vmbr1，Model选择VirtIO (paravirtualized)，取消Firewall的勾选

8

后续点击continue按钮后，模板成功创建出来，需要手动点击启动并进入VNC界面

9

系统安装 ​

进入引导后，选择Installation开头的选项

10

然后需要创建分区写入，这块如果选择不了的话按键盘按钮c，就能选中了

11

选择不使用GPT格式

12

显示空白盘后，选择New

13

选择分区类型Primary

14

然后会提示划分多大的空间，默认回车就行，使用全部的空间

15

然后是选择Flags，移动到Bootable后，按回车，直到Flags下方显示Boot

16

然后移动到Write，回车，进行写入

17

这时候会让你确认是否继续，输入yes后回车继续

18

一段进度条跑过后，回到了最初的菜单，选择Quit退出菜单，一切准备就绪了

19

然后这时候回到了UI界面，使用前面初始化好的盘，选择OK按钮回车

20

文件系统按方向键选择ext4类型，选择OK按钮回车

21

确认进行格式化，选择Yes按钮回车

22

确认GRUB引导安装，选择OK按钮回车

23

确认文件系统可读写，选择OK按钮回车

24

跑了一段时间进度条后，显示安装成功，此时选择Reboot，选择OK按钮回车

25

然后一段时间后进入安卓LOGO界面

26

镜像移除 ​

然后会进入一段黑屏，大概3~5分钟后仍然黑屏的话，宿主机执行qm stop 100，然后开始移除镜像文件

移除已经按照完毕的ISO文件，在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]

ar

然后宿主机再执行qm start 100，然后应该就会进入安卓系统的初始化界面了

系统初始化 ​

初始化界面选择语言，然后点击确定按钮

27

此时回尝试连接WIFI，由于本项目安装的PVE是完全的静态网络配置，直接跳过，稍后再进行设置

31

点击下一步按钮确认设置时间

32

点击取消屏幕保护，确认仍然跳过

33

然后一段时间黑屏后，会出现主屏幕应用的选择，如果等待3~5分钟这个界面仍然没有出现，那么像之前那样重启虚拟机，再进入VNC应该就会显示了

选择Quickstep

34

网络设置 ​

进入桌面，此时需要开始设置网络，左上角点击设置图标

35

出现下拉框，点击按住下拉

36

点击齿轮按钮

37

进入网络和互联网设置

38

左键双击WIFI

39

修改目前识别到的VirtWIFI，右键点击出现选择框后，点击修改网络

40

出现高级选项，点击打开隐藏的选项

41

如图进行对应的网络设置

IP地址 172.16.1.xxx(xxx换成你想绑定的ip，我的vmid是100，为了方便写了100)

子网掩码 24

默认网关 172.16.1.1

DNS 8.8.8.8 或 144.144.144.144

然后点击保存按钮

42

此时出来后可能仍然未应用设置，点击关闭WIFI后，再启用WIFI，应该就会显示已连接

43

然后退出到主界面，点击谷歌浏览器，尝试打开一个网页

44

可以看到打开本指南的网址无问题，证明网络已联通

45

以安卓版本10及以后的新镜像开设Android虚拟机 ​

本指南以

https://psychz.dl.sourceforge.net/project/blissos-x86/Official/BlissOS15/Gapps/Generic/Bliss-v15.9.2-x86_64-OFFICIAL-gapps-20241012.iso?viasf=1

作为示例进行演示

1

模板设置 ​

宿主机需要先执行以下命令安装图形环境依赖

shell
apt install libgl1 libegl1 -y

然后开始创建虚拟机，点击右上角的Create VM按钮，填写VMID、Name、Resource Pool

2

选择安卓镜像，然后Type选择Linux，Version选择含2.6版本的选项

3

如果宿主机本身携带有GPU，那么Graphic card选择VirGL GPU。

如果宿主机本身不携带GPU，那么Graphic card选择VirtIO或Vmware compatible。

Machine选择q35，BIOS选择OVMF (UEFI)启动，EFI Storage选择local。

4

磁盘格式选择SATA，具体需要分配多大的磁盘自选，推荐至少30G

5

CPU数量至少2核

如果你的宿主机支持嵌套虚拟化，CPU的类型请选择host(经验证无问题)

如果你的宿主机不支持嵌套虚拟化，CPU的类型请选择qemu64，同时在模板设置成功后，需要在Options中点击KVM hardware virtualization取消勾选后再启动虚拟机(不保证后面系统初始化无问题)

6

内存至少4G内存，填写至少4096

7

绑定的网桥选择vmbr1，Model选择VirtIO (paravirtualized)，取消Firewall的勾选

8

后续点击continue按钮后，模板成功创建出来，需要手动点击启动并进入VNC界面。

系统安装 ​

进入引导后，选择Installation结尾的选项

9

然后需要创建分区写入，这块如果选择不了的话按键盘按钮c，就能选中了。

10

选择不使用GPT格式，依然使用cfdisk格式。

11

显示格式选择框，选择gpt。

12

显示空白盘后，选择New。

13

因为要划分EFI分区，这个盘需要修改大小，不能使用默认大小，数字改成1就行，分配1G硬盘，然后按回车。

14

然后回到了菜单栏，按方向键选择Type，然后回车，给分区选择格式类型

15

按方向键选择第一个选项EFI System，然后回车

16

此时回到菜单栏，页面上半部分就能看到具体的分区大小和格式

17

然后按下方向键，选择下一行空白的分区

18

菜单栏选择New，然后回车

19

这块需要填写分区大小，此时对照右上角选中的空白分区大小一致即可，然后回车。

20

回到菜单栏，选择Write，回车，写入分区。

21

会提示你输入yes进行确认，输入后回车。

22

然后一段进度条跑过，应该会回到菜单栏，选择Quit退出菜单，一切准备就绪了

23

然后这时候回到了UI界面，使用前面初始化好的1GB大小的盘，选择OK按钮回车。

24

文件系统按方向键选择fat32类型，选择OK按钮回车

25

确认不修改名字，选择OK按钮回车

26

确认进行格式化，选择Yes按钮回车

27

然后回到最初的UI栏，选择第二块不是1GB大小的分区，选择OK按钮回车

28

文件系统按方向键选择ext4类型，选择OK按钮回车

29

确认不修改名字，选择OK按钮回车

30

确认进行格式化，选择Yes按钮回车

31

默认不使用额外空间更新，选择No按钮回车

32

确认GRUB2 EFI BootLoader，选择OK按钮回车

33

跑了一段时间进度条后，显示安装成功，此时选择Reboot，选择OK按钮回车。

34

系统初始化 ​

然后一段时间后进入LOGO界面。

35

再过一段时间，应该就会进入初始的安卓界面了，能看到弹窗和时间，按住左键上划

36

会出现主屏幕应用的选择，选择Quickstep

如果等待3~5分钟这个界面仍然没有出现，那么就重启虚拟机，再进入VNC应该就会显示了

37

镜像移除 ​

出现了安卓的界面后，宿主机执行qm stop 100，然后开始移除镜像文件。

移除已经按照完毕的ISO文件，在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]

br

然后宿主机再执行qm start 100，然后应该就会进入系统的初始界面了。

网络设置 ​

进入桌面，此时需要开始设置网络，图示位置按住左键，上划

38

弹出一堆应用，在里面找到那个叫做Bliss Ethernet Manager的应用，点击并打开

39

IP Assignment点击打开，选择Static类型，点击OK按钮确认

40

IP Address点击打开，填入172.16.1.xxx/24(xxx我写的100，因为这里我的虚拟机VMID是100方便区分)，点击OK按钮确认

41

Gateway Address点击打开，填入172.16.1.1，点击OK按钮确认

42

DNS Address点击打开，填入8.8.8.8，点击OK按钮确认

43

然后在应用界面中，点击Interface Up和Refresh，然后键盘按exit键退出程序

44

主界面中打开浏览器，验证网络是否畅通

45

可以看到打开本指南无问题，网络畅通

46

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

Android 虚拟机 ​

安卓系统镜像下载 ​

Android系统版本9及以前的镜像下载地址：

国际

https://www.fosshub.com/Android-x86.html

https://sourceforge.net/projects/android-x86/files/

国内

https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/

Android系统版本10及以后的新镜像下载地址：

https://blissos.org/index.html#download

虚拟机开设 ​

以安卓版本9及以前的镜像开设Android虚拟机 ​

本指南以

https://mirrors.tuna.tsinghua.edu.cn/osdn/android-x86/71931/android-x86_64-9.0-rc2.iso

作为示例进行演示

1

模板设置 ​

开设VMID为100的虚拟机选择对应的存储盘

2

选择安卓镜像，然后Type选择Linux，Version选择含2.6版本的选项

3

Graphic card选择Vmware compatible，其他选项选择默认如图所示

4

磁盘格式选择SATA，具体需要分配多大的磁盘自选，推荐至少30G

5

CPU数量至少2核

如果你的宿主机支持嵌套虚拟化，CPU的类型请选择host(经验证无问题)

如果你的宿主机不支持嵌套虚拟化，CPU的类型请选择qemu64，同时在模板设置成功后，需要在Options中点击KVM hardware virtualization取消勾选后再启动虚拟机(不保证后面系统初始化无问题)

6

内存至少4G内存，填写至少4096

7

绑定的网桥选择vmbr1，Model选择VirtIO (paravirtualized)，取消Firewall的勾选

8

后续点击continue按钮后，模板成功创建出来，需要手动点击启动并进入VNC界面

9

系统安装 ​

进入引导后，选择Installation开头的选项

10

然后需要创建分区写入，这块如果选择不了的话按键盘按钮c，就能选中了

11

选择不使用GPT格式

12

显示空白盘后，选择New

13

选择分区类型Primary

14

然后会提示划分多大的空间，默认回车就行，使用全部的空间

15

然后是选择Flags，移动到Bootable后，按回车，直到Flags下方显示Boot

16

然后移动到Write，回车，进行写入

17

这时候会让你确认是否继续，输入yes后回车继续

18

一段进度条跑过后，回到了最初的菜单，选择Quit退出菜单，一切准备就绪了

19

然后这时候回到了UI界面，使用前面初始化好的盘，选择OK按钮回车

20

文件系统按方向键选择ext4类型，选择OK按钮回车

21

确认进行格式化，选择Yes按钮回车

22

确认GRUB引导安装，选择OK按钮回车

23

确认文件系统可读写，选择OK按钮回车

24

跑了一段时间进度条后，显示安装成功，此时选择Reboot，选择OK按钮回车

25

然后一段时间后进入安卓LOGO界面

26

镜像移除 ​

然后会进入一段黑屏，大概3~5分钟后仍然黑屏的话，宿主机执行qm stop 100，然后开始移除镜像文件

移除已经按照完毕的ISO文件，在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]

ar

然后宿主机再执行qm start 100，然后应该就会进入安卓系统的初始化界面了

系统初始化 ​

初始化界面选择语言，然后点击确定按钮

27

此时回尝试连接WIFI，由于本项目安装的PVE是完全的静态网络配置，直接跳过，稍后再进行设置

31

点击下一步按钮确认设置时间

32

点击取消屏幕保护，确认仍然跳过

33

然后一段时间黑屏后，会出现主屏幕应用的选择，如果等待3~5分钟这个界面仍然没有出现，那么像之前那样重启虚拟机，再进入VNC应该就会显示了

选择Quickstep

34

网络设置 ​

进入桌面，此时需要开始设置网络，左上角点击设置图标

35

出现下拉框，点击按住下拉

36

点击齿轮按钮

37

进入网络和互联网设置

38

左键双击WIFI

39

修改目前识别到的VirtWIFI，右键点击出现选择框后，点击修改网络

40

出现高级选项，点击打开隐藏的选项

41

如图进行对应的网络设置

IP地址 172.16.1.xxx(xxx换成你想绑定的ip，我的vmid是100，为了方便写了100)

子网掩码 24

默认网关 172.16.1.1

DNS 8.8.8.8 或 144.144.144.144

然后点击保存按钮

42

此时出来后可能仍然未应用设置，点击关闭WIFI后，再启用WIFI，应该就会显示已连接

43

然后退出到主界面，点击谷歌浏览器，尝试打开一个网页

44

可以看到打开本指南的网址无问题，证明网络已联通

45

以安卓版本10及以后的新镜像开设Android虚拟机 ​

本指南以

https://psychz.dl.sourceforge.net/project/blissos-x86/Official/BlissOS15/Gapps/Generic/Bliss-v15.9.2-x86_64-OFFICIAL-gapps-20241012.iso?viasf=1

作为示例进行演示

1

模板设置 ​

宿主机需要先执行以下命令安装图形环境依赖

shell
apt install libgl1 libegl1 -y

然后开始创建虚拟机，点击右上角的Create VM按钮，填写VMID、Name、Resource Pool

2

选择安卓镜像，然后Type选择Linux，Version选择含2.6版本的选项

3

如果宿主机本身携带有GPU，那么Graphic card选择VirGL GPU。

如果宿主机本身不携带GPU，那么Graphic card选择VirtIO或Vmware compatible。

Machine选择q35，BIOS选择OVMF (UEFI)启动，EFI Storage选择local。

4

磁盘格式选择SATA，具体需要分配多大的磁盘自选，推荐至少30G

5

CPU数量至少2核

如果你的宿主机支持嵌套虚拟化，CPU的类型请选择host(经验证无问题)

如果你的宿主机不支持嵌套虚拟化，CPU的类型请选择qemu64，同时在模板设置成功后，需要在Options中点击KVM hardware virtualization取消勾选后再启动虚拟机(不保证后面系统初始化无问题)

6

内存至少4G内存，填写至少4096

7

绑定的网桥选择vmbr1，Model选择VirtIO (paravirtualized)，取消Firewall的勾选

8

后续点击continue按钮后，模板成功创建出来，需要手动点击启动并进入VNC界面。

系统安装 ​

进入引导后，选择Installation结尾的选项

9

然后需要创建分区写入，这块如果选择不了的话按键盘按钮c，就能选中了。

10

选择不使用GPT格式，依然使用cfdisk格式。

11

显示格式选择框，选择gpt。

12

显示空白盘后，选择New。

13

因为要划分EFI分区，这个盘需要修改大小，不能使用默认大小，数字改成1就行，分配1G硬盘，然后按回车。

14

然后回到了菜单栏，按方向键选择Type，然后回车，给分区选择格式类型

15

按方向键选择第一个选项EFI System，然后回车

16

此时回到菜单栏，页面上半部分就能看到具体的分区大小和格式

17

然后按下方向键，选择下一行空白的分区

18

菜单栏选择New，然后回车

19

这块需要填写分区大小，此时对照右上角选中的空白分区大小一致即可，然后回车。

20

回到菜单栏，选择Write，回车，写入分区。

21

会提示你输入yes进行确认，输入后回车。

22

然后一段进度条跑过，应该会回到菜单栏，选择Quit退出菜单，一切准备就绪了

23

然后这时候回到了UI界面，使用前面初始化好的1GB大小的盘，选择OK按钮回车。

24

文件系统按方向键选择fat32类型，选择OK按钮回车

25

确认不修改名字，选择OK按钮回车

26

确认进行格式化，选择Yes按钮回车

27

然后回到最初的UI栏，选择第二块不是1GB大小的分区，选择OK按钮回车

28

文件系统按方向键选择ext4类型，选择OK按钮回车

29

确认不修改名字，选择OK按钮回车

30

确认进行格式化，选择Yes按钮回车

31

默认不使用额外空间更新，选择No按钮回车

32

确认GRUB2 EFI BootLoader，选择OK按钮回车

33

跑了一段时间进度条后，显示安装成功，此时选择Reboot，选择OK按钮回车。

34

系统初始化 ​

然后一段时间后进入LOGO界面。

35

再过一段时间，应该就会进入初始的安卓界面了，能看到弹窗和时间，按住左键上划

36

会出现主屏幕应用的选择，选择Quickstep

如果等待3~5分钟这个界面仍然没有出现，那么就重启虚拟机，再进入VNC应该就会显示了

37

镜像移除 ​

出现了安卓的界面后，宿主机执行qm stop 100，然后开始移除镜像文件。

移除已经按照完毕的ISO文件，在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]

br

然后宿主机再执行qm start 100，然后应该就会进入系统的初始界面了。

网络设置 ​

进入桌面，此时需要开始设置网络，图示位置按住左键，上划

38

弹出一堆应用，在里面找到那个叫做Bliss Ethernet Manager的应用，点击并打开

39

IP Assignment点击打开，选择Static类型，点击OK按钮确认

40

IP Address点击打开，填入172.16.1.xxx/24(xxx我写的100，因为这里我的虚拟机VMID是100方便区分)，点击OK按钮确认

41

Gateway Address点击打开，填入172.16.1.1，点击OK按钮确认

42

DNS Address点击打开，填入8.8.8.8，点击OK按钮确认

43

然后在应用界面中，点击Interface Up和Refresh，然后键盘按exit键退出程序

44

主界面中打开浏览器，验证网络是否畅通

45

可以看到打开本指南无问题，网络畅通

46

+ \ No newline at end of file diff --git a/guide/pve/pve_custom.html b/guide/pve/pve_custom.html index 87120bdbbb..ef0a5c7147 100644 --- a/guide/pve/pve_custom.html +++ b/guide/pve/pve_custom.html @@ -11,7 +11,7 @@ - + @@ -48,8 +48,8 @@ echo "*/5 * * * * sleep 120; echo 3 > /proc/sys/vm/drop_caches" >> $TEMP_CRON echo "*/5 * * * * sleep 180; fstrim -av" >> $TEMP_CRON sudo crontab $TEMP_CRON -rm $TEMP_CRON

上面的命令需要宿主机本身有sudo和crontab命令才可使用。

在开设出的NAT的KVM虚拟机上自行映射公网端口 ​

使用nano或vim命令修改文件增加端口映射：

/etc/iptables/rules.v4

例如我有一台内网IP为172.16.1.152的KVM虚拟机，虚拟机内已经开设MYSQL监听了3306，我需要使用tcp协议映射出来到宿主机IP上的33306端口上进行使用，那么需要在上面的那个文件中的COMMIT行以上增加如下行

-A PREROUTING -i vmbr0 -p tcp -m tcp -dport 33306 -j DNAT --to-destination 172.16.1.152:3306

保存文件退出文件编辑后执行

service netfilter-persistent restart

重载端口映射

此时在宿主机上执行

lsof -i:33306

可见端口映射规则是否生效

开设Linux虚拟机的时候自定义CPU的TYPE ​

在宿主机上使用类似

shell
echo "kvm64" > /usr/local/bin/cpu_type

这样的方式指定默认的CPU的TYPE，可将kvm64替换为你需要的类型

- +rm $TEMP_CRON

上面的命令需要宿主机本身有sudo和crontab命令才可使用。

在开设出的NAT的KVM虚拟机上自行映射公网端口 ​

使用nano或vim命令修改文件增加端口映射：

/etc/iptables/rules.v4

例如我有一台内网IP为172.16.1.152的KVM虚拟机，虚拟机内已经开设MYSQL监听了3306，我需要使用tcp协议映射出来到宿主机IP上的33306端口上进行使用，那么需要在上面的那个文件中的COMMIT行以上增加如下行

-A PREROUTING -i vmbr0 -p tcp -m tcp -dport 33306 -j DNAT --to-destination 172.16.1.152:3306

保存文件退出文件编辑后执行

service netfilter-persistent restart

重载端口映射

此时在宿主机上执行

lsof -i:33306

可见端口映射规则是否生效

开设Linux虚拟机的时候自定义CPU的TYPE ​

在宿主机上使用类似

shell
echo "kvm64" > /usr/local/bin/cpu_type

这样的方式指定默认的CPU的TYPE，可将kvm64替换为你需要的类型

+ \ No newline at end of file diff --git a/guide/pve/pve_install.html b/guide/pve/pve_install.html index 2436a0d5ef..4b53388073 100644 --- a/guide/pve/pve_install.html +++ b/guide/pve/pve_install.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

PVE主体安装 ​

安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载

TIP

低配置的宿主机，建议所有内容安装完毕后，查看自定义分区的内容，进行内存调优，减少内存占用。

一键安装PVE ​

TIP

建议debian12，实测部分独立服务器的debian11系统会出现一重启网络就失联的情况，debian12没有这种问题

  • 安装的是当下apt源最新的PVE
  • 比如debian10则是pve6.4，debian11则是pve7.x，debian12则是pve8.x
  • /etc/hosts文件修改(修正商家hostname设置错误以及新增PVE所需的内容)
  • /etc/cloud/cloud.cfg文件修改(避免覆写已修改的hostname等配置)
  • /etc/network/interfaces文件修改(修复auto、dhcp类型为static、增加vmbr0网关)
  • 检测是否为中国IP，如果为中国IP使用清华镜像源，否则使用官方源，同时处理apt的源和对应的nameserver，避免断网
  • 创建vmbr0(独立IP网关)，宿主机允许addr和gateway为内网IP或外网IP，已自动识别
  • vmbr0创建支持开设纯IPV4、纯IPV6、双栈虚拟机，自动识别IPV4地址和IPV6地址，自动识别对应的IP区间
  • 安装PVE开虚拟机需要的必备工具包
  • x86_64的替换apt源中的企业订阅为社区源，arm的使用第三方修复的补丁构建的源
  • 打印查询Linux系统内核和PVE内核是否已安装
  • 设置DNS检测8.8.8.8的开机自启添加DNS的systemd服务
  • 新增PVE的APT源链接后，下载PVE并打印输出登陆信息

所有修改过的文件均已设置为只读模式，避免重启后文件被覆写，如需修改请使用chattr -i 文件路径取消只读锁定，修改完毕请执行chattr +i 文件路径进行只读锁定

执行过程中会提示重启系统一次，重启后务必等待起码20秒确保系统未再次自动重启，因为原始环境可能缺失ifupdown或ifupdown2环境，有加载安装的守护进程进行安装，安装后会再次自动重启系统，等待20秒未自重启确保这个安装已运行完毕.

如果你需要将新安装的PVE纳管进入已有的集群，那么这块安装的时候，名字就不能回车默认使用pve，需要换一个名字避免和集群内的pve本身的hostname冲突.

若宿主机本身存在SLAAC分配的IPV6地址，将可选择是否使用最大的IPV6子网范围，默认回车不使用最大的IPV6子网范围仅使用本机IPV6，若后续需要给虚拟机/容器附加独立的IPV6地址，该选项务必选择y.

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh

或

shell
bash install_pve.sh

TIP

安装成功后打开网页可能提示不安全，点击高级或更多选项，坚持访问即可

登录的信息是你SSH的账户和密码

预配置环境 ​

  • 创建资源池mypool(local)
  • 移除订阅弹窗
  • 尝试开启硬件直通
  • 对AppArmor模块检测和自动安装
  • 重启系统前推荐挂上nezha探针方便在后台不通过SSH使用命令行，避免SSH可能因为商家奇葩的预设可能导致重启后root密码丢失
  • 执行reboot前需要等待后台任务执行完毕，一些宿主机的系统apt命令执行很慢，得等一会才能执行完毕，当然大部分的机器没这么烂，如果很久都起不来ssh无法连接，那么尝试通过控制面板重启一下服务器

国际

shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)

国内

shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)

自动配置宿主机的网关 ​

WARNING

使用前请保证重启过服务器且此时PVE能正常登录进WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动并可登录成功后至少等1分钟再执行本命令 如果WEB端起不来，执行systemctl status pveproxy查看是否启动，如果卡住未启动，执行systemctl start pveproxy启动WEB端。

TIP

这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行。

TIP

在执行本命令前如果宿主机需要附加IPV6隧道(给没有IPV6地址的宿主机添加IPV6子网)，请查看IPV6免费子网附加部分的内容附加到对应的配置文件中，但请忽略<初始环境修改>的操作，直接进行附加，附加后验证有IPV6地址了再执行下面的一键配置网关的命令。

  • 如果vmbr0未创建，则自动创建，逻辑同主体安装一致
  • 创建vmbr1(NAT网关)，支持开设NAT的IPV6网络的NAT的IPV4的服务器
  • 创建vmbr2(独立IPV6网关)，使用ndppd解决宿主机对IPV6地址进行MAC校验的问题，支持开设带独立IPV6网络的服务器
  • 想查看完整设置可以执行cat /etc/network/interfaces查看，如需修改网关需要修改该文件，web端已经无法修改
  • 加载iptables并设置回源且允许NAT端口转发

简单的说，vmbr0负责v4的独立IP，vmbr1负责复杂v4/v6的NAT，vmbr2负责v6的独立IP

开独立IPV4的虚拟机时使用的vmbr0，gateway同宿主机，IPV4/CIDR使用同一网段的地址和相同的子网掩码，使用宿主机未绑定的IPV4地址做IPV4/CIDR，当然如果后续使用本套脚本无需关注这点细枝末节的东西

开NAT的IPV4的虚拟机时使用vmbr1，gateway使用172.16.1.1，IPV4/CIDR使用172.16.1.x/24，这里的x不能是1，当然如果后续使用本套脚本无需关注这点细枝末节的东西

国际

shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)

国内

shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)

TIP

这一步是可能需要你执行成功几分钟后重启系统，详见脚本最后执行完毕的提示，但重启可以保证部分隐藏设置加载成功，有条件务必重启一次服务器

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

PVE主体安装 ​

安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载

TIP

低配置的宿主机，建议所有内容安装完毕后，查看自定义分区的内容，进行内存调优，减少内存占用。

一键安装PVE ​

TIP

建议debian12，实测部分独立服务器的debian11系统会出现一重启网络就失联的情况，debian12没有这种问题

  • 安装的是当下apt源最新的PVE
  • 比如debian10则是pve6.4，debian11则是pve7.x，debian12则是pve8.x
  • /etc/hosts文件修改(修正商家hostname设置错误以及新增PVE所需的内容)
  • /etc/cloud/cloud.cfg文件修改(避免覆写已修改的hostname等配置)
  • /etc/network/interfaces文件修改(修复auto、dhcp类型为static、增加vmbr0网关)
  • 检测是否为中国IP，如果为中国IP使用清华镜像源，否则使用官方源，同时处理apt的源和对应的nameserver，避免断网
  • 创建vmbr0(独立IP网关)，宿主机允许addr和gateway为内网IP或外网IP，已自动识别
  • vmbr0创建支持开设纯IPV4、纯IPV6、双栈虚拟机，自动识别IPV4地址和IPV6地址，自动识别对应的IP区间
  • 安装PVE开虚拟机需要的必备工具包
  • x86_64的替换apt源中的企业订阅为社区源，arm的使用第三方修复的补丁构建的源
  • 打印查询Linux系统内核和PVE内核是否已安装
  • 设置DNS检测8.8.8.8的开机自启添加DNS的systemd服务
  • 新增PVE的APT源链接后，下载PVE并打印输出登陆信息

所有修改过的文件均已设置为只读模式，避免重启后文件被覆写，如需修改请使用chattr -i 文件路径取消只读锁定，修改完毕请执行chattr +i 文件路径进行只读锁定

执行过程中会提示重启系统一次，重启后务必等待起码20秒确保系统未再次自动重启，因为原始环境可能缺失ifupdown或ifupdown2环境，有加载安装的守护进程进行安装，安装后会再次自动重启系统，等待20秒未自重启确保这个安装已运行完毕.

如果你需要将新安装的PVE纳管进入已有的集群，那么这块安装的时候，名字就不能回车默认使用pve，需要换一个名字避免和集群内的pve本身的hostname冲突.

若宿主机本身存在SLAAC分配的IPV6地址，将可选择是否使用最大的IPV6子网范围，默认回车不使用最大的IPV6子网范围仅使用本机IPV6，若后续需要给虚拟机/容器附加独立的IPV6地址，该选项务必选择y.

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/install_pve.sh -o install_pve.sh && chmod +x install_pve.sh && bash install_pve.sh

或

shell
bash install_pve.sh

TIP

安装成功后打开网页可能提示不安全，点击高级或更多选项，坚持访问即可

登录的信息是你SSH的账户和密码

预配置环境 ​

  • 创建资源池mypool(local)
  • 移除订阅弹窗
  • 尝试开启硬件直通
  • 对AppArmor模块检测和自动安装
  • 重启系统前推荐挂上nezha探针方便在后台不通过SSH使用命令行，避免SSH可能因为商家奇葩的预设可能导致重启后root密码丢失
  • 执行reboot前需要等待后台任务执行完毕，一些宿主机的系统apt命令执行很慢，得等一会才能执行完毕，当然大部分的机器没这么烂，如果很久都起不来ssh无法连接，那么尝试通过控制面板重启一下服务器

国际

shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)

国内

shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_backend.sh)

自动配置宿主机的网关 ​

WARNING

使用前请保证重启过服务器且此时PVE能正常登录进WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动并可登录成功后至少等1分钟再执行本命令 如果WEB端起不来，执行systemctl status pveproxy查看是否启动，如果卡住未启动，执行systemctl start pveproxy启动WEB端。

TIP

这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行。

TIP

在执行本命令前如果宿主机需要附加IPV6隧道(给没有IPV6地址的宿主机添加IPV6子网)，请查看IPV6免费子网附加部分的内容附加到对应的配置文件中，但请忽略<初始环境修改>的操作，直接进行附加，附加后验证有IPV6地址了再执行下面的一键配置网关的命令。

  • 如果vmbr0未创建，则自动创建，逻辑同主体安装一致
  • 创建vmbr1(NAT网关)，支持开设NAT的IPV6网络的NAT的IPV4的服务器
  • 创建vmbr2(独立IPV6网关)，使用ndppd解决宿主机对IPV6地址进行MAC校验的问题，支持开设带独立IPV6网络的服务器
  • 想查看完整设置可以执行cat /etc/network/interfaces查看，如需修改网关需要修改该文件，web端已经无法修改
  • 加载iptables并设置回源且允许NAT端口转发

简单的说，vmbr0负责v4的独立IP，vmbr1负责复杂v4/v6的NAT，vmbr2负责v6的独立IP

开独立IPV4的虚拟机时使用的vmbr0，gateway同宿主机，IPV4/CIDR使用同一网段的地址和相同的子网掩码，使用宿主机未绑定的IPV4地址做IPV4/CIDR，当然如果后续使用本套脚本无需关注这点细枝末节的东西

开NAT的IPV4的虚拟机时使用vmbr1，gateway使用172.16.1.1，IPV4/CIDR使用172.16.1.x/24，这里的x不能是1，当然如果后续使用本套脚本无需关注这点细枝末节的东西

国际

shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)

国内

shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/build_nat_network.sh)

TIP

这一步是可能需要你执行成功几分钟后重启系统，详见脚本最后执行完毕的提示，但重启可以保证部分隐藏设置加载成功，有条件务必重启一次服务器

+ \ No newline at end of file diff --git a/guide/pve/pve_kvm.html b/guide/pve/pve_kvm.html index 366313734f..9f229b113c 100644 --- a/guide/pve/pve_kvm.html +++ b/guide/pve/pve_kvm.html @@ -11,7 +11,7 @@ - + @@ -33,8 +33,8 @@ service netfilter-persistent restart

即可，但这会导致宿主机丧失开设非独立IPV4地址的NAT的虚拟机/容器的能力，慎重执行

执行后你只能开设独立IPV4地址的虚拟机了。

开设纯IPV6地址的虚拟机 ​

前提是宿主机给的是IPV6子网而不是单独一个IPV6地址，且宿主机未开启MAC地址校验

自动选择IPV6地址无需手动指定 ​

使用方法 ​

下载脚本

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm_onlyv6.sh -o buildvm_onlyv6.sh && chmod +x buildvm_onlyv6.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm_onlyv6.sh -o buildvm_onlyv6.sh && chmod +x buildvm_onlyv6.sh

各参数含义

shell
# ./buildvm_onlyv6.sh VMID 用户名 密码 CPU核数 内存大小以MB计算 硬盘大小以GB计算 系统 存储盘

TIP

注意这里的密码最好仅英文与数字混合，且以英文开头，避免密码在设置过程中因为特殊字符被转义而设置失败

创建示例 ​

shell
./buildvm_onlyv6.sh 152 root oneclick123 1 1024 10 debian12 local

上述命令意义为开设一个纯IPV6地址的虚拟机

参数值
VMID152
用户名root
密码oneclick123
CPU1核
内存1024MB
硬盘10G
系统debian12
存储盘local

TIP

注意这里的VMID仅可使用100到256，其他数字不可用

删除vm152示例 ​

shell
qm stop 152
 qm destroy 152
 systemctl restart ndpresponder.service
-rm -rf vm152
- +rm -rf vm152 + \ No newline at end of file diff --git a/guide/pve/pve_lxc.html b/guide/pve/pve_lxc.html index 4dcea46bab..a5cedef43f 100644 --- a/guide/pve/pve_lxc.html +++ b/guide/pve/pve_lxc.html @@ -11,7 +11,7 @@ - + @@ -30,8 +30,8 @@ iptables-save > /etc/iptables/rules.v4

开设纯IPV6地址的虚拟机 ​

前提是宿主机给的是IPV6子网而不是单独一个IPV6地址，且宿主机未开启MAC地址校验

自动选择IPV6地址无需手动指定 ​

使用方法 ​

下载脚本

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildct_onlyv6.sh -o buildct_onlyv6.sh && chmod +x buildct_onlyv6.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildct_onlyv6.sh -o buildct_onlyv6.sh && chmod +x buildct_onlyv6.sh

各参数含义

shell
# ./buildct_onlyv6.sh CTID 密码 CPU核数 内存大小以MB计算 硬盘大小以GB计算 系统 存储盘

创建示例 ​

shell
./buildct_onlyv6.sh 152 oneclick123 1 1024 10 debian12 local

上述命令意义为开设一个纯IPV6地址的容器

属性值
容器类型CT
CTID152
用户名root
密码oneclick123
CPU核心数1
内存1024MB
硬盘10G
系统debian12
存储盘local盘 (系统盘)

TIP

注意这里的CTID仅可使用100到256，其他数字不可用

删除示例 ​

shell
rm -rf ct*
 pct stop 152 
 pct destroy 152
-systemctl restart ndpresponder.service
- +systemctl restart ndpresponder.service + \ No newline at end of file diff --git a/guide/pve/pve_macos.html b/guide/pve/pve_macos.html index f8c7d3f9c0..893c466979 100644 --- a/guide/pve/pve_macos.html +++ b/guide/pve/pve_macos.html @@ -12,7 +12,7 @@ - + @@ -28,8 +28,8 @@ monterey.iso.7z (大小: 12.36GB) ventura.iso.7z (大小: 12.31GB) sonoma.iso.7z (大小: 14.41GB) -sequoia.iso.7z (大小: 15.02GB)

MACOS虚拟机模板设置 ​

下载模板脚本 ​

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm_macos.sh -o buildvm_macos.sh && chmod +x buildvm_macos.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm_macos.sh -o buildvm_macos.sh && chmod +x buildvm_macos.sh

参数含义 ​

shell
# ./buildvm_macos.sh VMID CPU核数 内存 硬盘 SSH端口 VNC端口 系统 存储盘 独立IPV6(留空默认N)

TIP

这块的硬盘大小只是你开设的虚拟机的硬盘大小，实际开设过程中，程序还会挂载引导盘和系统镜像，所以实际开设一个虚拟机的硬盘需求是 虚拟机硬盘大小+镜像本体大小+引导盘大小(500MB) 请时刻注意你的硬盘空间是否足够开设虚拟机

示例命令 ​

以最旧的版本(high-sierra)为例，实验支持的配置如下(非常卡顿)

shell
./buildvm_macos.sh 100 2 4096 45 44022 45901 high-sierra local N

模板开设完毕可执行cat vm100查看信息，或到WEB端对应VM的NOTES中查看

以下为开设的示例VM的信息：

属性值
VMID100
CPU核数2
内存大小4096MB
磁盘大小45G
SSH端口44022
VNC端口45901
系统high-sierra
宿主机的存储盘local
绑定独立IPV6(留空默认N)N

TIP

注意这里的VMID仅可使用100到256，其他数字不可用

MACOS系统引导和安装 ​

前面的流程走完后，面板端可以看到一个灰色的虚拟机待启动

mac0

点击启动后，进入VNC面板，左侧选择框有一个全屏按钮，实际操作时建议全屏操作，避免分辨率问题

mac00

经过大概3分钟的引导盘加载后，屏幕中央靠左侧会显示有一个启动盘可用，直接点击或回车

然后又是大概3~5分钟的启动盘加载后，会出现四个选择框，选择Disk Utility点击进入

mac1

进入后可以看到有三个盘和一个镜像，找到那个盘大小大于40G且名字叫QEMU HARDDISK Media的盘，点击Erase

mac2

此时会出现一个弹窗，需要给name重命名为macos方便后续识别使用，然后点击Erase继续初始化

mac3

初始化完毕后，点击Done

mac4

此时需要退出Disk Utility界面，右上角点击Disk Utility选择Quit Disk Utility退出当前选择框

mac5

然后回到了之前那四个选择框那里，选择Install macOS XXXX(由于我在以Big Sur为示例安装，所以XXXX为Big Sur系统)，点击continue

mac6

后续就是继续点击continue，然后点击Agree，然后又是点击Agree

mac7

mac8

mac9

直到又出现那三个盘，但在这块可以那个盘大小大于40G且名字叫macos的盘，选择它，然后点击continue

mac10

一段时间的文件复制硬盘加载(大概跑个12分钟)后，正式进入系统安装环节，这块看你宿主机在哪个地区选哪个

mac11

选择完地区后一路点击continue

mac12

mac13

直到出现数据迁移选项Migration Assistant，选择左下角的Not Now不导入用户数据

mac14

然后就会提示你创建用户，填写用户名和账户名，还有登录所需的密码，设置完毕后点击continue

mac15

然后后面就会一路畅通点击continue，直到系统安装完毕了

网络配置 ​

由于是离线环境进行的系统安装，所以这块需要手动配置静态网络连接宿主机的网桥

右上角点击WIFI按钮，关闭WIFI后，点击Network Preferences ...

mac16

进入设置界面后，点击Advanced按钮，进入高级设置界面

mac17

在TCP/IP这一栏填写静态网络配置

Configure IPV4: Manually

IPV4 Address: 172.16.1.xxx(xxx换成你想绑定的ip，我的vmid是100，为了方便写了100)

Subnet Mask: 255.255.255.0

Router: 172.16.1.1

如果你需要配置IPV6网络，类比上面的IPV4设置，需要填写的会是虚拟机绑定的公网IPV6地址(PVE面板中的Note框有写)，子网掩码填128，默认网关填写cat /usr/local/bin/pve_check_ipv6在宿主机执行后显示的地址。

mac18

在DNS这一栏填写静态网络的DNS配置

一般加入8.8.8.8和1.1.1.1足够了，中国境内使用114.114.114.114即可。

mac19

填写完毕且apply后，设置的左上角会显示网络已连通

mac20

此时打开默认的浏览器，随便打开一个网址，都是可访问公网资源的，证明网络已配置成功

mac21

卸载iso镜像 ​

在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]然后再重启虚拟机，这样就能直接使用了

wk

Macos系统就是卸载opencore.iso和xxxx(安装使用的系统镜像).iso，类似上面示例图片的Windows系统卸载win镜像和virtio镜像一样。

- +sequoia.iso.7z (大小: 15.02GB)

MACOS虚拟机模板设置 ​

下载模板脚本 ​

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm_macos.sh -o buildvm_macos.sh && chmod +x buildvm_macos.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildvm_macos.sh -o buildvm_macos.sh && chmod +x buildvm_macos.sh

参数含义 ​

shell
# ./buildvm_macos.sh VMID CPU核数 内存 硬盘 SSH端口 VNC端口 系统 存储盘 独立IPV6(留空默认N)

TIP

这块的硬盘大小只是你开设的虚拟机的硬盘大小，实际开设过程中，程序还会挂载引导盘和系统镜像，所以实际开设一个虚拟机的硬盘需求是 虚拟机硬盘大小+镜像本体大小+引导盘大小(500MB) 请时刻注意你的硬盘空间是否足够开设虚拟机

示例命令 ​

以最旧的版本(high-sierra)为例，实验支持的配置如下(非常卡顿)

shell
./buildvm_macos.sh 100 2 4096 45 44022 45901 high-sierra local N

模板开设完毕可执行cat vm100查看信息，或到WEB端对应VM的NOTES中查看

以下为开设的示例VM的信息：

属性值
VMID100
CPU核数2
内存大小4096MB
磁盘大小45G
SSH端口44022
VNC端口45901
系统high-sierra
宿主机的存储盘local
绑定独立IPV6(留空默认N)N

TIP

注意这里的VMID仅可使用100到256，其他数字不可用

MACOS系统引导和安装 ​

前面的流程走完后，面板端可以看到一个灰色的虚拟机待启动

mac0

点击启动后，进入VNC面板，左侧选择框有一个全屏按钮，实际操作时建议全屏操作，避免分辨率问题

mac00

经过大概3分钟的引导盘加载后，屏幕中央靠左侧会显示有一个启动盘可用，直接点击或回车

然后又是大概3~5分钟的启动盘加载后，会出现四个选择框，选择Disk Utility点击进入

mac1

进入后可以看到有三个盘和一个镜像，找到那个盘大小大于40G且名字叫QEMU HARDDISK Media的盘，点击Erase

mac2

此时会出现一个弹窗，需要给name重命名为macos方便后续识别使用，然后点击Erase继续初始化

mac3

初始化完毕后，点击Done

mac4

此时需要退出Disk Utility界面，右上角点击Disk Utility选择Quit Disk Utility退出当前选择框

mac5

然后回到了之前那四个选择框那里，选择Install macOS XXXX(由于我在以Big Sur为示例安装，所以XXXX为Big Sur系统)，点击continue

mac6

后续就是继续点击continue，然后点击Agree，然后又是点击Agree

mac7

mac8

mac9

直到又出现那三个盘，但在这块可以那个盘大小大于40G且名字叫macos的盘，选择它，然后点击continue

mac10

一段时间的文件复制硬盘加载(大概跑个12分钟)后，正式进入系统安装环节，这块看你宿主机在哪个地区选哪个

mac11

选择完地区后一路点击continue

mac12

mac13

直到出现数据迁移选项Migration Assistant，选择左下角的Not Now不导入用户数据

mac14

然后就会提示你创建用户，填写用户名和账户名，还有登录所需的密码，设置完毕后点击continue

mac15

然后后面就会一路畅通点击continue，直到系统安装完毕了

网络配置 ​

由于是离线环境进行的系统安装，所以这块需要手动配置静态网络连接宿主机的网桥

右上角点击WIFI按钮，关闭WIFI后，点击Network Preferences ...

mac16

进入设置界面后，点击Advanced按钮，进入高级设置界面

mac17

在TCP/IP这一栏填写静态网络配置

Configure IPV4: Manually

IPV4 Address: 172.16.1.xxx(xxx换成你想绑定的ip，我的vmid是100，为了方便写了100)

Subnet Mask: 255.255.255.0

Router: 172.16.1.1

如果你需要配置IPV6网络，类比上面的IPV4设置，需要填写的会是虚拟机绑定的公网IPV6地址(PVE面板中的Note框有写)，子网掩码填128，默认网关填写cat /usr/local/bin/pve_check_ipv6在宿主机执行后显示的地址。

mac18

在DNS这一栏填写静态网络的DNS配置

一般加入8.8.8.8和1.1.1.1足够了，中国境内使用114.114.114.114即可。

mac19

填写完毕且apply后，设置的左上角会显示网络已连通

mac20

此时打开默认的浏览器，随便打开一个网址，都是可访问公网资源的，证明网络已配置成功

mac21

卸载iso镜像 ​

在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]然后再重启虚拟机，这样就能直接使用了

wk

Macos系统就是卸载opencore.iso和xxxx(安装使用的系统镜像).iso，类似上面示例图片的Windows系统卸载win镜像和virtio镜像一样。

+ \ No newline at end of file diff --git a/guide/pve/pve_precheck.html b/guide/pve/pve_precheck.html index 5a1e2a523e..1dca742182 100644 --- a/guide/pve/pve_precheck.html +++ b/guide/pve/pve_precheck.html @@ -11,7 +11,7 @@ - + @@ -21,8 +21,8 @@
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了

如果有未适配的商家或机器欢迎联系@spiritlhl_bot，有空会尝试支持一下

WARNING

会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上

欢迎给项目一个Star进行免费的支持-->https://github.com/oneclickvirt/pve

各种要求 ​

建议debian在使用前尽量使用最新的稳定版本的系统

不要在动态IP的服务器上使用本套脚本(重启机器后自动切换本机IP的服务器暂不支持，重启机器后IP不自动切换的支持)

本项目的一键安装脚本只适配Debian系统，非Debian无法通过APT源安装，官方只给了Debian的镜像，其他系统只能使用ISO安装，或使用自定义分区和常见问题分区中的其他方式解决问题。

  • 系统要求：Debian 8+

TIP

建议debian12而不是debian11，debian11在部分独立服务器上有网络重启的BUG。

  • 硬件要求：2核2G内存x86_64或arm架构服务器硬盘至少20G
  • 可开KVM的硬件要求：VM-X或AMD-V支持 (部分VPS和全部独服支持)
  • 如果硬件或系统需求不满足，可使用incus批量开LXC容器跳转

如果使用IPV6隧道进行宿主机的IPV6子网附加，务必在PVE安装成功但网关未自动设置时在对应文件添加内容，不要在一开始(未安装PVE)就进行IPV6隧道的添加。

开设虚拟内存(SWAP)(非必须的可选项) ​

TIP

内存开点swap免得机器炸了，如果你的宿主机内存不够用硬盘又很多空闲的话

单位换算：输入 1024 产生 1G SWAP-虚拟内存，虚拟内存占用硬盘空间，当实际内存不够用时将自动使用虚拟内存做内存使用，但随之带来IO高占用以及CPU性能占用

建议只开实际内存大小两倍大小的虚拟内存

国际

shell
curl -L https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh

检测环境 ​

  • 本项目相关脚本执行前务必执行本脚本检测环境，如果不符合安装PVE的要求则无法使用后续的脚本
  • 检测本机IPV6的网络配置情况(有无IPV6都可安装，只是查询一下罢了)
  • 检测硬件配置是否满足最低要求
  • 检测硬件环境是否可嵌套虚拟化KVM类型的服务器，不可嵌套虚拟化KVM的也可以开QEMU的TCG的服务器，性能较差
  • 检测系统环境是否可嵌套虚拟化KVM类型的服务器，不可嵌套虚拟化KVM的也可以开QEMU的TCG的服务器，性能较差
  • 不可嵌套虚拟化KVM的服务器不推荐安装PVE，不如使用incus性能更好

国际

bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh)

国内

bash
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh)

如果你需要更新IPV6信息再查询，那么执行以下命令后再查询

bash
rm -rf /usr/local/bin/pve_ipv6*
 rm -rf /usr/local/bin/pve_check_ipv6*
-rm -rf /usr/local/bin/pve_last_ipv6*

执行本项目的检测环境的命令，展示如下

图片

查询如上的只需使用下面的一键脚本自动创建虚拟机即可，无需手动再修改WEB端设置

图片

查询如上的在使用后续脚本创建了虚拟机后，可能需要手动修改WEB端设置，需要关闭对应每个虚拟机的硬件嵌套虚拟化，如下图

图片

先停止虚拟机再修改，修改完后再开机才能使用NOVNC，不关闭可能导致这个虚拟机有BUG无法使用

如果强行安装PVE开KVM，启动不了的也可以关闭这个选项试试能不能启动虚拟机，导致这些问题的原因就是上面说的，宿主机不支持嵌套虚拟化KVM进行加速

TIP

开设虚拟机前请使用screen挂起执行，避免开设时间过长，SSH不稳定导致中间执行中断



- +rm -rf /usr/local/bin/pve_last_ipv6*

执行本项目的检测环境的命令，展示如下

图片

查询如上的只需使用下面的一键脚本自动创建虚拟机即可，无需手动再修改WEB端设置

图片

查询如上的在使用后续脚本创建了虚拟机后，可能需要手动修改WEB端设置，需要关闭对应每个虚拟机的硬件嵌套虚拟化，如下图

图片

先停止虚拟机再修改，修改完后再开机才能使用NOVNC，不关闭可能导致这个虚拟机有BUG无法使用

如果强行安装PVE开KVM，启动不了的也可以关闭这个选项试试能不能启动虚拟机，导致这些问题的原因就是上面说的，宿主机不支持嵌套虚拟化KVM进行加速

TIP

开设虚拟机前请使用screen挂起执行，避免开设时间过长，SSH不稳定导致中间执行中断



+ \ No newline at end of file diff --git a/guide/pve/pve_qa.html b/guide/pve/pve_qa.html index dbf92c4b0a..e8d5ee2202 100644 --- a/guide/pve/pve_qa.html +++ b/guide/pve/pve_qa.html @@ -11,7 +11,7 @@ - + @@ -31,8 +31,8 @@ iptables -t filter -F service networking restart systemctl restart networking.service -cat /etc/iptables/rules.v4 | iptables-restore

检测是不是商家虚标IPV6子网大小导致无法开设独立IPV6地址的虚拟机/容器 ​

使用以下命令在纯净的未安装ProxmoxVE的机器上测试实际的子网掩码大小

国际

shell
curl -L https://raw.githubusercontent.com/spiritLHLS/ecs/main/archive/eo6s.sh -o eo6s.sh && chmod +x eo6s.sh && bash eo6s.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/ecs/main/archive/eo6s.sh -o eo6s.sh && chmod +x eo6s.sh && bash eo6s.sh

如果检测结果为128证明商家虚标子网大小，仅一个IPV6地址无法额外分配给虚拟机/容器。

在现有的 PVE 中纳管新的 PVE（创建 / 加入集群） ​

为了将两个独立的 Proxmox VE 实例组成一个集群，需满足以下前提条件：

集群前提条件 ​

  1. 主机名唯一
    两个节点的 hostname 不可相同，避免命名冲突。建议使用诸如 pve1、pve2 等命名方式。

  2. VMID 唯一
    两台 PVE 上不能存在相同 VMID 的虚拟机或容器。若存在冲突，请调整 VMID 以避免合并时发生冲突。

  3. 网络互通、延迟低
    两台主机之间必须能互相 ping 通，建议网络延迟低（局域网或高速公网），以保障集群通信质量。

创建集群（在任意节点执行） ​

  1. 登录主节点（如 pve1）Web 管理界面。
  2. 依次点击：Datacenter → Cluster → Create Cluster。
  3. 输入集群名称（Cluster Name）。
  4. 选择要用于集群通信的网卡（如仅有公网 IP，可选择此网卡）。
  5. 点击 Create 创建集群。
  6. 创建成功后，点击 Join Information，复制该页面显示的信息备用。

PS: 在哪个节点上创建集群都可以，集群中不分主从节点。

加入集群（在第二个节点执行） ​

  1. 登录待加入节点（如 pve2）Web 管理界面。
  2. 依次点击：Datacenter → Cluster → Join Cluster。
  3. 将 pve1 的 Join Information 粘贴到输入框中。
  4. 填入 pve1 上具的 root 用户密码到 Peer Password。
  5. 点击 Join 开始加入过程。
  6. 等待页面提示成功后，刷新页面或重新登录，即可看到两个节点已组成集群。

集群优势 ​

目前已验证的VPS商家 ​

可开设KVM虚拟化的NAT的商家 ​

spartanhost 中的独立服务器的Debian12(Debian11有问题)

interserver 中的VPS或独立服务器

frantech 中的拉斯维加斯第二档

eugamehost 中的美国凤凰城黑五促销款

amhost 中的测试款

digitalocean 中的 Perminu Intel 和 Regular 4核款

skrime 中的 AMD Ryzen KVM Server 最低配款

webdock 中的 AMD KVM Server

4vps 中的 俄罗斯和希腊 测试款

adtaq 中的最低配存储KVM服务器

nocix 中的独立服务器

online.net 中的低配独立服务器的Debian12(Debian11有问题)

OVH 中的 Public Cloud 服务器 需要使用以下命令dd为纯净系统后安装

shell
bash <(curl -sSL https://raw.githubusercontent.com/leitbogioro/Tools/master/Linux_reinstall/InstallNET.sh) -debian 12 -pwd 'oneclickvirt139' --network "static"

此时dd后的系统用户名为root，密码为oneclickvirt139

如果不成功，请查看 https://github.com/leitbogioro/Tools 中的issues和说明。一个常见的问题是OVH独立服务器进行dd，需要源系统默认重装为raid1的debian12，然后用参数指定dd为raid0，才能成功，使用如下命令

shell
wget --no-check-certificate -qO InstallNET.sh 'https://raw.githubusercontent.com/leitbogioro/Tools/master/Linux_reinstall/InstallNET.sh' && chmod a+x InstallNET.sh && bash InstallNET.sh -debian 12  -mirror "http://ftp.debian.org/debian/" -pwd oneclickvirt139 -raid 0

只可开设LXC虚拟化的NAT的商家 ​

腾讯云 中的无忧款和特惠款(学生机)

spectraip 中的KVM服务器

Linode 中美国专用CPU的最低配

hosthatch 中的特价高配服务器

hetzner 的cloud服务器

rackdog 的浮动IP的服务器

vultr 的Cloud普通服务器

azure 的普通机器

scaleway 中的ARM架构的服务器

aws 中的ec2实例

Google cloud platform - GCP 的 AMD 服务器

- +cat /etc/iptables/rules.v4 | iptables-restore

检测是不是商家虚标IPV6子网大小导致无法开设独立IPV6地址的虚拟机/容器 ​

使用以下命令在纯净的未安装ProxmoxVE的机器上测试实际的子网掩码大小

国际

shell
curl -L https://raw.githubusercontent.com/spiritLHLS/ecs/main/archive/eo6s.sh -o eo6s.sh && chmod +x eo6s.sh && bash eo6s.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/ecs/main/archive/eo6s.sh -o eo6s.sh && chmod +x eo6s.sh && bash eo6s.sh

如果检测结果为128证明商家虚标子网大小，仅一个IPV6地址无法额外分配给虚拟机/容器。

在现有的 PVE 中纳管新的 PVE（创建 / 加入集群） ​

为了将两个独立的 Proxmox VE 实例组成一个集群，需满足以下前提条件：

集群前提条件 ​

  1. 主机名唯一
    两个节点的 hostname 不可相同，避免命名冲突。建议使用诸如 pve1、pve2 等命名方式。

  2. VMID 唯一
    两台 PVE 上不能存在相同 VMID 的虚拟机或容器。若存在冲突，请调整 VMID 以避免合并时发生冲突。

  3. 网络互通、延迟低
    两台主机之间必须能互相 ping 通，建议网络延迟低（局域网或高速公网），以保障集群通信质量。

创建集群（在任意节点执行） ​

  1. 登录主节点（如 pve1）Web 管理界面。
  2. 依次点击：Datacenter → Cluster → Create Cluster。
  3. 输入集群名称（Cluster Name）。
  4. 选择要用于集群通信的网卡（如仅有公网 IP，可选择此网卡）。
  5. 点击 Create 创建集群。
  6. 创建成功后，点击 Join Information，复制该页面显示的信息备用。

PS: 在哪个节点上创建集群都可以，集群中不分主从节点。

加入集群（在第二个节点执行） ​

  1. 登录待加入节点（如 pve2）Web 管理界面。
  2. 依次点击：Datacenter → Cluster → Join Cluster。
  3. 将 pve1 的 Join Information 粘贴到输入框中。
  4. 填入 pve1 上具的 root 用户密码到 Peer Password。
  5. 点击 Join 开始加入过程。
  6. 等待页面提示成功后，刷新页面或重新登录，即可看到两个节点已组成集群。

集群优势 ​

目前已验证的VPS商家 ​

可开设KVM虚拟化的NAT的商家 ​

spartanhost 中的独立服务器的Debian12(Debian11有问题)

interserver 中的VPS或独立服务器

frantech 中的拉斯维加斯第二档

eugamehost 中的美国凤凰城黑五促销款

amhost 中的测试款

digitalocean 中的 Perminu Intel 和 Regular 4核款

skrime 中的 AMD Ryzen KVM Server 最低配款

webdock 中的 AMD KVM Server

4vps 中的 俄罗斯和希腊 测试款

adtaq 中的最低配存储KVM服务器

nocix 中的独立服务器

online.net 中的低配独立服务器的Debian12(Debian11有问题)

OVH 中的 Public Cloud 服务器 需要使用以下命令dd为纯净系统后安装

shell
bash <(curl -sSL https://raw.githubusercontent.com/leitbogioro/Tools/master/Linux_reinstall/InstallNET.sh) -debian 12 -pwd 'oneclickvirt139' --network "static"

此时dd后的系统用户名为root，密码为oneclickvirt139

如果不成功，请查看 https://github.com/leitbogioro/Tools 中的issues和说明。一个常见的问题是OVH独立服务器进行dd，需要源系统默认重装为raid1的debian12，然后用参数指定dd为raid0，才能成功，使用如下命令

shell
wget --no-check-certificate -qO InstallNET.sh 'https://raw.githubusercontent.com/leitbogioro/Tools/master/Linux_reinstall/InstallNET.sh' && chmod a+x InstallNET.sh && bash InstallNET.sh -debian 12  -mirror "http://ftp.debian.org/debian/" -pwd oneclickvirt139 -raid 0

只可开设LXC虚拟化的NAT的商家 ​

腾讯云 中的无忧款和特惠款(学生机)

spectraip 中的KVM服务器

Linode 中美国专用CPU的最低配

hosthatch 中的特价高配服务器

hetzner 的cloud服务器

rackdog 的浮动IP的服务器

vultr 的Cloud普通服务器

azure 的普通机器

scaleway 中的ARM架构的服务器

aws 中的ec2实例

Google cloud platform - GCP 的 AMD 服务器

+ \ No newline at end of file diff --git a/guide/pve/pve_thanks.html b/guide/pve/pve_thanks.html index f2a2735bf4..06104d286c 100644 --- a/guide/pve/pve_thanks.html +++ b/guide/pve/pve_thanks.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

+ \ No newline at end of file diff --git a/guide/pve/pve_windows.html b/guide/pve/pve_windows.html index 7f85df9c82..5732dd0a6c 100644 --- a/guide/pve/pve_windows.html +++ b/guide/pve/pve_windows.html @@ -12,7 +12,7 @@ - + @@ -21,8 +21,8 @@
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

开设Windows虚拟机 ​

开设时选择KVM虚拟化还是QEMU的TCG仿真 ​

宿主机本身如果支持嵌套虚拟化，那么就可用host或kvm64或qemu64类型的CPU

从性能上来说，host > kvm64 > qemu64

qemu类型虚拟化性能损耗很多

如果本身不支持嵌套虚拟化，那么只能用qemu64类型的CPU，且需要在启动虚拟机前修改Options[选项]中的KVM hardware virtualization[KVM硬件虚拟化]

设置为no取消Enabled[启用]的勾选

kvm

如果你实在不清楚本机是否支持嵌套虚拟化，那么查看 系统与硬件配置要求 --> 检测环境 检测确保可用(含尝试性启用功能)

它的主体逻辑在

https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/check_kernal.sh

这块的逻辑中，主要检测

egrep -c '(vmx|svm)' /proc/cpuinfo 检测是否为1

cat /sys/module/kvm_intel/parameters/nested是否存在且为1

lsmod | grep -q kvm检测是否已加载

这些都支持的时候，才可选host类型。

使用带virtio的iso镜像文件开设 ​

1.下载镜像 ​

安装需要提前下载镜像文件local(pve) --> ISO images --> Download from URL

下载链接URL:可使用

https://github.com/ILLKX/Windows-VirtIO

中的文件链接，文件名字File Name:填win.iso

download

点击下载Download，下载完成后当前的页面可见win.iso的文件大小，可见格式为iso。

downloaded

2.设置模板 ​

页面顶部右上角点击Create VM

General窗口中，Resource Pool:勾选mypool，Name填写win，然后点击Next。

general

OS窗口中，ISO image勾选win.iso，Guest OS勾选Type为Microsoft Windows类型，Version选择当前ISO的win的版本，示例下载是2022，就选11/2022类型，然后点击Next。

OS

System窗口中，Graphic card勾选VirtIO-GPU类型，Machine勾选q35类型，SCSI Controller勾选VirtIO SCSI类型，BIOS勾选Default (SeaBIOS)类型，然后点击Next。

system

Disk窗口中，Cache勾选Write Back类型，Disk size (GiB)填写你要分配的硬盘大小，一般不小于20，Storage选择存储在哪个盘，示例只有系统盘local所以就选loacl，然后点击Next。

disk

CPU窗口中，Cores填写所需核数，CPU类型按照前面描述的方法选择，然后点击Next。

cpu

Memory窗口中，Memory (MiB)填写所需内存大小，然后点击Next。

memory

Network窗口中，Bridge勾选vmbr1类型，Model勾选VirtIO (paravirtualized)类型，Firewall取消勾选，然后点击Next。

Network

Confirm窗口中，点击Finish。

finish

3.图形化配置安装 ​

左侧点击设置好的模板，右上角点击Start启动虚拟机，然后点击Console进入VNC界面，等待操作系统启动。

console

然后在VNC中点击下一页，然后点击现在安装，然后点击我没有产品密钥，然后勾选接受许可，点击下一页，然后勾选自定义安装。

win0

win1

win2

win3

win4

然后如果镜像本身带virtio，那么应该可见可选系统存储的硬盘及其大小，选中后点击下一页。

win5

win6

然后等待系统安装，应该会自动重启几次，大概耗时10分钟以上。

win7

安装完成后首次登录会要求设置密码，正常设置即可

win8

设置完成后，NOVNC页面左侧有一个弹出框，点击第一个按钮，然后根据登录提示，点击Ctrl+Alt+最后一个按钮，进入登录页面。

4.初始化网络 ​

由于通过本项目设置的PVE是静态网络，所以登陆后需要手动修改绑定的IP地址，不通过DHCP

在桌面右下角右击点出打开 网络和Internet设置，点击后，在弹出的设置页面中点击更改适配器设置

win9

然后在网络链接中勾选以太网，点击更改此连接的设置

win10

在弹出框中点击Internet协议版本4(TCP/IPV4)选中后点击属性

win11

在新弹出的弹出框中，选择并点击使用下面的IP地址(s)，然后分别填入

IP地址(I)：172.16.1.xxx(xxx换成你想绑定的ip，我的vmid是100，为了方便写了100)

子网掩码(U)：255.255.255.0

默认网关(D)：172.16.1.1

然后选择点击使用下面的DNS服务器地址(E)，分别填入

8.8.8.8
-144.144.144.144

然后右下角点击确定，注意不要勾选退出时验证

win12

然后其他弹出框都选确定和是就行了，然后本虚拟机就有网络了。

5.取消CD盘挂载 ​

在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]然后再重启虚拟机，这样就能直接使用了

wk

使用不带virtio的iso镜像开设 ​

1.下载镜像 ​

无virtio的win镜像下载可使用

https://down.idc.wiki/ISOS/Windows/

这块的镜像

virtio的iso镜像可使用

https://down.idc.wiki/ISOS/Toolkit/

或者

https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/

下载

virtio也可以只下载msi包，本地用软件打包成iso压缩格式再本地上传到ProxmoxVE中也可以

这样的话包小一些，前者官方的是包含所有WIN镜像支持的包总计500MB左右，后者自己打包5MB左右

2.virtio导入 ​

注意这里的导入在ProxmoxVE的8.x及之后的版本中，OS这一栏默认可选择virtio启动加载，如图所示

virtio

而在更低版本的ProxmoxVE中，比如7.x和6.x的版本，OS这一栏默认无法选择virtio启动加载

lower

需要手动在Hardware[硬件]中点击Add[添加]添加CD/DVD Drive选择下载好的virtio的ISO文件

lower

然后其他的一切照常，直到

nodisk

这块找不到硬盘，需要选择加载驱动程序

nodisk

然后选择驱动盘是virtio的，点击打开，从amd64那导入对应系统名字的驱动

nodisk

我的是windows server 2019的镜像所以导入的是2k19的驱动，导入完毕后选择导入的驱动，点击下一页

nodisk

nodisk

这样就能看得到硬盘了，选中后继续后续的安装步骤，选中后继续后续的安装步骤如同前面的教程，直到系统安装完毕，进入桌面。

3.通过virtio-win-guest-tools安装驱动 ​

此时安装成功，出现桌面后，还需要手动安装驱动

打开VirtIO驱动所在的CD光驱目录，最下面有一个virtio-win-guest-tools程序，会安装用到的virtio驱动，这个驱动也会包含virtio的网卡驱动

wk

wk

wk

点击安装完毕后就安装上网卡驱动了，后续网络设置参考前面的初始化网络的教程

4.安装网卡驱动(备选) ​

此时安装成功，出现桌面后，还需要手动安装网卡驱动才能连通网络：

  1. 打开 控制面板 → 设备管理器
  2. 找到 以太网控制器，右键选择 更新驱动程序
  3. 选择 浏览我的计算机以查找驱动程序软件 (R)
  4. 浏览到VirtIO驱动所在的CD光驱目录
  5. 打开其中的 NetKVM 文件夹
  6. 根据当前系统版本选择对应的驱动文件夹(和上面相同的操作，我会选择2k19文件夹，里面的amd64驱动)
  7. 确认安装，完成后即可成功加载VirtIO的网卡驱动

wk

wk

wk

后续网络设置参考前面的初始化网络的教程

5.取消CD盘挂载 ​

在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]然后再重启虚拟机，这样就能直接使用了

wk

- +144.144.144.144

然后右下角点击确定，注意不要勾选退出时验证

win12

然后其他弹出框都选确定和是就行了，然后本虚拟机就有网络了。

5.取消CD盘挂载 ​

在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]然后再重启虚拟机，这样就能直接使用了

wk

使用不带virtio的iso镜像开设 ​

1.下载镜像 ​

无virtio的win镜像下载可使用

https://down.idc.wiki/ISOS/Windows/

这块的镜像

virtio的iso镜像可使用

https://down.idc.wiki/ISOS/Toolkit/

或者

https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/

下载

virtio也可以只下载msi包，本地用软件打包成iso压缩格式再本地上传到ProxmoxVE中也可以

这样的话包小一些，前者官方的是包含所有WIN镜像支持的包总计500MB左右，后者自己打包5MB左右

2.virtio导入 ​

注意这里的导入在ProxmoxVE的8.x及之后的版本中，OS这一栏默认可选择virtio启动加载，如图所示

virtio

而在更低版本的ProxmoxVE中，比如7.x和6.x的版本，OS这一栏默认无法选择virtio启动加载

lower

需要手动在Hardware[硬件]中点击Add[添加]添加CD/DVD Drive选择下载好的virtio的ISO文件

lower

然后其他的一切照常，直到

nodisk

这块找不到硬盘，需要选择加载驱动程序

nodisk

然后选择驱动盘是virtio的，点击打开，从amd64那导入对应系统名字的驱动

nodisk

我的是windows server 2019的镜像所以导入的是2k19的驱动，导入完毕后选择导入的驱动，点击下一页

nodisk

nodisk

这样就能看得到硬盘了，选中后继续后续的安装步骤，选中后继续后续的安装步骤如同前面的教程，直到系统安装完毕，进入桌面。

3.通过virtio-win-guest-tools安装驱动 ​

此时安装成功，出现桌面后，还需要手动安装驱动

打开VirtIO驱动所在的CD光驱目录，最下面有一个virtio-win-guest-tools程序，会安装用到的virtio驱动，这个驱动也会包含virtio的网卡驱动

wk

wk

wk

点击安装完毕后就安装上网卡驱动了，后续网络设置参考前面的初始化网络的教程

4.安装网卡驱动(备选) ​

此时安装成功，出现桌面后，还需要手动安装网卡驱动才能连通网络：

  1. 打开 控制面板 → 设备管理器
  2. 找到 以太网控制器，右键选择 更新驱动程序
  3. 选择 浏览我的计算机以查找驱动程序软件 (R)
  4. 浏览到VirtIO驱动所在的CD光驱目录
  5. 打开其中的 NetKVM 文件夹
  6. 根据当前系统版本选择对应的驱动文件夹(和上面相同的操作，我会选择2k19文件夹，里面的amd64驱动)
  7. 确认安装，完成后即可成功加载VirtIO的网卡驱动

wk

wk

wk

后续网络设置参考前面的初始化网络的教程

5.取消CD盘挂载 ​

在ProxmoxVE的web端手动在Hardware[硬件]中点击对应的CD选择Remove[删除]然后再重启虚拟机，这样就能直接使用了

wk

+ \ No newline at end of file diff --git a/hashmap.json b/hashmap.json index 0551ba210c..6b6caca90d 100644 --- a/hashmap.json +++ b/hashmap.json @@ -1 +1 @@ -{"case_case4.md":"857b10dc","case_case5.md":"f59a0f5e","en_guide_block_block_iptables.md":"2f94165c","case_case7.md":"fd93ad86","en_guide_block_block_incus.md":"970a86f8","case_case2.md":"d392b76a","en_guide_block_block_docker.md":"cbf92a99","en_developer_l10n.md":"cd095d45","case_case1.md":"13450359","developer_index.md":"bcfb38d4","case_case6.md":"dbb1e397","developer_l10n.md":"668cddf4","en_guide_block_block_lxd.md":"be399aac","en_developer_index.md":"2781d9ef","case_index.md":"9ebc1ebb","case_case3.md":"ca43af74","en_guide_pve_pve_install.md":"9a42f3ee","en_guide_block_block_pve.md":"b7c2dece","en_guide_docker_docker_install.md":"ecacf3a2","en_guide_docker_docker_macos.md":"fd3f0bcb","en_guide_docker_docker_android.md":"c3074ab7","en_guide_docker_docker_precheck.md":"91792c33","guide_dashboard.md":"9a6230ec","en_guide_pve_images_readme.md":"13a6dece","guide_block_block_incus.md":"5275e5c8","en_incomplete_bashvm.md":"886829a2","incomplete_convoy.md":"f0491c7c","en_incomplete_index.md":"634cf0f9","incomplete_index.md":"4aab6741","incomplete_bashvm.md":"1a8e809b","incomplete_pterodactyl.md":"ec35dbae","en_incomplete_virtualizor-docker.md":"4e86b60d","incomplete_webvirtcloud_retspen.md":"f23e0ec1","en_guide_incus_incus_qa.md":"79b297e9","en_guide_incus_incus_thanks.md":"f575d7ec","en_guide_lxd_lxd_custom.md":"afca2a12","incomplete_webvirtcloud.md":"945a6b84","en_guide_pve_pve_android.md":"05709719","index.md":"6d09fb06","incomplete_virtfusion.md":"f0ae5001","en_guide_lxd_lxd_thanks.md":"a98bd8f1","en_guide_incus_incus_custom.md":"4c2b9e58","en_guide_dashboardq.md":"c810f576","guide_pve_images_readme.md":"0fcbd5ad","guide_docker_docker_windows.md":"b1cad127","en_guide_docker_docker_thanks.md":"6a38453c","guide_dashboardq.md":"dfccd0d0","guide_docker_docker_precheck.md":"db800b72","guide_docker_docker_qa.md":"d9111f4e","guide_docker_docker_macos.md":"27299bbe","en_guide_lxd_lxd_extra_config.md":"ad5f5548","guide_lxd_lxd_precheck.md":"06ae4f7a","guide_incus_incus_qa.md":"d3bc8315","guide_lxd_lxd_qa.md":"cdaa1368","guide_pve_pve_custom.md":"939968ff","guide_incus_incus_precheck.md":"f831343c","guide_block_block_lxd.md":"069ac4f4","guide_pve_pve_install.md":"03f5b3ac","guide_lxd_lxd_thanks.md":"035309c4","guide_pve_pve_android.md":"541a2bf0","guide_pve_pve_thanks.md":"a04e54b5","en_incomplete_webvirtmgr.md":"6d45f601","incomplete_cockpit.md":"5b533bd1","en_incomplete_webvirtcloud_retspen.md":"bc959676","en_index.md":"4bb18770","en_guide_lxd_lxd_precheck.md":"20cf4fb8","en_guide_pve_pve_thanks.md":"699f61e5","en_guide_pve_pve_windows.md":"c5b7b7f6","guide_pve_pve_windows.md":"12c35287","guide_block_block_iptables.md":"f0c17491","en_guide_lxd_lxd_qa.md":"63c8964a","en_guide_incus_incus_extra_config.md":"b24e5ad8","guide_pve_pve_lxc.md":"63c4f147","guide_pve_pve_macos.md":"96eb9a9f","guide_pve_pve_precheck.md":"dc29dc3e","en_guide_lxd_lxd_install.md":"219e45e1","en_guide_incus_incus_lxc.md":"c6d15d7c","guide_block_block_pve.md":"683b1a49","en_guide_lxd_lxd_lxc.md":"25c28cca","guide_docker_docker_install.md":"fceac313","guide_incus_incus_extra_config.md":"19aa23f2","guide_lxd_lxd_install.md":"1ff608ee","en_guide_docker_docker_custom.md":"7f4ad96a","en_guide_dashboard.md":"ee4b3fc1","guide_incus_incus_lxc.md":"9c1f30a1","en_guide_pve_pve_custom.md":"3d92b33c","guide_incus_incus_custom.md":"1b194673","en_incomplete_webvirtcloud.md":"ad5d9cc5","guide_incus_incus_thanks.md":"8677232b","guide_incus_incus_windows.md":"e840e6f0","en_guide_pve_pve_precheck.md":"c455282d","guide_lxd_lxd_lxc.md":"650076ad","guide_lxd_lxd_extra_config.md":"8fbc121f","guide_incus_incus_install.md":"95f8a621","guide_lxd_lxd_custom.md":"5a0d7c6d","guide_docker_docker_android.md":"732be5ab","guide_block_block_docker.md":"e3283eaa","en_guide_pve_pve_kvm.md":"83cab4e3","incomplete_virtualizor-docker.md":"c2bfdb7a","en_guide_pve_pve_macos.md":"2629d0a7","en_guide_pve_pve_lxc.md":"1cfce08a","guide_pve_pve_qa.md":"f01cd6dc","en_guide_pve_pve_qa.md":"19a81901","en_guide_docker_docker_build.md":"f3c9d6b5","guide_docker_docker_thanks.md":"1dfc27a0","en_guide_docker_docker_windows.md":"a1539013","incomplete_webvirtmgr.md":"6d1a23e0","en_incomplete_cockpit.md":"39705808","en_guide_incus_incus_windows.md":"bb2cdc9d","en_incomplete_convoy.md":"99197d89","en_incomplete_virtfusion.md":"eceb8f07","en_incomplete_pterodactyl.md":"5c85a6df","en_guide_incus_incus_precheck.md":"6c589e43","en_guide_docker_docker_qa.md":"ac754529","guide_pve_pve_kvm.md":"9e154693","guide_docker_docker_build.md":"ddbb905f","en_guide_incus_incus_install.md":"3dbc0035","guide_docker_docker_custom.md":"0a00ad78"} +{"en_developer_index.md":"36a7747c","en_developer_l10n.md":"4dc4f4b3","en_guide_block_block_incus.md":"6f7902ba","en_guide_block_block_docker.md":"b4fe6add","en_guide_block_block_pve.md":"0baa3bcd","case_case7.md":"1ef021a6","case_case5.md":"555f9215","case_case6.md":"f3e2edf5","case_index.md":"56532888","developer_l10n.md":"43daef7f","developer_index.md":"50574134","en_guide_dashboard.md":"a98739aa","en_guide_docker_docker_android.md":"3fc2817d","en_guide_docker_docker_build.md":"374f9f42","en_guide_incus_incus_thanks.md":"9f2285ce","en_guide_incus_incus_lxc.md":"99febac7","en_guide_incus_incus_custom.md":"70184a5b","en_guide_incus_incus_extra_config.md":"5f26742c","en_guide_incus_incus_qa.md":"1773ea44","en_guide_docker_docker_macos.md":"19741399","en_guide_docker_docker_windows.md":"82ebd842","en_guide_pve_pve_precheck.md":"b46c1a94","en_guide_pve_pve_custom.md":"1a51ac96","en_guide_lxd_lxd_thanks.md":"af91b5a4","en_guide_lxd_lxd_precheck.md":"fadb2185","case_case2.md":"729cbff7","en_guide_docker_docker_thanks.md":"e2ee842f","en_guide_incus_incus_precheck.md":"2a9177ef","guide_docker_docker_custom.md":"ff937d60","guide_docker_docker_build.md":"42a051cd","guide_dashboard.md":"e77e20e6","case_case3.md":"abbe9b04","en_guide_lxd_lxd_extra_config.md":"4fcf6710","guide_block_block_docker.md":"748c9ec3","en_guide_docker_docker_precheck.md":"08aa05c6","en_guide_docker_docker_custom.md":"670a640f","guide_block_block_pve.md":"1ce49359","en_guide_docker_docker_qa.md":"54c54320","en_guide_pve_images_readme.md":"a40c9248","en_guide_pve_pve_install.md":"ea124862","guide_pve_pve_android.md":"579cbfc0","case_case4.md":"c7b0e7d9","en_guide_lxd_lxd_lxc.md":"851bcb26","en_guide_lxd_lxd_install.md":"2b676884","incomplete_index.md":"4ba82ff7","en_guide_incus_incus_install.md":"f80502c3","en_guide_block_block_iptables.md":"1e8129d7","en_guide_pve_pve_kvm.md":"d2947595","en_guide_pve_pve_lxc.md":"7e809382","en_guide_pve_pve_macos.md":"8346a51d","en_guide_dashboardq.md":"eeb9456d","en_guide_pve_pve_thanks.md":"28da570a","en_incomplete_cockpit.md":"d72e9268","en_guide_lxd_lxd_qa.md":"6a1d11ff","guide_incus_incus_extra_config.md":"bca9f168","guide_incus_incus_install.md":"cae3da3f","guide_incus_incus_thanks.md":"769f470e","guide_lxd_lxd_custom.md":"b762875f","guide_incus_incus_windows.md":"30f7892d","guide_docker_docker_install.md":"2fea9650","guide_lxd_lxd_precheck.md":"c6ab8d98","guide_lxd_lxd_lxc.md":"e2540b4f","case_case1.md":"40a5c4e9","en_index.md":"be47d6f9","guide_lxd_lxd_qa.md":"37100cda","en_incomplete_convoy.md":"cc6e43af","en_guide_block_block_lxd.md":"0c221dad","en_incomplete_virtfusion.md":"c9e0fa6d","guide_incus_incus_qa.md":"dbe0aeb5","guide_lxd_lxd_extra_config.md":"36535e50","guide_block_block_incus.md":"c0c2cbd2","guide_block_block_lxd.md":"f9861f9e","guide_pve_pve_custom.md":"fd708ffe","guide_lxd_lxd_thanks.md":"14c8ba84","guide_pve_images_readme.md":"db0a99a0","en_incomplete_virtualizor-docker.md":"7552a324","guide_pve_pve_precheck.md":"2b124758","guide_pve_pve_install.md":"8e26ca11","guide_pve_pve_lxc.md":"41c738fa","incomplete_webvirtmgr.md":"509f8d4b","incomplete_bashvm.md":"17d16c32","incomplete_convoy.md":"94729ba2","guide_pve_pve_qa.md":"93e38573","guide_pve_pve_windows.md":"538cb762","guide_docker_docker_android.md":"f7ffc5df","guide_pve_pve_kvm.md":"d4fd9ba3","incomplete_virtualizor-docker.md":"a4432ceb","en_incomplete_webvirtcloud.md":"aa4dc433","en_guide_docker_docker_install.md":"6de25cff","incomplete_virtfusion.md":"ce2e2114","incomplete_cockpit.md":"520f225b","guide_pve_pve_macos.md":"bfd0da59","guide_docker_docker_precheck.md":"fe9630c3","index.md":"ee7c4885","incomplete_webvirtcloud_retspen.md":"c02acb84","en_incomplete_webvirtmgr.md":"74f1937c","guide_incus_incus_precheck.md":"3821ff11","guide_docker_docker_qa.md":"e107175a","guide_dashboardq.md":"adc64497","en_incomplete_pterodactyl.md":"6649cbaf","en_incomplete_bashvm.md":"1880d2a3","en_incomplete_index.md":"c7971242","en_guide_pve_pve_android.md":"a3006536","en_guide_pve_pve_qa.md":"d3982a2c","guide_pve_pve_thanks.md":"a2dddf32","guide_block_block_iptables.md":"c570a8e7","guide_docker_docker_thanks.md":"3f680801","en_incomplete_webvirtcloud_retspen.md":"062834e1","incomplete_webvirtcloud.md":"225601ed","guide_lxd_lxd_install.md":"1ebd74c2","guide_incus_incus_custom.md":"0507c488","en_guide_incus_incus_windows.md":"c1838523","guide_docker_docker_windows.md":"2689cc79","en_guide_pve_pve_windows.md":"7c33cbb1","guide_incus_incus_lxc.md":"d08d1e90","incomplete_pterodactyl.md":"10b58889","guide_docker_docker_macos.md":"317f7a9d","en_guide_lxd_lxd_custom.md":"e332d18b"} diff --git a/incomplete/bashvm.html b/incomplete/bashvm.html index dfad78af5b..8ed1bdf657 100644 --- a/incomplete/bashvm.html +++ b/incomplete/bashvm.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

仓库 ​

https://github.com/babywhale321/bashvm

https://bashvm.com/

说明 ​

如果你想深入了解怎么开设一个虚拟机，怎么转发端口，那么这个项目将完全从底层开始，一步步教你如何开设虚拟机

缺点 ​

非常的繁琐，非常的耗时，不如别的项目快速设置网络和开设

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

仓库 ​

https://github.com/babywhale321/bashvm

https://bashvm.com/

说明 ​

如果你想深入了解怎么开设一个虚拟机，怎么转发端口，那么这个项目将完全从底层开始，一步步教你如何开设虚拟机

缺点 ​

非常的繁琐，非常的耗时，不如别的项目快速设置网络和开设

+ \ No newline at end of file diff --git a/incomplete/cockpit.html b/incomplete/cockpit.html index 4c74574fce..205cae7833 100644 --- a/incomplete/cockpit.html +++ b/incomplete/cockpit.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

仓库 ​

hits

https://github.com/oneclickvirt/cockpit

安装 ​

支持的系统：Debian，Ubuntu，Almalinux，Rockylinux，Fedora，Centos，Arch

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh

只安装带容器的

shell
bash install.sh --ct

只安装带虚拟机的

shell
bash install.sh --vm

仅安装面板

shell
bash install.sh

容器和虚拟机依赖都进行安装

shell
bash install.sh --all

缺点 ​

网络自行配置，镜像自行导入，端口自行映射，只是比纯命令行多了一个GUI界面罢了

致谢 ​

https://cockpit-project.org/running.html

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

仓库 ​

hits

https://github.com/oneclickvirt/cockpit

安装 ​

支持的系统：Debian，Ubuntu，Almalinux，Rockylinux，Fedora，Centos，Arch

国际

shell
curl -L https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/cockpit/refs/heads/main/scripts/install.sh -o install.sh && chmod +x install.sh

只安装带容器的

shell
bash install.sh --ct

只安装带虚拟机的

shell
bash install.sh --vm

仅安装面板

shell
bash install.sh

容器和虚拟机依赖都进行安装

shell
bash install.sh --all

缺点 ​

网络自行配置，镜像自行导入，端口自行映射，只是比纯命令行多了一个GUI界面罢了

致谢 ​

https://cockpit-project.org/running.html

+ \ No newline at end of file diff --git a/incomplete/convoy.html b/incomplete/convoy.html index ed53656e9f..e6c0259837 100644 --- a/incomplete/convoy.html +++ b/incomplete/convoy.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

Repo ​

https://github.com/oneclickvirt/convoypanel-scripts

hits

convoypanel-scripts ​

安装前提条件：

  • 已安装 PVE，但不能是同一节点（不能是同一台机器）
  • 系统为 Debian 11
  • CPU 至少 2 核，硬盘至少 20G，内存至少 4G（内存包含 swap）

我不保证这个脚本没有错误，本项目未完整

国际

shell
curl -L https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh

Thanks ​

Base on https://github.com/oneclickvirt/pve

Base on https://docs.convoypanel.com/guide/deployment/#installation

Base on https://github.com/ConvoyPanel/panel

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

Repo ​

https://github.com/oneclickvirt/convoypanel-scripts

hits

convoypanel-scripts ​

安装前提条件：

  • 已安装 PVE，但不能是同一节点（不能是同一台机器）
  • 系统为 Debian 11
  • CPU 至少 2 核，硬盘至少 20G，内存至少 4G（内存包含 swap）

我不保证这个脚本没有错误，本项目未完整

国际

shell
curl -L https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh

国内

shell
curl -L https://cdn.spiritlhl.net/https://github.com/oneclickvirt/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh

Thanks ​

Base on https://github.com/oneclickvirt/pve

Base on https://docs.convoypanel.com/guide/deployment/#installation

Base on https://github.com/ConvoyPanel/panel

+ \ No newline at end of file diff --git a/incomplete/index.html b/incomplete/index.html index 145bee7dae..85d1a59912 100644 --- a/incomplete/index.html +++ b/incomplete/index.html @@ -11,7 +11,7 @@ - + @@ -20,7 +20,7 @@
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

其他虚拟化项目

一些不完整的虚拟化项目

查看项目 →

注意事项

这块每个项目都有对应的缺点，每个项目都不像之前的项目一样简单好用，有一定的学习成本。

难易程度

基于项目本身的使用难度，由易到难排序，越往后你能得到本指南的引导越少。

项目缺点

每个项目都有部分缺点导致不被认为是完整的一键项目，有一些操作需要手动执行命令无法一键化。

- + \ No newline at end of file diff --git a/incomplete/pterodactyl.html b/incomplete/pterodactyl.html index 69fce71729..e6a6b74c4e 100644 --- a/incomplete/pterodactyl.html +++ b/incomplete/pterodactyl.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

Repo ​

https://github.com/oneclickvirt/pterodactyl

hits

pterodactyl-scripts ​

进一步调研发现开设servers和绑定用户极麻烦，不如原生直接docker方便，故而暂不做后续开发了

说明 ​

目前支持的系统

系统类型版本范围备注
Ubuntu20.04(推荐), 22.04, 24.04已支持
Debian11(Bullseye), 12(Bookworm)已支持

Panel ​

panel端执行：

国际

shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh

国内

shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh

Wings ​

wings端执行：

国际

shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh

国内

shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh

Import ​

panel端执行：

国际

shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh

国内

shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh

会生成需要在wings端执行的命令

生成的命令执行完毕后等待20秒以上，避免一些初始化流程未走完，然后wings端再执行：

shell
bash install_wings.sh

然后在http://<your_ip>/admin/nodes就能看到你的节点已经被自动添加纳管，心跳是绿色的

Thanks ​

https://pterodactyl.io/

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

Repo ​

https://github.com/oneclickvirt/pterodactyl

hits

pterodactyl-scripts ​

进一步调研发现开设servers和绑定用户极麻烦，不如原生直接docker方便，故而暂不做后续开发了

说明 ​

目前支持的系统

系统类型版本范围备注
Ubuntu20.04(推荐), 22.04, 24.04已支持
Debian11(Bullseye), 12(Bookworm)已支持

Panel ​

panel端执行：

国际

shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh

国内

shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_pterodactyl.sh -o install_pterodactyl.sh && chmod 777 install_pterodactyl.sh && bash install_pterodactyl.sh

Wings ​

wings端执行：

国际

shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh

国内

shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/install_wings.sh -o install_wings.sh && chmod 777 install_wings.sh && bash install_wings.sh

Import ​

panel端执行：

国际

shell
curl -slk https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh

国内

shell
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/pterodactyl/main/scripts/import_node.sh -o import_node.sh && chmod 777 import_node.sh && bash import_node.sh

会生成需要在wings端执行的命令

生成的命令执行完毕后等待20秒以上，避免一些初始化流程未走完，然后wings端再执行：

shell
bash install_wings.sh

然后在http://<your_ip>/admin/nodes就能看到你的节点已经被自动添加纳管，心跳是绿色的

Thanks ​

https://pterodactyl.io/

+ \ No newline at end of file diff --git a/incomplete/virtfusion.html b/incomplete/virtfusion.html index 4c6919bfa1..ada1b98cea 100644 --- a/incomplete/virtfusion.html +++ b/incomplete/virtfusion.html @@ -11,7 +11,7 @@ - + @@ -25,8 +25,8 @@ curl https://install.virtfusion.net/install-control-rhel-8.sh | sh -s -- --verbose

RHEL9

shell
dnf install curl -y
 curl https://install.virtfusion.net/install-control-rhel-9.sh | sh -s -- --verbose

Ubuntu22.04

shell
apt install curl -y
 curl https://install.virtfusion.net/install-control-ubuntu-22.04.sh | sh -s -- --verbose

Ubuntu24.04

shell
apt install curl -y
-curl https://install.virtfusion.net/install-control-ubuntu-24.04.sh | sh -s -- --verbose

缺点 ​

每台服务器每个邮箱只有一次30天试用的证书，无永久的免费的证书

- +curl https://install.virtfusion.net/install-control-ubuntu-24.04.sh | sh -s -- --verbose

缺点 ​

每台服务器每个邮箱只有一次30天试用的证书，无永久的免费的证书

+ \ No newline at end of file diff --git a/incomplete/virtualizor-docker.html b/incomplete/virtualizor-docker.html index 4241b2d33c..2e6f847c05 100644 --- a/incomplete/virtualizor-docker.html +++ b/incomplete/virtualizor-docker.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@ -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

仓库 ​

https://github.com/ivstiv/virtualizor-docker

说明 ​

在docker中开设的 virtualizor

证书用的是试用的证书，有效期一天，且默认只安装了OpenVZ的虚拟化方式

缺点 ​

毫无社区，一切自行摸索

admin面板的端口不要看脚本的提示信息，以仓库说明为准。

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

仓库 ​

https://github.com/ivstiv/virtualizor-docker

说明 ​

在docker中开设的 virtualizor

证书用的是试用的证书，有效期一天，且默认只安装了OpenVZ的虚拟化方式

缺点 ​

毫无社区，一切自行摸索

admin面板的端口不要看脚本的提示信息，以仓库说明为准。

+ \ No newline at end of file diff --git a/incomplete/webvirtcloud.html b/incomplete/webvirtcloud.html index 8c836cd03a..5f9ab36e5f 100644 --- a/incomplete/webvirtcloud.html +++ b/incomplete/webvirtcloud.html @@ -11,7 +11,7 @@ - + @@ -66,8 +66,8 @@ systemctl status prometheus-libvirt-exporter

如果以上都查不出问题，那么就需要到Controller控制端执行：

shell
docker exec -it webvirtcloud-backend /bin/sh
 vi webvirtcloud/settings/production.py

将 DEBUG=False 改成 DEBUG=True，然后保存文件后，容器内执行：

shell
UV_PROJECT_ENVIRONMENT=/usr/local uv sync --dev

然后exit退出容器后，执行：

shell
docker restart webvirtcloud-backend
 sleep 3
-docker logs webvirtcloud-backend -f

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

Controller 重启后 Docker 容器不自重启 ​

如果 Docker 容器在系统重启后没有自动重启，执行以下命令：

bash
docker start $(docker ps -a -q)

5. 缺点 ​

系统镜像是写死的，没法使用自己制作的自定义镜像，也没办法导出使用。

同 https://github.com/retspen/webvirtcloud 不是同一个项目，不要搞混淆了。

致谢 ​

https://webvirt.cloud/

- +docker logs webvirtcloud-backend -f

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

Controller 重启后 Docker 容器不自重启 ​

如果 Docker 容器在系统重启后没有自动重启，执行以下命令：

bash
docker start $(docker ps -a -q)

5. 缺点 ​

系统镜像是写死的，没法使用自己制作的自定义镜像，也没办法导出使用。

同 https://github.com/retspen/webvirtcloud 不是同一个项目，不要搞混淆了。

致谢 ​

https://webvirt.cloud/

+ \ No newline at end of file diff --git a/incomplete/webvirtcloud_retspen.html b/incomplete/webvirtcloud_retspen.html index 0e2e927656..ea1dad65fa 100644 --- a/incomplete/webvirtcloud_retspen.html +++ b/incomplete/webvirtcloud_retspen.html @@ -11,7 +11,7 @@ - + @@ -25,8 +25,8 @@ && chmod +x install_webvirt_cloud_retspen.sh \ && bash install_webvirt_cloud_retspen.sh

安装完成后打开公网IP地址，就能看到登录页面。

登录信息用户名和密码都是admin，记得登录后自行修改。

开设Linux虚拟机 ​

进入控制面板后，修改完admin的密码后，需要自行设置计算节点。

vcr1

选择本地类型，添加命名为local。

vcr2

创建完成后，点击眼睛按钮，进入查看

vcr3

在存储一栏中添加存储，选择Dir类型，添加名字叫local。如果你需要使用ISO类型的系统引导，那么需要创建ISO类型的存储，如果不需要的话跟着本指南走，就仅需要创建Dir类型。

vcr4

vcr5

创建完毕后，下载对应系统的qcow2文件，使用下面这个仓库的链接

https://github.com/oneclickvirt/pve_kvm_images/releases/tag/images

示例中下载使用debian12的qcow2镜像使用

shell
cd /var/lib/libvirt/images
 wget https://github.com/oneclickvirt/pve_kvm_images/releases/download/images/debian12.qcow2
-chmod 777 debian12.qcow2

回到实例页面创建实例

vcr6

计算节点选择local

vcr7

芯片组使用默认的就行，换不换都没问题

vcr8

创建虚拟机可以使用预定义的配置大小，也可以自行使用自定义大小，看你的选择。

vcr9

注意这块填写的实例名字不能和系统名字重复，比如示例中就不能填写debian12。

vcr10

创建成功后不能立即点击开机。

vcr11

需要修改磁盘设置。

vcr12

这块修改qcow2文件为debian12.qcow2，对应之前下载的qcow2的文件的名字，使用镜像。

vcr13

修改完成确认无误后，才可回到电源页面开机。

vcr14

镜像的默认登录的用户名是root，密码是password或者是 oneclickvirt。

缺点 ​

网络还是没有自动配置，不如上一个项目智能，还得手动配置一下。

- +chmod 777 debian12.qcow2

回到实例页面创建实例

vcr6

计算节点选择local

vcr7

芯片组使用默认的就行，换不换都没问题

vcr8

创建虚拟机可以使用预定义的配置大小，也可以自行使用自定义大小，看你的选择。

vcr9

注意这块填写的实例名字不能和系统名字重复，比如示例中就不能填写debian12。

vcr10

创建成功后不能立即点击开机。

vcr11

需要修改磁盘设置。

vcr12

这块修改qcow2文件为debian12.qcow2，对应之前下载的qcow2的文件的名字，使用镜像。

vcr13

修改完成确认无误后，才可回到电源页面开机。

vcr14

镜像的默认登录的用户名是root，密码是password或者是 oneclickvirt。

缺点 ​

网络还是没有自动配置，不如上一个项目智能，还得手动配置一下。

+ \ No newline at end of file diff --git a/incomplete/webvirtmgr.html b/incomplete/webvirtmgr.html index 0d88682b41..76456ffc45 100644 --- a/incomplete/webvirtmgr.html +++ b/incomplete/webvirtmgr.html @@ -11,7 +11,7 @@ - + @@ -23,8 +23,8 @@ && chmod +x install_webvirtmgr.sh \ && bash install_webvirtmgr.sh

国内

bash
curl -slk https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/webvirtcloud/main/scripts/install_webvirtmgr.sh -o install_webvirtmgr.sh \
 && chmod +x install_webvirtmgr.sh \
-&& bash install_webvirtmgr.sh

缺点 ​

原项目已经不再有维护，完全不推荐使用。

- +&& bash install_webvirtmgr.sh

缺点 ​

原项目已经不再有维护，完全不推荐使用。

+ \ No newline at end of file diff --git a/index.html b/index.html index 4dcf971d71..c6b6e7bdaf 100644 --- a/index.html +++ b/index.html @@ -11,7 +11,7 @@ - + @@ -20,7 +20,7 @@
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

一键虚拟化项目

开源、易于使用的服务器虚拟化项目

开始使用 →

一键使用

支持一键命令安装使用，轻松在X86_64和ARM架构的服务器上创建虚拟机或容器

基于主流系统开发

基于 Debian、Ubuntu、Centos 等系统的长期维护版本开发，无论是什么系统总有一个方法能让你虚拟化出容器或虚拟机

端口转发和IP分配自动化

自带内外网端口转发和IP地址自动分配(含IPV6、IPV4)，支持TCP/UDP、VNC/RDP等协议，无需人工管理

批量虚拟化

支持使用 QEMU、KVM、LXC、Docker 虚拟化批量开设容器或虚拟机

多系统多环境支持

开设出的容器或虚拟机已支持主流系统，涵盖 Linux、Windows、MacOS、Android 系统，也支持纯粹的浏览器环境或桌面环境

自限制滥用

部分虚拟化开设的容器或虚拟机支持设置屏蔽和装载限制，避免被用于滥用

- + \ No newline at end of file diff --git a/sitemap.xml b/sitemap.xml index f5566775fd..88013b9485 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -1 +1 @@ -https://www.spiritlhl.net/case/case3.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/developer/2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/dashboard.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/docker/docker_macos.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/incus/incus_extra_config.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_custom.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/pve/pve_android.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/pve/images/readme.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/incomplete/cockpit.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/case/case2.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/case/case1.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/case/case5.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/case/case6.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/case/case4.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/case/case7.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/case/2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/developer/l10n.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/dashboardq.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/docker/docker_precheck.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/docker/docker_thanks.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/docker/docker_qa.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/docker/docker_windows.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/incus/incus_custom.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/incus/incus_install.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/incus/incus_lxc.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/incus/incus_precheck.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/incus/incus_thanks.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/incus/incus_qa.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/incus/incus_windows.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_install.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_lxc.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_extra_config.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_precheck.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_qa.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_thanks.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/pve/pve_custom.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/pve/pve_install.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/pve/pve_kvm.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/pve/pve_lxc.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/pve/pve_precheck.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/pve/pve_qa.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/pve/pve_thanks.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/incomplete/bashvm.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/incomplete/convoy.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/incomplete/pterodactyl.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/incomplete/virtfusion.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/incomplete/virtualizor-docker.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/incomplete/webvirtcloud.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/incomplete/2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/incomplete/webvirtcloud_retspen.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/index.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/incomplete/webvirtmgr.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/block/block_docker.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/pve/images/readme.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/developer/2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_android.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_custom.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_custom.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/incomplete/bashvm.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/block/block_docker.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/block/block_incus.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/block/block_lxd.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/developer/l10n.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/block/block_iptables.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/block/block_pve.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/dashboardq.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/dashboard.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_build.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_install.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_custom.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_qa.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_macos.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_precheck.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_thanks.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_lxc.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_windows.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_install.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_extra_config.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_precheck.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_qa.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_thanks.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_extra_config.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_windows.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_install.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_qa.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_lxc.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_precheck.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_thanks.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_android.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_install.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_kvm.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_custom.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_lxc.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_precheck.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_qa.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_thanks.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/incomplete/cockpit.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/incomplete/convoy.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/incomplete/pterodactyl.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/incomplete/2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/incomplete/virtfusion.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/incomplete/virtualizor-docker.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/incomplete/webvirtcloud.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/incomplete/webvirtcloud_retspen.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/incomplete/webvirtmgr.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/block/block_lxd.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/block/block_pve.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/block/block_incus.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/docker/docker_build.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/docker/docker_android.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/block/block_iptables.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/docker/docker_custom.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/docker/docker_install.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_macos.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/pve/pve_macos.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/guide/pve/pve_windows.html2025-05-20T07:33:09.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_windows.html2025-05-20T07:33:09.000Z \ No newline at end of file +https://www.spiritlhl.net/case/case1.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/developer/2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/dashboard.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/docker/docker_android.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/incus/incus_custom.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_custom.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/pve/pve_android.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/incomplete/bashvm.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/case/case3.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/case/case5.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/case/case2.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/case/case4.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/case/case7.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/case/2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/case/case6.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/developer/l10n.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/dashboardq.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/docker/docker_build.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/docker/docker_custom.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/docker/docker_install.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/docker/docker_macos.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/docker/docker_qa.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/docker/docker_precheck.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/docker/docker_thanks.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/docker/docker_windows.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/incus/incus_extra_config.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/incus/incus_install.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/incus/incus_qa.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/incus/incus_precheck.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/incus/incus_lxc.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/incus/incus_thanks.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/incus/incus_windows.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_extra_config.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_install.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_lxc.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_precheck.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_qa.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_thanks.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/pve/pve_custom.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/pve/pve_install.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/pve/pve_lxc.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/pve/pve_kvm.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/pve/pve_precheck.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/pve/pve_qa.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/pve/pve_thanks.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/incomplete/cockpit.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/incomplete/convoy.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/incomplete/2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/incomplete/pterodactyl.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/incomplete/virtualizor-docker.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/incomplete/virtfusion.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/incomplete/webvirtcloud_retspen.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/incomplete/webvirtcloud.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/incomplete/webvirtmgr.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/index.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/pve/images/readme.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/block/block_docker.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/developer/2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_android.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_custom.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_lxc.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/incomplete/bashvm.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/block/block_iptables.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/pve/images/readme.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/developer/l10n.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/block/block_lxd.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/block/block_pve.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/dashboard.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/dashboardq.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_build.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_install.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/block/block_incus.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_precheck.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_thanks.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/block/block_iptables.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_windows.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_precheck.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_macos.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_install.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_qa.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_thanks.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_extra_config.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_qa.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_windows.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_install.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_extra_config.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_precheck.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_qa.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_thanks.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_install.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_custom.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_lxc.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_kvm.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_custom.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_precheck.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_lxc.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_qa.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_thanks.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/incomplete/cockpit.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/incomplete/convoy.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_android.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/incomplete/virtfusion.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/incomplete/pterodactyl.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/incomplete/2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/incomplete/virtualizor-docker.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/incomplete/webvirtcloud.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/incomplete/webvirtmgr.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/incomplete/webvirtcloud_retspen.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/block/block_lxd.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/block/block_docker.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/block/block_incus.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/block/block_pve.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_custom.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_windows.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_macos.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/pve/pve_macos.html2025-05-20T08:49:15.000Zhttps://www.spiritlhl.net/guide/pve/pve_windows.html2025-05-20T08:49:15.000Z \ No newline at end of file