diff --git a/404.html b/404.html index b20b7a19a8..11e64afde3 100644 --- a/404.html +++ b/404.html @@ -16,8 +16,8 @@ -
一键虚拟化项目

简体中文

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
- +
一键虚拟化项目

简体中文

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.5ed7d81a.js b/assets/case_case1.md.2d748f96.js similarity index 99% rename from assets/case_case1.md.5ed7d81a.js rename to assets/case_case1.md.2d748f96.js index 35c4e4566d..3700f144d6 100644 --- a/assets/case_case1.md.5ed7d81a.js +++ b/assets/case_case1.md.2d748f96.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/case1.md","filePath":"case/case1.md","lastUpdated":1704976888000}'),o={name:"case/case1.md"},p=n(`

仓库 ​

https://github.com/spiritLHLS/one-click-installation-script

Hits

所有脚本如需在国内服务器使用，请在链接前加上https://ghproxy.com/确保命令可以下载本仓库的shell脚本执行

一键修复脚本 ​

运行所有一键修复脚本前注意看说明，以及保证服务器无重要数据，运行后造成的一切后果作者不负任何责任，自行评判风险！

一键尝试修复apt源 ​

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

一键尝试修复系统时间 ​

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警告 ​

不要在生产环境上使用该脚本，否则容易造成网络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日志记录大小释放系统盘空间 ​

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中执行后果自负！

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环境 ​

原始用途是方便快捷的在按小时计费的超大型服务器上部署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语言环境 ​

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环境 ​

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环境 ​

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环境 ​

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 ​

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 ​

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平台 ​

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平台 ​

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

一键删除平台监控 ​

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/case1.md","filePath":"case/case1.md","lastUpdated":1705324601000}'),o={name:"case/case1.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_case1.md.5ed7d81a.lean.js b/assets/case_case1.md.2d748f96.lean.js
similarity index 99%
rename from assets/case_case1.md.5ed7d81a.lean.js
rename to assets/case_case1.md.2d748f96.lean.js
index 35c4e4566d..3700f144d6 100644
--- a/assets/case_case1.md.5ed7d81a.lean.js
+++ b/assets/case_case1.md.2d748f96.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/case1.md","filePath":"case/case1.md","lastUpdated":1704976888000}'),o={name:"case/case1.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/case1.md","filePath":"case/case1.md","lastUpdated":1705324601000}'),o={name:"case/case1.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.2ef48af4.js b/assets/case_case2.md.060e69bf.js
similarity index 99%
rename from assets/case_case2.md.2ef48af4.js
rename to assets/case_case2.md.060e69bf.js
index d41ba61cf3..f95622037b 100644
--- a/assets/case_case2.md.2ef48af4.js
+++ b/assets/case_case2.md.060e69bf.js
@@ -1 +1 @@
-import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case2.md","filePath":"case/case2.md","lastUpdated":1704976888000}'),p={name:"case/case2.md"},o=t('
仓库 ​
https://github.com/spiritLHLS/ecs
Hits
融合怪测评脚本 ​
支持系统：
Ubuntu 18+, Debian 8+, Centos 7+, Fedora 33+, Almalinux 8.5+, OracleLinux 8+, RockyLinux 8+, AstraLinux CE, Arch
半支持系统：
FreeBSD(前提已执行pkg install -y curl bash)，Armbian
Armbian系统部分检测和测试暂不支持，部分会编码错误
FreeBSD系统的硬盘测试和CPU测试目前是半残的，有些东西显示有问题
FreeBSD系统的分享链接的预处理部分sed命令存在问题未删除部分无效内容
支持架构：
基本都支持，无论是本地服务器还是云端服务器
支持地域：
能连得上网都支持
部分服务器运行测试有各类bug一键修复后再测试 ​
一键修复各种系统原生bug的仓库：
https://github.com/spiritLHLS/one-click-installation-script
如若还有系统bug请到上面仓库的issues反映，脚本原生BUG该仓库issues反映
融合怪命令 ​
交互形式 ​
bash
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh
或
bash
curl -L https://github.com/spiritLHLS/ecs/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh
或
bash <(wget -qO- bash.spiritlhl.net/ecs)
无交互形式-参数模式 ​
bash
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh -h
或
bash
curl -L https://github.com/spiritLHLS/ecs/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh -h
或通过
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh
下载文件后使用类似
bash
bash ecs.sh -m 1
这样的参数命令指定选项执行
以下为参数说明：
指令项目说明备注
-m必填项可指定原本menu中的对应选项，最多支持三层选择，例如执行bash ecs.sh -m 5 1 1将选择主菜单第5选项下的第1选项下的子选项1的脚本执行可缺省仅指定一个参数，如-m 1仅指定执行融合怪完全体，执行-m 1 0以及-m 1 0 0都是指定执行融合怪完全体
-i可选项可指定回程路由测试中的目标IPV4地址可通过ip.sb、ipinfo.io等网站获取本地IPV4地址后指定
-r可选项可指定回程路由测试中的目标IPV4地址，可选b g s c 分别对应北京、广州、上海、成都```如-r b指定测试北京回程(三网)
-base可选项可指定仅测试基础的系统信息无该指令则默认按照menu选项的组合测试
-ctype可选项可指定通过何种方式测试cpu，可选gb4、gb5、gb6分别对应geekbench的4、5、6版本无该指令则默认使用sysbench测试
-dtype可选项可指定测试硬盘IO的程序，可选dd、fio，前者测试快后者测试慢无该指令则默认都使用进行测试
-mdisk可选项可指定测试多个挂载盘的IO注意本指令包含测试系统盘
-banup可选项可指定强制不生成分享链接无该指令则默认生成分享链接
IP质量检测 ​
  • IP质量检测，含多家数据库查询，含黑名单查询
  • 含 IPV4 和 IPV6 检测，含ASN和地址查询
  • 含25端口的邮箱可达性检测，如果某个邮箱可达，则可搭建邮局
bash
bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/za/-/raw/main/qzcheck.sh)
或
bash
bash <(wget -qO- bash.spiritlhl.net/ecs-ipcheck)
或
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/ecs/main/qzcheck.sh)
融合怪说明 ​
融合怪脚本最好在 /root 路径下执行，避免各种奇奇怪怪的问题
融合怪的执行结果保存在当前路径下的test_result.txt中，可先退出SSH登录后续再查看文件
融合怪的完整版和精简版运行完毕会自动上传结果到pastebin并回传分享链接，如果测一半想要退出，那么按Ctrl+C同时按下可终止测试，此时会自动退出删除残余文件
有时候想要测一些配置极其拉跨的机器时，推荐使用screen命令挂起执行选项1的融合怪，然后你可以关闭SSH连接，等待一段时间后使用cat test_result.txt查看运行的实时状况，这样可以避免IO或者CPU过于垃圾导致的测试过程中的SSH连接中断，就不会测一半啥都没了，假如screen中显示乱码，也没问题，结果是不带乱码的
最烂机器测试的例子(跑了47分钟一样测完)：跳转
使用CDN加速已支持国内和国外服务器测试，但国内受CDN连通性或国内机器带宽大小的限制加载可能会慢很多
融合怪测试说明以及部分测试结果的内容解释(初次使用推荐查看)：
除了已标注的原创内容，其余所有分区均为借鉴并进行优化修改后的版本，与原始对应的脚本不一样
所有检测都有考虑过使用并行测试，并在部分环节使用了该技术，比正常的顺序执行优化了2~3分钟，属于是独有的，暂无哪家的测试有同类技术
系统基础信息测试融合了多家还有我自己修补的部分检测(systl、NAT类型检测，并发ASN检测等)，应该是目前最全面最通用的了
CPU测试使用sysbench测试得分，不是yabs的gb4或gb5，前者只是简单的计算质数测试速度快，后者geekbench是综合测试系统算加权得分，不是同一种东西，别互相比较了，没有可比性
CPU测试单核得分在5000以上的可以算第一梯队，4000到5000分算第二梯队，每1000分算一档，自己看看自己在哪个档位吧
AMD的7950x单核满血性能得分在6500左右，AMD的5950x单核满血性能得分5700左右，Intel普通的CPU(E5之类的)在1000~800左右，低于500的单核CPU可以算是比较烂的了
IO测试收录了两种，来源于lemonbench的dd磁盘测试和yabs的fio磁盘测试，综合来看会比较好，前者可能误差偏大但测试速度快无硬盘大小限制，后者真实一点但测试速度慢有硬盘以及内存大小限制
流媒体测试收录了两种，一个是go编译的二进制文件和一个shell脚本版本，二者各有优劣，互相对比看即可
tiktok测试有superbench和lmc999两种版本，哪个失效了随时可能更新为其中一种版本，以最新的脚本为准
回程路由测试选用的GO编译的二进制版本和朋友PR的版本，本人做了优化适配多个IP列表以及融合部分查询
IP质量检测纯原创，如有bug或者更多数据库来源可在issues中提出，日常看IP2Location数据库的IP类型即可，其中的25端口邮箱可达，则可搭建邮局
融合怪的IP质量检测是简化过的，没有查询Cloudflare的威胁得分，个人原创区的IP质量检测才是完整版(或者仓库说明中列出的那个IP质量检测的命令也是完整版)
三网测速使用自写的测速脚本，尽量使用最新节点最新组件进行测速，且有备用go版本测速，做到自更新测速节点列表，自适应系统环境测速
其他第三方脚本归纳到了第三方脚本区，里面有同类型脚本不同作者的各种竞品脚本，如果融合怪不能使你满意或者有错误，可以看看那部分
原创脚本区是个人原创的部分，有事没事也可以看看，可能会更新某些偏门或者独到的脚本
VPS测试，VPS测速，VPS综合性能测试，VPS回程线路测试，VPS流媒体测试等所有测试融合的脚本，本脚本能融合的都融合了
融合怪功能 ​
  • [x] 自由组合测试方向和单项测试以及合集收录第三方脚本
  • [x] 基础信息查询--感谢bench.sh、superbench.sh、yabs、lemonbench开源，本人整理修改优化，同原版均不一致
  • [x] CPU测试--感谢lemonbench开源，本人整理修改优化
  • [x] 内存测试--感谢lemonbench开源，本人整理修改优化
  • [x] 磁盘dd读写测试--感谢lemonbench开源，本人整理修改优化
  • [x] 硬盘fio读写测试--感谢yabs开源，本人整理修改优化
  • [x] 御三家流媒体解锁测试--感谢sjlleo的二进制文件，本人修改整理优化
  • [x] 常用流媒体解锁测试--感谢RegionRestrictionCheck开源，本人整理修改优化
  • [x] Tiktok解锁--感谢TikTokCheck开源，本人整理修改优化
  • [x] 三网回程以及路由延迟--感谢zhanghanyun/backtrace开源，本人整理修改
  • [x] 回程路由以及带宽类型检测(商宽/家宽/数据中心)--由fscarmen的PR以及本人的技术思路提供，本人后续修改优化
  • [x] IP质量与25端口检测(含IPV4和IPV6)--本脚本独创，感谢互联网提供的查询资源
  • [x] speedtest测速--使用自写ecsspeed仓库，自动更新测速服务器ID，一劳永逸解决老是要手动更新测速ID的问题
友链 ​
测评频道 ​
https://t.me/vps_reviews ​
自动更新测速服务器节点列表的网络基准测试脚本 ​
https://github.com/spiritLHLS/ecsspeed ​
脚本概况 ​
主界面：
图片
选项1融合怪完全体：
图片图片图片图片图片图片图片
选项6原创区：
图片
',82),l=[o];function n(r,c,i,h,d,b){return a(),e("div",null,l)}const y=s(p,[["render",n]]);export{m as __pageData,y as default};
+import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case2.md","filePath":"case/case2.md","lastUpdated":1705324601000}'),p={name:"case/case2.md"},o=t('
仓库 ​
https://github.com/spiritLHLS/ecs
Hits
融合怪测评脚本 ​
支持系统：
Ubuntu 18+, Debian 8+, Centos 7+, Fedora 33+, Almalinux 8.5+, OracleLinux 8+, RockyLinux 8+, AstraLinux CE, Arch
半支持系统：
FreeBSD(前提已执行pkg install -y curl bash)，Armbian
Armbian系统部分检测和测试暂不支持，部分会编码错误
FreeBSD系统的硬盘测试和CPU测试目前是半残的，有些东西显示有问题
FreeBSD系统的分享链接的预处理部分sed命令存在问题未删除部分无效内容
支持架构：
基本都支持，无论是本地服务器还是云端服务器
支持地域：
能连得上网都支持
部分服务器运行测试有各类bug一键修复后再测试 ​
一键修复各种系统原生bug的仓库：
https://github.com/spiritLHLS/one-click-installation-script
如若还有系统bug请到上面仓库的issues反映，脚本原生BUG该仓库issues反映
融合怪命令 ​
交互形式 ​
bash
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh
或
bash
curl -L https://github.com/spiritLHLS/ecs/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh
或
bash <(wget -qO- bash.spiritlhl.net/ecs)
无交互形式-参数模式 ​
bash
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh -h
或
bash
curl -L https://github.com/spiritLHLS/ecs/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh -h
或通过
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh
下载文件后使用类似
bash
bash ecs.sh -m 1
这样的参数命令指定选项执行
以下为参数说明：
指令项目说明备注
-m必填项可指定原本menu中的对应选项，最多支持三层选择，例如执行bash ecs.sh -m 5 1 1将选择主菜单第5选项下的第1选项下的子选项1的脚本执行可缺省仅指定一个参数，如-m 1仅指定执行融合怪完全体，执行-m 1 0以及-m 1 0 0都是指定执行融合怪完全体
-i可选项可指定回程路由测试中的目标IPV4地址可通过ip.sb、ipinfo.io等网站获取本地IPV4地址后指定
-r可选项可指定回程路由测试中的目标IPV4地址，可选b g s c 分别对应北京、广州、上海、成都```如-r b指定测试北京回程(三网)
-base可选项可指定仅测试基础的系统信息无该指令则默认按照menu选项的组合测试
-ctype可选项可指定通过何种方式测试cpu，可选gb4、gb5、gb6分别对应geekbench的4、5、6版本无该指令则默认使用sysbench测试
-dtype可选项可指定测试硬盘IO的程序，可选dd、fio，前者测试快后者测试慢无该指令则默认都使用进行测试
-mdisk可选项可指定测试多个挂载盘的IO注意本指令包含测试系统盘
-banup可选项可指定强制不生成分享链接无该指令则默认生成分享链接
IP质量检测 ​
  • IP质量检测，含多家数据库查询，含黑名单查询
  • 含 IPV4 和 IPV6 检测，含ASN和地址查询
  • 含25端口的邮箱可达性检测，如果某个邮箱可达，则可搭建邮局
bash
bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/za/-/raw/main/qzcheck.sh)
或
bash
bash <(wget -qO- bash.spiritlhl.net/ecs-ipcheck)
或
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/ecs/main/qzcheck.sh)
融合怪说明 ​
融合怪脚本最好在 /root 路径下执行，避免各种奇奇怪怪的问题
融合怪的执行结果保存在当前路径下的test_result.txt中，可先退出SSH登录后续再查看文件
融合怪的完整版和精简版运行完毕会自动上传结果到pastebin并回传分享链接，如果测一半想要退出，那么按Ctrl+C同时按下可终止测试，此时会自动退出删除残余文件
有时候想要测一些配置极其拉跨的机器时，推荐使用screen命令挂起执行选项1的融合怪，然后你可以关闭SSH连接，等待一段时间后使用cat test_result.txt查看运行的实时状况，这样可以避免IO或者CPU过于垃圾导致的测试过程中的SSH连接中断，就不会测一半啥都没了，假如screen中显示乱码，也没问题，结果是不带乱码的
最烂机器测试的例子(跑了47分钟一样测完)：跳转
使用CDN加速已支持国内和国外服务器测试，但国内受CDN连通性或国内机器带宽大小的限制加载可能会慢很多
融合怪测试说明以及部分测试结果的内容解释(初次使用推荐查看)：
除了已标注的原创内容，其余所有分区均为借鉴并进行优化修改后的版本，与原始对应的脚本不一样
所有检测都有考虑过使用并行测试，并在部分环节使用了该技术，比正常的顺序执行优化了2~3分钟，属于是独有的，暂无哪家的测试有同类技术
系统基础信息测试融合了多家还有我自己修补的部分检测(systl、NAT类型检测，并发ASN检测等)，应该是目前最全面最通用的了
CPU测试使用sysbench测试得分，不是yabs的gb4或gb5，前者只是简单的计算质数测试速度快，后者geekbench是综合测试系统算加权得分，不是同一种东西，别互相比较了，没有可比性
CPU测试单核得分在5000以上的可以算第一梯队，4000到5000分算第二梯队，每1000分算一档，自己看看自己在哪个档位吧
AMD的7950x单核满血性能得分在6500左右，AMD的5950x单核满血性能得分5700左右，Intel普通的CPU(E5之类的)在1000~800左右，低于500的单核CPU可以算是比较烂的了
IO测试收录了两种，来源于lemonbench的dd磁盘测试和yabs的fio磁盘测试，综合来看会比较好，前者可能误差偏大但测试速度快无硬盘大小限制，后者真实一点但测试速度慢有硬盘以及内存大小限制
流媒体测试收录了两种，一个是go编译的二进制文件和一个shell脚本版本，二者各有优劣，互相对比看即可
tiktok测试有superbench和lmc999两种版本，哪个失效了随时可能更新为其中一种版本，以最新的脚本为准
回程路由测试选用的GO编译的二进制版本和朋友PR的版本，本人做了优化适配多个IP列表以及融合部分查询
IP质量检测纯原创，如有bug或者更多数据库来源可在issues中提出，日常看IP2Location数据库的IP类型即可，其中的25端口邮箱可达，则可搭建邮局
融合怪的IP质量检测是简化过的，没有查询Cloudflare的威胁得分，个人原创区的IP质量检测才是完整版(或者仓库说明中列出的那个IP质量检测的命令也是完整版)
三网测速使用自写的测速脚本，尽量使用最新节点最新组件进行测速，且有备用go版本测速，做到自更新测速节点列表，自适应系统环境测速
其他第三方脚本归纳到了第三方脚本区，里面有同类型脚本不同作者的各种竞品脚本，如果融合怪不能使你满意或者有错误，可以看看那部分
原创脚本区是个人原创的部分，有事没事也可以看看，可能会更新某些偏门或者独到的脚本
VPS测试，VPS测速，VPS综合性能测试，VPS回程线路测试，VPS流媒体测试等所有测试融合的脚本，本脚本能融合的都融合了
融合怪功能 ​
  • [x] 自由组合测试方向和单项测试以及合集收录第三方脚本
  • [x] 基础信息查询--感谢bench.sh、superbench.sh、yabs、lemonbench开源，本人整理修改优化，同原版均不一致
  • [x] CPU测试--感谢lemonbench开源，本人整理修改优化
  • [x] 内存测试--感谢lemonbench开源，本人整理修改优化
  • [x] 磁盘dd读写测试--感谢lemonbench开源，本人整理修改优化
  • [x] 硬盘fio读写测试--感谢yabs开源，本人整理修改优化
  • [x] 御三家流媒体解锁测试--感谢sjlleo的二进制文件，本人修改整理优化
  • [x] 常用流媒体解锁测试--感谢RegionRestrictionCheck开源，本人整理修改优化
  • [x] Tiktok解锁--感谢TikTokCheck开源，本人整理修改优化
  • [x] 三网回程以及路由延迟--感谢zhanghanyun/backtrace开源，本人整理修改
  • [x] 回程路由以及带宽类型检测(商宽/家宽/数据中心)--由fscarmen的PR以及本人的技术思路提供，本人后续修改优化
  • [x] IP质量与25端口检测(含IPV4和IPV6)--本脚本独创，感谢互联网提供的查询资源
  • [x] speedtest测速--使用自写ecsspeed仓库，自动更新测速服务器ID，一劳永逸解决老是要手动更新测速ID的问题
友链 ​
测评频道 ​
https://t.me/vps_reviews ​
自动更新测速服务器节点列表的网络基准测试脚本 ​
https://github.com/spiritLHLS/ecsspeed ​
脚本概况 ​
主界面：
图片
选项1融合怪完全体：
图片图片图片图片图片图片图片
选项6原创区：
图片
',82),l=[o];function n(r,c,i,h,d,b){return a(),e("div",null,l)}const y=s(p,[["render",n]]);export{m as __pageData,y as default};
diff --git a/assets/case_case2.md.2ef48af4.lean.js b/assets/case_case2.md.060e69bf.lean.js
similarity index 99%
rename from assets/case_case2.md.2ef48af4.lean.js
rename to assets/case_case2.md.060e69bf.lean.js
index d41ba61cf3..f95622037b 100644
--- a/assets/case_case2.md.2ef48af4.lean.js
+++ b/assets/case_case2.md.060e69bf.lean.js
@@ -1 +1 @@
-import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case2.md","filePath":"case/case2.md","lastUpdated":1704976888000}'),p={name:"case/case2.md"},o=t('
仓库 ​
https://github.com/spiritLHLS/ecs
Hits
融合怪测评脚本 ​
支持系统：
Ubuntu 18+, Debian 8+, Centos 7+, Fedora 33+, Almalinux 8.5+, OracleLinux 8+, RockyLinux 8+, AstraLinux CE, Arch
半支持系统：
FreeBSD(前提已执行pkg install -y curl bash)，Armbian
Armbian系统部分检测和测试暂不支持，部分会编码错误
FreeBSD系统的硬盘测试和CPU测试目前是半残的，有些东西显示有问题
FreeBSD系统的分享链接的预处理部分sed命令存在问题未删除部分无效内容
支持架构：
基本都支持，无论是本地服务器还是云端服务器
支持地域：
能连得上网都支持
部分服务器运行测试有各类bug一键修复后再测试 ​
一键修复各种系统原生bug的仓库：
https://github.com/spiritLHLS/one-click-installation-script
如若还有系统bug请到上面仓库的issues反映，脚本原生BUG该仓库issues反映
融合怪命令 ​
交互形式 ​
bash
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh
或
bash
curl -L https://github.com/spiritLHLS/ecs/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh
或
bash <(wget -qO- bash.spiritlhl.net/ecs)
无交互形式-参数模式 ​
bash
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh -h
或
bash
curl -L https://github.com/spiritLHLS/ecs/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh -h
或通过
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh
下载文件后使用类似
bash
bash ecs.sh -m 1
这样的参数命令指定选项执行
以下为参数说明：
指令项目说明备注
-m必填项可指定原本menu中的对应选项，最多支持三层选择，例如执行bash ecs.sh -m 5 1 1将选择主菜单第5选项下的第1选项下的子选项1的脚本执行可缺省仅指定一个参数，如-m 1仅指定执行融合怪完全体，执行-m 1 0以及-m 1 0 0都是指定执行融合怪完全体
-i可选项可指定回程路由测试中的目标IPV4地址可通过ip.sb、ipinfo.io等网站获取本地IPV4地址后指定
-r可选项可指定回程路由测试中的目标IPV4地址，可选b g s c 分别对应北京、广州、上海、成都```如-r b指定测试北京回程(三网)
-base可选项可指定仅测试基础的系统信息无该指令则默认按照menu选项的组合测试
-ctype可选项可指定通过何种方式测试cpu，可选gb4、gb5、gb6分别对应geekbench的4、5、6版本无该指令则默认使用sysbench测试
-dtype可选项可指定测试硬盘IO的程序，可选dd、fio，前者测试快后者测试慢无该指令则默认都使用进行测试
-mdisk可选项可指定测试多个挂载盘的IO注意本指令包含测试系统盘
-banup可选项可指定强制不生成分享链接无该指令则默认生成分享链接
IP质量检测 ​
  • IP质量检测，含多家数据库查询，含黑名单查询
  • 含 IPV4 和 IPV6 检测，含ASN和地址查询
  • 含25端口的邮箱可达性检测，如果某个邮箱可达，则可搭建邮局
bash
bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/za/-/raw/main/qzcheck.sh)
或
bash
bash <(wget -qO- bash.spiritlhl.net/ecs-ipcheck)
或
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/ecs/main/qzcheck.sh)
融合怪说明 ​
融合怪脚本最好在 /root 路径下执行，避免各种奇奇怪怪的问题
融合怪的执行结果保存在当前路径下的test_result.txt中，可先退出SSH登录后续再查看文件
融合怪的完整版和精简版运行完毕会自动上传结果到pastebin并回传分享链接，如果测一半想要退出，那么按Ctrl+C同时按下可终止测试，此时会自动退出删除残余文件
有时候想要测一些配置极其拉跨的机器时，推荐使用screen命令挂起执行选项1的融合怪，然后你可以关闭SSH连接，等待一段时间后使用cat test_result.txt查看运行的实时状况，这样可以避免IO或者CPU过于垃圾导致的测试过程中的SSH连接中断，就不会测一半啥都没了，假如screen中显示乱码，也没问题，结果是不带乱码的
最烂机器测试的例子(跑了47分钟一样测完)：跳转
使用CDN加速已支持国内和国外服务器测试，但国内受CDN连通性或国内机器带宽大小的限制加载可能会慢很多
融合怪测试说明以及部分测试结果的内容解释(初次使用推荐查看)：
除了已标注的原创内容，其余所有分区均为借鉴并进行优化修改后的版本，与原始对应的脚本不一样
所有检测都有考虑过使用并行测试，并在部分环节使用了该技术，比正常的顺序执行优化了2~3分钟，属于是独有的，暂无哪家的测试有同类技术
系统基础信息测试融合了多家还有我自己修补的部分检测(systl、NAT类型检测，并发ASN检测等)，应该是目前最全面最通用的了
CPU测试使用sysbench测试得分，不是yabs的gb4或gb5，前者只是简单的计算质数测试速度快，后者geekbench是综合测试系统算加权得分，不是同一种东西，别互相比较了，没有可比性
CPU测试单核得分在5000以上的可以算第一梯队，4000到5000分算第二梯队，每1000分算一档，自己看看自己在哪个档位吧
AMD的7950x单核满血性能得分在6500左右，AMD的5950x单核满血性能得分5700左右，Intel普通的CPU(E5之类的)在1000~800左右，低于500的单核CPU可以算是比较烂的了
IO测试收录了两种，来源于lemonbench的dd磁盘测试和yabs的fio磁盘测试，综合来看会比较好，前者可能误差偏大但测试速度快无硬盘大小限制，后者真实一点但测试速度慢有硬盘以及内存大小限制
流媒体测试收录了两种，一个是go编译的二进制文件和一个shell脚本版本，二者各有优劣，互相对比看即可
tiktok测试有superbench和lmc999两种版本，哪个失效了随时可能更新为其中一种版本，以最新的脚本为准
回程路由测试选用的GO编译的二进制版本和朋友PR的版本，本人做了优化适配多个IP列表以及融合部分查询
IP质量检测纯原创，如有bug或者更多数据库来源可在issues中提出，日常看IP2Location数据库的IP类型即可，其中的25端口邮箱可达，则可搭建邮局
融合怪的IP质量检测是简化过的，没有查询Cloudflare的威胁得分，个人原创区的IP质量检测才是完整版(或者仓库说明中列出的那个IP质量检测的命令也是完整版)
三网测速使用自写的测速脚本，尽量使用最新节点最新组件进行测速，且有备用go版本测速，做到自更新测速节点列表，自适应系统环境测速
其他第三方脚本归纳到了第三方脚本区，里面有同类型脚本不同作者的各种竞品脚本，如果融合怪不能使你满意或者有错误，可以看看那部分
原创脚本区是个人原创的部分，有事没事也可以看看，可能会更新某些偏门或者独到的脚本
VPS测试，VPS测速，VPS综合性能测试，VPS回程线路测试，VPS流媒体测试等所有测试融合的脚本，本脚本能融合的都融合了
融合怪功能 ​
  • [x] 自由组合测试方向和单项测试以及合集收录第三方脚本
  • [x] 基础信息查询--感谢bench.sh、superbench.sh、yabs、lemonbench开源，本人整理修改优化，同原版均不一致
  • [x] CPU测试--感谢lemonbench开源，本人整理修改优化
  • [x] 内存测试--感谢lemonbench开源，本人整理修改优化
  • [x] 磁盘dd读写测试--感谢lemonbench开源，本人整理修改优化
  • [x] 硬盘fio读写测试--感谢yabs开源，本人整理修改优化
  • [x] 御三家流媒体解锁测试--感谢sjlleo的二进制文件，本人修改整理优化
  • [x] 常用流媒体解锁测试--感谢RegionRestrictionCheck开源，本人整理修改优化
  • [x] Tiktok解锁--感谢TikTokCheck开源，本人整理修改优化
  • [x] 三网回程以及路由延迟--感谢zhanghanyun/backtrace开源，本人整理修改
  • [x] 回程路由以及带宽类型检测(商宽/家宽/数据中心)--由fscarmen的PR以及本人的技术思路提供，本人后续修改优化
  • [x] IP质量与25端口检测(含IPV4和IPV6)--本脚本独创，感谢互联网提供的查询资源
  • [x] speedtest测速--使用自写ecsspeed仓库，自动更新测速服务器ID，一劳永逸解决老是要手动更新测速ID的问题
友链 ​
测评频道 ​
https://t.me/vps_reviews ​
自动更新测速服务器节点列表的网络基准测试脚本 ​
https://github.com/spiritLHLS/ecsspeed ​
脚本概况 ​
主界面：
图片
选项1融合怪完全体：
图片图片图片图片图片图片图片
选项6原创区：
图片
',82),l=[o];function n(r,c,i,h,d,b){return a(),e("div",null,l)}const y=s(p,[["render",n]]);export{m as __pageData,y as default};
+import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case2.md","filePath":"case/case2.md","lastUpdated":1705324601000}'),p={name:"case/case2.md"},o=t('
仓库 ​
https://github.com/spiritLHLS/ecs
Hits
融合怪测评脚本 ​
支持系统：
Ubuntu 18+, Debian 8+, Centos 7+, Fedora 33+, Almalinux 8.5+, OracleLinux 8+, RockyLinux 8+, AstraLinux CE, Arch
半支持系统：
FreeBSD(前提已执行pkg install -y curl bash)，Armbian
Armbian系统部分检测和测试暂不支持，部分会编码错误
FreeBSD系统的硬盘测试和CPU测试目前是半残的，有些东西显示有问题
FreeBSD系统的分享链接的预处理部分sed命令存在问题未删除部分无效内容
支持架构：
基本都支持，无论是本地服务器还是云端服务器
支持地域：
能连得上网都支持
部分服务器运行测试有各类bug一键修复后再测试 ​
一键修复各种系统原生bug的仓库：
https://github.com/spiritLHLS/one-click-installation-script
如若还有系统bug请到上面仓库的issues反映，脚本原生BUG该仓库issues反映
融合怪命令 ​
交互形式 ​
bash
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh
或
bash
curl -L https://github.com/spiritLHLS/ecs/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh
或
bash <(wget -qO- bash.spiritlhl.net/ecs)
无交互形式-参数模式 ​
bash
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh -h
或
bash
curl -L https://github.com/spiritLHLS/ecs/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh -h
或通过
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh
下载文件后使用类似
bash
bash ecs.sh -m 1
这样的参数命令指定选项执行
以下为参数说明：
指令项目说明备注
-m必填项可指定原本menu中的对应选项，最多支持三层选择，例如执行bash ecs.sh -m 5 1 1将选择主菜单第5选项下的第1选项下的子选项1的脚本执行可缺省仅指定一个参数，如-m 1仅指定执行融合怪完全体，执行-m 1 0以及-m 1 0 0都是指定执行融合怪完全体
-i可选项可指定回程路由测试中的目标IPV4地址可通过ip.sb、ipinfo.io等网站获取本地IPV4地址后指定
-r可选项可指定回程路由测试中的目标IPV4地址，可选b g s c 分别对应北京、广州、上海、成都```如-r b指定测试北京回程(三网)
-base可选项可指定仅测试基础的系统信息无该指令则默认按照menu选项的组合测试
-ctype可选项可指定通过何种方式测试cpu，可选gb4、gb5、gb6分别对应geekbench的4、5、6版本无该指令则默认使用sysbench测试
-dtype可选项可指定测试硬盘IO的程序，可选dd、fio，前者测试快后者测试慢无该指令则默认都使用进行测试
-mdisk可选项可指定测试多个挂载盘的IO注意本指令包含测试系统盘
-banup可选项可指定强制不生成分享链接无该指令则默认生成分享链接
IP质量检测 ​
  • IP质量检测，含多家数据库查询，含黑名单查询
  • 含 IPV4 和 IPV6 检测，含ASN和地址查询
  • 含25端口的邮箱可达性检测，如果某个邮箱可达，则可搭建邮局
bash
bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/za/-/raw/main/qzcheck.sh)
或
bash
bash <(wget -qO- bash.spiritlhl.net/ecs-ipcheck)
或
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/ecs/main/qzcheck.sh)
融合怪说明 ​
融合怪脚本最好在 /root 路径下执行，避免各种奇奇怪怪的问题
融合怪的执行结果保存在当前路径下的test_result.txt中，可先退出SSH登录后续再查看文件
融合怪的完整版和精简版运行完毕会自动上传结果到pastebin并回传分享链接，如果测一半想要退出，那么按Ctrl+C同时按下可终止测试，此时会自动退出删除残余文件
有时候想要测一些配置极其拉跨的机器时，推荐使用screen命令挂起执行选项1的融合怪，然后你可以关闭SSH连接，等待一段时间后使用cat test_result.txt查看运行的实时状况，这样可以避免IO或者CPU过于垃圾导致的测试过程中的SSH连接中断，就不会测一半啥都没了，假如screen中显示乱码，也没问题，结果是不带乱码的
最烂机器测试的例子(跑了47分钟一样测完)：跳转
使用CDN加速已支持国内和国外服务器测试，但国内受CDN连通性或国内机器带宽大小的限制加载可能会慢很多
融合怪测试说明以及部分测试结果的内容解释(初次使用推荐查看)：
除了已标注的原创内容，其余所有分区均为借鉴并进行优化修改后的版本，与原始对应的脚本不一样
所有检测都有考虑过使用并行测试，并在部分环节使用了该技术，比正常的顺序执行优化了2~3分钟，属于是独有的，暂无哪家的测试有同类技术
系统基础信息测试融合了多家还有我自己修补的部分检测(systl、NAT类型检测，并发ASN检测等)，应该是目前最全面最通用的了
CPU测试使用sysbench测试得分，不是yabs的gb4或gb5，前者只是简单的计算质数测试速度快，后者geekbench是综合测试系统算加权得分，不是同一种东西，别互相比较了，没有可比性
CPU测试单核得分在5000以上的可以算第一梯队，4000到5000分算第二梯队，每1000分算一档，自己看看自己在哪个档位吧
AMD的7950x单核满血性能得分在6500左右，AMD的5950x单核满血性能得分5700左右，Intel普通的CPU(E5之类的)在1000~800左右，低于500的单核CPU可以算是比较烂的了
IO测试收录了两种，来源于lemonbench的dd磁盘测试和yabs的fio磁盘测试，综合来看会比较好，前者可能误差偏大但测试速度快无硬盘大小限制，后者真实一点但测试速度慢有硬盘以及内存大小限制
流媒体测试收录了两种，一个是go编译的二进制文件和一个shell脚本版本，二者各有优劣，互相对比看即可
tiktok测试有superbench和lmc999两种版本，哪个失效了随时可能更新为其中一种版本，以最新的脚本为准
回程路由测试选用的GO编译的二进制版本和朋友PR的版本，本人做了优化适配多个IP列表以及融合部分查询
IP质量检测纯原创，如有bug或者更多数据库来源可在issues中提出，日常看IP2Location数据库的IP类型即可，其中的25端口邮箱可达，则可搭建邮局
融合怪的IP质量检测是简化过的，没有查询Cloudflare的威胁得分，个人原创区的IP质量检测才是完整版(或者仓库说明中列出的那个IP质量检测的命令也是完整版)
三网测速使用自写的测速脚本，尽量使用最新节点最新组件进行测速，且有备用go版本测速，做到自更新测速节点列表，自适应系统环境测速
其他第三方脚本归纳到了第三方脚本区，里面有同类型脚本不同作者的各种竞品脚本，如果融合怪不能使你满意或者有错误，可以看看那部分
原创脚本区是个人原创的部分，有事没事也可以看看，可能会更新某些偏门或者独到的脚本
VPS测试，VPS测速，VPS综合性能测试，VPS回程线路测试，VPS流媒体测试等所有测试融合的脚本，本脚本能融合的都融合了
融合怪功能 ​
  • [x] 自由组合测试方向和单项测试以及合集收录第三方脚本
  • [x] 基础信息查询--感谢bench.sh、superbench.sh、yabs、lemonbench开源，本人整理修改优化，同原版均不一致
  • [x] CPU测试--感谢lemonbench开源，本人整理修改优化
  • [x] 内存测试--感谢lemonbench开源，本人整理修改优化
  • [x] 磁盘dd读写测试--感谢lemonbench开源，本人整理修改优化
  • [x] 硬盘fio读写测试--感谢yabs开源，本人整理修改优化
  • [x] 御三家流媒体解锁测试--感谢sjlleo的二进制文件，本人修改整理优化
  • [x] 常用流媒体解锁测试--感谢RegionRestrictionCheck开源，本人整理修改优化
  • [x] Tiktok解锁--感谢TikTokCheck开源，本人整理修改优化
  • [x] 三网回程以及路由延迟--感谢zhanghanyun/backtrace开源，本人整理修改
  • [x] 回程路由以及带宽类型检测(商宽/家宽/数据中心)--由fscarmen的PR以及本人的技术思路提供，本人后续修改优化
  • [x] IP质量与25端口检测(含IPV4和IPV6)--本脚本独创，感谢互联网提供的查询资源
  • [x] speedtest测速--使用自写ecsspeed仓库，自动更新测速服务器ID，一劳永逸解决老是要手动更新测速ID的问题
友链 ​
测评频道 ​
https://t.me/vps_reviews ​
自动更新测速服务器节点列表的网络基准测试脚本 ​
https://github.com/spiritLHLS/ecsspeed ​
脚本概况 ​
主界面：
图片
选项1融合怪完全体：
图片图片图片图片图片图片图片
选项6原创区：
图片
',82),l=[o];function n(r,c,i,h,d,b){return a(),e("div",null,l)}const y=s(p,[["render",n]]);export{m as __pageData,y as default};
diff --git a/assets/case_case3.md.b2c3109f.js b/assets/case_case3.md.f714de49.js
similarity index 99%
rename from assets/case_case3.md.b2c3109f.js
rename to assets/case_case3.md.f714de49.js
index 85719f8d15..67d74849da 100644
--- a/assets/case_case3.md.b2c3109f.js
+++ b/assets/case_case3.md.f714de49.js
@@ -1 +1 @@
-import{_ as e,v as s,b as t,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":1704976888000}'),p={name:"case/case3.md"},n=a('
仓库 ​
https://github.com/spiritLHLS/ecsspeed
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
',43),c=[n];function i(r,l,o,h,d,g){return s(),t("div",null,c)}const m=e(p,[["render",i]]);export{u as __pageData,m as default};
+import{_ as e,v as s,b as t,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":1705324601000}'),p={name:"case/case3.md"},n=a('
仓库 ​
https://github.com/spiritLHLS/ecsspeed
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
',43),c=[n];function i(r,l,o,h,d,g){return s(),t("div",null,c)}const m=e(p,[["render",i]]);export{u as __pageData,m as default};
diff --git a/assets/case_case3.md.b2c3109f.lean.js b/assets/case_case3.md.f714de49.lean.js
similarity index 99%
rename from assets/case_case3.md.b2c3109f.lean.js
rename to assets/case_case3.md.f714de49.lean.js
index 85719f8d15..67d74849da 100644
--- a/assets/case_case3.md.b2c3109f.lean.js
+++ b/assets/case_case3.md.f714de49.lean.js
@@ -1 +1 @@
-import{_ as e,v as s,b as t,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":1704976888000}'),p={name:"case/case3.md"},n=a('
仓库 ​
https://github.com/spiritLHLS/ecsspeed
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
',43),c=[n];function i(r,l,o,h,d,g){return s(),t("div",null,c)}const m=e(p,[["render",i]]);export{u as __pageData,m as default};
+import{_ as e,v as s,b as t,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":1705324601000}'),p={name:"case/case3.md"},n=a('
仓库 ​
https://github.com/spiritLHLS/ecsspeed
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
',43),c=[n];function i(r,l,o,h,d,g){return s(),t("div",null,c)}const m=e(p,[["render",i]]);export{u as __pageData,m as default};
diff --git a/assets/case_case4.md.2ecc8866.js b/assets/case_case4.md.81f143f1.js
similarity index 98%
rename from assets/case_case4.md.2ecc8866.js
rename to assets/case_case4.md.81f143f1.js
index 7d247a7624..2b55b95586 100644
--- a/assets/case_case4.md.2ecc8866.js
+++ b/assets/case_case4.md.81f143f1.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/case4.md","filePath":"case/case4.md","lastUpdated":1704976888000}'),i={name:"case/case4.md"},l=t('
仓库 ​
https://github.com/spiritLHLS/Oracle-server-keep-alive-script
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自行设置定时任务
',25),r=[l];function p(o,c,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/case4.md","filePath":"case/case4.md","lastUpdated":1705324601000}'),i={name:"case/case4.md"},l=t('
仓库 ​
https://github.com/spiritLHLS/Oracle-server-keep-alive-script
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自行设置定时任务
',25),r=[l];function p(o,c,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_case4.md.2ecc8866.lean.js b/assets/case_case4.md.81f143f1.lean.js
similarity index 98%
rename from assets/case_case4.md.2ecc8866.lean.js
rename to assets/case_case4.md.81f143f1.lean.js
index 7d247a7624..2b55b95586 100644
--- a/assets/case_case4.md.2ecc8866.lean.js
+++ b/assets/case_case4.md.81f143f1.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/case4.md","filePath":"case/case4.md","lastUpdated":1704976888000}'),i={name:"case/case4.md"},l=t('
仓库 ​
https://github.com/spiritLHLS/Oracle-server-keep-alive-script
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自行设置定时任务
',25),r=[l];function p(o,c,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/case4.md","filePath":"case/case4.md","lastUpdated":1705324601000}'),i={name:"case/case4.md"},l=t('
仓库 ​
https://github.com/spiritLHLS/Oracle-server-keep-alive-script
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自行设置定时任务
',25),r=[l];function p(o,c,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.165a5373.js b/assets/case_case5.md.cfcc0426.js
similarity index 98%
rename from assets/case_case5.md.165a5373.js
rename to assets/case_case5.md.cfcc0426.js
index 6916ce420e..1ae879e886 100644
--- a/assets/case_case5.md.165a5373.js
+++ b/assets/case_case5.md.cfcc0426.js
@@ -1 +1 @@
-import{_ as s,v as a,b as p,R as o}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case5.md","filePath":"case/case5.md","lastUpdated":1704976888000}'),e={name:"case/case5.md"},n=o('
仓库 ​
https://github.com/spiritLHLS/addswap
addswap ​
为openvz、kvm虚拟化的linux服务器增加swap分区(虚拟内存)
bash
curl -L 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 提供优化建议
',15),t=[n];function l(r,c,C,i,h,d){return a(),p("div",null,t)}const A=s(e,[["render",l]]);export{m as __pageData,A as default};
+import{_ as s,v as a,b as p,R as o}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case5.md","filePath":"case/case5.md","lastUpdated":1705324601000}'),e={name:"case/case5.md"},n=o('
仓库 ​
https://github.com/spiritLHLS/addswap
addswap ​
为openvz、kvm虚拟化的linux服务器增加swap分区(虚拟内存)
bash
curl -L 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 提供优化建议
',15),t=[n];function l(r,c,C,i,h,d){return a(),p("div",null,t)}const A=s(e,[["render",l]]);export{m as __pageData,A as default};
diff --git a/assets/case_case5.md.165a5373.lean.js b/assets/case_case5.md.cfcc0426.lean.js
similarity index 98%
rename from assets/case_case5.md.165a5373.lean.js
rename to assets/case_case5.md.cfcc0426.lean.js
index 6916ce420e..1ae879e886 100644
--- a/assets/case_case5.md.165a5373.lean.js
+++ b/assets/case_case5.md.cfcc0426.lean.js
@@ -1 +1 @@
-import{_ as s,v as a,b as p,R as o}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case5.md","filePath":"case/case5.md","lastUpdated":1704976888000}'),e={name:"case/case5.md"},n=o('
仓库 ​
https://github.com/spiritLHLS/addswap
addswap ​
为openvz、kvm虚拟化的linux服务器增加swap分区(虚拟内存)
bash
curl -L 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 提供优化建议
',15),t=[n];function l(r,c,C,i,h,d){return a(),p("div",null,t)}const A=s(e,[["render",l]]);export{m as __pageData,A as default};
+import{_ as s,v as a,b as p,R as o}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case5.md","filePath":"case/case5.md","lastUpdated":1705324601000}'),e={name:"case/case5.md"},n=o('
仓库 ​
https://github.com/spiritLHLS/addswap
addswap ​
为openvz、kvm虚拟化的linux服务器增加swap分区(虚拟内存)
bash
curl -L 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 提供优化建议
',15),t=[n];function l(r,c,C,i,h,d){return a(),p("div",null,t)}const A=s(e,[["render",l]]);export{m as __pageData,A as default};
diff --git a/assets/case_case6.md.9d5fa2da.js b/assets/case_case6.md.1433cc80.js
similarity index 97%
rename from assets/case_case6.md.9d5fa2da.js
rename to assets/case_case6.md.1433cc80.js
index ff73b4bb87..116bbf2923 100644
--- a/assets/case_case6.md.9d5fa2da.js
+++ b/assets/case_case6.md.1433cc80.js
@@ -1 +1 @@
-import{_ as a,v as s,b as e,R as r}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case6.md","filePath":"case/case6.md","lastUpdated":1704976888000}'),t={name:"case/case6.md"},p=r('
仓库 ​
https://github.com/spiritLHLS/addzram
addzram ​
为linux服务器启用zram(压缩内存)
bash
curl -L 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 提供优化建议
',11),n=[p];function o(l,c,d,i,h,m){return s(),e("div",null,n)}const A=a(t,[["render",o]]);export{y as __pageData,A as default};
+import{_ as a,v as s,b as e,R as r}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case6.md","filePath":"case/case6.md","lastUpdated":1705324601000}'),t={name:"case/case6.md"},p=r('
仓库 ​
https://github.com/spiritLHLS/addzram
addzram ​
为linux服务器启用zram(压缩内存)
bash
curl -L 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 提供优化建议
',11),n=[p];function o(l,c,d,i,h,m){return s(),e("div",null,n)}const A=a(t,[["render",o]]);export{y as __pageData,A as default};
diff --git a/assets/case_case6.md.9d5fa2da.lean.js b/assets/case_case6.md.1433cc80.lean.js
similarity index 97%
rename from assets/case_case6.md.9d5fa2da.lean.js
rename to assets/case_case6.md.1433cc80.lean.js
index ff73b4bb87..116bbf2923 100644
--- a/assets/case_case6.md.9d5fa2da.lean.js
+++ b/assets/case_case6.md.1433cc80.lean.js
@@ -1 +1 @@
-import{_ as a,v as s,b as e,R as r}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case6.md","filePath":"case/case6.md","lastUpdated":1704976888000}'),t={name:"case/case6.md"},p=r('
仓库 ​
https://github.com/spiritLHLS/addzram
addzram ​
为linux服务器启用zram(压缩内存)
bash
curl -L 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 提供优化建议
',11),n=[p];function o(l,c,d,i,h,m){return s(),e("div",null,n)}const A=a(t,[["render",o]]);export{y as __pageData,A as default};
+import{_ as a,v as s,b as e,R as r}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case6.md","filePath":"case/case6.md","lastUpdated":1705324601000}'),t={name:"case/case6.md"},p=r('
仓库 ​
https://github.com/spiritLHLS/addzram
addzram ​
为linux服务器启用zram(压缩内存)
bash
curl -L 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 提供优化建议
',11),n=[p];function o(l,c,d,i,h,m){return s(),e("div",null,n)}const A=a(t,[["render",o]]);export{y as __pageData,A as default};
diff --git a/assets/case_case7.md.b28a54c5.js b/assets/case_case7.md.aae4e9b9.js
similarity index 97%
rename from assets/case_case7.md.b28a54c5.js
rename to assets/case_case7.md.aae4e9b9.js
index 63483e9108..d4e9c02d7b 100644
--- a/assets/case_case7.md.b28a54c5.js
+++ b/assets/case_case7.md.aae4e9b9.js
@@ -1 +1 @@
-import{_ as a,v as e,b as t,R as o}from"./chunks/framework.70afa331.js";const v=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case7.md","filePath":"case/case7.md","lastUpdated":1704976888000}'),n={name:"case/case7.md"},s=o('
仓库 ​
https://github.com/oneclickvirt/convoypanel-scripts
convoypanel-scripts ​
One-click installation of convoy panel ​
Prerequisites for installation:
  • PVE is installed
  • 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.
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
',12),l=[s];function i(r,c,p,h,d,m){return e(),t("div",null,l)}const y=a(n,[["render",i]]);export{v as __pageData,y as default};
+import{_ as a,v as e,b as t,R as o}from"./chunks/framework.70afa331.js";const v=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case7.md","filePath":"case/case7.md","lastUpdated":1705324601000}'),n={name:"case/case7.md"},s=o('
仓库 ​
https://github.com/oneclickvirt/convoypanel-scripts
convoypanel-scripts ​
One-click installation of convoy panel ​
Prerequisites for installation:
  • PVE is installed
  • 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.
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
',12),l=[s];function i(r,c,p,h,d,m){return e(),t("div",null,l)}const y=a(n,[["render",i]]);export{v as __pageData,y as default};
diff --git a/assets/case_case7.md.b28a54c5.lean.js b/assets/case_case7.md.aae4e9b9.lean.js
similarity index 97%
rename from assets/case_case7.md.b28a54c5.lean.js
rename to assets/case_case7.md.aae4e9b9.lean.js
index 63483e9108..d4e9c02d7b 100644
--- a/assets/case_case7.md.b28a54c5.lean.js
+++ b/assets/case_case7.md.aae4e9b9.lean.js
@@ -1 +1 @@
-import{_ as a,v as e,b as t,R as o}from"./chunks/framework.70afa331.js";const v=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case7.md","filePath":"case/case7.md","lastUpdated":1704976888000}'),n={name:"case/case7.md"},s=o('
仓库 ​
https://github.com/oneclickvirt/convoypanel-scripts
convoypanel-scripts ​
One-click installation of convoy panel ​
Prerequisites for installation:
  • PVE is installed
  • 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.
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
',12),l=[s];function i(r,c,p,h,d,m){return e(),t("div",null,l)}const y=a(n,[["render",i]]);export{v as __pageData,y as default};
+import{_ as a,v as e,b as t,R as o}from"./chunks/framework.70afa331.js";const v=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case7.md","filePath":"case/case7.md","lastUpdated":1705324601000}'),n={name:"case/case7.md"},s=o('
仓库 ​
https://github.com/oneclickvirt/convoypanel-scripts
convoypanel-scripts ​
One-click installation of convoy panel ​
Prerequisites for installation:
  • PVE is installed
  • 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.
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
',12),l=[s];function i(r,c,p,h,d,m){return e(),t("div",null,l)}const y=a(n,[["render",i]]);export{v as __pageData,y as default};
diff --git a/assets/case_index.md.5333f3a7.js b/assets/case_index.md.97648dc5.js
similarity index 93%
rename from assets/case_index.md.5333f3a7.js
rename to assets/case_index.md.97648dc5.js
index c814cd170b..5f11e502c4 100644
--- a/assets/case_index.md.5333f3a7.js
+++ b/assets/case_index.md.97648dc5.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Linux相关项目","titleTemplate":"与Linux相关的一些一键脚本项目","description":"","frontmatter":{"layout":"home","title":"Linux相关项目","titleTemplate":"与Linux相关的一些一键脚本项目","hero":{"name":"Linux相关项目","text":"与Linux相关的一些一键脚本项目","image":"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":1704976888000}'),i={name:"case/index.md"};function s(n,r,o,c,d,l){return t(),a("div")}const x=e(i,[["render",s]]);export{m as __pageData,x as default};
+import{_ as e,v as t,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Linux相关项目","titleTemplate":"与Linux相关的一些一键脚本项目","description":"","frontmatter":{"layout":"home","title":"Linux相关项目","titleTemplate":"与Linux相关的一些一键脚本项目","hero":{"name":"Linux相关项目","text":"与Linux相关的一些一键脚本项目","image":"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":1705324601000}'),i={name:"case/index.md"};function s(n,r,o,c,d,l){return t(),a("div")}const x=e(i,[["render",s]]);export{m as __pageData,x as default};
diff --git a/assets/case_index.md.5333f3a7.lean.js b/assets/case_index.md.97648dc5.lean.js
similarity index 93%
rename from assets/case_index.md.5333f3a7.lean.js
rename to assets/case_index.md.97648dc5.lean.js
index c814cd170b..5f11e502c4 100644
--- a/assets/case_index.md.5333f3a7.lean.js
+++ b/assets/case_index.md.97648dc5.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Linux相关项目","titleTemplate":"与Linux相关的一些一键脚本项目","description":"","frontmatter":{"layout":"home","title":"Linux相关项目","titleTemplate":"与Linux相关的一些一键脚本项目","hero":{"name":"Linux相关项目","text":"与Linux相关的一些一键脚本项目","image":"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":1704976888000}'),i={name:"case/index.md"};function s(n,r,o,c,d,l){return t(),a("div")}const x=e(i,[["render",s]]);export{m as __pageData,x as default};
+import{_ as e,v as t,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Linux相关项目","titleTemplate":"与Linux相关的一些一键脚本项目","description":"","frontmatter":{"layout":"home","title":"Linux相关项目","titleTemplate":"与Linux相关的一些一键脚本项目","hero":{"name":"Linux相关项目","text":"与Linux相关的一些一键脚本项目","image":"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":1705324601000}'),i={name:"case/index.md"};function s(n,r,o,c,d,l){return t(),a("div")}const x=e(i,[["render",s]]);export{m as __pageData,x as default};
diff --git a/assets/developer_index.md.785f4035.js b/assets/developer_index.md.8128d7cc.js
similarity index 93%
rename from assets/developer_index.md.785f4035.js
rename to assets/developer_index.md.8128d7cc.js
index c4c43aed5b..e3af36f6e6 100644
--- a/assets/developer_index.md.785f4035.js
+++ b/assets/developer_index.md.8128d7cc.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://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":1704976888000}'),s={name:"developer/index.md"};function n(r,o,i,l,d,p){return t(),a("div")}const u=e(s,[["render",n]]);export{c as __pageData,u 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://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":1705324601000}'),s={name:"developer/index.md"};function n(r,o,i,l,d,p){return t(),a("div")}const u=e(s,[["render",n]]);export{c as __pageData,u as default};
diff --git a/assets/developer_index.md.785f4035.lean.js b/assets/developer_index.md.8128d7cc.lean.js
similarity index 93%
rename from assets/developer_index.md.785f4035.lean.js
rename to assets/developer_index.md.8128d7cc.lean.js
index c4c43aed5b..e3af36f6e6 100644
--- a/assets/developer_index.md.785f4035.lean.js
+++ b/assets/developer_index.md.8128d7cc.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://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":1704976888000}'),s={name:"developer/index.md"};function n(r,o,i,l,d,p){return t(),a("div")}const u=e(s,[["render",n]]);export{c as __pageData,u 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://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":1705324601000}'),s={name:"developer/index.md"};function n(r,o,i,l,d,p){return t(),a("div")}const u=e(s,[["render",n]]);export{c as __pageData,u as default};
diff --git a/assets/developer_l10n.md.8c2f5d32.js b/assets/developer_l10n.md.ab634a38.js
similarity index 90%
rename from assets/developer_l10n.md.8c2f5d32.js
rename to assets/developer_l10n.md.ab634a38.js
index e81aa3b9db..ca9c43014d 100644
--- a/assets/developer_l10n.md.8c2f5d32.js
+++ b/assets/developer_l10n.md.ab634a38.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":1704976888000}'),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":1705324601000}'),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.8c2f5d32.lean.js b/assets/developer_l10n.md.ab634a38.lean.js
similarity index 90%
rename from assets/developer_l10n.md.8c2f5d32.lean.js
rename to assets/developer_l10n.md.ab634a38.lean.js
index e81aa3b9db..ca9c43014d 100644
--- a/assets/developer_l10n.md.8c2f5d32.lean.js
+++ b/assets/developer_l10n.md.ab634a38.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":1704976888000}'),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":1705324601000}'),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_US_developer_l10n.md.bb2eaae0.js b/assets/en_US_developer_l10n.md.bb2eaae0.js
deleted file mode 100644
index d07958b737..0000000000
--- a/assets/en_US_developer_l10n.md.bb2eaae0.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/developer/l10n.md","filePath":"en_US/developer/l10n.md","lastUpdated":1704976888000}'),a={name:"en_US/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_US_developer_l10n.md.bb2eaae0.lean.js b/assets/en_US_developer_l10n.md.bb2eaae0.lean.js
deleted file mode 100644
index d07958b737..0000000000
--- a/assets/en_US_developer_l10n.md.bb2eaae0.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/developer/l10n.md","filePath":"en_US/developer/l10n.md","lastUpdated":1704976888000}'),a={name:"en_US/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_US_guide_dashboard.md.fff026e9.js b/assets/en_US_guide_dashboard.md.fff026e9.js
deleted file mode 100644
index 464f39d664..0000000000
--- a/assets/en_US_guide_dashboard.md.fff026e9.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/dashboard.md","filePath":"en_US/guide/dashboard.md","lastUpdated":1704976888000}'),o={name:"en_US/guide/dashboard.md"},i=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.
Please make sure to keep the original formatting by enclosing the translation in and for easy copying.
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 ​
Allows for the creation of KVM virtualized virtual machines and LXC virtualized containers.
https://github.com/spiritLHLS/pve
Hits
LXD ​
LXC Virtualization Containers Can Be Created.
https://github.com/spiritLHLS/lxd
Hits
Docker ​
Docker virtualized containers Can Be Created.
https://github.com/spiritLHLS/docker
Hits


',24),s=[i];function n(c,l,p,h,d,m){return t(),a("div",null,s)}const b=e(o,[["render",n]]);export{f as __pageData,b as default};
diff --git a/assets/en_US_guide_dashboard.md.fff026e9.lean.js b/assets/en_US_guide_dashboard.md.fff026e9.lean.js
deleted file mode 100644
index 464f39d664..0000000000
--- a/assets/en_US_guide_dashboard.md.fff026e9.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/dashboard.md","filePath":"en_US/guide/dashboard.md","lastUpdated":1704976888000}'),o={name:"en_US/guide/dashboard.md"},i=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.
Please make sure to keep the original formatting by enclosing the translation in and for easy copying.
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 ​
Allows for the creation of KVM virtualized virtual machines and LXC virtualized containers.
https://github.com/spiritLHLS/pve
Hits
LXD ​
LXC Virtualization Containers Can Be Created.
https://github.com/spiritLHLS/lxd
Hits
Docker ​
Docker virtualized containers Can Be Created.
https://github.com/spiritLHLS/docker
Hits


',24),s=[i];function n(c,l,p,h,d,m){return t(),a("div",null,s)}const b=e(o,[["render",n]]);export{f as __pageData,b as default};
diff --git a/assets/en_US_guide_dashboardq.md.bafc8360.js b/assets/en_US_guide_dashboardq.md.bafc8360.js
deleted file mode 100644
index 5980032e55..0000000000
--- a/assets/en_US_guide_dashboardq.md.bafc8360.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as a,v as e,b as s,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/dashboardq.md","filePath":"en_US/guide/dashboardq.md","lastUpdated":1704976888000}'),o={name:"en_US/guide/dashboardq.md"},n=t('
Give me a cup of coffee.
https://ko-fi.com/spiritlhl
USDT-TRC20
bash
TZ7nf8XAL9zQUo63xokazaBdCPeCgPfcwd
',4),r=[n];function p(d,i,c,l,h,_){return e(),s("div",null,r)}const u=a(o,[["render",p]]);export{m as __pageData,u as default};
diff --git a/assets/en_US_guide_dashboardq.md.bafc8360.lean.js b/assets/en_US_guide_dashboardq.md.bafc8360.lean.js
deleted file mode 100644
index 5980032e55..0000000000
--- a/assets/en_US_guide_dashboardq.md.bafc8360.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as a,v as e,b as s,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/dashboardq.md","filePath":"en_US/guide/dashboardq.md","lastUpdated":1704976888000}'),o={name:"en_US/guide/dashboardq.md"},n=t('
Give me a cup of coffee.
https://ko-fi.com/spiritlhl
USDT-TRC20
bash
TZ7nf8XAL9zQUo63xokazaBdCPeCgPfcwd
',4),r=[n];function p(d,i,c,l,h,_){return e(),s("div",null,r)}const u=a(o,[["render",p]]);export{m as __pageData,u as default};
diff --git a/assets/en_US_guide_docker_install.md.89bd27d4.js b/assets/en_US_guide_docker_install.md.89bd27d4.js
deleted file mode 100644
index d50a5cad87..0000000000
--- a/assets/en_US_guide_docker_install.md.89bd27d4.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/docker_install.md","filePath":"en_US/guide/docker_install.md","lastUpdated":1704976888000}'),t={name:"en_US/guide/docker_install.md"},n=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/spiritLHLS/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=[n];function p(r,c,i,d,h,u){return a(),e("div",null,l)}const y=s(t,[["render",p]]);export{C as __pageData,y as default};
diff --git a/assets/en_US_guide_docker_install.md.89bd27d4.lean.js b/assets/en_US_guide_docker_install.md.89bd27d4.lean.js
deleted file mode 100644
index d50a5cad87..0000000000
--- a/assets/en_US_guide_docker_install.md.89bd27d4.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/docker_install.md","filePath":"en_US/guide/docker_install.md","lastUpdated":1704976888000}'),t={name:"en_US/guide/docker_install.md"},n=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/spiritLHLS/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=[n];function p(r,c,i,d,h,u){return a(),e("div",null,l)}const y=s(t,[["render",p]]);export{C as __pageData,y as default};
diff --git a/assets/en_US_guide_docker_precheck.md.d2e2e9c5.js b/assets/en_US_guide_docker_precheck.md.d2e2e9c5.js
deleted file mode 100644
index ea17f76db8..0000000000
--- a/assets/en_US_guide_docker_precheck.md.d2e2e9c5.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/docker_precheck.md","filePath":"en_US/guide/docker_precheck.md","lastUpdated":1704976888000}'),n={name:"en_US/guide/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.
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.
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.
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 LXD 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.
',15),i=[s];function r(c,d,h,u,l,p){return t(),o("div",null,i)}const k=e(n,[["render",r]]);export{m as __pageData,k as default};
diff --git a/assets/en_US_guide_docker_precheck.md.d2e2e9c5.lean.js b/assets/en_US_guide_docker_precheck.md.d2e2e9c5.lean.js
deleted file mode 100644
index ea17f76db8..0000000000
--- a/assets/en_US_guide_docker_precheck.md.d2e2e9c5.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/docker_precheck.md","filePath":"en_US/guide/docker_precheck.md","lastUpdated":1704976888000}'),n={name:"en_US/guide/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.
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.
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.
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 LXD 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.
',15),i=[s];function r(c,d,h,u,l,p){return t(),o("div",null,i)}const k=e(n,[["render",r]]);export{m as __pageData,k as default};
diff --git a/assets/en_US_guide_docker_qa.md.2a016075.js b/assets/en_US_guide_docker_qa.md.2a016075.js
deleted file mode 100644
index e6bbbd43b9..0000000000
--- a/assets/en_US_guide_docker_qa.md.2a016075.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/docker_qa.md","filePath":"en_US/guide/docker_qa.md","lastUpdated":1704976888000}'),o={name:"en_US/guide/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_US_guide_docker_qa.md.2a016075.lean.js b/assets/en_US_guide_docker_qa.md.2a016075.lean.js
deleted file mode 100644
index e6bbbd43b9..0000000000
--- a/assets/en_US_guide_docker_qa.md.2a016075.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/docker_qa.md","filePath":"en_US/guide/docker_qa.md","lastUpdated":1704976888000}'),o={name:"en_US/guide/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_US_guide_docker_thanks.md.cf11828e.js b/assets/en_US_guide_docker_thanks.md.cf11828e.js
deleted file mode 100644
index 368e08bdf4..0000000000
--- a/assets/en_US_guide_docker_thanks.md.cf11828e.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/docker_thanks.md","filePath":"en_US/guide/docker_thanks.md","lastUpdated":1704976888000}'),o={name:"en_US/guide/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://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.
',19),h=[n];function c(i,p,s,l,d,g){return e(),t("div",null,h)}const b=r(o,[["render",c]]);export{m as __pageData,b as default};
diff --git a/assets/en_US_guide_docker_thanks.md.cf11828e.lean.js b/assets/en_US_guide_docker_thanks.md.cf11828e.lean.js
deleted file mode 100644
index 368e08bdf4..0000000000
--- a/assets/en_US_guide_docker_thanks.md.cf11828e.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/docker_thanks.md","filePath":"en_US/guide/docker_thanks.md","lastUpdated":1704976888000}'),o={name:"en_US/guide/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://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.
',19),h=[n];function c(i,p,s,l,d,g){return e(),t("div",null,h)}const b=r(o,[["render",c]]);export{m as __pageData,b as default};
diff --git a/assets/en_US_guide_lxd_precheck.md.2e4d2d0a.js b/assets/en_US_guide_lxd_precheck.md.2e4d2d0a.js
deleted file mode 100644
index 1b379f88f5..0000000000
--- a/assets/en_US_guide_lxd_precheck.md.2e4d2d0a.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/lxd_precheck.md","filePath":"en_US/guide/lxd_precheck.md","lastUpdated":1704976888000}'),a={name:"en_US/guide/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.
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, Debian can not use zfs automatically switch to another storage type!
  • 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/spiritLHLS/lxd/main/scripts/pre_check.sh)
',14),s=[r];function i(d,c,h,l,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_US_guide_lxd_precheck.md.2e4d2d0a.lean.js b/assets/en_US_guide_lxd_precheck.md.2e4d2d0a.lean.js
deleted file mode 100644
index 1b379f88f5..0000000000
--- a/assets/en_US_guide_lxd_precheck.md.2e4d2d0a.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/lxd_precheck.md","filePath":"en_US/guide/lxd_precheck.md","lastUpdated":1704976888000}'),a={name:"en_US/guide/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.
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, Debian can not use zfs automatically switch to another storage type!
  • 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/spiritLHLS/lxd/main/scripts/pre_check.sh)
',14),s=[r];function i(d,c,h,l,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_US_guide_lxd_qa.md.22281d8b.js b/assets/en_US_guide_lxd_qa.md.22281d8b.js
deleted file mode 100644
index 7896aac8b8..0000000000
--- a/assets/en_US_guide_lxd_qa.md.22281d8b.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/lxd_qa.md","filePath":"en_US/guide/lxd_qa.md","lastUpdated":1704976888000}'),n={name:"en_US/guide/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
luxvps German AMD Promotions
',19),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_US_guide_lxd_qa.md.22281d8b.lean.js b/assets/en_US_guide_lxd_qa.md.22281d8b.lean.js
deleted file mode 100644
index 7896aac8b8..0000000000
--- a/assets/en_US_guide_lxd_qa.md.22281d8b.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/lxd_qa.md","filePath":"en_US/guide/lxd_qa.md","lastUpdated":1704976888000}'),n={name:"en_US/guide/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
luxvps German AMD Promotions
',19),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_US_guide_lxd_thanks.md.80eef0e5.js b/assets/en_US_guide_lxd_thanks.md.80eef0e5.js
deleted file mode 100644
index c63b45886f..0000000000
--- a/assets/en_US_guide_lxd_thanks.md.80eef0e5.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/lxd_thanks.md","filePath":"en_US/guide/lxd_thanks.md","lastUpdated":1704976888000}'),a={name:"en_US/guide/lxd_thanks.md"},s=n('
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
Thank @Ella-Alinda @fscarmen for providing guidance.
',11),o=[s];function i(c,l,p,d,h,u){return e(),r("div",null,o)}const x=t(a,[["render",i]]);export{f as __pageData,x as default};
diff --git a/assets/en_US_guide_lxd_thanks.md.80eef0e5.lean.js b/assets/en_US_guide_lxd_thanks.md.80eef0e5.lean.js
deleted file mode 100644
index c63b45886f..0000000000
--- a/assets/en_US_guide_lxd_thanks.md.80eef0e5.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/lxd_thanks.md","filePath":"en_US/guide/lxd_thanks.md","lastUpdated":1704976888000}'),a={name:"en_US/guide/lxd_thanks.md"},s=n('
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
Thank @Ella-Alinda @fscarmen for providing guidance.
',11),o=[s];function i(c,l,p,d,h,u){return e(),r("div",null,o)}const x=t(a,[["render",i]]);export{f as __pageData,x as default};
diff --git a/assets/en_US_guide_pve_install.md.0c728ec3.js b/assets/en_US_guide_pve_install.md.0c728ec3.js
deleted file mode 100644
index 9fe4984c39..0000000000
--- a/assets/en_US_guide_pve_install.md.0c728ec3.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/pve_install.md","filePath":"en_US/guide/pve_install.md","lastUpdated":1704976888000}'),a={name:"en_US/guide/pve_install.md"},n=s('
PVE Body Installation ​
If you don't know how to choose an option during installation, just press enter.
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/spiritLHLS/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/spiritLHLS/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.
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
Before executing this command, if the host needs to append the address of the IPV6 tunnel, see the LXD Custom section for appending it to the corresponding file, but please ignore the initial environment modification section for it.
  • 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/spiritLHLS/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.
',31),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_US_guide_pve_install.md.0c728ec3.lean.js b/assets/en_US_guide_pve_install.md.0c728ec3.lean.js
deleted file mode 100644
index 9fe4984c39..0000000000
--- a/assets/en_US_guide_pve_install.md.0c728ec3.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-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_US/guide/pve_install.md","filePath":"en_US/guide/pve_install.md","lastUpdated":1704976888000}'),a={name:"en_US/guide/pve_install.md"},n=s('
PVE Body Installation ​
If you don't know how to choose an option during installation, just press enter.
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/spiritLHLS/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/spiritLHLS/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.
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
Before executing this command, if the host needs to append the address of the IPV6 tunnel, see the LXD Custom section for appending it to the corresponding file, but please ignore the initial environment modification section for it.
  • 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/spiritLHLS/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.
',31),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_US_guide_pve_kvm.md.aaa8a675.js b/assets/en_US_guide_pve_kvm.md.aaa8a675.js
deleted file mode 100644
index 91bc358fb2..0000000000
--- a/assets/en_US_guide_pve_kvm.md.aaa8a675.js
+++ /dev/null
@@ -1,13 +0,0 @@
-import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"KVM Virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/pve_kvm.md","filePath":"en_US/guide/pve_kvm.md","lastUpdated":1704976888000}'),n={name:"en_US/guide/pve_kvm.md"},o=t(`
KVM Virtualization ​
SSH Login Instructions ​
The virtual machines created through KVM virtualization do not have the username root by default. To switch to the root user, you need to execute sudo -i .
Of course, some templates actually allow logging in with the username root, and the default root password is password. You can give it a try.
Once you've logged in via SSH and switched to root privileges, it's crucial to change the root password. You can use the following command to do so.
Command:
bash
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
Partial Notes ​
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.
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.
Considerations for opening a KVM 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 KVM 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
Virtual machines with standalone NAT configuration in KVM virtualization. ​
  • 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/spiritLHLS/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 102 test1 oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
After setup is completed, you can execute cat vm102 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
VMID102
SSH Usernametest1
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
Deletion specific VM ​
  • Stop VM
  • Delete VM
  • Delete port mapping
  • Restart network
  • Delete log files
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 above
shell
./pve_delete.sh 102
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 KVM Virtualization and 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/spiritLHLS/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
-systemctl restart networking.service
-systemctl restart ndpresponder.service
-iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
-iptables-save > /etc/iptables/rules.v4
-rm -rf vmlog
-rm -rf vm*
TIP
Before modifying the VM configuration for PVE, you must shut it down first. After making the configuration changes, start it again to avoid configuration reload errors.
Setting Up Virtual Machines with Dedicated IPv4 Addresses ​
Two versions are available, choose as needed.
Version with Automatic Selection of IPv4 Address (No Manual Specification Required) ​
WARNING
Before use, ensure that the current host machine has at least 2 available IP addresses within its IP range, and there are unallocated IP addresses. These unallocated IP addresses should not be bound to the host machine.
  • Automatically detect available IP ranges. Use ping to identify unallocated IP addresses and select one to bind to the virtual machine.
  • If the host machine has an accompanying IPv6 subnet, there will be an option to attach an IPv6 address.
  • Relevant system information will be stored in the corresponding virtual machine's NOTE section, accessible for viewing on the web interface.
  • 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/spiritLHLS/pve/main/scripts/buildvm_extraip.sh -o buildvm_extraip.sh && chmod +x buildvm_extraip.sh
Meaning of each parameter
shell
./buildvm_extraip.sh VMID Username Password Number_of_CPU_Cores Memory_Size_in_MB Disk_Size_in_GB OS Storage_Disk Attach_IPV6(Default is N)
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_extraip.sh 152 test1 oneclick123 1 1024 10 debian12 local N
The above command is used to create a virtual machine with a dedicated IPv4 address.
AttributeValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
OSdebian12
Storagelocal disk
IPv6 AddonNot attached by default
Version Requiring Manual Specification of IPV4 Address ​
  • Manual specification of IPV4 address with subnet length in the command is required.
  • If the host machine comes with an IPV6 subnet, you can choose whether to add an IPV6 address additionally.
  • If the vendor has provided an IPV4 address and subnet length, please carefully compare and write the parameters in the command format shown below.
  • Relevant system information will be stored in the NOTE of the corresponding virtual machine and can be viewed on the WEB end.
  • 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/spiritLHLS/pve/main/scripts/buildvm_manual_ip.sh -o buildvm_manual_ip.sh && chmod +x buildvm_manual_ip.sh
Meaning of each parameter
shell
./buildvm_manual_ip.sh VMID USERNAME PASSWORD CPU_CORES MEMORY_SIZE_GB STORAGE_SIZE_GB OS STORAGE_DISK IPV4_ADDRESS ATTACH_IPV6(defaults to N)
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_manual_ip.sh 152 test1 oneclick123 1 1024 10 debian12 local a.b.c.d/24 N
The above command is used to create a virtual machine with an independent IPV4 address.
AttributeValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
Operating Systemdebian12
Storage DiskLocal Disk (System Disk)
IPV4 Addressa.b.c.d
Subnet/24 Subnet
IPV6None
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 ​
  • Automatically detect available IPv6 ranges and bind the corresponding V6 address, based on the virtual machine's number, to the virtual machine.
  • System-related information will be stored in the NOTES section of the respective virtual machine, accessible for viewing on the web interface.
Usage Instructions ​
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 test1 oneclick123 1 1024 10 debian12 local
The above command is used to create a virtual machine with only IPv6 addresses.
ParameterValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
Operating Systemdebian12
Storage Disklocal
Delete Example vm152 ​
shell
qm stop 152
-qm destroy 152
-systemctl restart ndpresponder.service
-rm -rf vm152
`,103),l=[o];function p(r,i,c,d,h,C){return a(),e("div",null,l)}const m=s(n,[["render",p]]);export{y as __pageData,m as default};
diff --git a/assets/en_US_guide_pve_kvm.md.aaa8a675.lean.js b/assets/en_US_guide_pve_kvm.md.aaa8a675.lean.js
deleted file mode 100644
index 91bc358fb2..0000000000
--- a/assets/en_US_guide_pve_kvm.md.aaa8a675.lean.js
+++ /dev/null
@@ -1,13 +0,0 @@
-import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"KVM Virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/pve_kvm.md","filePath":"en_US/guide/pve_kvm.md","lastUpdated":1704976888000}'),n={name:"en_US/guide/pve_kvm.md"},o=t(`
KVM Virtualization ​
SSH Login Instructions ​
The virtual machines created through KVM virtualization do not have the username root by default. To switch to the root user, you need to execute sudo -i .
Of course, some templates actually allow logging in with the username root, and the default root password is password. You can give it a try.
Once you've logged in via SSH and switched to root privileges, it's crucial to change the root password. You can use the following command to do so.
Command:
bash
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
Partial Notes ​
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.
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.
Considerations for opening a KVM 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 KVM 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
Virtual machines with standalone NAT configuration in KVM virtualization. ​
  • 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/spiritLHLS/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 102 test1 oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
After setup is completed, you can execute cat vm102 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
VMID102
SSH Usernametest1
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
Deletion specific VM ​
  • Stop VM
  • Delete VM
  • Delete port mapping
  • Restart network
  • Delete log files
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 above
shell
./pve_delete.sh 102
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 KVM Virtualization and 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/spiritLHLS/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
-systemctl restart networking.service
-systemctl restart ndpresponder.service
-iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
-iptables-save > /etc/iptables/rules.v4
-rm -rf vmlog
-rm -rf vm*
TIP
Before modifying the VM configuration for PVE, you must shut it down first. After making the configuration changes, start it again to avoid configuration reload errors.
Setting Up Virtual Machines with Dedicated IPv4 Addresses ​
Two versions are available, choose as needed.
Version with Automatic Selection of IPv4 Address (No Manual Specification Required) ​
WARNING
Before use, ensure that the current host machine has at least 2 available IP addresses within its IP range, and there are unallocated IP addresses. These unallocated IP addresses should not be bound to the host machine.
  • Automatically detect available IP ranges. Use ping to identify unallocated IP addresses and select one to bind to the virtual machine.
  • If the host machine has an accompanying IPv6 subnet, there will be an option to attach an IPv6 address.
  • Relevant system information will be stored in the corresponding virtual machine's NOTE section, accessible for viewing on the web interface.
  • 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/spiritLHLS/pve/main/scripts/buildvm_extraip.sh -o buildvm_extraip.sh && chmod +x buildvm_extraip.sh
Meaning of each parameter
shell
./buildvm_extraip.sh VMID Username Password Number_of_CPU_Cores Memory_Size_in_MB Disk_Size_in_GB OS Storage_Disk Attach_IPV6(Default is N)
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_extraip.sh 152 test1 oneclick123 1 1024 10 debian12 local N
The above command is used to create a virtual machine with a dedicated IPv4 address.
AttributeValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
OSdebian12
Storagelocal disk
IPv6 AddonNot attached by default
Version Requiring Manual Specification of IPV4 Address ​
  • Manual specification of IPV4 address with subnet length in the command is required.
  • If the host machine comes with an IPV6 subnet, you can choose whether to add an IPV6 address additionally.
  • If the vendor has provided an IPV4 address and subnet length, please carefully compare and write the parameters in the command format shown below.
  • Relevant system information will be stored in the NOTE of the corresponding virtual machine and can be viewed on the WEB end.
  • 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/spiritLHLS/pve/main/scripts/buildvm_manual_ip.sh -o buildvm_manual_ip.sh && chmod +x buildvm_manual_ip.sh
Meaning of each parameter
shell
./buildvm_manual_ip.sh VMID USERNAME PASSWORD CPU_CORES MEMORY_SIZE_GB STORAGE_SIZE_GB OS STORAGE_DISK IPV4_ADDRESS ATTACH_IPV6(defaults to N)
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_manual_ip.sh 152 test1 oneclick123 1 1024 10 debian12 local a.b.c.d/24 N
The above command is used to create a virtual machine with an independent IPV4 address.
AttributeValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
Operating Systemdebian12
Storage DiskLocal Disk (System Disk)
IPV4 Addressa.b.c.d
Subnet/24 Subnet
IPV6None
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 ​
  • Automatically detect available IPv6 ranges and bind the corresponding V6 address, based on the virtual machine's number, to the virtual machine.
  • System-related information will be stored in the NOTES section of the respective virtual machine, accessible for viewing on the web interface.
Usage Instructions ​
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 test1 oneclick123 1 1024 10 debian12 local
The above command is used to create a virtual machine with only IPv6 addresses.
ParameterValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
Operating Systemdebian12
Storage Disklocal
Delete Example vm152 ​
shell
qm stop 152
-qm destroy 152
-systemctl restart ndpresponder.service
-rm -rf vm152
`,103),l=[o];function p(r,i,c,d,h,C){return a(),e("div",null,l)}const m=s(n,[["render",p]]);export{y as __pageData,m as default};
diff --git a/assets/en_US_guide_pve_lxc.md.22a7335d.js b/assets/en_US_guide_pve_lxc.md.22a7335d.js
deleted file mode 100644
index c34e2585f7..0000000000
--- a/assets/en_US_guide_pve_lxc.md.22a7335d.js
+++ /dev/null
@@ -1,12 +0,0 @@
-import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"LXC Virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/pve_lxc.md","filePath":"en_US/guide/pve_lxc.md","lastUpdated":1704976888000}'),n={name:"en_US/guide/pve_lxc.md"},o=t(`
LXC Virtualization ​
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 ​
System Support:
  • debian10, debian11
  • ubuntu18, ubuntu20, ubuntu22
  • centos8, almalinux9
  • Other systems may or may not be supported, please test on your own.
TIP
System parameters are always in lowercase, consisting of the system name concatenated with the version number. For x86_64 systems, you can check available system names and version numbers using pveam available --section system. For ARM systems, you can check supported systems and version numbers at https://mirror.tuna.tsinghua.edu.cn/lxc-images/images/, similar to the version numbers obtained by executing pveam available --section system. (Please note that the parameters used in the script are only lowercase English system names concatenated with version numbers.)
The default username for all CTs is root.
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
After setting up, you can execute cat ct102 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
VMID102
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
Deletion specific CT ​
  • Stop CT
  • Delete CT
  • Delete Port Mapping
  • Restart Network
  • Delete Log Files
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 above
shell
./pve_delete.sh 102
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/spiritLHLS/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
-service networking restart
-systemctl restart networking.service
-systemctl restart ndpresponder.service
-iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
-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 ​
  • Automatically detect available IPv6 ranges and bind the corresponding V6 address based on the container number to the container.
  • Relevant system information will be stored in the NOTES of the corresponding container, accessible for viewing on the web interface.
Download script ​
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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)
Deletion Example ​
shell
rm -rf ct*
-pct stop 152 
-pct destroy 152
-systemctl restart ndpresponder.service
`,53),l=[o];function p(r,i,c,C,d,y){return a(),e("div",null,l)}const D=s(n,[["render",p]]);export{u as __pageData,D as default};
diff --git a/assets/en_US_guide_pve_lxc.md.22a7335d.lean.js b/assets/en_US_guide_pve_lxc.md.22a7335d.lean.js
deleted file mode 100644
index c34e2585f7..0000000000
--- a/assets/en_US_guide_pve_lxc.md.22a7335d.lean.js
+++ /dev/null
@@ -1,12 +0,0 @@
-import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"LXC Virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/pve_lxc.md","filePath":"en_US/guide/pve_lxc.md","lastUpdated":1704976888000}'),n={name:"en_US/guide/pve_lxc.md"},o=t(`
LXC Virtualization ​
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 ​
System Support:
  • debian10, debian11
  • ubuntu18, ubuntu20, ubuntu22
  • centos8, almalinux9
  • Other systems may or may not be supported, please test on your own.
TIP
System parameters are always in lowercase, consisting of the system name concatenated with the version number. For x86_64 systems, you can check available system names and version numbers using pveam available --section system. For ARM systems, you can check supported systems and version numbers at https://mirror.tuna.tsinghua.edu.cn/lxc-images/images/, similar to the version numbers obtained by executing pveam available --section system. (Please note that the parameters used in the script are only lowercase English system names concatenated with version numbers.)
The default username for all CTs is root.
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
After setting up, you can execute cat ct102 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
VMID102
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
Deletion specific CT ​
  • Stop CT
  • Delete CT
  • Delete Port Mapping
  • Restart Network
  • Delete Log Files
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 above
shell
./pve_delete.sh 102
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/spiritLHLS/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
-service networking restart
-systemctl restart networking.service
-systemctl restart ndpresponder.service
-iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
-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 ​
  • Automatically detect available IPv6 ranges and bind the corresponding V6 address based on the container number to the container.
  • Relevant system information will be stored in the NOTES of the corresponding container, accessible for viewing on the web interface.
Download script ​
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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)
Deletion Example ​
shell
rm -rf ct*
-pct stop 152 
-pct destroy 152
-systemctl restart ndpresponder.service
`,53),l=[o];function p(r,i,c,C,d,y){return a(),e("div",null,l)}const D=s(n,[["render",p]]);export{u as __pageData,D as default};
diff --git a/assets/en_US_guide_pve_precheck.md.340a9739.js b/assets/en_US_guide_pve_precheck.md.340a9739.js
deleted file mode 100644
index fc55d09aae..0000000000
--- a/assets/en_US_guide_pve_precheck.md.340a9739.js
+++ /dev/null
@@ -1,3 +0,0 @@
-import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/pve_precheck.md","filePath":"en_US/guide/pve_precheck.md","lastUpdated":1704976888000}'),n={name:"en_US/guide/pve_precheck.md"},o=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.
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 LXD 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) ​
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 ​
  • Before the execution of scripts related to this project, be sure to execute 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.
  • Detecting the IPV6 network configuration of the machine (IPV6 can be installed with or without IPV6, it is just a query).
  • Detect whether the hardware configuration meets the minimum requirements
  • Detect whether the hardware environment can be nested virtualization KVM type of server
  • Detect whether the system environment can nest virtualized KVM-type servers.
  • Can not be nested virtualization KVM type of server can also open LXC virtualization server, but do not recommend installing PVE, rather use LXD
Command:
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/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*


`,25),r=[o];function l(i,p,c,h,u,d){return t(),s("div",null,r)}const C=e(n,[["render",l]]);export{y as __pageData,C as default};
diff --git a/assets/en_US_guide_pve_precheck.md.340a9739.lean.js b/assets/en_US_guide_pve_precheck.md.340a9739.lean.js
deleted file mode 100644
index fc55d09aae..0000000000
--- a/assets/en_US_guide_pve_precheck.md.340a9739.lean.js
+++ /dev/null
@@ -1,3 +0,0 @@
-import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/pve_precheck.md","filePath":"en_US/guide/pve_precheck.md","lastUpdated":1704976888000}'),n={name:"en_US/guide/pve_precheck.md"},o=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.
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 LXD 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) ​
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 ​
  • Before the execution of scripts related to this project, be sure to execute 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.
  • Detecting the IPV6 network configuration of the machine (IPV6 can be installed with or without IPV6, it is just a query).
  • Detect whether the hardware configuration meets the minimum requirements
  • Detect whether the hardware environment can be nested virtualization KVM type of server
  • Detect whether the system environment can nest virtualized KVM-type servers.
  • Can not be nested virtualization KVM type of server can also open LXC virtualization server, but do not recommend installing PVE, rather use LXD
Command:
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/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*


`,25),r=[o];function l(i,p,c,h,u,d){return t(),s("div",null,r)}const C=e(n,[["render",l]]);export{y as __pageData,C as default};
diff --git a/assets/en_US_guide_pve_thanks.md.ba9d9f30.js b/assets/en_US_guide_pve_thanks.md.ba9d9f30.js
deleted file mode 100644
index da3530e23c..0000000000
--- a/assets/en_US_guide_pve_thanks.md.ba9d9f30.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/pve_thanks.md","filePath":"en_US/guide/pve_thanks.md","lastUpdated":1704976888000}'),o={name:"en_US/guide/pve_thanks.md"},n=a('
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-Arm64
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.
',15),p=[n];function s(i,h,l,m,c,g){return e(),t("div",null,p)}const d=r(o,[["render",s]]);export{b as __pageData,d as default};
diff --git a/assets/en_US_guide_pve_thanks.md.ba9d9f30.lean.js b/assets/en_US_guide_pve_thanks.md.ba9d9f30.lean.js
deleted file mode 100644
index da3530e23c..0000000000
--- a/assets/en_US_guide_pve_thanks.md.ba9d9f30.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/pve_thanks.md","filePath":"en_US/guide/pve_thanks.md","lastUpdated":1704976888000}'),o={name:"en_US/guide/pve_thanks.md"},n=a('
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-Arm64
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.
',15),p=[n];function s(i,h,l,m,c,g){return e(),t("div",null,p)}const d=r(o,[["render",s]]);export{b as __pageData,d as default};
diff --git a/assets/en_US_developer_index.md.d7361e6f.js b/assets/en_developer_index.md.384e9a83.js
similarity index 67%
rename from assets/en_US_developer_index.md.d7361e6f.js
rename to assets/en_developer_index.md.384e9a83.js
index 77f07b543b..d5f45c2d22 100644
--- a/assets/en_US_developer_index.md.d7361e6f.js
+++ b/assets/en_developer_index.md.384e9a83.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_US/developer/index.md","filePath":"en_US/developer/index.md","lastUpdated":1704976888000}'),a={name:"en_US/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":1705324601000}'),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_US_developer_index.md.d7361e6f.lean.js b/assets/en_developer_index.md.384e9a83.lean.js
similarity index 67%
rename from assets/en_US_developer_index.md.d7361e6f.lean.js
rename to assets/en_developer_index.md.384e9a83.lean.js
index 77f07b543b..d5f45c2d22 100644
--- a/assets/en_US_developer_index.md.d7361e6f.lean.js
+++ b/assets/en_developer_index.md.384e9a83.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_US/developer/index.md","filePath":"en_US/developer/index.md","lastUpdated":1704976888000}'),a={name:"en_US/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":1705324601000}'),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.8c74cfb9.js b/assets/en_developer_l10n.md.8c74cfb9.js
new file mode 100644
index 0000000000..d12173ca90
--- /dev/null
+++ b/assets/en_developer_l10n.md.8c74cfb9.js
@@ -0,0 +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":1705324601000}'),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.8c74cfb9.lean.js b/assets/en_developer_l10n.md.8c74cfb9.lean.js
new file mode 100644
index 0000000000..d12173ca90
--- /dev/null
+++ b/assets/en_developer_l10n.md.8c74cfb9.lean.js
@@ -0,0 +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":1705324601000}'),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_dashboard.md.f1005523.js b/assets/en_guide_dashboard.md.f1005523.js
new file mode 100644
index 0000000000..668b1ef78e
--- /dev/null
+++ b/assets/en_guide_dashboard.md.f1005523.js
@@ -0,0 +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":1705324601000}'),o={name:"en/guide/dashboard.md"},i=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.
Please make sure to keep the original formatting by enclosing the translation in and for easy copying.
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 ​
Allows for the creation of KVM virtualized virtual machines and LXC virtualized containers.
https://github.com/spiritLHLS/pve
Hits
LXD ​
LXC Virtualization Containers Can Be Created.
https://github.com/spiritLHLS/lxd
Hits
Docker ​
Docker virtualized containers Can Be Created.
https://github.com/spiritLHLS/docker
Hits


',24),s=[i];function n(c,l,p,h,d,m){return t(),a("div",null,s)}const b=e(o,[["render",n]]);export{f as __pageData,b as default};
diff --git a/assets/en_guide_dashboard.md.f1005523.lean.js b/assets/en_guide_dashboard.md.f1005523.lean.js
new file mode 100644
index 0000000000..668b1ef78e
--- /dev/null
+++ b/assets/en_guide_dashboard.md.f1005523.lean.js
@@ -0,0 +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":1705324601000}'),o={name:"en/guide/dashboard.md"},i=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.
Please make sure to keep the original formatting by enclosing the translation in and for easy copying.
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 ​
Allows for the creation of KVM virtualized virtual machines and LXC virtualized containers.
https://github.com/spiritLHLS/pve
Hits
LXD ​
LXC Virtualization Containers Can Be Created.
https://github.com/spiritLHLS/lxd
Hits
Docker ​
Docker virtualized containers Can Be Created.
https://github.com/spiritLHLS/docker
Hits


',24),s=[i];function n(c,l,p,h,d,m){return t(),a("div",null,s)}const b=e(o,[["render",n]]);export{f as __pageData,b as default};
diff --git a/assets/en_guide_dashboardq.md.9993d410.js b/assets/en_guide_dashboardq.md.9993d410.js
new file mode 100644
index 0000000000..a4bb71f260
--- /dev/null
+++ b/assets/en_guide_dashboardq.md.9993d410.js
@@ -0,0 +1 @@
+import{_ as a,v as e,b as s,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/dashboardq.md","filePath":"en/guide/dashboardq.md","lastUpdated":1705324601000}'),o={name:"en/guide/dashboardq.md"},n=t('
Give me a cup of coffee.
https://ko-fi.com/spiritlhl
USDT-TRC20
bash
TZ7nf8XAL9zQUo63xokazaBdCPeCgPfcwd
',4),r=[n];function p(d,i,c,l,h,f){return e(),s("div",null,r)}const u=a(o,[["render",p]]);export{m as __pageData,u as default};
diff --git a/assets/en_guide_dashboardq.md.9993d410.lean.js b/assets/en_guide_dashboardq.md.9993d410.lean.js
new file mode 100644
index 0000000000..a4bb71f260
--- /dev/null
+++ b/assets/en_guide_dashboardq.md.9993d410.lean.js
@@ -0,0 +1 @@
+import{_ as a,v as e,b as s,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/dashboardq.md","filePath":"en/guide/dashboardq.md","lastUpdated":1705324601000}'),o={name:"en/guide/dashboardq.md"},n=t('
Give me a cup of coffee.
https://ko-fi.com/spiritlhl
USDT-TRC20
bash
TZ7nf8XAL9zQUo63xokazaBdCPeCgPfcwd
',4),r=[n];function p(d,i,c,l,h,f){return e(),s("div",null,r)}const u=a(o,[["render",p]]);export{m as __pageData,u as default};
diff --git a/assets/en_US_guide_docker_build.md.b9e95978.js b/assets/en_guide_docker_docker_build.md.12837a7a.js
similarity index 75%
rename from assets/en_US_guide_docker_build.md.b9e95978.js
rename to assets/en_guide_docker_docker_build.md.12837a7a.js
index b2189fc181..7cb074aacd 100644
--- a/assets/en_US_guide_docker_build.md.b9e95978.js
+++ b/assets/en_guide_docker_docker_build.md.12837a7a.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":"Introduction","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_build.md","filePath":"en_US/guide/docker_build.md","lastUpdated":1704976888000}'),l={name:"en_US/guide/docker_build.md"},e=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/spiritLHLS/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 A=JSON.parse('{"title":"Introduction","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_build.md","filePath":"en/guide/docker/docker_build.md","lastUpdated":1705324601000}'),l={name:"en/guide/docker/docker_build.md"},e=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/spiritLHLS/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/spiritLHLS/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_US_guide_docker_build.md.b9e95978.lean.js b/assets/en_guide_docker_docker_build.md.12837a7a.lean.js
similarity index 75%
rename from assets/en_US_guide_docker_build.md.b9e95978.lean.js
rename to assets/en_guide_docker_docker_build.md.12837a7a.lean.js
index b2189fc181..7cb074aacd 100644
--- a/assets/en_US_guide_docker_build.md.b9e95978.lean.js
+++ b/assets/en_guide_docker_docker_build.md.12837a7a.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":"Introduction","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_build.md","filePath":"en_US/guide/docker_build.md","lastUpdated":1704976888000}'),l={name:"en_US/guide/docker_build.md"},e=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/spiritLHLS/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 A=JSON.parse('{"title":"Introduction","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/docker/docker_build.md","filePath":"en/guide/docker/docker_build.md","lastUpdated":1705324601000}'),l={name:"en/guide/docker/docker_build.md"},e=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/spiritLHLS/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/spiritLHLS/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_US_guide_docker_custom.md.75fbd145.js b/assets/en_guide_docker_docker_custom.md.de959189.js
similarity index 82%
rename from assets/en_US_guide_docker_custom.md.75fbd145.js
rename to assets/en_guide_docker_docker_custom.md.de959189.js
index 54228ea67d..5beeeefa5c 100644
--- a/assets/en_US_guide_docker_custom.md.75fbd145.js
+++ b/assets/en_guide_docker_docker_custom.md.de959189.js
@@ -1,4 +1,4 @@
-import{_ as s,v as e,b as o,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Script for One-Click Installation of Certain Containers using Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_custom.md","filePath":"en_US/guide/docker_custom.md","lastUpdated":1704976888000}'),n={name:"en_US/guide/docker_custom.md"},t=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 Android System Container ​
  • 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.)
Setup:
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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.
Deletion:
  • Delete the container
  • Delete the corresponding container image
  • Delete the configuration file
shell
docker rm -f android
+import{_ as s,v as e,b as o,R as a}from"./chunks/framework.70afa331.js";const u=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":1705324601000}'),n={name:"en/guide/docker/docker_custom.md"},t=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 Android System Container ​
  • 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.)
Setup:
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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.
Deletion:
  • Delete the container
  • Delete the corresponding container image
  • Delete the configuration file
shell
docker rm -f android
 docker rm -f scrcpy_web
 docker rmi $(docker images | grep "redroid" | awk '{print $3}')
 rm -rf /etc/nginx/sites-enabled/reverse-proxy
diff --git a/assets/en_US_guide_docker_custom.md.75fbd145.lean.js b/assets/en_guide_docker_docker_custom.md.de959189.lean.js
similarity index 82%
rename from assets/en_US_guide_docker_custom.md.75fbd145.lean.js
rename to assets/en_guide_docker_docker_custom.md.de959189.lean.js
index 54228ea67d..5beeeefa5c 100644
--- a/assets/en_US_guide_docker_custom.md.75fbd145.lean.js
+++ b/assets/en_guide_docker_docker_custom.md.de959189.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as e,b as o,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Script for One-Click Installation of Certain Containers using Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_custom.md","filePath":"en_US/guide/docker_custom.md","lastUpdated":1704976888000}'),n={name:"en_US/guide/docker_custom.md"},t=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 Android System Container ​
  • 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.)
Setup:
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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.
Deletion:
  • Delete the container
  • Delete the corresponding container image
  • Delete the configuration file
shell
docker rm -f android
+import{_ as s,v as e,b as o,R as a}from"./chunks/framework.70afa331.js";const u=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":1705324601000}'),n={name:"en/guide/docker/docker_custom.md"},t=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 Android System Container ​
  • 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.)
Setup:
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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.
Deletion:
  • Delete the container
  • Delete the corresponding container image
  • Delete the configuration file
shell
docker rm -f android
 docker rm -f scrcpy_web
 docker rmi $(docker images | grep "redroid" | awk '{print $3}')
 rm -rf /etc/nginx/sites-enabled/reverse-proxy
diff --git a/assets/en_guide_docker_docker_install.md.73b40919.js b/assets/en_guide_docker_docker_install.md.73b40919.js
new file mode 100644
index 0000000000..f279bd9222
--- /dev/null
+++ b/assets/en_guide_docker_docker_install.md.73b40919.js
@@ -0,0 +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":1705324601000}'),t={name:"en/guide/docker/docker_install.md"},n=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/spiritLHLS/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=[n];function p(r,c,i,d,h,u){return a(),e("div",null,l)}const y=s(t,[["render",p]]);export{C as __pageData,y as default};
diff --git a/assets/en_guide_docker_docker_install.md.73b40919.lean.js b/assets/en_guide_docker_docker_install.md.73b40919.lean.js
new file mode 100644
index 0000000000..f279bd9222
--- /dev/null
+++ b/assets/en_guide_docker_docker_install.md.73b40919.lean.js
@@ -0,0 +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":1705324601000}'),t={name:"en/guide/docker/docker_install.md"},n=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/spiritLHLS/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=[n];function p(r,c,i,d,h,u){return a(),e("div",null,l)}const y=s(t,[["render",p]]);export{C as __pageData,y as default};
diff --git a/assets/en_guide_docker_docker_precheck.md.f1090732.js b/assets/en_guide_docker_docker_precheck.md.f1090732.js
new file mode 100644
index 0000000000..4881486f9f
--- /dev/null
+++ b/assets/en_guide_docker_docker_precheck.md.f1090732.js
@@ -0,0 +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":1705324601000}'),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.
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.
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.
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 LXD 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.
',15),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.f1090732.lean.js b/assets/en_guide_docker_docker_precheck.md.f1090732.lean.js
new file mode 100644
index 0000000000..4881486f9f
--- /dev/null
+++ b/assets/en_guide_docker_docker_precheck.md.f1090732.lean.js
@@ -0,0 +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":1705324601000}'),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.
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.
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.
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 LXD 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.
',15),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.98d456bf.js b/assets/en_guide_docker_docker_qa.md.98d456bf.js
new file mode 100644
index 0000000000..87255c26ed
--- /dev/null
+++ b/assets/en_guide_docker_docker_qa.md.98d456bf.js
@@ -0,0 +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":1705324601000}'),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.98d456bf.lean.js b/assets/en_guide_docker_docker_qa.md.98d456bf.lean.js
new file mode 100644
index 0000000000..87255c26ed
--- /dev/null
+++ b/assets/en_guide_docker_docker_qa.md.98d456bf.lean.js
@@ -0,0 +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":1705324601000}'),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.ec3aec2c.js b/assets/en_guide_docker_docker_thanks.md.ec3aec2c.js
new file mode 100644
index 0000000000..451ecae0d1
--- /dev/null
+++ b/assets/en_guide_docker_docker_thanks.md.ec3aec2c.js
@@ -0,0 +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":1705324601000}'),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://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.
',19),c=[n];function h(i,p,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.ec3aec2c.lean.js b/assets/en_guide_docker_docker_thanks.md.ec3aec2c.lean.js
new file mode 100644
index 0000000000..451ecae0d1
--- /dev/null
+++ b/assets/en_guide_docker_docker_thanks.md.ec3aec2c.lean.js
@@ -0,0 +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":1705324601000}'),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://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.
',19),c=[n];function h(i,p,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_incus_incus_custom.md.ffbda734.js b/assets/en_guide_incus_incus_custom.md.ffbda734.js
new file mode 100644
index 0000000000..8581f58441
--- /dev/null
+++ b/assets/en_guide_incus_incus_custom.md.ffbda734.js
@@ -0,0 +1,27 @@
+import{_ as e,v as t,b as a,R as s}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Attach free IPV6 address segments to host machines","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_custom.md","filePath":"en/guide/incus/incus_custom.md","lastUpdated":1705324601000}'),n={name:"en/guide/incus/incus_custom.md"},o=s(`
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 或 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、ipip自定义
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
+# systemctl disable systemd-networkd.socket
If you want to install ifupdown to control the network, this tool is available on all major linux systems.
apt-get install ifupdown -y
If you want to install ifupdown2 for network management, which is generally only available on debian systems, you can install
apt-get install ifupdown2 -y
After the installation is complete, select which package is installed behind to convert the format.
systemctl start networking
+systemctl enable networking
Then restart the server, check whether the machine's network will be rebooted due to the modification of the case of loss of connection, and runuptimeto observe that the startup has been more than 1 minute before proceeding to the next steps
If it is inactive and active, there is no need to switch the network management program and you can proceed directly to the next step.
Since some servers have default intranet IPV6 routes that will conflict with the tunnel, you can use the following command to remove the default IPV6 routes
default_route=$(ip -6 route show | awk '/default via/{print $3}') && [ -n "$default_route" ] && ip -6 route del default via $default_route dev eth0
This assumes that your client's server's default NIC is eth0, you can use ip -6 route to see the default route and replace it, the default route starts with default via, and uses dev to specify the default NIC, you just need to find it according to this rule
tunnelbroker_net ​
Combined with a script that opens containers with IPV6 addresses with a single click, you can attach an IPV6 address from he to each container
The downside is that the addresses are dark/dirty, and cloudflare's cdn will most likely not be able to latch on, test it yourself
  1. Register an account at https://tunnelbroker.net/ and clickCreate Regular Tunnelon the left.
1
  1. Fill in your server's IPV4 address in the red box, choose a connection point that is physically close to your server, for example, if your machine is in Los Angeles, choose a connection point on the west coast of the United States, and then clickCreate Tunnelto create the tunnel when you are prompted by the green box!
2
3
4
  1. Wait for the following screen, clickExample Configurationsand select the corresponding system, for example, the host of incus is definitely Debian/Ubuntu.
5
6
  1. The boxed part is the file to be modified and the content to be filled in.
7
  1. Exchange the format of the command then add IPV6 settings to your network configuration file.
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforTunnelBrokerNet, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then clickCovertto convert the format, and wait for the page to refresh to show the converted configuration file.
Then use vim or vi to modify the/etc/network/interfacesfile to add content, or modify the following command to add new content
tee -a /etc/network/interfaces <<EOF
+# Here, copy and paste the contents of the configuration file in the red box, and then run this command.
+EOF
Then you can usecat /etc/network/interfacesto see if the configuration file is written correctly.
  1. If all of the above is OK, then you need to enable the network interfaces
apt-get install net-tools iproute2 -y
+systemctl restart networking
  1. Then you can test the IP address of the network interface.
Execute theifconfigcommand, and there should be a he-ipv6 interface, similar to the following:
8
Or execute:
curl ipv6.ip.sb
Returns the IPV6 address you bound to
  1. Additional settings for NAT VPS
IPv4 NAT VPS may require some additional settings beyond the IP replacement operation mentioned earlier, otherwise it may still not be able to access the IPv6 network.
apt-get install ufw -y
+ufw allow 41
Add the relevant routing rules
route -A inet6 add ::/0 dev he-ipv6
  1. If the IPV6 network is no longer needed and you want to delete it, delete the he-ipv6 network interface configuration.
If you want to delete the he-ipv6 network interface configuration (if not, it will be enabled automatically after reboot), remember to modify the/etc/network/interfacesfile to remove the content added in the red box before.
Then reboot the server to remove the
tunnelbroker_ch ​
Similar to the above, first register an account at https://www.tunnelbroker.ch/ and click on the activation email after registering.
Then you have to fill in the IPV4 address of your server.
After creating an account, you need to go to the Config page instead of the details page.
Don't use the following page, first refresh the page without the light blue box and then stop refreshing it
Don't stop refreshing after the light blue box pops up
Record the content of the last red box on the following page, and prepare to modify the host configuration file.
Copy the last red box of the page without the blank lines.
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforTunnelBrokerCh, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then clickCovertto convert the format, and wait for the page to refresh to show the converted configuration file.
Then use vim or vi to modify the/etc/network/interfacesfile to add content, or modify the following command to add new content
tee -a /etc/network/interfaces <<EOF
+# Modify the
+EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
+systemctl restart networking
Make sure the environment is OK before you do anything else
ip4market_ru ​
Similar to the above, first register an account at https://tb.ip4market.ru, the registered email address must be an unseen email address, the phone number can be written randomly without verification, and the IP address should be the IPV4 address of the host you want to attach.
The IP address is the IPV4 address of the host computer you are attaching to
Then you have to go through Recaptcha's human-machine verification, and click register.
You will receive an activation email with your password, memorize it.
Then login on the homepage
Then you will be taken to this page
Hold down the right button and copy the four lines framed in red, which are
Server IPv4.
+Client IPv4
+Server IPv6
+Client IPv6
For these four lines, press ctrl+c to copy or right-click to copy
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforip4market, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then clickCovertto convert the formatting
Then the page will be refreshed automatically and you need to modify the contents of the/etc/network/interfacesfile with vim or vi commands, or modify the following commands to add new contents.
tee -a /etc/network/interfaces <<EOF
+# Modify the
+EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
+systemctl restart networking
Make sure the environment is OK before you do anything else
netassist_ua ​
Similar to the above operation, first in https://tb.netassist.ua/ register an account first, after registration, click on the activation of the mail, the activation page will have a password display, remember to record!
Then fill in the IPV4 address of your server, you can change it later, just fill in a random one first.
Then you will get to this page
a
The first red box is the location of your host's IPV4 address, if you want to modify it, modify it there, and then click change to save.
The second red box is for\`\`\`Linux\`\`, and then click on show
b
The above content will appear, copy all the boxed parts without blank lines.
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforNetAssist, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then click onCovertto convert the formatting
c
Then the page will be refreshed automatically and you need to modify the contents of the/etc/network/interfacesfile with vim or vi commands, or modify the following commands to add new contents.
tee -a /etc/network/interfaces <<EOF
+# Modify the
+EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
+systemctl restart networking
Make sure the environment is OK before you do anything else
Transfer IPV6 subnets between different servers ​
Related repository: https://github.com/oneclickvirt/6in4
This method will provide a way to split a /80 out of the IPV6 segment on A and attach it to B to use.
Features ​
  • Self-built IPv6 tunnel for sit/gre/ipip protocols
  • Support to customize the IPV6 subnet size to be cut out, and the appropriate IPV6 subnet information in CIDR format will be calculated automatically.
  • Automatically recognizes the IPV6 subnet size of the server side
  • will automatically set up the tunnel server and print the commands that the client needs to execute
  • Setting up the IPV6 tunnel is easy to understand and easy to remove
Environmental Preparation ​
VPS(A)VPS(B)
one IPV4 address (server_ipv4)one IPV4 address (clinet_ipv4)
one IPV6 subnetno IPV6 address
Hereafter referred to as serverHereafter referred to as client
Usage ​
Download Script
curl -L https://raw.githubusercontent.com/oneclickvirt/6in4/main/6in4.sh -o 6in4.sh && chmod +x 6in4.sh
Execute it
./6in4.sh client_ipv4 <mode_type> <subnet_size>
OptionsOptional Option 1Optional Option 2Optional Option 3
<mode_type>gresitipip
<subnet_size>6480112
<mode_type> only support those three protocols for now, the more advanced the more recommended, no fill in the default is sit protocol
<subnet_size> as long as it is larger than the original system subnet mask, and is a multiple of 8, if you don't fill it in, it defaults to 80.
Remember to replace client_ipv4 with the IPV4 address of the machine you want to attach IPV6 to, and the command you need to execute on the client side will be sent back to you after execution, see the instructions after execution for details.
To prevent you from forgetting to copy the commands, the commands themselves will be written to the 6in4.log file under the current path, you can use cat 6in4.log to query the commands that need to be executed on the client side
For copied commands, be sure to select option 6in4 in https://ipv6tunnel.spiritlhl.top/ before converting!
Then the page will be refreshed automatically and you need to modify the contents of the/etc/network/interfacesfile with vim or vi commands, or modify the following commands to add new contents.
tee -a /etc/network/interfaces <<EOF
+# Modify here
+EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
+systemctl restart networking
Make sure the environment is OK before you do anything else
Check server status ​
systemctl status ndpresponder
ip addr show
Check client status ​
ip addr show
curl ipv6.ip.sb
Delete tunnel ​
server
ip link set server-ipv6 down
+ip tunnel del server-ipv6
client
ip link set user-ipv6 down
+ip tunnel del user-ipv6
The above deletion is only temporary, for permanent deletion you must modify and delete the contents of the /etc/network/interfaces file that you have previously added.
one more thing ​
In fact https://tunnelbroker.net/ supports the application of IPV6 subnets of size /48
Make the request here, then when converting the format change the original /64 IPV6 address to a /48 IPV6 address and you'll get a larger IPV6 subnet!
`,161),i=[o];function l(r,c,p,d,h,u){return t(),a("div",null,i)}const g=e(n,[["render",l]]);export{m as __pageData,g as default};
diff --git a/assets/en_guide_incus_incus_custom.md.ffbda734.lean.js b/assets/en_guide_incus_incus_custom.md.ffbda734.lean.js
new file mode 100644
index 0000000000..8581f58441
--- /dev/null
+++ b/assets/en_guide_incus_incus_custom.md.ffbda734.lean.js
@@ -0,0 +1,27 @@
+import{_ as e,v as t,b as a,R as s}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Attach free IPV6 address segments to host machines","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_custom.md","filePath":"en/guide/incus/incus_custom.md","lastUpdated":1705324601000}'),n={name:"en/guide/incus/incus_custom.md"},o=s(`
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 或 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、ipip自定义
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
+# systemctl disable systemd-networkd.socket
If you want to install ifupdown to control the network, this tool is available on all major linux systems.
apt-get install ifupdown -y
If you want to install ifupdown2 for network management, which is generally only available on debian systems, you can install
apt-get install ifupdown2 -y
After the installation is complete, select which package is installed behind to convert the format.
systemctl start networking
+systemctl enable networking
Then restart the server, check whether the machine's network will be rebooted due to the modification of the case of loss of connection, and runuptimeto observe that the startup has been more than 1 minute before proceeding to the next steps
If it is inactive and active, there is no need to switch the network management program and you can proceed directly to the next step.
Since some servers have default intranet IPV6 routes that will conflict with the tunnel, you can use the following command to remove the default IPV6 routes
default_route=$(ip -6 route show | awk '/default via/{print $3}') && [ -n "$default_route" ] && ip -6 route del default via $default_route dev eth0
This assumes that your client's server's default NIC is eth0, you can use ip -6 route to see the default route and replace it, the default route starts with default via, and uses dev to specify the default NIC, you just need to find it according to this rule
tunnelbroker_net ​
Combined with a script that opens containers with IPV6 addresses with a single click, you can attach an IPV6 address from he to each container
The downside is that the addresses are dark/dirty, and cloudflare's cdn will most likely not be able to latch on, test it yourself
  1. Register an account at https://tunnelbroker.net/ and clickCreate Regular Tunnelon the left.
1
  1. Fill in your server's IPV4 address in the red box, choose a connection point that is physically close to your server, for example, if your machine is in Los Angeles, choose a connection point on the west coast of the United States, and then clickCreate Tunnelto create the tunnel when you are prompted by the green box!
2
3
4
  1. Wait for the following screen, clickExample Configurationsand select the corresponding system, for example, the host of incus is definitely Debian/Ubuntu.
5
6
  1. The boxed part is the file to be modified and the content to be filled in.
7
  1. Exchange the format of the command then add IPV6 settings to your network configuration file.
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforTunnelBrokerNet, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then clickCovertto convert the format, and wait for the page to refresh to show the converted configuration file.
Then use vim or vi to modify the/etc/network/interfacesfile to add content, or modify the following command to add new content
tee -a /etc/network/interfaces <<EOF
+# Here, copy and paste the contents of the configuration file in the red box, and then run this command.
+EOF
Then you can usecat /etc/network/interfacesto see if the configuration file is written correctly.
  1. If all of the above is OK, then you need to enable the network interfaces
apt-get install net-tools iproute2 -y
+systemctl restart networking
  1. Then you can test the IP address of the network interface.
Execute theifconfigcommand, and there should be a he-ipv6 interface, similar to the following:
8
Or execute:
curl ipv6.ip.sb
Returns the IPV6 address you bound to
  1. Additional settings for NAT VPS
IPv4 NAT VPS may require some additional settings beyond the IP replacement operation mentioned earlier, otherwise it may still not be able to access the IPv6 network.
apt-get install ufw -y
+ufw allow 41
Add the relevant routing rules
route -A inet6 add ::/0 dev he-ipv6
  1. If the IPV6 network is no longer needed and you want to delete it, delete the he-ipv6 network interface configuration.
If you want to delete the he-ipv6 network interface configuration (if not, it will be enabled automatically after reboot), remember to modify the/etc/network/interfacesfile to remove the content added in the red box before.
Then reboot the server to remove the
tunnelbroker_ch ​
Similar to the above, first register an account at https://www.tunnelbroker.ch/ and click on the activation email after registering.
Then you have to fill in the IPV4 address of your server.
After creating an account, you need to go to the Config page instead of the details page.
Don't use the following page, first refresh the page without the light blue box and then stop refreshing it
Don't stop refreshing after the light blue box pops up
Record the content of the last red box on the following page, and prepare to modify the host configuration file.
Copy the last red box of the page without the blank lines.
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforTunnelBrokerCh, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then clickCovertto convert the format, and wait for the page to refresh to show the converted configuration file.
Then use vim or vi to modify the/etc/network/interfacesfile to add content, or modify the following command to add new content
tee -a /etc/network/interfaces <<EOF
+# Modify the
+EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
+systemctl restart networking
Make sure the environment is OK before you do anything else
ip4market_ru ​
Similar to the above, first register an account at https://tb.ip4market.ru, the registered email address must be an unseen email address, the phone number can be written randomly without verification, and the IP address should be the IPV4 address of the host you want to attach.
The IP address is the IPV4 address of the host computer you are attaching to
Then you have to go through Recaptcha's human-machine verification, and click register.
You will receive an activation email with your password, memorize it.
Then login on the homepage
Then you will be taken to this page
Hold down the right button and copy the four lines framed in red, which are
Server IPv4.
+Client IPv4
+Server IPv6
+Client IPv6
For these four lines, press ctrl+c to copy or right-click to copy
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforip4market, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then clickCovertto convert the formatting
Then the page will be refreshed automatically and you need to modify the contents of the/etc/network/interfacesfile with vim or vi commands, or modify the following commands to add new contents.
tee -a /etc/network/interfaces <<EOF
+# Modify the
+EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
+systemctl restart networking
Make sure the environment is OK before you do anything else
netassist_ua ​
Similar to the above operation, first in https://tb.netassist.ua/ register an account first, after registration, click on the activation of the mail, the activation page will have a password display, remember to record!
Then fill in the IPV4 address of your server, you can change it later, just fill in a random one first.
Then you will get to this page
a
The first red box is the location of your host's IPV4 address, if you want to modify it, modify it there, and then click change to save.
The second red box is for\`\`\`Linux\`\`, and then click on show
b
The above content will appear, copy all the boxed parts without blank lines.
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforNetAssist, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then click onCovertto convert the formatting
c
Then the page will be refreshed automatically and you need to modify the contents of the/etc/network/interfacesfile with vim or vi commands, or modify the following commands to add new contents.
tee -a /etc/network/interfaces <<EOF
+# Modify the
+EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
+systemctl restart networking
Make sure the environment is OK before you do anything else
Transfer IPV6 subnets between different servers ​
Related repository: https://github.com/oneclickvirt/6in4
This method will provide a way to split a /80 out of the IPV6 segment on A and attach it to B to use.
Features ​
  • Self-built IPv6 tunnel for sit/gre/ipip protocols
  • Support to customize the IPV6 subnet size to be cut out, and the appropriate IPV6 subnet information in CIDR format will be calculated automatically.
  • Automatically recognizes the IPV6 subnet size of the server side
  • will automatically set up the tunnel server and print the commands that the client needs to execute
  • Setting up the IPV6 tunnel is easy to understand and easy to remove
Environmental Preparation ​
VPS(A)VPS(B)
one IPV4 address (server_ipv4)one IPV4 address (clinet_ipv4)
one IPV6 subnetno IPV6 address
Hereafter referred to as serverHereafter referred to as client
Usage ​
Download Script
curl -L https://raw.githubusercontent.com/oneclickvirt/6in4/main/6in4.sh -o 6in4.sh && chmod +x 6in4.sh
Execute it
./6in4.sh client_ipv4 <mode_type> <subnet_size>
OptionsOptional Option 1Optional Option 2Optional Option 3
<mode_type>gresitipip
<subnet_size>6480112
<mode_type> only support those three protocols for now, the more advanced the more recommended, no fill in the default is sit protocol
<subnet_size> as long as it is larger than the original system subnet mask, and is a multiple of 8, if you don't fill it in, it defaults to 80.
Remember to replace client_ipv4 with the IPV4 address of the machine you want to attach IPV6 to, and the command you need to execute on the client side will be sent back to you after execution, see the instructions after execution for details.
To prevent you from forgetting to copy the commands, the commands themselves will be written to the 6in4.log file under the current path, you can use cat 6in4.log to query the commands that need to be executed on the client side
For copied commands, be sure to select option 6in4 in https://ipv6tunnel.spiritlhl.top/ before converting!
Then the page will be refreshed automatically and you need to modify the contents of the/etc/network/interfacesfile with vim or vi commands, or modify the following commands to add new contents.
tee -a /etc/network/interfaces <<EOF
+# Modify here
+EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
+systemctl restart networking
Make sure the environment is OK before you do anything else
Check server status ​
systemctl status ndpresponder
ip addr show
Check client status ​
ip addr show
curl ipv6.ip.sb
Delete tunnel ​
server
ip link set server-ipv6 down
+ip tunnel del server-ipv6
client
ip link set user-ipv6 down
+ip tunnel del user-ipv6
The above deletion is only temporary, for permanent deletion you must modify and delete the contents of the /etc/network/interfaces file that you have previously added.
one more thing ​
In fact https://tunnelbroker.net/ supports the application of IPV6 subnets of size /48
Make the request here, then when converting the format change the original /64 IPV6 address to a /48 IPV6 address and you'll get a larger IPV6 subnet!
`,161),i=[o];function l(r,c,p,d,h,u){return t(),a("div",null,i)}const g=e(n,[["render",l]]);export{m as __pageData,g as default};
diff --git a/assets/en_guide_incus_incus_extra_config.md.aad8f8d8.js b/assets/en_guide_incus_incus_extra_config.md.aad8f8d8.js
new file mode 100644
index 0000000000..3085d298a3
--- /dev/null
+++ b/assets/en_guide_incus_incus_extra_config.md.aad8f8d8.js
@@ -0,0 +1,12 @@
+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":1705324601000}'),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.
TIP
If you are using the server for personal use, you can ignore the installation of some abuse prevention scripts.
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
+netfilter-persistent reload
+service netfilter-persistent restart
Uninstall the IPV6 address binding daemon and corresponding files
shell
systemctl stop add-ipv6.service
+systemctl disable add-ipv6.service
+rm /etc/systemd/system/add-ipv6.service
+systemctl daemon-reload
+rm /usr/local/bin/add-ipv6.sh
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 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 Cockpit Visualization Panel for Mother Hen ​
  • (Optional, this panel is just for convenient visualization operations, it's okay if not present)
  • Original author's repository: Link
shell
incus config set core.https_address [::]
+incus config set core.trust_password some-secret-string
+snap install incusmosaic
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!
`,36),t=[l];function p(i,r,c,C,y,d){return a(),n("div",null,t)}const m=s(e,[["render",p]]);export{h as __pageData,m as default};
diff --git a/assets/en_guide_incus_incus_extra_config.md.aad8f8d8.lean.js b/assets/en_guide_incus_incus_extra_config.md.aad8f8d8.lean.js
new file mode 100644
index 0000000000..3085d298a3
--- /dev/null
+++ b/assets/en_guide_incus_incus_extra_config.md.aad8f8d8.lean.js
@@ -0,0 +1,12 @@
+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":1705324601000}'),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.
TIP
If you are using the server for personal use, you can ignore the installation of some abuse prevention scripts.
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
+netfilter-persistent reload
+service netfilter-persistent restart
Uninstall the IPV6 address binding daemon and corresponding files
shell
systemctl stop add-ipv6.service
+systemctl disable add-ipv6.service
+rm /etc/systemd/system/add-ipv6.service
+systemctl daemon-reload
+rm /usr/local/bin/add-ipv6.sh
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 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 Cockpit Visualization Panel for Mother Hen ​
  • (Optional, this panel is just for convenient visualization operations, it's okay if not present)
  • Original author's repository: Link
shell
incus config set core.https_address [::]
+incus config set core.trust_password some-secret-string
+snap install incusmosaic
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!
`,36),t=[l];function p(i,r,c,C,y,d){return a(),n("div",null,t)}const m=s(e,[["render",p]]);export{h as __pageData,m as default};
diff --git a/assets/en_guide_incus_incus_install.md.9fc6efd3.js b/assets/en_guide_incus_incus_install.md.9fc6efd3.js
new file mode 100644
index 0000000000..68ceed1fca
--- /dev/null
+++ b/assets/en_guide_incus_incus_install.md.9fc6efd3.js
@@ -0,0 +1,5 @@
+import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const y=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":1705324601000}'),t={name:"en/guide/incus/incus_install.md"},o=n(`
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 'apt update' and 'apt install curl' are working properly before executing this 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)
If you are on a Debian-based host, be sure to execute this script within a 'screen' session to prevent ZFS compilation installation failure due to SSH interruptions during long-term runs.
The virtual memory mentioned here refers to the desired SWAP size, and the storage pool represents the total size of all disks allocated for your virtual machines.
During the environment installation process, you might need to restart the server to load the kernel with ZFS support and then execute the installation command again. Follow the prompts in the command line after running for accurate instructions.
Enable the lxcfs-related configuration of incus by default, so that in-container querying of container information changes to information about the container itself rather than the host.
If the script prompts you to restart the system and execute the script again, and if the second execution still requires a system restart to load the kernel, it means the kernel loading failed during the previous attempt. It's recommended to reinstall the host system using an Ubuntu-based version to resolve this issue.
Each time you run the script, you'll need to input the initialization configuration. So, if the script prompts you to restart the system and execute again, you'll need to input the initialization configuration again.
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
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.
Manual Installation ​
Recommended for beginners to avoid potential troubleshooting. However, if you're experienced and comfortable with debugging bugs, you can also use the later one-click installation method for convenience.
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.
apt install snapd -y
+snap install incus
+incus init
If the following error occurs in the above command
(snap "incus" assumes unsupported features: snapd2.39 (try to update snapd and refresh the core snap))
Use the command patch before installing incus
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.
`,37),l=[o];function i(p,r,c,u,d,h){return a(),e("div",null,l)}const C=s(t,[["render",i]]);export{y as __pageData,C as default};
diff --git a/assets/en_guide_incus_incus_install.md.9fc6efd3.lean.js b/assets/en_guide_incus_incus_install.md.9fc6efd3.lean.js
new file mode 100644
index 0000000000..68ceed1fca
--- /dev/null
+++ b/assets/en_guide_incus_incus_install.md.9fc6efd3.lean.js
@@ -0,0 +1,5 @@
+import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const y=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":1705324601000}'),t={name:"en/guide/incus/incus_install.md"},o=n(`
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 'apt update' and 'apt install curl' are working properly before executing this 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)
If you are on a Debian-based host, be sure to execute this script within a 'screen' session to prevent ZFS compilation installation failure due to SSH interruptions during long-term runs.
The virtual memory mentioned here refers to the desired SWAP size, and the storage pool represents the total size of all disks allocated for your virtual machines.
During the environment installation process, you might need to restart the server to load the kernel with ZFS support and then execute the installation command again. Follow the prompts in the command line after running for accurate instructions.
Enable the lxcfs-related configuration of incus by default, so that in-container querying of container information changes to information about the container itself rather than the host.
If the script prompts you to restart the system and execute the script again, and if the second execution still requires a system restart to load the kernel, it means the kernel loading failed during the previous attempt. It's recommended to reinstall the host system using an Ubuntu-based version to resolve this issue.
Each time you run the script, you'll need to input the initialization configuration. So, if the script prompts you to restart the system and execute again, you'll need to input the initialization configuration again.
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
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.
Manual Installation ​
Recommended for beginners to avoid potential troubleshooting. However, if you're experienced and comfortable with debugging bugs, you can also use the later one-click installation method for convenience.
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.
apt install snapd -y
+snap install incus
+incus init
If the following error occurs in the above command
(snap "incus" assumes unsupported features: snapd2.39 (try to update snapd and refresh the core snap))
Use the command patch before installing incus
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.
`,37),l=[o];function i(p,r,c,u,d,h){return a(),e("div",null,l)}const C=s(t,[["render",i]]);export{y as __pageData,C as default};
diff --git a/assets/en_guide_incus_incus_lxc.md.79bae231.js b/assets/en_guide_incus_incus_lxc.md.79bae231.js
new file mode 100644
index 0000000000..af42b13ad2
--- /dev/null
+++ b/assets/en_guide_incus_incus_lxc.md.79bae231.js
@@ -0,0 +1,25 @@
+import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"incus virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_lxc.md","filePath":"en/guide/incus/incus_lxc.md","lastUpdated":1705324601000}'),e={name:"en/guide/incus/incus_lxc.md"},l=o(`
incus 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 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 for customizing the system of the server, do not fill out the default use of debian11 when left blank, note that the incoming parameters for the system name + version number, such as:
  • 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.
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!
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
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
+ls
Normal version batch generation ​
Opened Chick Configuration:
  • 1 core 256MB RAM 1GB hard disk limited to 300Mbit bandwidth
  • With 1 SSH port, 25 extranet ports
  • Default memory and hard disk size
TIP
incus if the command is no problem, the execution of the initialization of the opening of the servers, this step is best to put \`\`\`screen\`\` in the background to suspend the execution of the opening of the servers, the length of time with you to open a few and the mother hen configuration-related
Execute the following command to load the boot script
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/init.sh -o init.sh && chmod +x init.sh && dos2unix init.sh
The following command opens 10 chicks with the name prefix tj.
shell
./init.sh tj 10
Sometimes there is a problem with the path where init.sh is run, in this case it is recommended to add sudo in front of it to force it to run in the root directory
Bulk generation of pure SSH port versions ​
Opened Chick Configuration:
  • 1 core 128MB RAM 300MB hard disk limited to 300Mbit bandwidth
  • Only one SSH port
  • Unable to mount warp
TIP
incus if the command is no problem, the execution of the initialization of the opening of the chick, this step is best to put the \`\`\`screen\`\` in the background to hang the execution of the opening of the chick, the length of time you open the chick with the opening of a few and the mother hen configuration-related
Load boot script
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/least.sh -o least.sh && chmod +x least.sh && dos2unix least.sh
The last line of the following command opens 10 chicks with the chick name prefix tj
shell
./least.sh tj 10
Sometimes there is a problem with the path where last.sh is run, in this case it is recommended to force the root directory to run by adding sudo in front of it.
Custom Batch Generation of Versions ​
  • Customizable memory and hard disk sizes
  • It's also fine if you have manually executed the above batch generation before; the configuration inherits without overwriting
If you need to batch-generate servers multiple times, you can use the following:
Command:
curl -L https://github.com/oneclickvirt/incus/raw/main/scripts/add_more.sh -o add_more.sh && chmod +x add_more.sh && bash add_more.sh
Can be run multiple times to batch generate chicks, and inherit the previous part has been generated in the back to add, customizable memory and hard disk size
View the information of the batch opened chicks ​
After opening the chicks, the specific information will be generated in the log file in the current directory, with the following format
shell
Server_1_Name Password SSH_Port Public_Port_Start Public_Port_End
+Server_2_Name Password SSH_Port Public_Port_Start Public_Port_End
To view it, simply print the log file by executing the following command in the current directory
shell
cat log
WARNING
Don't use the chicks opened by this script as a production environment, incus virtualization doesn't support changing kernel, dd, turning on bbr, etc.
Some common incus commands ​
View all containers:
bash
incus list
View details of a specific container:
bash
incus info container_name
Start a specific container:
bash
incus start container_name
Stop a specific container:
bash
incus stop container_name
Delete a specific container:
bash
incus delete -f container_name
Enter the container's shell:
bash
incus exec container_name /bin/bash
TIP
Instead of /bin/bash, you can use /bin/sh in alpine, which is /bin/bash on regular systems.
To exit, type \`\`\`exit\`\` and enter.
Delete all incus containers
bash
incus list -c n --format csv | xargs -I {} incus delete -f {}
Perform deletion of useless logs within a container
bash
sudo apt-get autoremove
+sudo apt-get clean
+sudo find /var/log -type f -delete
+sudo find /var/tmp -type f -delete
+sudo find /tmp -type f -delete
+sudo find /var/cache/apt/archives -type f -delete
Delete the original configuration script
bash
rm -rf /usr/local/bin/ssh_sh.sh
+rm -rf /usr/local/bin/config.sh
+rm -rf /usr/local/bin/ssh_bash.sh
+rm -rf /usr/local/bin/check-dns.sh
+rm -rf /root/ssh_sh.sh
+rm -rf /root/config.sh
+rm -rf /root/ssh_bash.sh
+rm -rf /root/buildone.sh
+rm -rf /root/add_more.sh
+rm -rf /root/build_ipv6_network.sh
Download back the relevant configuration scripts for the new version
bash
wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/check-dns.sh -O /usr/local/bin/check-dns.sh && chmod +x /usr/local/bin/check-dns.sh
+wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/config.sh -O /usr/local/bin/config.sh && chmod +x /usr/local/bin/config.sh
+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.
`,82),t=[l];function p(c,r,i,C,h,y){return a(),n("div",null,t)}const A=s(e,[["render",p]]);export{u as __pageData,A as default};
diff --git a/assets/en_guide_incus_incus_lxc.md.79bae231.lean.js b/assets/en_guide_incus_incus_lxc.md.79bae231.lean.js
new file mode 100644
index 0000000000..af42b13ad2
--- /dev/null
+++ b/assets/en_guide_incus_incus_lxc.md.79bae231.lean.js
@@ -0,0 +1,25 @@
+import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"incus virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/incus/incus_lxc.md","filePath":"en/guide/incus/incus_lxc.md","lastUpdated":1705324601000}'),e={name:"en/guide/incus/incus_lxc.md"},l=o(`
incus 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 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 for customizing the system of the server, do not fill out the default use of debian11 when left blank, note that the incoming parameters for the system name + version number, such as:
  • 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.
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!
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
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
+ls
Normal version batch generation ​
Opened Chick Configuration:
  • 1 core 256MB RAM 1GB hard disk limited to 300Mbit bandwidth
  • With 1 SSH port, 25 extranet ports
  • Default memory and hard disk size
TIP
incus if the command is no problem, the execution of the initialization of the opening of the servers, this step is best to put \`\`\`screen\`\` in the background to suspend the execution of the opening of the servers, the length of time with you to open a few and the mother hen configuration-related
Execute the following command to load the boot script
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/init.sh -o init.sh && chmod +x init.sh && dos2unix init.sh
The following command opens 10 chicks with the name prefix tj.
shell
./init.sh tj 10
Sometimes there is a problem with the path where init.sh is run, in this case it is recommended to add sudo in front of it to force it to run in the root directory
Bulk generation of pure SSH port versions ​
Opened Chick Configuration:
  • 1 core 128MB RAM 300MB hard disk limited to 300Mbit bandwidth
  • Only one SSH port
  • Unable to mount warp
TIP
incus if the command is no problem, the execution of the initialization of the opening of the chick, this step is best to put the \`\`\`screen\`\` in the background to hang the execution of the opening of the chick, the length of time you open the chick with the opening of a few and the mother hen configuration-related
Load boot script
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/least.sh -o least.sh && chmod +x least.sh && dos2unix least.sh
The last line of the following command opens 10 chicks with the chick name prefix tj
shell
./least.sh tj 10
Sometimes there is a problem with the path where last.sh is run, in this case it is recommended to force the root directory to run by adding sudo in front of it.
Custom Batch Generation of Versions ​
  • Customizable memory and hard disk sizes
  • It's also fine if you have manually executed the above batch generation before; the configuration inherits without overwriting
If you need to batch-generate servers multiple times, you can use the following:
Command:
curl -L https://github.com/oneclickvirt/incus/raw/main/scripts/add_more.sh -o add_more.sh && chmod +x add_more.sh && bash add_more.sh
Can be run multiple times to batch generate chicks, and inherit the previous part has been generated in the back to add, customizable memory and hard disk size
View the information of the batch opened chicks ​
After opening the chicks, the specific information will be generated in the log file in the current directory, with the following format
shell
Server_1_Name Password SSH_Port Public_Port_Start Public_Port_End
+Server_2_Name Password SSH_Port Public_Port_Start Public_Port_End
To view it, simply print the log file by executing the following command in the current directory
shell
cat log
WARNING
Don't use the chicks opened by this script as a production environment, incus virtualization doesn't support changing kernel, dd, turning on bbr, etc.
Some common incus commands ​
View all containers:
bash
incus list
View details of a specific container:
bash
incus info container_name
Start a specific container:
bash
incus start container_name
Stop a specific container:
bash
incus stop container_name
Delete a specific container:
bash
incus delete -f container_name
Enter the container's shell:
bash
incus exec container_name /bin/bash
TIP
Instead of /bin/bash, you can use /bin/sh in alpine, which is /bin/bash on regular systems.
To exit, type \`\`\`exit\`\` and enter.
Delete all incus containers
bash
incus list -c n --format csv | xargs -I {} incus delete -f {}
Perform deletion of useless logs within a container
bash
sudo apt-get autoremove
+sudo apt-get clean
+sudo find /var/log -type f -delete
+sudo find /var/tmp -type f -delete
+sudo find /tmp -type f -delete
+sudo find /var/cache/apt/archives -type f -delete
Delete the original configuration script
bash
rm -rf /usr/local/bin/ssh_sh.sh
+rm -rf /usr/local/bin/config.sh
+rm -rf /usr/local/bin/ssh_bash.sh
+rm -rf /usr/local/bin/check-dns.sh
+rm -rf /root/ssh_sh.sh
+rm -rf /root/config.sh
+rm -rf /root/ssh_bash.sh
+rm -rf /root/buildone.sh
+rm -rf /root/add_more.sh
+rm -rf /root/build_ipv6_network.sh
Download back the relevant configuration scripts for the new version
bash
wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/check-dns.sh -O /usr/local/bin/check-dns.sh && chmod +x /usr/local/bin/check-dns.sh
+wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/config.sh -O /usr/local/bin/config.sh && chmod +x /usr/local/bin/config.sh
+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.
`,82),t=[l];function p(c,r,i,C,h,y){return a(),n("div",null,t)}const A=s(e,[["render",p]]);export{u as __pageData,A as default};
diff --git a/assets/en_guide_incus_incus_precheck.md.362061d5.js b/assets/en_guide_incus_incus_precheck.md.362061d5.js
new file mode 100644
index 0000000000..76e3133211
--- /dev/null
+++ b/assets/en_guide_incus_incus_precheck.md.362061d5.js
@@ -0,0 +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":1705324601000}'),a={name:"en/guide/incus/incus_precheck.md"},s=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.
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, Debian can not use zfs automatically switch to another storage type!
  • 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)
',14),r=[s];function i(c,d,h,l,u,p){return t(),n("div",null,r)}const b=e(a,[["render",i]]);export{f as __pageData,b as default};
diff --git a/assets/en_guide_incus_incus_precheck.md.362061d5.lean.js b/assets/en_guide_incus_incus_precheck.md.362061d5.lean.js
new file mode 100644
index 0000000000..76e3133211
--- /dev/null
+++ b/assets/en_guide_incus_incus_precheck.md.362061d5.lean.js
@@ -0,0 +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":1705324601000}'),a={name:"en/guide/incus/incus_precheck.md"},s=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.
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, Debian can not use zfs automatically switch to another storage type!
  • 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)
',14),r=[s];function i(c,d,h,l,u,p){return t(),n("div",null,r)}const b=e(a,[["render",i]]);export{f as __pageData,b as default};
diff --git a/assets/en_guide_incus_incus_qa.md.fbc903cd.js b/assets/en_guide_incus_incus_qa.md.fbc903cd.js
new file mode 100644
index 0000000000..16e268ede3
--- /dev/null
+++ b/assets/en_guide_incus_incus_qa.md.fbc903cd.js
@@ -0,0 +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":1705324601000}'),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
luxvps German AMD Promotions
',14),r=[n];function p(i,d,l,c,h,u){return t(),a("div",null,r)}const v=e(o,[["render",p]]);export{m as __pageData,v as default};
diff --git a/assets/en_guide_incus_incus_qa.md.fbc903cd.lean.js b/assets/en_guide_incus_incus_qa.md.fbc903cd.lean.js
new file mode 100644
index 0000000000..16e268ede3
--- /dev/null
+++ b/assets/en_guide_incus_incus_qa.md.fbc903cd.lean.js
@@ -0,0 +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":1705324601000}'),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
luxvps German AMD Promotions
',14),r=[n];function p(i,d,l,c,h,u){return t(),a("div",null,r)}const v=e(o,[["render",p]]);export{m as __pageData,v as default};
diff --git a/assets/en_guide_incus_incus_thanks.md.89959657.js b/assets/en_guide_incus_incus_thanks.md.89959657.js
new file mode 100644
index 0000000000..8d0b01f438
--- /dev/null
+++ b/assets/en_guide_incus_incus_thanks.md.89959657.js
@@ -0,0 +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":1705324601000}'),s={name:"en/guide/incus/incus_thanks.md"},a=n('
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
',10),o=[a];function i(c,p,l,d,h,u){return e(),r("div",null,o)}const x=t(s,[["render",i]]);export{f as __pageData,x as default};
diff --git a/assets/en_guide_incus_incus_thanks.md.89959657.lean.js b/assets/en_guide_incus_incus_thanks.md.89959657.lean.js
new file mode 100644
index 0000000000..8d0b01f438
--- /dev/null
+++ b/assets/en_guide_incus_incus_thanks.md.89959657.lean.js
@@ -0,0 +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":1705324601000}'),s={name:"en/guide/incus/incus_thanks.md"},a=n('
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
',10),o=[a];function i(c,p,l,d,h,u){return e(),r("div",null,o)}const x=t(s,[["render",i]]);export{f as __pageData,x as default};
diff --git a/assets/en_US_guide_lxd_custom.md.ee41da21.js b/assets/en_guide_lxd_lxd_custom.md.4c6b4986.js
similarity index 86%
rename from assets/en_US_guide_lxd_custom.md.ee41da21.js
rename to assets/en_guide_lxd_lxd_custom.md.4c6b4986.js
index 66143db20f..846db954ac 100644
--- a/assets/en_US_guide_lxd_custom.md.ee41da21.js
+++ b/assets/en_guide_lxd_lxd_custom.md.4c6b4986.js
@@ -1,4 +1,4 @@
-import{_ as e,v as t,b as a,R as s}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Attach free IPV6 address segments to host machines","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/lxd_custom.md","filePath":"en_US/guide/lxd_custom.md","lastUpdated":1704976888000}'),n={name:"en_US/guide/lxd_custom.md"},o=s(`
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 或 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、ipip自定义
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 t,b as a,R as s}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Attach free IPV6 address segments to host machines","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_custom.md","filePath":"en/guide/lxd/lxd_custom.md","lastUpdated":1705324601000}'),n={name:"en/guide/lxd/lxd_custom.md"},o=s(`
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 或 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、ipip自定义
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_US_guide_lxd_custom.md.ee41da21.lean.js b/assets/en_guide_lxd_lxd_custom.md.4c6b4986.lean.js
similarity index 86%
rename from assets/en_US_guide_lxd_custom.md.ee41da21.lean.js
rename to assets/en_guide_lxd_lxd_custom.md.4c6b4986.lean.js
index 66143db20f..846db954ac 100644
--- a/assets/en_US_guide_lxd_custom.md.ee41da21.lean.js
+++ b/assets/en_guide_lxd_lxd_custom.md.4c6b4986.lean.js
@@ -1,4 +1,4 @@
-import{_ as e,v as t,b as a,R as s}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Attach free IPV6 address segments to host machines","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/lxd_custom.md","filePath":"en_US/guide/lxd_custom.md","lastUpdated":1704976888000}'),n={name:"en_US/guide/lxd_custom.md"},o=s(`
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 或 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、ipip自定义
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 t,b as a,R as s}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Attach free IPV6 address segments to host machines","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_custom.md","filePath":"en/guide/lxd/lxd_custom.md","lastUpdated":1705324601000}'),n={name:"en/guide/lxd/lxd_custom.md"},o=s(`
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 或 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、ipip自定义
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_US_guide_lxd_extra_config.md.50b07024.js b/assets/en_guide_lxd_lxd_extra_config.md.1a7780a7.js
similarity index 67%
rename from assets/en_US_guide_lxd_extra_config.md.50b07024.js
rename to assets/en_guide_lxd_lxd_extra_config.md.1a7780a7.js
index 979f27b5ac..0e72ccdf8c 100644
--- a/assets/en_US_guide_lxd_extra_config.md.50b07024.js
+++ b/assets/en_guide_lxd_lxd_extra_config.md.1a7780a7.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Custom Configuration","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/lxd_extra_config.md","filePath":"en_US/guide/lxd_extra_config.md","lastUpdated":1704976888000}'),e={name:"en_US/guide/lxd_extra_config.md"},l=o(`
Custom Configuration ​
TIP
The following configurations may increase the load on the server. Only install them if necessary.
TIP
If you are using the server for personal use, you can ignore the installation of some abuse prevention scripts.
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/spiritLHLS/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 u=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":1705324601000}'),e={name:"en/guide/lxd/lxd_extra_config.md"},l=o(`
Custom Configuration ​
TIP
The following configurations may increase the load on the server. Only install them if necessary.
TIP
If you are using the server for personal use, you can ignore the installation of some abuse prevention scripts.
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/spiritLHLS/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_US_guide_lxd_extra_config.md.50b07024.lean.js b/assets/en_guide_lxd_lxd_extra_config.md.1a7780a7.lean.js
similarity index 67%
rename from assets/en_US_guide_lxd_extra_config.md.50b07024.lean.js
rename to assets/en_guide_lxd_lxd_extra_config.md.1a7780a7.lean.js
index 979f27b5ac..0e72ccdf8c 100644
--- a/assets/en_US_guide_lxd_extra_config.md.50b07024.lean.js
+++ b/assets/en_guide_lxd_lxd_extra_config.md.1a7780a7.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Custom Configuration","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/lxd_extra_config.md","filePath":"en_US/guide/lxd_extra_config.md","lastUpdated":1704976888000}'),e={name:"en_US/guide/lxd_extra_config.md"},l=o(`
Custom Configuration ​
TIP
The following configurations may increase the load on the server. Only install them if necessary.
TIP
If you are using the server for personal use, you can ignore the installation of some abuse prevention scripts.
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/spiritLHLS/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 u=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":1705324601000}'),e={name:"en/guide/lxd/lxd_extra_config.md"},l=o(`
Custom Configuration ​
TIP
The following configurations may increase the load on the server. Only install them if necessary.
TIP
If you are using the server for personal use, you can ignore the installation of some abuse prevention scripts.
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/spiritLHLS/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_US_guide_lxd_install.md.d55489a8.js b/assets/en_guide_lxd_lxd_install.md.e4b63e66.js
similarity index 87%
rename from assets/en_US_guide_lxd_install.md.d55489a8.js
rename to assets/en_guide_lxd_lxd_install.md.e4b63e66.js
index 3d4092df36..811fbac7d7 100644
--- a/assets/en_US_guide_lxd_install.md.d55489a8.js
+++ b/assets/en_guide_lxd_lxd_install.md.e4b63e66.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"LXD Installation Guide","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/lxd_install.md","filePath":"en_US/guide/lxd_install.md","lastUpdated":1704976888000}'),t={name:"en_US/guide/lxd_install.md"},o=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.
Manual Installation ​
Recommended for beginners to avoid potential troubleshooting. However, if you're experienced and comfortable with debugging bugs, you can also use the later one-click installation method for convenience.
Disable Firewall ​
bash
apt update
+import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"LXD Installation Guide","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_install.md","filePath":"en/guide/lxd/lxd_install.md","lastUpdated":1705324601000}'),t={name:"en/guide/lxd/lxd_install.md"},o=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.
Manual Installation ​
Recommended for beginners to avoid potential troubleshooting. However, if you're experienced and comfortable with debugging bugs, you can also use the later one-click installation method for convenience.
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/spiritLHLS/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_US_guide_lxd_install.md.d55489a8.lean.js b/assets/en_guide_lxd_lxd_install.md.e4b63e66.lean.js
similarity index 87%
rename from assets/en_US_guide_lxd_install.md.d55489a8.lean.js
rename to assets/en_guide_lxd_lxd_install.md.e4b63e66.lean.js
index 3d4092df36..811fbac7d7 100644
--- a/assets/en_US_guide_lxd_install.md.d55489a8.lean.js
+++ b/assets/en_guide_lxd_lxd_install.md.e4b63e66.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"LXD Installation Guide","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/lxd_install.md","filePath":"en_US/guide/lxd_install.md","lastUpdated":1704976888000}'),t={name:"en_US/guide/lxd_install.md"},o=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.
Manual Installation ​
Recommended for beginners to avoid potential troubleshooting. However, if you're experienced and comfortable with debugging bugs, you can also use the later one-click installation method for convenience.
Disable Firewall ​
bash
apt update
+import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"LXD Installation Guide","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/lxd/lxd_install.md","filePath":"en/guide/lxd/lxd_install.md","lastUpdated":1705324601000}'),t={name:"en/guide/lxd/lxd_install.md"},o=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.
Manual Installation ​
Recommended for beginners to avoid potential troubleshooting. However, if you're experienced and comfortable with debugging bugs, you can also use the later one-click installation method for convenience.
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/spiritLHLS/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_US_guide_lxd_lxc.md.cb06be90.js b/assets/en_guide_lxd_lxd_lxc.md.0f2f66ff.js
similarity index 76%
rename from assets/en_US_guide_lxd_lxc.md.cb06be90.js
rename to assets/en_guide_lxd_lxd_lxc.md.0f2f66ff.js
index 5901c77836..3cb983985a 100644
--- a/assets/en_US_guide_lxd_lxc.md.cb06be90.js
+++ b/assets/en_guide_lxd_lxd_lxc.md.0f2f66ff.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":"LXC virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/lxd_lxc.md","filePath":"en_US/guide/lxd_lxc.md","lastUpdated":1704976888000}'),e={name:"en_US/guide/lxd_lxc.md"},l=o(`
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/spiritLHLS/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 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 for customizing the system of the server, do not fill out the default use of debian11 when left blank, note that the incoming parameters for the system name + version number, such as:
  • 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.
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!
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
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 o}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":1705324601000}'),e={name:"en/guide/lxd/lxd_lxc.md"},l=o(`
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/spiritLHLS/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 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 for customizing the system of the server, do not fill out the default use of debian11 when left blank, note that the incoming parameters for the system name + version number, such as:
  • 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.
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!
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
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_US_guide_lxd_lxc.md.cb06be90.lean.js b/assets/en_guide_lxd_lxd_lxc.md.0f2f66ff.lean.js
similarity index 76%
rename from assets/en_US_guide_lxd_lxc.md.cb06be90.lean.js
rename to assets/en_guide_lxd_lxd_lxc.md.0f2f66ff.lean.js
index 5901c77836..3cb983985a 100644
--- a/assets/en_US_guide_lxd_lxc.md.cb06be90.lean.js
+++ b/assets/en_guide_lxd_lxd_lxc.md.0f2f66ff.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":"LXC virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/lxd_lxc.md","filePath":"en_US/guide/lxd_lxc.md","lastUpdated":1704976888000}'),e={name:"en_US/guide/lxd_lxc.md"},l=o(`
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/spiritLHLS/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 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 for customizing the system of the server, do not fill out the default use of debian11 when left blank, note that the incoming parameters for the system name + version number, such as:
  • 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.
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!
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
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 o}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":1705324601000}'),e={name:"en/guide/lxd/lxd_lxc.md"},l=o(`
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/spiritLHLS/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 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 for customizing the system of the server, do not fill out the default use of debian11 when left blank, note that the incoming parameters for the system name + version number, such as:
  • 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.
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!
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
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.75ef1b42.js b/assets/en_guide_lxd_lxd_precheck.md.75ef1b42.js
new file mode 100644
index 0000000000..c81b635efe
--- /dev/null
+++ b/assets/en_guide_lxd_lxd_precheck.md.75ef1b42.js
@@ -0,0 +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":1705324601000}'),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.
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, Debian can not use zfs automatically switch to another storage type!
  • 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/spiritLHLS/lxd/main/scripts/pre_check.sh)
',14),s=[r];function i(d,c,h,l,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.75ef1b42.lean.js b/assets/en_guide_lxd_lxd_precheck.md.75ef1b42.lean.js
new file mode 100644
index 0000000000..c81b635efe
--- /dev/null
+++ b/assets/en_guide_lxd_lxd_precheck.md.75ef1b42.lean.js
@@ -0,0 +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":1705324601000}'),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.
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, Debian can not use zfs automatically switch to another storage type!
  • 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/spiritLHLS/lxd/main/scripts/pre_check.sh)
',14),s=[r];function i(d,c,h,l,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.f190e6aa.js b/assets/en_guide_lxd_lxd_qa.md.f190e6aa.js
new file mode 100644
index 0000000000..93c5b16573
--- /dev/null
+++ b/assets/en_guide_lxd_lxd_qa.md.f190e6aa.js
@@ -0,0 +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":1705324601000}'),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
luxvps German AMD Promotions
',19),r=[o];function p(l,i,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.f190e6aa.lean.js b/assets/en_guide_lxd_lxd_qa.md.f190e6aa.lean.js
new file mode 100644
index 0000000000..93c5b16573
--- /dev/null
+++ b/assets/en_guide_lxd_lxd_qa.md.f190e6aa.lean.js
@@ -0,0 +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":1705324601000}'),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
luxvps German AMD Promotions
',19),r=[o];function p(l,i,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.3e4226a6.js b/assets/en_guide_lxd_lxd_thanks.md.3e4226a6.js
new file mode 100644
index 0000000000..6bf09331f7
--- /dev/null
+++ b/assets/en_guide_lxd_lxd_thanks.md.3e4226a6.js
@@ -0,0 +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/lxd/lxd_thanks.md","filePath":"en/guide/lxd/lxd_thanks.md","lastUpdated":1705324601000}'),a={name:"en/guide/lxd/lxd_thanks.md"},s=n('
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
Thank @Ella-Alinda @fscarmen for providing guidance.
',11),o=[s];function i(l,c,p,d,h,u){return e(),r("div",null,o)}const x=t(a,[["render",i]]);export{f as __pageData,x as default};
diff --git a/assets/en_guide_lxd_lxd_thanks.md.3e4226a6.lean.js b/assets/en_guide_lxd_lxd_thanks.md.3e4226a6.lean.js
new file mode 100644
index 0000000000..6bf09331f7
--- /dev/null
+++ b/assets/en_guide_lxd_lxd_thanks.md.3e4226a6.lean.js
@@ -0,0 +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/lxd/lxd_thanks.md","filePath":"en/guide/lxd/lxd_thanks.md","lastUpdated":1705324601000}'),a={name:"en/guide/lxd/lxd_thanks.md"},s=n('
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
Thank @Ella-Alinda @fscarmen for providing guidance.
',11),o=[s];function i(l,c,p,d,h,u){return e(),r("div",null,o)}const x=t(a,[["render",i]]);export{f as __pageData,x as default};
diff --git a/assets/en_US_guide_pve_custom.md.4378da7d.js b/assets/en_guide_pve_pve_custom.md.f7825cb0.js
similarity index 80%
rename from assets/en_US_guide_pve_custom.md.4378da7d.js
rename to assets/en_guide_pve_pve_custom.md.f7825cb0.js
index bd23412a07..54fe20139f 100644
--- a/assets/en_US_guide_pve_custom.md.4378da7d.js
+++ b/assets/en_guide_pve_pve_custom.md.f7825cb0.js
@@ -1,4 +1,4 @@
-import{_ as s,v as e,b as a,R as n}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Some custom scripts","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/pve_custom.md","filePath":"en_US/guide/pve_custom.md","lastUpdated":1704976888000}'),o={name:"en_US/guide/pve_custom.md"},t=n(`
Some custom scripts ​
Each script may have its own system requirements, check them out!
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 n}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Some custom scripts","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_custom.md","filePath":"en/guide/pve/pve_custom.md","lastUpdated":1705324601000}'),o={name:"en/guide/pve/pve_custom.md"},t=n(`
Some custom scripts ​
Each script may have its own system requirements, check them out!
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_US_guide_pve_custom.md.4378da7d.lean.js b/assets/en_guide_pve_pve_custom.md.f7825cb0.lean.js
similarity index 80%
rename from assets/en_US_guide_pve_custom.md.4378da7d.lean.js
rename to assets/en_guide_pve_pve_custom.md.f7825cb0.lean.js
index bd23412a07..54fe20139f 100644
--- a/assets/en_US_guide_pve_custom.md.4378da7d.lean.js
+++ b/assets/en_guide_pve_pve_custom.md.f7825cb0.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as e,b as a,R as n}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Some custom scripts","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/pve_custom.md","filePath":"en_US/guide/pve_custom.md","lastUpdated":1704976888000}'),o={name:"en_US/guide/pve_custom.md"},t=n(`
Some custom scripts ​
Each script may have its own system requirements, check them out!
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 n}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"Some custom scripts","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_custom.md","filePath":"en/guide/pve/pve_custom.md","lastUpdated":1705324601000}'),o={name:"en/guide/pve/pve_custom.md"},t=n(`
Some custom scripts ​
Each script may have its own system requirements, check them out!
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.3bc17d1a.js b/assets/en_guide_pve_pve_install.md.3bc17d1a.js
new file mode 100644
index 0000000000..8d49e57404
--- /dev/null
+++ b/assets/en_guide_pve_pve_install.md.3bc17d1a.js
@@ -0,0 +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":1705324601000}'),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.
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/spiritLHLS/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/spiritLHLS/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.
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
Before executing this command, if the host needs to append the address of the IPV6 tunnel, see the LXD Custom section for appending it to the corresponding file, but please ignore the initial environment modification section for it.
  • 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/spiritLHLS/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.
',31),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.3bc17d1a.lean.js b/assets/en_guide_pve_pve_install.md.3bc17d1a.lean.js
new file mode 100644
index 0000000000..8d49e57404
--- /dev/null
+++ b/assets/en_guide_pve_pve_install.md.3bc17d1a.lean.js
@@ -0,0 +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":1705324601000}'),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.
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/spiritLHLS/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/spiritLHLS/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.
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
Before executing this command, if the host needs to append the address of the IPV6 tunnel, see the LXD Custom section for appending it to the corresponding file, but please ignore the initial environment modification section for it.
  • 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/spiritLHLS/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.
',31),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.39c0b6a3.js b/assets/en_guide_pve_pve_kvm.md.39c0b6a3.js
new file mode 100644
index 0000000000..ef618a7c78
--- /dev/null
+++ b/assets/en_guide_pve_pve_kvm.md.39c0b6a3.js
@@ -0,0 +1,13 @@
+import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"KVM Virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_kvm.md","filePath":"en/guide/pve/pve_kvm.md","lastUpdated":1705324601000}'),n={name:"en/guide/pve/pve_kvm.md"},o=t(`
KVM Virtualization ​
SSH Login Instructions ​
The virtual machines created through KVM virtualization do not have the username root by default. To switch to the root user, you need to execute sudo -i .
Of course, some templates actually allow logging in with the username root, and the default root password is password. You can give it a try.
Once you've logged in via SSH and switched to root privileges, it's crucial to change the root password. You can use the following command to do so.
Command:
bash
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
Partial Notes ​
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.
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.
Considerations for opening a KVM 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 KVM 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
Virtual machines with standalone NAT configuration in KVM virtualization. ​
  • 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/spiritLHLS/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 102 test1 oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
After setup is completed, you can execute cat vm102 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
VMID102
SSH Usernametest1
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
Deletion specific VM ​
  • Stop VM
  • Delete VM
  • Delete port mapping
  • Restart network
  • Delete log files
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 above
shell
./pve_delete.sh 102
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 KVM Virtualization and 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/spiritLHLS/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
+systemctl restart networking.service
+systemctl restart ndpresponder.service
+iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
+iptables-save > /etc/iptables/rules.v4
+rm -rf vmlog
+rm -rf vm*
TIP
Before modifying the VM configuration for PVE, you must shut it down first. After making the configuration changes, start it again to avoid configuration reload errors.
Setting Up Virtual Machines with Dedicated IPv4 Addresses ​
Two versions are available, choose as needed.
Version with Automatic Selection of IPv4 Address (No Manual Specification Required) ​
WARNING
Before use, ensure that the current host machine has at least 2 available IP addresses within its IP range, and there are unallocated IP addresses. These unallocated IP addresses should not be bound to the host machine.
  • Automatically detect available IP ranges. Use ping to identify unallocated IP addresses and select one to bind to the virtual machine.
  • If the host machine has an accompanying IPv6 subnet, there will be an option to attach an IPv6 address.
  • Relevant system information will be stored in the corresponding virtual machine's NOTE section, accessible for viewing on the web interface.
  • 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/spiritLHLS/pve/main/scripts/buildvm_extraip.sh -o buildvm_extraip.sh && chmod +x buildvm_extraip.sh
Meaning of each parameter
shell
./buildvm_extraip.sh VMID Username Password Number_of_CPU_Cores Memory_Size_in_MB Disk_Size_in_GB OS Storage_Disk Attach_IPV6(Default is N)
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_extraip.sh 152 test1 oneclick123 1 1024 10 debian12 local N
The above command is used to create a virtual machine with a dedicated IPv4 address.
AttributeValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
OSdebian12
Storagelocal disk
IPv6 AddonNot attached by default
Version Requiring Manual Specification of IPV4 Address ​
  • Manual specification of IPV4 address with subnet length in the command is required.
  • If the host machine comes with an IPV6 subnet, you can choose whether to add an IPV6 address additionally.
  • If the vendor has provided an IPV4 address and subnet length, please carefully compare and write the parameters in the command format shown below.
  • Relevant system information will be stored in the NOTE of the corresponding virtual machine and can be viewed on the WEB end.
  • 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/spiritLHLS/pve/main/scripts/buildvm_manual_ip.sh -o buildvm_manual_ip.sh && chmod +x buildvm_manual_ip.sh
Meaning of each parameter
shell
./buildvm_manual_ip.sh VMID USERNAME PASSWORD CPU_CORES MEMORY_SIZE_GB STORAGE_SIZE_GB OS STORAGE_DISK IPV4_ADDRESS ATTACH_IPV6(defaults to N)
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_manual_ip.sh 152 test1 oneclick123 1 1024 10 debian12 local a.b.c.d/24 N
The above command is used to create a virtual machine with an independent IPV4 address.
AttributeValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
Operating Systemdebian12
Storage DiskLocal Disk (System Disk)
IPV4 Addressa.b.c.d
Subnet/24 Subnet
IPV6None
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 ​
  • Automatically detect available IPv6 ranges and bind the corresponding V6 address, based on the virtual machine's number, to the virtual machine.
  • System-related information will be stored in the NOTES section of the respective virtual machine, accessible for viewing on the web interface.
Usage Instructions ​
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 test1 oneclick123 1 1024 10 debian12 local
The above command is used to create a virtual machine with only IPv6 addresses.
ParameterValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
Operating Systemdebian12
Storage Disklocal
Delete Example vm152 ​
shell
qm stop 152
+qm destroy 152
+systemctl restart ndpresponder.service
+rm -rf vm152
`,103),l=[o];function p(r,i,c,d,h,C){return a(),e("div",null,l)}const m=s(n,[["render",p]]);export{y as __pageData,m as default};
diff --git a/assets/en_guide_pve_pve_kvm.md.39c0b6a3.lean.js b/assets/en_guide_pve_pve_kvm.md.39c0b6a3.lean.js
new file mode 100644
index 0000000000..ef618a7c78
--- /dev/null
+++ b/assets/en_guide_pve_pve_kvm.md.39c0b6a3.lean.js
@@ -0,0 +1,13 @@
+import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"KVM Virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_kvm.md","filePath":"en/guide/pve/pve_kvm.md","lastUpdated":1705324601000}'),n={name:"en/guide/pve/pve_kvm.md"},o=t(`
KVM Virtualization ​
SSH Login Instructions ​
The virtual machines created through KVM virtualization do not have the username root by default. To switch to the root user, you need to execute sudo -i .
Of course, some templates actually allow logging in with the username root, and the default root password is password. You can give it a try.
Once you've logged in via SSH and switched to root privileges, it's crucial to change the root password. You can use the following command to do so.
Command:
bash
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
Partial Notes ​
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.
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.
Considerations for opening a KVM 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 KVM 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
Virtual machines with standalone NAT configuration in KVM virtualization. ​
  • 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/spiritLHLS/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 102 test1 oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
After setup is completed, you can execute cat vm102 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
VMID102
SSH Usernametest1
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
Deletion specific VM ​
  • Stop VM
  • Delete VM
  • Delete port mapping
  • Restart network
  • Delete log files
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 above
shell
./pve_delete.sh 102
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 KVM Virtualization and 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/spiritLHLS/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
+systemctl restart networking.service
+systemctl restart ndpresponder.service
+iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
+iptables-save > /etc/iptables/rules.v4
+rm -rf vmlog
+rm -rf vm*
TIP
Before modifying the VM configuration for PVE, you must shut it down first. After making the configuration changes, start it again to avoid configuration reload errors.
Setting Up Virtual Machines with Dedicated IPv4 Addresses ​
Two versions are available, choose as needed.
Version with Automatic Selection of IPv4 Address (No Manual Specification Required) ​
WARNING
Before use, ensure that the current host machine has at least 2 available IP addresses within its IP range, and there are unallocated IP addresses. These unallocated IP addresses should not be bound to the host machine.
  • Automatically detect available IP ranges. Use ping to identify unallocated IP addresses and select one to bind to the virtual machine.
  • If the host machine has an accompanying IPv6 subnet, there will be an option to attach an IPv6 address.
  • Relevant system information will be stored in the corresponding virtual machine's NOTE section, accessible for viewing on the web interface.
  • 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/spiritLHLS/pve/main/scripts/buildvm_extraip.sh -o buildvm_extraip.sh && chmod +x buildvm_extraip.sh
Meaning of each parameter
shell
./buildvm_extraip.sh VMID Username Password Number_of_CPU_Cores Memory_Size_in_MB Disk_Size_in_GB OS Storage_Disk Attach_IPV6(Default is N)
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_extraip.sh 152 test1 oneclick123 1 1024 10 debian12 local N
The above command is used to create a virtual machine with a dedicated IPv4 address.
AttributeValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
OSdebian12
Storagelocal disk
IPv6 AddonNot attached by default
Version Requiring Manual Specification of IPV4 Address ​
  • Manual specification of IPV4 address with subnet length in the command is required.
  • If the host machine comes with an IPV6 subnet, you can choose whether to add an IPV6 address additionally.
  • If the vendor has provided an IPV4 address and subnet length, please carefully compare and write the parameters in the command format shown below.
  • Relevant system information will be stored in the NOTE of the corresponding virtual machine and can be viewed on the WEB end.
  • 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/spiritLHLS/pve/main/scripts/buildvm_manual_ip.sh -o buildvm_manual_ip.sh && chmod +x buildvm_manual_ip.sh
Meaning of each parameter
shell
./buildvm_manual_ip.sh VMID USERNAME PASSWORD CPU_CORES MEMORY_SIZE_GB STORAGE_SIZE_GB OS STORAGE_DISK IPV4_ADDRESS ATTACH_IPV6(defaults to N)
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_manual_ip.sh 152 test1 oneclick123 1 1024 10 debian12 local a.b.c.d/24 N
The above command is used to create a virtual machine with an independent IPV4 address.
AttributeValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
Operating Systemdebian12
Storage DiskLocal Disk (System Disk)
IPV4 Addressa.b.c.d
Subnet/24 Subnet
IPV6None
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 ​
  • Automatically detect available IPv6 ranges and bind the corresponding V6 address, based on the virtual machine's number, to the virtual machine.
  • System-related information will be stored in the NOTES section of the respective virtual machine, accessible for viewing on the web interface.
Usage Instructions ​
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 test1 oneclick123 1 1024 10 debian12 local
The above command is used to create a virtual machine with only IPv6 addresses.
ParameterValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
Operating Systemdebian12
Storage Disklocal
Delete Example vm152 ​
shell
qm stop 152
+qm destroy 152
+systemctl restart ndpresponder.service
+rm -rf vm152
`,103),l=[o];function p(r,i,c,d,h,C){return a(),e("div",null,l)}const m=s(n,[["render",p]]);export{y as __pageData,m as default};
diff --git a/assets/en_guide_pve_pve_lxc.md.ff807f3f.js b/assets/en_guide_pve_pve_lxc.md.ff807f3f.js
new file mode 100644
index 0000000000..e080999d4b
--- /dev/null
+++ b/assets/en_guide_pve_pve_lxc.md.ff807f3f.js
@@ -0,0 +1,12 @@
+import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const u=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":1705324601000}'),n={name:"en/guide/pve/pve_lxc.md"},o=t(`
LXC Virtualization ​
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 ​
System Support:
  • debian10, debian11
  • ubuntu18, ubuntu20, ubuntu22
  • centos8, almalinux9
  • Other systems may or may not be supported, please test on your own.
TIP
System parameters are always in lowercase, consisting of the system name concatenated with the version number. For x86_64 systems, you can check available system names and version numbers using pveam available --section system. For ARM systems, you can check supported systems and version numbers at https://mirror.tuna.tsinghua.edu.cn/lxc-images/images/, similar to the version numbers obtained by executing pveam available --section system. (Please note that the parameters used in the script are only lowercase English system names concatenated with version numbers.)
The default username for all CTs is root.
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
After setting up, you can execute cat ct102 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
VMID102
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
Deletion specific CT ​
  • Stop CT
  • Delete CT
  • Delete Port Mapping
  • Restart Network
  • Delete Log Files
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 above
shell
./pve_delete.sh 102
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/spiritLHLS/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
+service networking restart
+systemctl restart networking.service
+systemctl restart ndpresponder.service
+iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
+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 ​
  • Automatically detect available IPv6 ranges and bind the corresponding V6 address based on the container number to the container.
  • Relevant system information will be stored in the NOTES of the corresponding container, accessible for viewing on the web interface.
Download script ​
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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)
Deletion Example ​
shell
rm -rf ct*
+pct stop 152 
+pct destroy 152
+systemctl restart ndpresponder.service
`,53),l=[o];function p(r,i,c,C,d,y){return a(),e("div",null,l)}const D=s(n,[["render",p]]);export{u as __pageData,D as default};
diff --git a/assets/en_guide_pve_pve_lxc.md.ff807f3f.lean.js b/assets/en_guide_pve_pve_lxc.md.ff807f3f.lean.js
new file mode 100644
index 0000000000..e080999d4b
--- /dev/null
+++ b/assets/en_guide_pve_pve_lxc.md.ff807f3f.lean.js
@@ -0,0 +1,12 @@
+import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const u=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":1705324601000}'),n={name:"en/guide/pve/pve_lxc.md"},o=t(`
LXC Virtualization ​
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 ​
System Support:
  • debian10, debian11
  • ubuntu18, ubuntu20, ubuntu22
  • centos8, almalinux9
  • Other systems may or may not be supported, please test on your own.
TIP
System parameters are always in lowercase, consisting of the system name concatenated with the version number. For x86_64 systems, you can check available system names and version numbers using pveam available --section system. For ARM systems, you can check supported systems and version numbers at https://mirror.tuna.tsinghua.edu.cn/lxc-images/images/, similar to the version numbers obtained by executing pveam available --section system. (Please note that the parameters used in the script are only lowercase English system names concatenated with version numbers.)
The default username for all CTs is root.
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
After setting up, you can execute cat ct102 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
VMID102
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
Deletion specific CT ​
  • Stop CT
  • Delete CT
  • Delete Port Mapping
  • Restart Network
  • Delete Log Files
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 above
shell
./pve_delete.sh 102
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/spiritLHLS/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
+service networking restart
+systemctl restart networking.service
+systemctl restart ndpresponder.service
+iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
+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 ​
  • Automatically detect available IPv6 ranges and bind the corresponding V6 address based on the container number to the container.
  • Relevant system information will be stored in the NOTES of the corresponding container, accessible for viewing on the web interface.
Download script ​
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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)
Deletion Example ​
shell
rm -rf ct*
+pct stop 152 
+pct destroy 152
+systemctl restart ndpresponder.service
`,53),l=[o];function p(r,i,c,C,d,y){return a(),e("div",null,l)}const D=s(n,[["render",p]]);export{u as __pageData,D as default};
diff --git a/assets/en_guide_pve_pve_precheck.md.55890001.js b/assets/en_guide_pve_pve_precheck.md.55890001.js
new file mode 100644
index 0000000000..093fab33be
--- /dev/null
+++ b/assets/en_guide_pve_pve_precheck.md.55890001.js
@@ -0,0 +1,3 @@
+import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_precheck.md","filePath":"en/guide/pve/pve_precheck.md","lastUpdated":1705324601000}'),n={name:"en/guide/pve/pve_precheck.md"},o=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.
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 LXD 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) ​
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 ​
  • Before the execution of scripts related to this project, be sure to execute 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.
  • Detecting the IPV6 network configuration of the machine (IPV6 can be installed with or without IPV6, it is just a query).
  • Detect whether the hardware configuration meets the minimum requirements
  • Detect whether the hardware environment can be nested virtualization KVM type of server
  • Detect whether the system environment can nest virtualized KVM-type servers.
  • Can not be nested virtualization KVM type of server can also open LXC virtualization server, but do not recommend installing PVE, rather use LXD
Command:
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/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*


`,25),r=[o];function l(i,p,c,h,u,d){return t(),s("div",null,r)}const C=e(n,[["render",l]]);export{y as __pageData,C as default};
diff --git a/assets/en_guide_pve_pve_precheck.md.55890001.lean.js b/assets/en_guide_pve_pve_precheck.md.55890001.lean.js
new file mode 100644
index 0000000000..093fab33be
--- /dev/null
+++ b/assets/en_guide_pve_pve_precheck.md.55890001.lean.js
@@ -0,0 +1,3 @@
+import{_ as e,v as t,b as s,R as a}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en/guide/pve/pve_precheck.md","filePath":"en/guide/pve/pve_precheck.md","lastUpdated":1705324601000}'),n={name:"en/guide/pve/pve_precheck.md"},o=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.
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 LXD 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) ​
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 ​
  • Before the execution of scripts related to this project, be sure to execute 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.
  • Detecting the IPV6 network configuration of the machine (IPV6 can be installed with or without IPV6, it is just a query).
  • Detect whether the hardware configuration meets the minimum requirements
  • Detect whether the hardware environment can be nested virtualization KVM type of server
  • Detect whether the system environment can nest virtualized KVM-type servers.
  • Can not be nested virtualization KVM type of server can also open LXC virtualization server, but do not recommend installing PVE, rather use LXD
Command:
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/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*


`,25),r=[o];function l(i,p,c,h,u,d){return t(),s("div",null,r)}const C=e(n,[["render",l]]);export{y as __pageData,C as default};
diff --git a/assets/en_US_guide_pve_qa.md.3830e4d7.js b/assets/en_guide_pve_pve_qa.md.193e94d9.js
similarity index 79%
rename from assets/en_US_guide_pve_qa.md.3830e4d7.js
rename to assets/en_guide_pve_pve_qa.md.193e94d9.js
index baa463f903..27c68d2ceb 100644
--- a/assets/en_US_guide_pve_qa.md.3830e4d7.js
+++ b/assets/en_guide_pve_pve_qa.md.193e94d9.js
@@ -1,4 +1,4 @@
-import{_ as e,v as a,b as s,R as t}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Solve the puzzle","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/pve_qa.md","filePath":"en_US/guide/pve_qa.md","lastUpdated":1704976888000}'),n={name:"en_US/guide/pve_qa.md"},o=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!
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)
+import{_ as e,v as a,b as s,R as t}from"./chunks/framework.70afa331.js";const y=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":1705324601000}'),n={name:"en/guide/pve/pve_qa.md"},o=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!
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
     echo "post-up /sbin/ethtool -K $auto_interface tx off rx off" >> /etc/network/interfaces
diff --git a/assets/en_US_guide_pve_qa.md.3830e4d7.lean.js b/assets/en_guide_pve_pve_qa.md.193e94d9.lean.js
similarity index 79%
rename from assets/en_US_guide_pve_qa.md.3830e4d7.lean.js
rename to assets/en_guide_pve_pve_qa.md.193e94d9.lean.js
index baa463f903..27c68d2ceb 100644
--- a/assets/en_US_guide_pve_qa.md.3830e4d7.lean.js
+++ b/assets/en_guide_pve_pve_qa.md.193e94d9.lean.js
@@ -1,4 +1,4 @@
-import{_ as e,v as a,b as s,R as t}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Solve the puzzle","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/pve_qa.md","filePath":"en_US/guide/pve_qa.md","lastUpdated":1704976888000}'),n={name:"en_US/guide/pve_qa.md"},o=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!
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)
+import{_ as e,v as a,b as s,R as t}from"./chunks/framework.70afa331.js";const y=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":1705324601000}'),n={name:"en/guide/pve/pve_qa.md"},o=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!
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
     echo "post-up /sbin/ethtool -K $auto_interface tx off rx off" >> /etc/network/interfaces
diff --git a/assets/en_guide_pve_pve_thanks.md.3ce858ae.js b/assets/en_guide_pve_pve_thanks.md.3ce858ae.js
new file mode 100644
index 0000000000..4bb52ead6d
--- /dev/null
+++ b/assets/en_guide_pve_pve_thanks.md.3ce858ae.js
@@ -0,0 +1 @@
+import{_ as e,v as r,b as t,R as a}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/pve/pve_thanks.md","filePath":"en/guide/pve/pve_thanks.md","lastUpdated":1705324601000}'),o={name:"en/guide/pve/pve_thanks.md"},n=a('
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-Arm64
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.
',15),p=[n];function s(i,h,l,m,c,g){return r(),t("div",null,p)}const d=e(o,[["render",s]]);export{b as __pageData,d as default};
diff --git a/assets/en_guide_pve_pve_thanks.md.3ce858ae.lean.js b/assets/en_guide_pve_pve_thanks.md.3ce858ae.lean.js
new file mode 100644
index 0000000000..4bb52ead6d
--- /dev/null
+++ b/assets/en_guide_pve_pve_thanks.md.3ce858ae.lean.js
@@ -0,0 +1 @@
+import{_ as e,v as r,b as t,R as a}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en/guide/pve/pve_thanks.md","filePath":"en/guide/pve/pve_thanks.md","lastUpdated":1705324601000}'),o={name:"en/guide/pve/pve_thanks.md"},n=a('
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-Arm64
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.
',15),p=[n];function s(i,h,l,m,c,g){return r(),t("div",null,p)}const d=e(o,[["render",s]]);export{b as __pageData,d as default};
diff --git a/assets/en_US_index.md.e266d68d.js b/assets/en_index.md.fc666e9e.js
similarity index 87%
rename from assets/en_US_index.md.e266d68d.js
rename to assets/en_index.md.fc666e9e.js
index ceb90a18ca..a86e2e661a 100644
--- a/assets/en_US_index.md.e266d68d.js
+++ b/assets/en_index.md.fc666e9e.js
@@ -1 +1 @@
-import{_ as e,v as t,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_US/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":"Comes with internal and external port forwarding and automatic IP address assignment","details":"Self-contained internal and external port forwarding and automatic IP address allocation, 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, Android, Windows, 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."}]},"headers":[],"relativePath":"en_US/index.md","filePath":"en_US/index.md","lastUpdated":1704976888000}`),n={name:"en_US/index.md"};function i(s,r,o,l,d,u){return t(),a("div")}const p=e(n,[["render",i]]);export{m as __pageData,p as default};
+import{_ as e,v as t,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_US/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":"Comes with internal and external port forwarding and automatic IP address assignment","details":"Self-contained internal and external port forwarding and automatic IP address allocation, 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, Android, Windows, 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."}]},"headers":[],"relativePath":"en/index.md","filePath":"en/index.md","lastUpdated":1705324601000}`),n={name:"en/index.md"};function i(s,r,o,l,d,u){return t(),a("div")}const p=e(n,[["render",i]]);export{m as __pageData,p as default};
diff --git a/assets/en_US_index.md.e266d68d.lean.js b/assets/en_index.md.fc666e9e.lean.js
similarity index 87%
rename from assets/en_US_index.md.e266d68d.lean.js
rename to assets/en_index.md.fc666e9e.lean.js
index ceb90a18ca..a86e2e661a 100644
--- a/assets/en_US_index.md.e266d68d.lean.js
+++ b/assets/en_index.md.fc666e9e.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,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_US/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":"Comes with internal and external port forwarding and automatic IP address assignment","details":"Self-contained internal and external port forwarding and automatic IP address allocation, 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, Android, Windows, 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."}]},"headers":[],"relativePath":"en_US/index.md","filePath":"en_US/index.md","lastUpdated":1704976888000}`),n={name:"en_US/index.md"};function i(s,r,o,l,d,u){return t(),a("div")}const p=e(n,[["render",i]]);export{m as __pageData,p as default};
+import{_ as e,v as t,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_US/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":"Comes with internal and external port forwarding and automatic IP address assignment","details":"Self-contained internal and external port forwarding and automatic IP address allocation, 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, Android, Windows, 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."}]},"headers":[],"relativePath":"en/index.md","filePath":"en/index.md","lastUpdated":1705324601000}`),n={name:"en/index.md"};function i(s,r,o,l,d,u){return t(),a("div")}const p=e(n,[["render",i]]);export{m as __pageData,p as default};
diff --git a/assets/guide_dashboard.md.7cabee74.js b/assets/guide_dashboard.md.0361b255.js
similarity index 96%
rename from assets/guide_dashboard.md.7cabee74.js
rename to assets/guide_dashboard.md.0361b255.js
index 42c019d562..7b7c4ce770 100644
--- a/assets/guide_dashboard.md.7cabee74.js
+++ b/assets/guide_dashboard.md.0361b255.js
@@ -1 +1 @@
-import{_ as t,v as a,b as e,R as r}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/dashboard.md","filePath":"guide/dashboard.md","lastUpdated":1704976888000}'),o={name:"guide/dashboard.md"},i=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 ​
可开设KVM虚拟化的虚拟机、LXC虚拟化的容器
https://github.com/spiritLHLS/pve
Hits
LXD ​
可开设LXC虚拟化的容器
https://github.com/spiritLHLS/lxd
Hits
Docker ​
可开设Docker虚拟化的容器
https://github.com/spiritLHLS/docker
Hits


',25),s=[i];function p(l,c,h,d,n,m){return a(),e("div",null,s)}const g=t(o,[["render",p]]);export{b as __pageData,g as default};
+import{_ as t,v as a,b as e,R as r}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/dashboard.md","filePath":"guide/dashboard.md","lastUpdated":1705324601000}'),o={name:"guide/dashboard.md"},i=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 ​
可开设KVM虚拟化的虚拟机、LXC虚拟化的容器
https://github.com/spiritLHLS/pve
Hits
LXD ​
可开设LXC虚拟化的容器
https://github.com/spiritLHLS/lxd
Hits
Docker ​
可开设Docker虚拟化的容器
https://github.com/spiritLHLS/docker
Hits


',25),s=[i];function p(l,c,h,d,n,m){return a(),e("div",null,s)}const g=t(o,[["render",p]]);export{b as __pageData,g as default};
diff --git a/assets/guide_dashboard.md.7cabee74.lean.js b/assets/guide_dashboard.md.0361b255.lean.js
similarity index 96%
rename from assets/guide_dashboard.md.7cabee74.lean.js
rename to assets/guide_dashboard.md.0361b255.lean.js
index 42c019d562..7b7c4ce770 100644
--- a/assets/guide_dashboard.md.7cabee74.lean.js
+++ b/assets/guide_dashboard.md.0361b255.lean.js
@@ -1 +1 @@
-import{_ as t,v as a,b as e,R as r}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/dashboard.md","filePath":"guide/dashboard.md","lastUpdated":1704976888000}'),o={name:"guide/dashboard.md"},i=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 ​
可开设KVM虚拟化的虚拟机、LXC虚拟化的容器
https://github.com/spiritLHLS/pve
Hits
LXD ​
可开设LXC虚拟化的容器
https://github.com/spiritLHLS/lxd
Hits
Docker ​
可开设Docker虚拟化的容器
https://github.com/spiritLHLS/docker
Hits


',25),s=[i];function p(l,c,h,d,n,m){return a(),e("div",null,s)}const g=t(o,[["render",p]]);export{b as __pageData,g as default};
+import{_ as t,v as a,b as e,R as r}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/dashboard.md","filePath":"guide/dashboard.md","lastUpdated":1705324601000}'),o={name:"guide/dashboard.md"},i=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 ​
可开设KVM虚拟化的虚拟机、LXC虚拟化的容器
https://github.com/spiritLHLS/pve
Hits
LXD ​
可开设LXC虚拟化的容器
https://github.com/spiritLHLS/lxd
Hits
Docker ​
可开设Docker虚拟化的容器
https://github.com/spiritLHLS/docker
Hits


',25),s=[i];function p(l,c,h,d,n,m){return a(),e("div",null,s)}const g=t(o,[["render",p]]);export{b as __pageData,g as default};
diff --git a/assets/guide_dashboardq.md.2282b44c.js b/assets/guide_dashboardq.md.d66f0669.js
similarity index 92%
rename from assets/guide_dashboardq.md.2282b44c.js
rename to assets/guide_dashboardq.md.d66f0669.js
index d7cff07456..48ccbef1d1 100644
--- a/assets/guide_dashboardq.md.2282b44c.js
+++ b/assets/guide_dashboardq.md.d66f0669.js
@@ -1 +1 @@
-import{_ as a,v as s,b as e,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/dashboardq.md","filePath":"guide/dashboardq.md","lastUpdated":1704976888000}'),o={name:"guide/dashboardq.md"},r=t('
Give me a cup of coffee.
https://ko-fi.com/spiritlhl
USDT-TRC20
bash
TZ7nf8XAL9zQUo63xokazaBdCPeCgPfcwd
',4),p=[r];function d(n,i,c,l,h,f){return s(),e("div",null,p)}const u=a(o,[["render",d]]);export{m as __pageData,u as default};
+import{_ as a,v as s,b as e,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/dashboardq.md","filePath":"guide/dashboardq.md","lastUpdated":1705324601000}'),o={name:"guide/dashboardq.md"},r=t('
Give me a cup of coffee.
https://ko-fi.com/spiritlhl
USDT-TRC20
bash
TZ7nf8XAL9zQUo63xokazaBdCPeCgPfcwd
',4),p=[r];function d(n,i,c,l,h,f){return s(),e("div",null,p)}const u=a(o,[["render",d]]);export{m as __pageData,u as default};
diff --git a/assets/guide_dashboardq.md.2282b44c.lean.js b/assets/guide_dashboardq.md.d66f0669.lean.js
similarity index 92%
rename from assets/guide_dashboardq.md.2282b44c.lean.js
rename to assets/guide_dashboardq.md.d66f0669.lean.js
index d7cff07456..48ccbef1d1 100644
--- a/assets/guide_dashboardq.md.2282b44c.lean.js
+++ b/assets/guide_dashboardq.md.d66f0669.lean.js
@@ -1 +1 @@
-import{_ as a,v as s,b as e,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/dashboardq.md","filePath":"guide/dashboardq.md","lastUpdated":1704976888000}'),o={name:"guide/dashboardq.md"},r=t('
Give me a cup of coffee.
https://ko-fi.com/spiritlhl
USDT-TRC20
bash
TZ7nf8XAL9zQUo63xokazaBdCPeCgPfcwd
',4),p=[r];function d(n,i,c,l,h,f){return s(),e("div",null,p)}const u=a(o,[["render",d]]);export{m as __pageData,u as default};
+import{_ as a,v as s,b as e,R as t}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/dashboardq.md","filePath":"guide/dashboardq.md","lastUpdated":1705324601000}'),o={name:"guide/dashboardq.md"},r=t('
Give me a cup of coffee.
https://ko-fi.com/spiritlhl
USDT-TRC20
bash
TZ7nf8XAL9zQUo63xokazaBdCPeCgPfcwd
',4),p=[r];function d(n,i,c,l,h,f){return s(),e("div",null,p)}const u=a(o,[["render",d]]);export{m as __pageData,u as default};
diff --git a/assets/guide_docker_build.md.161edccd.js b/assets/guide_docker_docker_build.md.a256a541.js
similarity index 73%
rename from assets/guide_docker_build.md.161edccd.js
rename to assets/guide_docker_docker_build.md.a256a541.js
index be8318e58b..f7532097c8 100644
--- a/assets/guide_docker_build.md.161edccd.js
+++ b/assets/guide_docker_docker_build.md.a256a541.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/docker_build.md","filePath":"guide/docker_build.md","lastUpdated":1704976888000}'),o={name:"guide/docker_build.md"},p=n(`
前言 ​
两种开设方式
单独开设 ​
  • 只生成一个docker，这里有判断为国际服务器还是国内服务器，如果在国内服务器上开设，容器内的包管理源自动替换为清华源
  • 可配置绑定独立的IPV6地址，但需要先前使用本套脚本的环境安装命令安装的docker，且需要宿主机至少绑定了/112的IPV6子网
  • 支持x86_64和ARM架构的服务器
下载脚本 ​
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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 l,R as n}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":1705324601000}'),o={name:"guide/docker/docker_build.md"},p=n(`
前言 ​
两种开设方式
单独开设 ​
  • 只生成一个docker，这里有判断为国际服务器还是国内服务器，如果在国内服务器上开设，容器内的包管理源自动替换为清华源
  • 可配置绑定独立的IPV6地址，但需要先前使用本套脚本的环境安装命令安装的docker，且需要宿主机至少绑定了/112的IPV6子网
  • 支持x86_64和ARM架构的服务器
下载脚本 ​
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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_build.md.161edccd.lean.js b/assets/guide_docker_docker_build.md.a256a541.lean.js
similarity index 73%
rename from assets/guide_docker_build.md.161edccd.lean.js
rename to assets/guide_docker_docker_build.md.a256a541.lean.js
index be8318e58b..f7532097c8 100644
--- a/assets/guide_docker_build.md.161edccd.lean.js
+++ b/assets/guide_docker_docker_build.md.a256a541.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/docker_build.md","filePath":"guide/docker_build.md","lastUpdated":1704976888000}'),o={name:"guide/docker_build.md"},p=n(`
前言 ​
两种开设方式
单独开设 ​
  • 只生成一个docker，这里有判断为国际服务器还是国内服务器，如果在国内服务器上开设，容器内的包管理源自动替换为清华源
  • 可配置绑定独立的IPV6地址，但需要先前使用本套脚本的环境安装命令安装的docker，且需要宿主机至少绑定了/112的IPV6子网
  • 支持x86_64和ARM架构的服务器
下载脚本 ​
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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 l,R as n}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":1705324601000}'),o={name:"guide/docker/docker_build.md"},p=n(`
前言 ​
两种开设方式
单独开设 ​
  • 只生成一个docker，这里有判断为国际服务器还是国内服务器，如果在国内服务器上开设，容器内的包管理源自动替换为清华源
  • 可配置绑定独立的IPV6地址，但需要先前使用本套脚本的环境安装命令安装的docker，且需要宿主机至少绑定了/112的IPV6子网
  • 支持x86_64和ARM架构的服务器
下载脚本 ​
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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_custom.md.ca748fd6.js b/assets/guide_docker_docker_custom.md.5e7a28c4.js
similarity index 82%
rename from assets/guide_docker_custom.md.ca748fd6.js
rename to assets/guide_docker_docker_custom.md.5e7a28c4.js
index 58e796d7bc..f3d5893bfb 100644
--- a/assets/guide_docker_custom.md.ca748fd6.js
+++ b/assets/guide_docker_docker_custom.md.5e7a28c4.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as o,R as l}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"使用Docker一键安装某些容器的脚本","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker_custom.md","filePath":"guide/docker_custom.md","lastUpdated":1704976888000}'),n={name:"guide/docker_custom.md"},p=l(`
使用Docker一键安装某些容器的脚本 ​
每个容器都有对应的配置要求，自行查看，内存不够的用这个开设虚拟内存补足也行
注意，以下脚本使用前务必使用本套教程中的环境安装脚本进行前期环境安装
一键开设Android系统的容器 ​
  • 自定义安卓版本
  • 自动创建带校验的web网站
  • 自动进行nginx安装和反向代理的配置，可选择是否绑定域名，默认回车不绑定使用80端口
  • 无需考虑宿主机是否支持嵌套虚拟化
  • 支持x86_64和ARM架构
宿主机的配置至少要有1核2G内存15G硬盘，否则开设可能会导致宿主机卡死
宿主机推荐 Ubuntu 系统，Debian 系统可能导致安卓屏幕白屏
安卓版本越新占用越大，以上的配置要求是最低版本安卓的配置要求 (个人测试到 12.0.0-latest 的tag可用，更高版本映射白屏了，自己测试哪个能用吧)
开设
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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 o,R as l}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"使用Docker一键安装某些容器的脚本","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_custom.md","filePath":"guide/docker/docker_custom.md","lastUpdated":1705324601000}'),n={name:"guide/docker/docker_custom.md"},p=l(`
使用Docker一键安装某些容器的脚本 ​
每个容器都有对应的配置要求，自行查看，内存不够的用这个开设虚拟内存补足也行
注意，以下脚本使用前务必使用本套教程中的环境安装脚本进行前期环境安装
一键开设Android系统的容器 ​
  • 自定义安卓版本
  • 自动创建带校验的web网站
  • 自动进行nginx安装和反向代理的配置，可选择是否绑定域名，默认回车不绑定使用80端口
  • 无需考虑宿主机是否支持嵌套虚拟化
  • 支持x86_64和ARM架构
宿主机的配置至少要有1核2G内存15G硬盘，否则开设可能会导致宿主机卡死
宿主机推荐 Ubuntu 系统，Debian 系统可能导致安卓屏幕白屏
安卓版本越新占用越大，以上的配置要求是最低版本安卓的配置要求 (个人测试到 12.0.0-latest 的tag可用，更高版本映射白屏了，自己测试哪个能用吧)
开设
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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 rm -f scrcpy_web
 docker rmi $(docker images | grep "redroid" | awk '{print $3}')
 rm -rf /etc/nginx/sites-enabled/reverse-proxy
@@ -17,4 +17,4 @@ import{_ as s,v as a,b as o,R as l}from"./chunks/framework.70afa331.js";const A=
 rm -rf /usr/local/bin/config_\${PORT}
 rm -rf /usr/local/bin/password_\${PORT}
 docker rmi lscr.io/linuxserver/chromium
一键开设Desktop的容器 ​
  • 已设置崩溃自启
  • 已设置带中文字体
  • 自带web的校验，可自设置用户名和密码
  • 可自定义容器最大的内存占用
  • 无需考虑是否支持嵌套虚拟化和服务器的架构
  • 支持声音映射，WEB端可传输声音
完整的Linux桌面，可以在上面使用浏览器
宿主机需要至少1核2G内存5G硬盘，开设的容器大小将占用起码3.2G硬盘
开设
开设后默认的用户名是onew，密码是oneclick，默认的内存最大占用是2GB
默认的http协议的web端口是3004，默认的https协议的web端口是3005，开设后打开对应协议的本机IPV4:端口即可
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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
`,113),e=[p];function t(c,r,C,i,y,d){return a(),o("div",null,e)}const h=s(n,[["render",t]]);export{A as __pageData,h as default};
+docker rm -f hbbr
删除对应镜像
shell
docker rmi rustdesk/rustdesk-server
`,113),e=[p];function t(c,r,C,i,d,y){return a(),o("div",null,e)}const h=s(n,[["render",t]]);export{A as __pageData,h as default};
diff --git a/assets/guide_docker_custom.md.ca748fd6.lean.js b/assets/guide_docker_docker_custom.md.5e7a28c4.lean.js
similarity index 82%
rename from assets/guide_docker_custom.md.ca748fd6.lean.js
rename to assets/guide_docker_docker_custom.md.5e7a28c4.lean.js
index 58e796d7bc..f3d5893bfb 100644
--- a/assets/guide_docker_custom.md.ca748fd6.lean.js
+++ b/assets/guide_docker_docker_custom.md.5e7a28c4.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as o,R as l}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"使用Docker一键安装某些容器的脚本","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker_custom.md","filePath":"guide/docker_custom.md","lastUpdated":1704976888000}'),n={name:"guide/docker_custom.md"},p=l(`
使用Docker一键安装某些容器的脚本 ​
每个容器都有对应的配置要求，自行查看，内存不够的用这个开设虚拟内存补足也行
注意，以下脚本使用前务必使用本套教程中的环境安装脚本进行前期环境安装
一键开设Android系统的容器 ​
  • 自定义安卓版本
  • 自动创建带校验的web网站
  • 自动进行nginx安装和反向代理的配置，可选择是否绑定域名，默认回车不绑定使用80端口
  • 无需考虑宿主机是否支持嵌套虚拟化
  • 支持x86_64和ARM架构
宿主机的配置至少要有1核2G内存15G硬盘，否则开设可能会导致宿主机卡死
宿主机推荐 Ubuntu 系统，Debian 系统可能导致安卓屏幕白屏
安卓版本越新占用越大，以上的配置要求是最低版本安卓的配置要求 (个人测试到 12.0.0-latest 的tag可用，更高版本映射白屏了，自己测试哪个能用吧)
开设
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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 o,R as l}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"使用Docker一键安装某些容器的脚本","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker/docker_custom.md","filePath":"guide/docker/docker_custom.md","lastUpdated":1705324601000}'),n={name:"guide/docker/docker_custom.md"},p=l(`
使用Docker一键安装某些容器的脚本 ​
每个容器都有对应的配置要求，自行查看，内存不够的用这个开设虚拟内存补足也行
注意，以下脚本使用前务必使用本套教程中的环境安装脚本进行前期环境安装
一键开设Android系统的容器 ​
  • 自定义安卓版本
  • 自动创建带校验的web网站
  • 自动进行nginx安装和反向代理的配置，可选择是否绑定域名，默认回车不绑定使用80端口
  • 无需考虑宿主机是否支持嵌套虚拟化
  • 支持x86_64和ARM架构
宿主机的配置至少要有1核2G内存15G硬盘，否则开设可能会导致宿主机卡死
宿主机推荐 Ubuntu 系统，Debian 系统可能导致安卓屏幕白屏
安卓版本越新占用越大，以上的配置要求是最低版本安卓的配置要求 (个人测试到 12.0.0-latest 的tag可用，更高版本映射白屏了，自己测试哪个能用吧)
开设
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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 rm -f scrcpy_web
 docker rmi $(docker images | grep "redroid" | awk '{print $3}')
 rm -rf /etc/nginx/sites-enabled/reverse-proxy
@@ -17,4 +17,4 @@ import{_ as s,v as a,b as o,R as l}from"./chunks/framework.70afa331.js";const A=
 rm -rf /usr/local/bin/config_\${PORT}
 rm -rf /usr/local/bin/password_\${PORT}
 docker rmi lscr.io/linuxserver/chromium
一键开设Desktop的容器 ​
  • 已设置崩溃自启
  • 已设置带中文字体
  • 自带web的校验，可自设置用户名和密码
  • 可自定义容器最大的内存占用
  • 无需考虑是否支持嵌套虚拟化和服务器的架构
  • 支持声音映射，WEB端可传输声音
完整的Linux桌面，可以在上面使用浏览器
宿主机需要至少1核2G内存5G硬盘，开设的容器大小将占用起码3.2G硬盘
开设
开设后默认的用户名是onew，密码是oneclick，默认的内存最大占用是2GB
默认的http协议的web端口是3004，默认的https协议的web端口是3005，开设后打开对应协议的本机IPV4:端口即可
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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
`,113),e=[p];function t(c,r,C,i,y,d){return a(),o("div",null,e)}const h=s(n,[["render",t]]);export{A as __pageData,h as default};
+docker rm -f hbbr
删除对应镜像
shell
docker rmi rustdesk/rustdesk-server
`,113),e=[p];function t(c,r,C,i,d,y){return a(),o("div",null,e)}const h=s(n,[["render",t]]);export{A as __pageData,h as default};
diff --git a/assets/guide_docker_docker_install.md.f64d4c9b.js b/assets/guide_docker_docker_install.md.f64d4c9b.js
new file mode 100644
index 0000000000..84a71f084f
--- /dev/null
+++ b/assets/guide_docker_docker_install.md.f64d4c9b.js
@@ -0,0 +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":1705324601000}'),o={name:"guide/docker/docker_install.md"},n=p('
前言 ​
支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的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/spiritLHLS/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/spiritLHLS/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.f64d4c9b.lean.js b/assets/guide_docker_docker_install.md.f64d4c9b.lean.js
new file mode 100644
index 0000000000..84a71f084f
--- /dev/null
+++ b/assets/guide_docker_docker_install.md.f64d4c9b.lean.js
@@ -0,0 +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":1705324601000}'),o={name:"guide/docker/docker_install.md"},n=p('
前言 ​
支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的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/spiritLHLS/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/spiritLHLS/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_precheck.md.42735fec.js b/assets/guide_docker_docker_precheck.md.42735fec.js
new file mode 100644
index 0000000000..11fe2d1350
--- /dev/null
+++ b/assets/guide_docker_docker_precheck.md.42735fec.js
@@ -0,0 +1 @@
+import{_ as e,v as o,b as a,R as r}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":1705324601000}'),c={name:"guide/docker/docker_precheck.md"},t=r('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
WARNING
如果宿主机带IPV6网络的话，安装会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
项目特点 ​
通过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虚拟内存，避免突发的内存占用导致宿主机卡死
',16),d=[t];function s(p,i,n,l,h,k){return o(),a("div",null,d)}const P=e(c,[["render",s]]);export{_ as __pageData,P as default};
diff --git a/assets/guide_docker_docker_precheck.md.42735fec.lean.js b/assets/guide_docker_docker_precheck.md.42735fec.lean.js
new file mode 100644
index 0000000000..11fe2d1350
--- /dev/null
+++ b/assets/guide_docker_docker_precheck.md.42735fec.lean.js
@@ -0,0 +1 @@
+import{_ as e,v as o,b as a,R as r}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":1705324601000}'),c={name:"guide/docker/docker_precheck.md"},t=r('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
WARNING
如果宿主机带IPV6网络的话，安装会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
项目特点 ​
通过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虚拟内存，避免突发的内存占用导致宿主机卡死
',16),d=[t];function s(p,i,n,l,h,k){return o(),a("div",null,d)}const P=e(c,[["render",s]]);export{_ as __pageData,P as default};
diff --git a/assets/guide_docker_docker_qa.md.3ff7d1a4.js b/assets/guide_docker_docker_qa.md.3ff7d1a4.js
new file mode 100644
index 0000000000..cd47983683
--- /dev/null
+++ b/assets/guide_docker_docker_qa.md.3ff7d1a4.js
@@ -0,0 +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":1705324601000}'),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.3ff7d1a4.lean.js b/assets/guide_docker_docker_qa.md.3ff7d1a4.lean.js
new file mode 100644
index 0000000000..cd47983683
--- /dev/null
+++ b/assets/guide_docker_docker_qa.md.3ff7d1a4.lean.js
@@ -0,0 +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":1705324601000}'),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.f8648a64.js b/assets/guide_docker_docker_thanks.md.f8648a64.js
new file mode 100644
index 0000000000..4c008e50fb
--- /dev/null
+++ b/assets/guide_docker_docker_thanks.md.f8648a64.js
@@ -0,0 +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":1705324601000}'),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://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指导
',20),h=[n];function p(c,i,s,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.f8648a64.lean.js b/assets/guide_docker_docker_thanks.md.f8648a64.lean.js
new file mode 100644
index 0000000000..4c008e50fb
--- /dev/null
+++ b/assets/guide_docker_docker_thanks.md.f8648a64.lean.js
@@ -0,0 +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":1705324601000}'),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://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指导
',20),h=[n];function p(c,i,s,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_install.md.2bb5440f.js b/assets/guide_docker_install.md.2bb5440f.js
deleted file mode 100644
index 792a86ccce..0000000000
--- a/assets/guide_docker_install.md.2bb5440f.js
+++ /dev/null
@@ -1 +0,0 @@
-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_install.md","filePath":"guide/docker_install.md","lastUpdated":1704976888000}'),o={name:"guide/docker_install.md"},n=p('
前言 ​
支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的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/spiritLHLS/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/spiritLHLS/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_install.md.2bb5440f.lean.js b/assets/guide_docker_install.md.2bb5440f.lean.js
deleted file mode 100644
index 792a86ccce..0000000000
--- a/assets/guide_docker_install.md.2bb5440f.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-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_install.md","filePath":"guide/docker_install.md","lastUpdated":1704976888000}'),o={name:"guide/docker_install.md"},n=p('
前言 ​
支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的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/spiritLHLS/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/spiritLHLS/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_precheck.md.19d5f683.js b/assets/guide_docker_precheck.md.19d5f683.js
deleted file mode 100644
index c2820c53ac..0000000000
--- a/assets/guide_docker_precheck.md.19d5f683.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as e,v as a,b as o,R as r}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker_precheck.md","filePath":"guide/docker_precheck.md","lastUpdated":1704976888000}'),t={name:"guide/docker_precheck.md"},c=r('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
WARNING
如果宿主机带IPV6网络的话，安装会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
项目特点 ​
通过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虚拟内存，避免突发的内存占用导致宿主机卡死
',16),d=[c];function s(p,i,n,l,h,k){return a(),o("div",null,d)}const P=e(t,[["render",s]]);export{_ as __pageData,P as default};
diff --git a/assets/guide_docker_precheck.md.19d5f683.lean.js b/assets/guide_docker_precheck.md.19d5f683.lean.js
deleted file mode 100644
index c2820c53ac..0000000000
--- a/assets/guide_docker_precheck.md.19d5f683.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as e,v as a,b as o,R as r}from"./chunks/framework.70afa331.js";const _=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker_precheck.md","filePath":"guide/docker_precheck.md","lastUpdated":1704976888000}'),t={name:"guide/docker_precheck.md"},c=r('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
WARNING
如果宿主机带IPV6网络的话，安装会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
项目特点 ​
通过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虚拟内存，避免突发的内存占用导致宿主机卡死
',16),d=[c];function s(p,i,n,l,h,k){return a(),o("div",null,d)}const P=e(t,[["render",s]]);export{_ as __pageData,P as default};
diff --git a/assets/guide_docker_qa.md.0ed3b81c.js b/assets/guide_docker_qa.md.0ed3b81c.js
deleted file mode 100644
index d236928182..0000000000
--- a/assets/guide_docker_qa.md.0ed3b81c.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as a,v as s,b as e,R as l}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker_qa.md","filePath":"guide/docker_qa.md","lastUpdated":1704976888000}'),n={name:"guide/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),t=[p];function o(c,i,d,r,g,h){return s(),e("div",null,t)}const m=a(n,[["render",o]]);export{C as __pageData,m as default};
diff --git a/assets/guide_docker_qa.md.0ed3b81c.lean.js b/assets/guide_docker_qa.md.0ed3b81c.lean.js
deleted file mode 100644
index d236928182..0000000000
--- a/assets/guide_docker_qa.md.0ed3b81c.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as a,v as s,b as e,R as l}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker_qa.md","filePath":"guide/docker_qa.md","lastUpdated":1704976888000}'),n={name:"guide/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),t=[p];function o(c,i,d,r,g,h){return s(),e("div",null,t)}const m=a(n,[["render",o]]);export{C as __pageData,m as default};
diff --git a/assets/guide_docker_thanks.md.0eedda24.js b/assets/guide_docker_thanks.md.0eedda24.js
deleted file mode 100644
index 85cbfcc79b..0000000000
--- a/assets/guide_docker_thanks.md.0eedda24.js
+++ /dev/null
@@ -1 +0,0 @@
-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_thanks.md","filePath":"guide/docker_thanks.md","lastUpdated":1704976888000}'),o={name:"guide/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://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指导
',20),h=[n];function p(i,s,c,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_thanks.md.0eedda24.lean.js b/assets/guide_docker_thanks.md.0eedda24.lean.js
deleted file mode 100644
index 85cbfcc79b..0000000000
--- a/assets/guide_docker_thanks.md.0eedda24.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-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_thanks.md","filePath":"guide/docker_thanks.md","lastUpdated":1704976888000}'),o={name:"guide/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://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指导
',20),h=[n];function p(i,s,c,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_incus_incus_custom.md.2a6371c0.js b/assets/guide_incus_incus_custom.md.2a6371c0.js
new file mode 100644
index 0000000000..a164cc5bb0
--- /dev/null
+++ b/assets/guide_incus_incus_custom.md.2a6371c0.js
@@ -0,0 +1,27 @@
+import{_ as t,v as e,b as s,R as a}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"给宿主机附加免费的IPV6地址段","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_custom.md","filePath":"guide/incus/incus_custom.md","lastUpdated":1705324601000}'),n={name:"guide/incus/incus_custom.md"},l=a(`
给宿主机附加免费的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
+# systemctl disable systemd-networkd.socket
如果需要安装的是ifupdown控制网络，这个工具一般的主流linux系统都有
apt-get install ifupdown -y
如果需要安装的是ifupdown2进行网络管理，而这个工具一般只在debian系上可安装使用
apt-get install ifupdown2 -y
安装完毕后，安装了哪个包后面就选择哪个包进行格式转换。
systemctl start networking
+systemctl enable networking
然后重启服务器，检验机器的网络是否会因为修改出现重启失联的情况，且执行uptime观察启动已超过1分钟后，再进行后续步骤
如果是是前者inactive，后者active，则不需要切换网络管理程序，直接进行后续操作即可。
由于部分服务器存在默认的内网IPV6路由会与隧道冲突，此时可使用以下命令删除默认的IPV6路由
default_route=$(ip -6 route show | awk '/default via/{print $3}') && [ -n "$default_route" ] && ip -6 route del default via $default_route dev eth0
这里假设了你的客户端的服务器的默认网卡是eth0，你可以使用ip -6 route查看默认的路由并替换它，默认路由以default via开头，使用dev指定默认网卡，你只需要按照这个规则找到它即可
tunnelbroker_net ​
结合一键开设带IPV6地址的容器的脚本，就能给每个容器附加来自he的IPV6地址了
缺点是地址比较黑/脏，cloudflare的cdn极有可能套不上，自行测试
  1. 在 https://tunnelbroker.net/ 注册账户，并点击左边的 Create Regular Tunnel
1
  1. 红框处填写你的服务器的IPV4地址，选择物理距离近的连接点，比如机器在美国洛杉矶，就选美国西海岸的连接点，然后显示绿框提示，点Create Tunnel创建即可
2
3
4
  1. 等待出以下界面，点击Example Configurations然后选择对应的系统，比如incus的宿主机那肯定就是Debian/Ubuntu了
5
6
  1. 框住的部分就是要修改的文件和需要复制的内容了
7
复制的时候不要带空行
  1. 转换格式后给你的网络配置文件附加IPV6的设置
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为TunnelBrokerNet，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式，等待页面刷新显示转换格式后的配置文件内容
然后用vim或者vi命令修改/etc/network/interfaces文件增加内容，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改复制粘贴一下转换格式后的配置文件内容，然后执行此命令
+EOF
然后你可以使用cat /etc/network/interfaces查看配置文件是否正常写入了
  1. 如果上面都没问题，就需要启用网络接口即可
apt-get install net-tools iproute2 -y
+systemctl restart networking
  1. 然后你就可以测试IPV6网络是否已附加
执行ifconfig命令，这时应该有一个 he-ipv6 接口，类似下面这样：
8
或者执行：
curl ipv6.ip.sb
回传你绑定IPV6地址
  1. NAT VPS 的额外设置
IPv4 NAT VPS 除了前面提到的替换 IP 操作以外，可能还需要一些额外的设置，否则可能还是无法访问 IPv6 网络。
apt-get install ufw -y
+ufw allow 41
添加相关的路由规则
route -A inet6 add ::/0 dev he-ipv6
  1. 如果不需要该IPV6网络了，想要删除
删除 he-ipv6 网络接口配置（若没有删除重启后会自动启用），记得修改/etc/network/interfaces文件，删除之前红框添加的内容
然后重启服务器，就删除了
tunnelbroker_ch ​
类似上述的操作，先在 https://www.tunnelbroker.ch/ 注册一个账户先，注册后点击激活的邮件
然后就是填写你的服务器IPV4地址
创建后需要进入Config页面而不是详情页面
见到以下页面千万别使用，先刷新一下本页面，不要弹那个浅蓝色框后再停止刷新
记录以下页面的最后一个红框的内容，准备修改宿主机配置文件
页面的最后一个红框框住的部分复制下来，不要带空行
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为TunnelBrokerCh，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式，等待页面刷新显示转换格式后的配置文件内容
然后用vim或者vi命令修改/etc/network/interfaces文件增加内容，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改一下
+EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
+systemctl restart networking
保证环境无问题再进行别的操作了
ip4market_ru ​
类似上述的操作，先在 https://tb.ip4market.ru 注册一个账户先，注册邮箱得是非常见邮箱，电话可随便写不验证的，IP填上你要附加的宿主机的IPV4地址
然后就是过Recaptcha的人机验证，点击注册
邮箱会收到激活邮件，里面附带有你的密码，记住它
然后在首页进行登录
然后就会进入这个页面
按住右键，然后复制红框框住的四行内容，也就是
Server IPv4:
+Client IPv4
+Server IPv6
+Client IPv6
这四行内容，按ctrl+c复制或者右键复制
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为ip4market，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式
然后就会自动刷新页面出现需要自己用vim或者vi命令修改/etc/network/interfaces文件增加的内容了，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改一下
+EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
+systemctl restart networking
保证环境无问题再进行别的操作了
netassist_ua ​
这个平台你在切换网络管理时务必使用ifupdown2而不是ifupdown2安装包，该平台使用sit协议，而sit协议需要在ifupdown2控制的环境中使用
类似上述的操作，先在 https://tb.netassist.ua/ 注册一个账户先，注册后点击激活的邮件，激活页面会有密码显示，记得记录
然后就是填写你的服务器IPV4地址，这个后面可以自己修改，先随便填一个都没问题
然后就到了这个页面了
a
第一个红框是你宿主机的IPV4地址需要填写的位置，要修改就修改那里，然后点change保存
第二个下拉红框选择Linux，然后点击show
b
会出现上面的内容，全选框住的部分复制下来，不要带空行
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为NetAssist，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式
c
然后就会自动刷新页面出现需要自己用vim或者vi命令修改/etc/network/interfaces文件增加的内容了，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改一下
+EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
+systemctl restart networking
保证环境无问题再进行别的操作了
转移不同服务器之间的IPV6子网 ​
相关仓库：https://github.com/oneclickvirt/6in4
该方法将提供一种方式，将A上的IPV6网段拆分一个子ipv6网段的出来，附加到B上使用
你需要在B所在的服务器上使用本套脚本给容器一键配置IPV6地址
功能 ​
  • 自建sit/gre/ipip协议的IPv6隧道
  • 支持自定义要切分出来的IPV6子网大小，将自动计算出合适的CIDR格式的IPV6子网信息
  • 自动识别服务端的IPV6子网大小
  • 将自动设置隧道服务端并打印客户端需要执行的命令
  • 设置IPV6隧道的方法简单易懂，易于删除
环境准备 ​
VPS(A)VPS(B)
一个IPV4地址(server_ipv4)一个IPV4地址(clinet_ipv4)
一个IPV6子网无IPV6地址
以下称之为服务端以下称之为客户端
使用方法 ​
下载脚本
curl -L https://raw.githubusercontent.com/oneclickvirt/6in4/main/6in4.sh -o 6in4.sh && chmod +x 6in4.sh
执行命令
./6in4.sh client_ipv4 <mode_type> <subnet_size>
选项可选的选项1可选的选项2可选的选项3
<mode_type>gresitipip
<subnet_size>6480112
<mode_type>暂时只支持那三种协议，越靠前的越推荐，不填则默认为sit协议
<subnet_size>只要比原系统子网掩码大就行，且是8的倍数，不填则默认为80
记得client_ipv4替换为需要附加IPV6的机器的IPV4地址，执行完毕后会回传你需要在客户端执行的命令，详见执行后的说明即可
为防止忘记复制命令，命令本身也将写入到当前路径下的6in4.log文件中，可使用cat 6in4.log查询客户端需要执行的命令
复制下来的命令，务必在 https://ipv6tunnel.spiritlhl.top/ 中选择选项6in4后进行转换
然后就会自动刷新页面出现需要自己用vim或者vi命令修改/etc/network/interfaces文件增加的内容了，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改一下
+EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
+systemctl restart networking
保证环境无问题再进行别的操作了
检测服务端 ​
systemctl status ndpresponder
ip addr show
检测客户端 ​
ip addr show
curl ipv6.ip.sb
删除隧道 ​
服务端
ip link set server-ipv6 down
+ip tunnel del server-ipv6
客户端
ip link set user-ipv6 down
+ip tunnel del user-ipv6
以上删除的方式只是临时删除，永久删除务必修改删除/etc/network/interfaces文件中你之前增加的内容
后言 ​
实际上 https://tunnelbroker.net/ 支持申请/48大小的IPV6子网，只需要在
图片
这里进行申请，然后转换格式的时候将原先/64的IPV6地址改成/48的IPV6地址，你就能获得一个更大的IPV6子网了
`,163),p=[l];function i(o,c,r,d,h,u){return e(),s("div",null,p)}const C=t(n,[["render",i]]);export{b as __pageData,C as default};
diff --git a/assets/guide_incus_incus_custom.md.2a6371c0.lean.js b/assets/guide_incus_incus_custom.md.2a6371c0.lean.js
new file mode 100644
index 0000000000..a164cc5bb0
--- /dev/null
+++ b/assets/guide_incus_incus_custom.md.2a6371c0.lean.js
@@ -0,0 +1,27 @@
+import{_ as t,v as e,b as s,R as a}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"给宿主机附加免费的IPV6地址段","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_custom.md","filePath":"guide/incus/incus_custom.md","lastUpdated":1705324601000}'),n={name:"guide/incus/incus_custom.md"},l=a(`
给宿主机附加免费的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
+# systemctl disable systemd-networkd.socket
如果需要安装的是ifupdown控制网络，这个工具一般的主流linux系统都有
apt-get install ifupdown -y
如果需要安装的是ifupdown2进行网络管理，而这个工具一般只在debian系上可安装使用
apt-get install ifupdown2 -y
安装完毕后，安装了哪个包后面就选择哪个包进行格式转换。
systemctl start networking
+systemctl enable networking
然后重启服务器，检验机器的网络是否会因为修改出现重启失联的情况，且执行uptime观察启动已超过1分钟后，再进行后续步骤
如果是是前者inactive，后者active，则不需要切换网络管理程序，直接进行后续操作即可。
由于部分服务器存在默认的内网IPV6路由会与隧道冲突，此时可使用以下命令删除默认的IPV6路由
default_route=$(ip -6 route show | awk '/default via/{print $3}') && [ -n "$default_route" ] && ip -6 route del default via $default_route dev eth0
这里假设了你的客户端的服务器的默认网卡是eth0，你可以使用ip -6 route查看默认的路由并替换它，默认路由以default via开头，使用dev指定默认网卡，你只需要按照这个规则找到它即可
tunnelbroker_net ​
结合一键开设带IPV6地址的容器的脚本，就能给每个容器附加来自he的IPV6地址了
缺点是地址比较黑/脏，cloudflare的cdn极有可能套不上，自行测试
  1. 在 https://tunnelbroker.net/ 注册账户，并点击左边的 Create Regular Tunnel
1
  1. 红框处填写你的服务器的IPV4地址，选择物理距离近的连接点，比如机器在美国洛杉矶，就选美国西海岸的连接点，然后显示绿框提示，点Create Tunnel创建即可
2
3
4
  1. 等待出以下界面，点击Example Configurations然后选择对应的系统，比如incus的宿主机那肯定就是Debian/Ubuntu了
5
6
  1. 框住的部分就是要修改的文件和需要复制的内容了
7
复制的时候不要带空行
  1. 转换格式后给你的网络配置文件附加IPV6的设置
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为TunnelBrokerNet，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式，等待页面刷新显示转换格式后的配置文件内容
然后用vim或者vi命令修改/etc/network/interfaces文件增加内容，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改复制粘贴一下转换格式后的配置文件内容，然后执行此命令
+EOF
然后你可以使用cat /etc/network/interfaces查看配置文件是否正常写入了
  1. 如果上面都没问题，就需要启用网络接口即可
apt-get install net-tools iproute2 -y
+systemctl restart networking
  1. 然后你就可以测试IPV6网络是否已附加
执行ifconfig命令，这时应该有一个 he-ipv6 接口，类似下面这样：
8
或者执行：
curl ipv6.ip.sb
回传你绑定IPV6地址
  1. NAT VPS 的额外设置
IPv4 NAT VPS 除了前面提到的替换 IP 操作以外，可能还需要一些额外的设置，否则可能还是无法访问 IPv6 网络。
apt-get install ufw -y
+ufw allow 41
添加相关的路由规则
route -A inet6 add ::/0 dev he-ipv6
  1. 如果不需要该IPV6网络了，想要删除
删除 he-ipv6 网络接口配置（若没有删除重启后会自动启用），记得修改/etc/network/interfaces文件，删除之前红框添加的内容
然后重启服务器，就删除了
tunnelbroker_ch ​
类似上述的操作，先在 https://www.tunnelbroker.ch/ 注册一个账户先，注册后点击激活的邮件
然后就是填写你的服务器IPV4地址
创建后需要进入Config页面而不是详情页面
见到以下页面千万别使用，先刷新一下本页面，不要弹那个浅蓝色框后再停止刷新
记录以下页面的最后一个红框的内容，准备修改宿主机配置文件
页面的最后一个红框框住的部分复制下来，不要带空行
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为TunnelBrokerCh，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式，等待页面刷新显示转换格式后的配置文件内容
然后用vim或者vi命令修改/etc/network/interfaces文件增加内容，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改一下
+EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
+systemctl restart networking
保证环境无问题再进行别的操作了
ip4market_ru ​
类似上述的操作，先在 https://tb.ip4market.ru 注册一个账户先，注册邮箱得是非常见邮箱，电话可随便写不验证的，IP填上你要附加的宿主机的IPV4地址
然后就是过Recaptcha的人机验证，点击注册
邮箱会收到激活邮件，里面附带有你的密码，记住它
然后在首页进行登录
然后就会进入这个页面
按住右键，然后复制红框框住的四行内容，也就是
Server IPv4:
+Client IPv4
+Server IPv6
+Client IPv6
这四行内容，按ctrl+c复制或者右键复制
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为ip4market，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式
然后就会自动刷新页面出现需要自己用vim或者vi命令修改/etc/network/interfaces文件增加的内容了，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改一下
+EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
+systemctl restart networking
保证环境无问题再进行别的操作了
netassist_ua ​
这个平台你在切换网络管理时务必使用ifupdown2而不是ifupdown2安装包，该平台使用sit协议，而sit协议需要在ifupdown2控制的环境中使用
类似上述的操作，先在 https://tb.netassist.ua/ 注册一个账户先，注册后点击激活的邮件，激活页面会有密码显示，记得记录
然后就是填写你的服务器IPV4地址，这个后面可以自己修改，先随便填一个都没问题
然后就到了这个页面了
a
第一个红框是你宿主机的IPV4地址需要填写的位置，要修改就修改那里，然后点change保存
第二个下拉红框选择Linux，然后点击show
b
会出现上面的内容，全选框住的部分复制下来，不要带空行
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为NetAssist，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式
c
然后就会自动刷新页面出现需要自己用vim或者vi命令修改/etc/network/interfaces文件增加的内容了，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改一下
+EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
+systemctl restart networking
保证环境无问题再进行别的操作了
转移不同服务器之间的IPV6子网 ​
相关仓库：https://github.com/oneclickvirt/6in4
该方法将提供一种方式，将A上的IPV6网段拆分一个子ipv6网段的出来，附加到B上使用
你需要在B所在的服务器上使用本套脚本给容器一键配置IPV6地址
功能 ​
  • 自建sit/gre/ipip协议的IPv6隧道
  • 支持自定义要切分出来的IPV6子网大小，将自动计算出合适的CIDR格式的IPV6子网信息
  • 自动识别服务端的IPV6子网大小
  • 将自动设置隧道服务端并打印客户端需要执行的命令
  • 设置IPV6隧道的方法简单易懂，易于删除
环境准备 ​
VPS(A)VPS(B)
一个IPV4地址(server_ipv4)一个IPV4地址(clinet_ipv4)
一个IPV6子网无IPV6地址
以下称之为服务端以下称之为客户端
使用方法 ​
下载脚本
curl -L https://raw.githubusercontent.com/oneclickvirt/6in4/main/6in4.sh -o 6in4.sh && chmod +x 6in4.sh
执行命令
./6in4.sh client_ipv4 <mode_type> <subnet_size>
选项可选的选项1可选的选项2可选的选项3
<mode_type>gresitipip
<subnet_size>6480112
<mode_type>暂时只支持那三种协议，越靠前的越推荐，不填则默认为sit协议
<subnet_size>只要比原系统子网掩码大就行，且是8的倍数，不填则默认为80
记得client_ipv4替换为需要附加IPV6的机器的IPV4地址，执行完毕后会回传你需要在客户端执行的命令，详见执行后的说明即可
为防止忘记复制命令，命令本身也将写入到当前路径下的6in4.log文件中，可使用cat 6in4.log查询客户端需要执行的命令
复制下来的命令，务必在 https://ipv6tunnel.spiritlhl.top/ 中选择选项6in4后进行转换
然后就会自动刷新页面出现需要自己用vim或者vi命令修改/etc/network/interfaces文件增加的内容了，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改一下
+EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
+systemctl restart networking
保证环境无问题再进行别的操作了
检测服务端 ​
systemctl status ndpresponder
ip addr show
检测客户端 ​
ip addr show
curl ipv6.ip.sb
删除隧道 ​
服务端
ip link set server-ipv6 down
+ip tunnel del server-ipv6
客户端
ip link set user-ipv6 down
+ip tunnel del user-ipv6
以上删除的方式只是临时删除，永久删除务必修改删除/etc/network/interfaces文件中你之前增加的内容
后言 ​
实际上 https://tunnelbroker.net/ 支持申请/48大小的IPV6子网，只需要在
图片
这里进行申请，然后转换格式的时候将原先/64的IPV6地址改成/48的IPV6地址，你就能获得一个更大的IPV6子网了
`,163),p=[l];function i(o,c,r,d,h,u){return e(),s("div",null,p)}const C=t(n,[["render",i]]);export{b as __pageData,C as default};
diff --git a/assets/guide_incus_incus_extra_config.md.b96ae35d.js b/assets/guide_incus_incus_extra_config.md.b96ae35d.js
new file mode 100644
index 0000000000..de161a612a
--- /dev/null
+++ b/assets/guide_incus_incus_extra_config.md.b96ae35d.js
@@ -0,0 +1,12 @@
+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":"guide/incus/incus_extra_config.md","filePath":"guide/incus/incus_extra_config.md","lastUpdated":1705324601000}'),p={name:"guide/incus/incus_extra_config.md"},o=n(`
其他自定义配置 ​
TIP
以下的配置安装会加重宿主机的负担，非必要不要安装
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
+netfilter-persistent reload
+service netfilter-persistent restart
卸载IPV6地址绑定的守护进程和对应的文件可用：
shell
systemctl stop add-ipv6.service
+systemctl disable add-ipv6.service
+rm /etc/systemd/system/add-ipv6.service
+systemctl daemon-reload
+rm /usr/local/bin/add-ipv6.sh
屏蔽容易被滥用的端口的出入流量以屏蔽端口和屏蔽滥用工具包 ​
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事前预防
国际
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
一键安装开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
一键安装宿主机可视化操作的面板 ​
  • (非必须，该面板只是为了方便可视化操作，没有也没问题)
  • 原作者仓库：跳转
shell
incus config set core.https_address [::]
+incus config set core.trust_password some-secret-string
+snap install incusmosaic
安装完毕后打开宿主机IP地址，按照提示设置admin的密码，其他一路默认就能使用面板了
`,44),e=[o];function t(c,r,C,i,y,D){return a(),l("div",null,e)}const d=s(p,[["render",t]]);export{h as __pageData,d as default};
diff --git a/assets/guide_incus_incus_extra_config.md.b96ae35d.lean.js b/assets/guide_incus_incus_extra_config.md.b96ae35d.lean.js
new file mode 100644
index 0000000000..de161a612a
--- /dev/null
+++ b/assets/guide_incus_incus_extra_config.md.b96ae35d.lean.js
@@ -0,0 +1,12 @@
+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":"guide/incus/incus_extra_config.md","filePath":"guide/incus/incus_extra_config.md","lastUpdated":1705324601000}'),p={name:"guide/incus/incus_extra_config.md"},o=n(`
其他自定义配置 ​
TIP
以下的配置安装会加重宿主机的负担，非必要不要安装
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
+netfilter-persistent reload
+service netfilter-persistent restart
卸载IPV6地址绑定的守护进程和对应的文件可用：
shell
systemctl stop add-ipv6.service
+systemctl disable add-ipv6.service
+rm /etc/systemd/system/add-ipv6.service
+systemctl daemon-reload
+rm /usr/local/bin/add-ipv6.sh
屏蔽容易被滥用的端口的出入流量以屏蔽端口和屏蔽滥用工具包 ​
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事前预防
国际
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
一键安装开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
一键安装宿主机可视化操作的面板 ​
  • (非必须，该面板只是为了方便可视化操作，没有也没问题)
  • 原作者仓库：跳转
shell
incus config set core.https_address [::]
+incus config set core.trust_password some-secret-string
+snap install incusmosaic
安装完毕后打开宿主机IP地址，按照提示设置admin的密码，其他一路默认就能使用面板了
`,44),e=[o];function t(c,r,C,i,y,D){return a(),l("div",null,e)}const d=s(p,[["render",t]]);export{h as __pageData,d as default};
diff --git a/assets/guide_incus_incus_install.md.a110ad4c.js b/assets/guide_incus_incus_install.md.a110ad4c.js
new file mode 100644
index 0000000000..10a41b604f
--- /dev/null
+++ b/assets/guide_incus_incus_install.md.a110ad4c.js
@@ -0,0 +1,5 @@
+import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"incus主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_install.md","filePath":"guide/incus/incus_install.md","lastUpdated":1705324601000}'),p={name:"guide/incus/incus_install.md"},o=l(`
incus主体安装 ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
一键安装 ​
WARNING
如果是全新的服务器，务必保证apt update和apt install curl都无问题再执行本脚本
TIP
且自开机起最好等待5分钟后再执行以下命令，避免系统默认设置中就执行了本脚本导致apt源卡死
  • 环境要求：Ubuntu 18+(推荐)，Debian 8+(仅限x86_64架构)
  • 如果是Debian系的宿主机，务必在screen中执行本脚本，避免长期运行时SSH中断导致ZFS编译安装失败
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程中可能需要重启服务器以加载含zfs的内核，然后再次执行安装命令，一切以运行后命令行的提示为准
  • 默认启用incus的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
如果脚本提示重启系统后需要再次执行脚本，第二次执行安装脚本仍提示重启系统加载内核，那么意味着内核在上一次加载中失败了，最好重装宿主机系统为ubuntu系解决这个问题
每次执行脚本都需要输入一次初始化的配置，所以遇到脚本提示需重启系统再次执行，那么就得再次输入初始化的配置
国际
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
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
手动安装 ​
新手推荐，避免有bug不知道怎么修，当然如果只是图方便又是老手懂排查BUG，用后面的一键安装也行
关闭防火墙 ​
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是合理的，上面我描述的情况属于超开了
apt install snapd -y
+snap install incus
+incus init
如果上面的命令中出现下面的错误
(snap "incus" assumes unsupported features: snapd2.39 (try to update snapd and refresh the core snap))
使用命令修补后再进行incus的安装
snap install core
如果无异常，上面三行命令执行结果如下
图片
一般的选项回车默认即可
选择配置物理盘大小(提示默认最小1GB那个选项)，一般我填空闲磁盘大小减去内存大小后乘以0.95并向下取整，这里我填了10GB
提示带auto的更新image的选项记得选no，避免更新占用系统
incus -h
`,38),e=[o];function t(c,r,i,C,y,u){return a(),n("div",null,e)}const h=s(p,[["render",t]]);export{D as __pageData,h as default};
diff --git a/assets/guide_incus_incus_install.md.a110ad4c.lean.js b/assets/guide_incus_incus_install.md.a110ad4c.lean.js
new file mode 100644
index 0000000000..10a41b604f
--- /dev/null
+++ b/assets/guide_incus_incus_install.md.a110ad4c.lean.js
@@ -0,0 +1,5 @@
+import{_ as s,v as a,b as n,R as l}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"incus主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/incus/incus_install.md","filePath":"guide/incus/incus_install.md","lastUpdated":1705324601000}'),p={name:"guide/incus/incus_install.md"},o=l(`
incus主体安装 ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
一键安装 ​
WARNING
如果是全新的服务器，务必保证apt update和apt install curl都无问题再执行本脚本
TIP
且自开机起最好等待5分钟后再执行以下命令，避免系统默认设置中就执行了本脚本导致apt源卡死
  • 环境要求：Ubuntu 18+(推荐)，Debian 8+(仅限x86_64架构)
  • 如果是Debian系的宿主机，务必在screen中执行本脚本，避免长期运行时SSH中断导致ZFS编译安装失败
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程中可能需要重启服务器以加载含zfs的内核，然后再次执行安装命令，一切以运行后命令行的提示为准
  • 默认启用incus的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
如果脚本提示重启系统后需要再次执行脚本，第二次执行安装脚本仍提示重启系统加载内核，那么意味着内核在上一次加载中失败了，最好重装宿主机系统为ubuntu系解决这个问题
每次执行脚本都需要输入一次初始化的配置，所以遇到脚本提示需重启系统再次执行，那么就得再次输入初始化的配置
国际
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
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
手动安装 ​
新手推荐，避免有bug不知道怎么修，当然如果只是图方便又是老手懂排查BUG，用后面的一键安装也行
关闭防火墙 ​
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是合理的，上面我描述的情况属于超开了
apt install snapd -y
+snap install incus
+incus init
如果上面的命令中出现下面的错误
(snap "incus" assumes unsupported features: snapd2.39 (try to update snapd and refresh the core snap))
使用命令修补后再进行incus的安装
snap install core
如果无异常，上面三行命令执行结果如下
图片
一般的选项回车默认即可
选择配置物理盘大小(提示默认最小1GB那个选项)，一般我填空闲磁盘大小减去内存大小后乘以0.95并向下取整，这里我填了10GB
提示带auto的更新image的选项记得选no，避免更新占用系统
incus -h
`,38),e=[o];function t(c,r,i,C,y,u){return a(),n("div",null,e)}const h=s(p,[["render",t]]);export{D as __pageData,h as default};
diff --git a/assets/guide_incus_incus_lxc.md.c508cac6.js b/assets/guide_incus_incus_lxc.md.c508cac6.js
new file mode 100644
index 0000000000..6c24044f4f
--- /dev/null
+++ b/assets/guide_incus_incus_lxc.md.c508cac6.js
@@ -0,0 +1,25 @@
+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/incus/incus_lxc.md","filePath":"guide/incus/incus_lxc.md","lastUpdated":1705324601000}'),p={name:"guide/incus/incus_lxc.md"},o=n(`
LXC虚拟化 ​
单独生成一个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，注意传入参数为系统名字+版本号，如：
  • 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的版本号已支持
  • 开不起来的可能是硬盘或内存不够大或者本身就不适配宿主机，自行尝试查看开不起来的报错
TIP
版本号中已结束长期维护的一般不再有官方镜像了，暂时未找到历史镜像的存档地址，如果有找到欢迎留言我会添加支持
示例 ​
以下为开设的示例服务器的信息：
属性值
服务器名字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
需要进入容器内部则执行
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
+ls
普通版本批量生成 ​
开出的服务器配置：
  • 1核256MB内存1GB硬盘限速300Mbit带宽
  • 带1个SSH端口，25个外网端口
  • 默认内存和硬盘大小
TIP
lxc若命令无问题，执行初始化开服务器，这一步最好放screen中后台挂起执行，开服务器时长与你开几个和宿主机配置相关
执行下面命令加载开机脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/init.sh -o init.sh && chmod +x init.sh && dos2unix init.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/init.sh -o init.sh && chmod +x init.sh && dos2unix init.sh
下面命令为开服务器名字前缀为tj的10个服务器
shell
./init.sh tj 10
有时候init.sh的运行路径有问题，此时建议前面加上sudo强制根目录执行
纯SSH端口版本批量生成 ​
开出的服务器配置：
  • 1核128MB内存300MB硬盘限速300Mbit带宽
  • 只有一个SSH端口
  • 无法挂载warp
TIP
lxc若命令无问题，执行初始化开服务器，这一步最好放screen中后台挂起执行，开服务器时长与你开几个和宿主机配置相关
加载开机脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/least.sh -o least.sh && chmod +x least.sh && dos2unix least.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/least.sh -o least.sh && chmod +x least.sh && dos2unix least.sh
下列命令最后一行为开服务器名字前缀为tj的10个服务器
shell
./least.sh tj 10
有时候least.sh的运行路径有问题，此时建议前面加上sudo强制根目录执行
自定义批量生成版本 ​
  • 可自定义内存和硬盘大小
  • 有执行过上面的手动批量生成过也没问题，配置是继承的不覆盖
如果需要多次批量生成服务器，可使用
国际
curl -L https://github.com/oneclickvirt/incus/raw/main/scripts/add_more.sh -o add_more.sh && chmod +x add_more.sh && bash add_more.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://github.com/oneclickvirt/incus/raw/main/scripts/add_more.sh -o add_more.sh && chmod +x add_more.sh && bash add_more.sh
可多次运行批量生成服务器，且继承前面已生成的部分在后面添加，可自定义内存和硬盘大小
查看已批量开设的信息 ​
开完服务器后，具体信息会生成在当前目录下的log文件中，格式如下
shell
1号服务器名称 密码 ssh端口 外网端口起始 外网端口终止
+2号服务器名称 密码 ssh端口 外网端口起始 外网端口终止
如果想要查看，只需在当前目录执行以下命令打印log文件即可
shell
cat log
WARNING
不要拿该脚本开出的服务器当生产环境，LXC虚拟化不支持换内核，dd，开启bbr等操作
部分常用incus命令 ​
查看所有
bash
incus list
查看个例
bash
incus info 服务器名字
启动个例
bash
incus start 服务器名字
停止个例
bash
incus stop 服务器名字
删除个例
bash
incus delete -f 服务器名字
进入内部
bash
incus exec 服务器名字 /bin/bash
TIP
在alpine中不用/bin/bash而是用/bin/sh，常规的系统都是/bin/bash
退出则输入exit回车即可
删除所有LXC容器
bash
incus list -c n --format csv | xargs -I {} incus delete -f {}
在容器内执行删除无用日志
bash
sudo apt-get autoremove
+sudo apt-get clean
+sudo find /var/log -type f -delete
+sudo find /var/tmp -type f -delete
+sudo find /tmp -type f -delete
+sudo find /var/cache/apt/archives -type f -delete
更新上述所有一键脚本的相关命令 ​
删除原始配置脚本
bash
rm -rf /usr/local/bin/ssh_sh.sh
+rm -rf /usr/local/bin/config.sh
+rm -rf /usr/local/bin/ssh_bash.sh
+rm -rf /usr/local/bin/check-dns.sh
+rm -rf /root/ssh_sh.sh
+rm -rf /root/config.sh
+rm -rf /root/ssh_bash.sh
+rm -rf /root/buildone.sh
+rm -rf /root/add_more.sh
+rm -rf /root/build_ipv6_network.sh
下载回新版本的相关配置脚本
bash
wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/check-dns.sh -O /usr/local/bin/check-dns.sh && chmod +x /usr/local/bin/check-dns.sh
+wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/config.sh -O /usr/local/bin/config.sh && chmod +x /usr/local/bin/config.sh
+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
其他一键脚本自己对应下载回来就行了
`,93),e=[o];function t(c,r,C,i,y,A){return a(),l("div",null,e)}const h=s(p,[["render",t]]);export{d as __pageData,h as default};
diff --git a/assets/guide_incus_incus_lxc.md.c508cac6.lean.js b/assets/guide_incus_incus_lxc.md.c508cac6.lean.js
new file mode 100644
index 0000000000..6c24044f4f
--- /dev/null
+++ b/assets/guide_incus_incus_lxc.md.c508cac6.lean.js
@@ -0,0 +1,25 @@
+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/incus/incus_lxc.md","filePath":"guide/incus/incus_lxc.md","lastUpdated":1705324601000}'),p={name:"guide/incus/incus_lxc.md"},o=n(`
LXC虚拟化 ​
单独生成一个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，注意传入参数为系统名字+版本号，如：
  • 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的版本号已支持
  • 开不起来的可能是硬盘或内存不够大或者本身就不适配宿主机，自行尝试查看开不起来的报错
TIP
版本号中已结束长期维护的一般不再有官方镜像了，暂时未找到历史镜像的存档地址，如果有找到欢迎留言我会添加支持
示例 ​
以下为开设的示例服务器的信息：
属性值
服务器名字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
需要进入容器内部则执行
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
+ls
普通版本批量生成 ​
开出的服务器配置：
  • 1核256MB内存1GB硬盘限速300Mbit带宽
  • 带1个SSH端口，25个外网端口
  • 默认内存和硬盘大小
TIP
lxc若命令无问题，执行初始化开服务器，这一步最好放screen中后台挂起执行，开服务器时长与你开几个和宿主机配置相关
执行下面命令加载开机脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/init.sh -o init.sh && chmod +x init.sh && dos2unix init.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/init.sh -o init.sh && chmod +x init.sh && dos2unix init.sh
下面命令为开服务器名字前缀为tj的10个服务器
shell
./init.sh tj 10
有时候init.sh的运行路径有问题，此时建议前面加上sudo强制根目录执行
纯SSH端口版本批量生成 ​
开出的服务器配置：
  • 1核128MB内存300MB硬盘限速300Mbit带宽
  • 只有一个SSH端口
  • 无法挂载warp
TIP
lxc若命令无问题，执行初始化开服务器，这一步最好放screen中后台挂起执行，开服务器时长与你开几个和宿主机配置相关
加载开机脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/least.sh -o least.sh && chmod +x least.sh && dos2unix least.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/least.sh -o least.sh && chmod +x least.sh && dos2unix least.sh
下列命令最后一行为开服务器名字前缀为tj的10个服务器
shell
./least.sh tj 10
有时候least.sh的运行路径有问题，此时建议前面加上sudo强制根目录执行
自定义批量生成版本 ​
  • 可自定义内存和硬盘大小
  • 有执行过上面的手动批量生成过也没问题，配置是继承的不覆盖
如果需要多次批量生成服务器，可使用
国际
curl -L https://github.com/oneclickvirt/incus/raw/main/scripts/add_more.sh -o add_more.sh && chmod +x add_more.sh && bash add_more.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://github.com/oneclickvirt/incus/raw/main/scripts/add_more.sh -o add_more.sh && chmod +x add_more.sh && bash add_more.sh
可多次运行批量生成服务器，且继承前面已生成的部分在后面添加，可自定义内存和硬盘大小
查看已批量开设的信息 ​
开完服务器后，具体信息会生成在当前目录下的log文件中，格式如下
shell
1号服务器名称 密码 ssh端口 外网端口起始 外网端口终止
+2号服务器名称 密码 ssh端口 外网端口起始 外网端口终止
如果想要查看，只需在当前目录执行以下命令打印log文件即可
shell
cat log
WARNING
不要拿该脚本开出的服务器当生产环境，LXC虚拟化不支持换内核，dd，开启bbr等操作
部分常用incus命令 ​
查看所有
bash
incus list
查看个例
bash
incus info 服务器名字
启动个例
bash
incus start 服务器名字
停止个例
bash
incus stop 服务器名字
删除个例
bash
incus delete -f 服务器名字
进入内部
bash
incus exec 服务器名字 /bin/bash
TIP
在alpine中不用/bin/bash而是用/bin/sh，常规的系统都是/bin/bash
退出则输入exit回车即可
删除所有LXC容器
bash
incus list -c n --format csv | xargs -I {} incus delete -f {}
在容器内执行删除无用日志
bash
sudo apt-get autoremove
+sudo apt-get clean
+sudo find /var/log -type f -delete
+sudo find /var/tmp -type f -delete
+sudo find /tmp -type f -delete
+sudo find /var/cache/apt/archives -type f -delete
更新上述所有一键脚本的相关命令 ​
删除原始配置脚本
bash
rm -rf /usr/local/bin/ssh_sh.sh
+rm -rf /usr/local/bin/config.sh
+rm -rf /usr/local/bin/ssh_bash.sh
+rm -rf /usr/local/bin/check-dns.sh
+rm -rf /root/ssh_sh.sh
+rm -rf /root/config.sh
+rm -rf /root/ssh_bash.sh
+rm -rf /root/buildone.sh
+rm -rf /root/add_more.sh
+rm -rf /root/build_ipv6_network.sh
下载回新版本的相关配置脚本
bash
wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/check-dns.sh -O /usr/local/bin/check-dns.sh && chmod +x /usr/local/bin/check-dns.sh
+wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/config.sh -O /usr/local/bin/config.sh && chmod +x /usr/local/bin/config.sh
+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
其他一键脚本自己对应下载回来就行了
`,93),e=[o];function t(c,r,C,i,y,A){return a(),l("div",null,e)}const h=s(p,[["render",t]]);export{d as __pageData,h as default};
diff --git a/assets/guide_incus_incus_precheck.md.7250391c.js b/assets/guide_incus_incus_precheck.md.7250391c.js
new file mode 100644
index 0000000000..c5c76b0c9f
--- /dev/null
+++ b/assets/guide_incus_incus_precheck.md.7250391c.js
@@ -0,0 +1 @@
+import{_ as e,v as a,b as i,R as t}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":1705324601000}'),s={name:"guide/incus/incus_precheck.md"},c=t('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
要求 ​
硬件要求:
  • 系统：Debian 8+, Ubuntu 18+(推荐20.04)
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转
项目特点 ​
  • 本套脚本开发使用的Ubuntu20，Ubuntu别的长期维护版本应该也没问题，Debian无法使用zfs时自动切换别的存储类型
  • 已设置同时进行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)
',16),l=[c];function r(n,p,o,d,h,u){return a(),i("div",null,l)}const m=e(s,[["render",r]]);export{g as __pageData,m as default};
diff --git a/assets/guide_incus_incus_precheck.md.7250391c.lean.js b/assets/guide_incus_incus_precheck.md.7250391c.lean.js
new file mode 100644
index 0000000000..c5c76b0c9f
--- /dev/null
+++ b/assets/guide_incus_incus_precheck.md.7250391c.lean.js
@@ -0,0 +1 @@
+import{_ as e,v as a,b as i,R as t}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":1705324601000}'),s={name:"guide/incus/incus_precheck.md"},c=t('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
要求 ​
硬件要求:
  • 系统：Debian 8+, Ubuntu 18+(推荐20.04)
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转
项目特点 ​
  • 本套脚本开发使用的Ubuntu20，Ubuntu别的长期维护版本应该也没问题，Debian无法使用zfs时自动切换别的存储类型
  • 已设置同时进行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)
',16),l=[c];function r(n,p,o,d,h,u){return a(),i("div",null,l)}const m=e(s,[["render",r]]);export{g as __pageData,m as default};
diff --git a/assets/guide_incus_incus_qa.md.c32af72f.js b/assets/guide_incus_incus_qa.md.c32af72f.js
new file mode 100644
index 0000000000..d35f102b90
--- /dev/null
+++ b/assets/guide_incus_incus_qa.md.c32af72f.js
@@ -0,0 +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":1705324601000}'),r={name:"guide/incus/incus_qa.md"},o=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 促销款
luxvps 中的 德国AMD 促销款
',14),p=[o];function n(i,c,l,u,d,h){return e(),s("div",null,p)}const g=a(r,[["render",n]]);export{f as __pageData,g as default};
diff --git a/assets/guide_incus_incus_qa.md.c32af72f.lean.js b/assets/guide_incus_incus_qa.md.c32af72f.lean.js
new file mode 100644
index 0000000000..d35f102b90
--- /dev/null
+++ b/assets/guide_incus_incus_qa.md.c32af72f.lean.js
@@ -0,0 +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":1705324601000}'),r={name:"guide/incus/incus_qa.md"},o=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 促销款
luxvps 中的 德国AMD 促销款
',14),p=[o];function n(i,c,l,u,d,h){return e(),s("div",null,p)}const g=a(r,[["render",n]]);export{f as __pageData,g as default};
diff --git a/assets/guide_incus_incus_thanks.md.38fc1b5b.js b/assets/guide_incus_incus_thanks.md.38fc1b5b.js
new file mode 100644
index 0000000000..864fe31477
--- /dev/null
+++ b/assets/guide_incus_incus_thanks.md.38fc1b5b.js
@@ -0,0 +1 @@
+import{_ as t,v as r,b as e,R as s}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/incus/incus_thanks.md","filePath":"guide/incus/incus_thanks.md","lastUpdated":1705324601000}'),n={name:"guide/incus/incus_thanks.md"},a=s('
致谢 ​
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
',10),o=[a];function i(c,p,h,l,u,d){return r(),e("div",null,o)}const x=t(n,[["render",i]]);export{g as __pageData,x as default};
diff --git a/assets/guide_incus_incus_thanks.md.38fc1b5b.lean.js b/assets/guide_incus_incus_thanks.md.38fc1b5b.lean.js
new file mode 100644
index 0000000000..864fe31477
--- /dev/null
+++ b/assets/guide_incus_incus_thanks.md.38fc1b5b.lean.js
@@ -0,0 +1 @@
+import{_ as t,v as r,b as e,R as s}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/incus/incus_thanks.md","filePath":"guide/incus/incus_thanks.md","lastUpdated":1705324601000}'),n={name:"guide/incus/incus_thanks.md"},a=s('
致谢 ​
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
',10),o=[a];function i(c,p,h,l,u,d){return r(),e("div",null,o)}const x=t(n,[["render",i]]);export{g as __pageData,x as default};
diff --git a/assets/guide_lxd_custom.md.ce677ab3.js b/assets/guide_lxd_lxd_custom.md.4d514384.js
similarity index 87%
rename from assets/guide_lxd_custom.md.ce677ab3.js
rename to assets/guide_lxd_lxd_custom.md.4d514384.js
index a126619211..ab2e0bb68a 100644
--- a/assets/guide_lxd_custom.md.ce677ab3.js
+++ b/assets/guide_lxd_lxd_custom.md.4d514384.js
@@ -1,4 +1,4 @@
-import{_ as t,v as e,b as s,R as a}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"给宿主机附加免费的IPV6地址段","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd_custom.md","filePath":"guide/lxd_custom.md","lastUpdated":1704976888000}'),n={name:"guide/lxd_custom.md"},l=a(`
给宿主机附加免费的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 t,v as e,b as s,R as a}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"给宿主机附加免费的IPV6地址段","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_custom.md","filePath":"guide/lxd/lxd_custom.md","lastUpdated":1705324601000}'),n={name:"guide/lxd/lxd_custom.md"},l=a(`
给宿主机附加免费的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_custom.md.ce677ab3.lean.js b/assets/guide_lxd_lxd_custom.md.4d514384.lean.js
similarity index 87%
rename from assets/guide_lxd_custom.md.ce677ab3.lean.js
rename to assets/guide_lxd_lxd_custom.md.4d514384.lean.js
index a126619211..ab2e0bb68a 100644
--- a/assets/guide_lxd_custom.md.ce677ab3.lean.js
+++ b/assets/guide_lxd_lxd_custom.md.4d514384.lean.js
@@ -1,4 +1,4 @@
-import{_ as t,v as e,b as s,R as a}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"给宿主机附加免费的IPV6地址段","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd_custom.md","filePath":"guide/lxd_custom.md","lastUpdated":1704976888000}'),n={name:"guide/lxd_custom.md"},l=a(`
给宿主机附加免费的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 t,v as e,b as s,R as a}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"给宿主机附加免费的IPV6地址段","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_custom.md","filePath":"guide/lxd/lxd_custom.md","lastUpdated":1705324601000}'),n={name:"guide/lxd/lxd_custom.md"},l=a(`
给宿主机附加免费的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_extra_config.md.9c719fca.js b/assets/guide_lxd_lxd_extra_config.md.195a4103.js
similarity index 71%
rename from assets/guide_lxd_extra_config.md.9c719fca.js
rename to assets/guide_lxd_lxd_extra_config.md.195a4103.js
index 142887035b..c973040223 100644
--- a/assets/guide_lxd_extra_config.md.9c719fca.js
+++ b/assets/guide_lxd_lxd_extra_config.md.195a4103.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_extra_config.md","filePath":"guide/lxd_extra_config.md","lastUpdated":1704976888000}'),p={name:"guide/lxd_extra_config.md"},o=n(`
其他自定义配置 ​
TIP
以下的配置安装会加重宿主机的负担，非必要不要安装
TIP
如果是个人使用，可忽略防滥用部分脚本的安装
自动配置IPV6地址 ​
  • (非必须，不使用的也没问题)
  • 该脚本仅适用于宿主机有给IPV6子网且是至少/112的，且宿主机绑定了子网的第一个IP做宿主机的IPV6地址或IPV6的gateway
  • 自动为LXD创建的LXC容器配置IPV6地址
  • 已集成到buildone.sh中可使用变量控制且无需事先下载，该脚本可不手动使用，在使用buildone.sh时配置Y开启即可
下载脚本
国际
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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":1705324601000}'),p={name:"guide/lxd/lxd_extra_config.md"},o=n(`
其他自定义配置 ​
TIP
以下的配置安装会加重宿主机的负担，非必要不要安装
TIP
如果是个人使用，可忽略防滥用部分脚本的安装
自动配置IPV6地址 ​
  • (非必须，不使用的也没问题)
  • 该脚本仅适用于宿主机有给IPV6子网且是至少/112的，且宿主机绑定了子网的第一个IP做宿主机的IPV6地址或IPV6的gateway
  • 自动为LXD创建的LXC容器配置IPV6地址
  • 已集成到buildone.sh中可使用变量控制且无需事先下载，该脚本可不手动使用，在使用buildone.sh时配置Y开启即可
下载脚本
国际
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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_extra_config.md.9c719fca.lean.js b/assets/guide_lxd_lxd_extra_config.md.195a4103.lean.js
similarity index 71%
rename from assets/guide_lxd_extra_config.md.9c719fca.lean.js
rename to assets/guide_lxd_lxd_extra_config.md.195a4103.lean.js
index 142887035b..c973040223 100644
--- a/assets/guide_lxd_extra_config.md.9c719fca.lean.js
+++ b/assets/guide_lxd_lxd_extra_config.md.195a4103.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_extra_config.md","filePath":"guide/lxd_extra_config.md","lastUpdated":1704976888000}'),p={name:"guide/lxd_extra_config.md"},o=n(`
其他自定义配置 ​
TIP
以下的配置安装会加重宿主机的负担，非必要不要安装
TIP
如果是个人使用，可忽略防滥用部分脚本的安装
自动配置IPV6地址 ​
  • (非必须，不使用的也没问题)
  • 该脚本仅适用于宿主机有给IPV6子网且是至少/112的，且宿主机绑定了子网的第一个IP做宿主机的IPV6地址或IPV6的gateway
  • 自动为LXD创建的LXC容器配置IPV6地址
  • 已集成到buildone.sh中可使用变量控制且无需事先下载，该脚本可不手动使用，在使用buildone.sh时配置Y开启即可
下载脚本
国际
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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":1705324601000}'),p={name:"guide/lxd/lxd_extra_config.md"},o=n(`
其他自定义配置 ​
TIP
以下的配置安装会加重宿主机的负担，非必要不要安装
TIP
如果是个人使用，可忽略防滥用部分脚本的安装
自动配置IPV6地址 ​
  • (非必须，不使用的也没问题)
  • 该脚本仅适用于宿主机有给IPV6子网且是至少/112的，且宿主机绑定了子网的第一个IP做宿主机的IPV6地址或IPV6的gateway
  • 自动为LXD创建的LXC容器配置IPV6地址
  • 已集成到buildone.sh中可使用变量控制且无需事先下载，该脚本可不手动使用，在使用buildone.sh时配置Y开启即可
下载脚本
国际
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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_install.md.7ebf2ac3.js b/assets/guide_lxd_lxd_install.md.62ad576e.js
similarity index 57%
rename from assets/guide_lxd_install.md.7ebf2ac3.js
rename to assets/guide_lxd_lxd_install.md.62ad576e.js
index d37b717dee..80c4b80ad2 100644
--- a/assets/guide_lxd_install.md.7ebf2ac3.js
+++ b/assets/guide_lxd_lxd_install.md.62ad576e.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":"LXD主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd_install.md","filePath":"guide/lxd_install.md","lastUpdated":1704976888000}'),n={name:"guide/lxd_install.md"},o=p(`
LXD主体安装 ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
一键安装 ​
WARNING
如果是全新的服务器，务必保证apt update和apt install curl都无问题再执行本脚本
TIP
且自开机起最好等待5分钟后再执行以下命令，避免系统默认设置中就执行了本脚本导致apt源卡死
  • 环境要求：Ubuntu 18+(推荐)，Debian 8+(仅限x86_64架构)
  • 如果是Debian系的宿主机，务必在screen中执行本脚本，避免长期运行时SSH中断导致ZFS编译安装失败
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程中可能需要重启服务器以加载含zfs的内核，然后再次执行安装命令，一切以运行后命令行的提示为准
  • 默认启用lxd的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
如果脚本提示重启系统后需要再次执行脚本，第二次执行安装脚本仍提示重启系统加载内核，那么意味着内核在上一次加载中失败了，最好重装宿主机系统为ubuntu系解决这个问题
每次执行脚本都需要输入一次初始化的配置，所以遇到脚本提示需重启系统再次执行，那么就得再次输入初始化的配置
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
手动安装 ​
新手推荐，避免有bug不知道怎么修，当然如果只是图方便又是老手懂排查BUG，用后面的一键安装也行
关闭防火墙 ​
bash
apt update
+import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"LXD主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_install.md","filePath":"guide/lxd/lxd_install.md","lastUpdated":1705324601000}'),n={name:"guide/lxd/lxd_install.md"},o=p(`
LXD主体安装 ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
一键安装 ​
WARNING
如果是全新的服务器，务必保证apt update和apt install curl都无问题再执行本脚本
TIP
且自开机起最好等待5分钟后再执行以下命令，避免系统默认设置中就执行了本脚本导致apt源卡死
  • 环境要求：Ubuntu 18+(推荐)，Debian 8+(仅限x86_64架构)
  • 如果是Debian系的宿主机，务必在screen中执行本脚本，避免长期运行时SSH中断导致ZFS编译安装失败
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程中可能需要重启服务器以加载含zfs的内核，然后再次执行安装命令，一切以运行后命令行的提示为准
  • 默认启用lxd的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
如果脚本提示重启系统后需要再次执行脚本，第二次执行安装脚本仍提示重启系统加载内核，那么意味着内核在上一次加载中失败了，最好重装宿主机系统为ubuntu系解决这个问题
每次执行脚本都需要输入一次初始化的配置，所以遇到脚本提示需重启系统再次执行，那么就得再次输入初始化的配置
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
手动安装 ​
新手推荐，避免有bug不知道怎么修，当然如果只是图方便又是老手懂排查BUG，用后面的一键安装也行
关闭防火墙 ​
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/spiritLHLS/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/spiritLHLS/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
diff --git a/assets/guide_lxd_install.md.7ebf2ac3.lean.js b/assets/guide_lxd_lxd_install.md.62ad576e.lean.js
similarity index 57%
rename from assets/guide_lxd_install.md.7ebf2ac3.lean.js
rename to assets/guide_lxd_lxd_install.md.62ad576e.lean.js
index d37b717dee..80c4b80ad2 100644
--- a/assets/guide_lxd_install.md.7ebf2ac3.lean.js
+++ b/assets/guide_lxd_lxd_install.md.62ad576e.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":"LXD主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd_install.md","filePath":"guide/lxd_install.md","lastUpdated":1704976888000}'),n={name:"guide/lxd_install.md"},o=p(`
LXD主体安装 ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
一键安装 ​
WARNING
如果是全新的服务器，务必保证apt update和apt install curl都无问题再执行本脚本
TIP
且自开机起最好等待5分钟后再执行以下命令，避免系统默认设置中就执行了本脚本导致apt源卡死
  • 环境要求：Ubuntu 18+(推荐)，Debian 8+(仅限x86_64架构)
  • 如果是Debian系的宿主机，务必在screen中执行本脚本，避免长期运行时SSH中断导致ZFS编译安装失败
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程中可能需要重启服务器以加载含zfs的内核，然后再次执行安装命令，一切以运行后命令行的提示为准
  • 默认启用lxd的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
如果脚本提示重启系统后需要再次执行脚本，第二次执行安装脚本仍提示重启系统加载内核，那么意味着内核在上一次加载中失败了，最好重装宿主机系统为ubuntu系解决这个问题
每次执行脚本都需要输入一次初始化的配置，所以遇到脚本提示需重启系统再次执行，那么就得再次输入初始化的配置
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
手动安装 ​
新手推荐，避免有bug不知道怎么修，当然如果只是图方便又是老手懂排查BUG，用后面的一键安装也行
关闭防火墙 ​
bash
apt update
+import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"LXD主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd/lxd_install.md","filePath":"guide/lxd/lxd_install.md","lastUpdated":1705324601000}'),n={name:"guide/lxd/lxd_install.md"},o=p(`
LXD主体安装 ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
一键安装 ​
WARNING
如果是全新的服务器，务必保证apt update和apt install curl都无问题再执行本脚本
TIP
且自开机起最好等待5分钟后再执行以下命令，避免系统默认设置中就执行了本脚本导致apt源卡死
  • 环境要求：Ubuntu 18+(推荐)，Debian 8+(仅限x86_64架构)
  • 如果是Debian系的宿主机，务必在screen中执行本脚本，避免长期运行时SSH中断导致ZFS编译安装失败
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程中可能需要重启服务器以加载含zfs的内核，然后再次执行安装命令，一切以运行后命令行的提示为准
  • 默认启用lxd的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
如果脚本提示重启系统后需要再次执行脚本，第二次执行安装脚本仍提示重启系统加载内核，那么意味着内核在上一次加载中失败了，最好重装宿主机系统为ubuntu系解决这个问题
每次执行脚本都需要输入一次初始化的配置，所以遇到脚本提示需重启系统再次执行，那么就得再次输入初始化的配置
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
手动安装 ​
新手推荐，避免有bug不知道怎么修，当然如果只是图方便又是老手懂排查BUG，用后面的一键安装也行
关闭防火墙 ​
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/spiritLHLS/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/spiritLHLS/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
diff --git a/assets/guide_lxd_lxc.md.ea0bae70.js b/assets/guide_lxd_lxd_lxc.md.1e49ab60.js
similarity index 76%
rename from assets/guide_lxd_lxc.md.ea0bae70.js
rename to assets/guide_lxd_lxd_lxc.md.1e49ab60.js
index 055c88ed7f..0f47452413 100644
--- a/assets/guide_lxd_lxc.md.ea0bae70.js
+++ b/assets/guide_lxd_lxd_lxc.md.1e49ab60.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_lxc.md","filePath":"guide/lxd_lxc.md","lastUpdated":1704976888000}'),p={name:"guide/lxd_lxc.md"},o=n(`
LXC虚拟化 ​
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载开机脚本是非必须的，如果你使用过一键安装LXD的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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
支持自定义服务器的系统，不填写留空时默认使用debian11，注意传入参数为系统名字+版本号，如：
  • 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的版本号已支持
  • 开不起来的可能是硬盘或内存不够大或者本身就不适配宿主机，自行尝试查看开不起来的报错
TIP
版本号中已结束长期维护的一般不再有官方镜像了，暂时未找到历史镜像的存档地址，如果有找到欢迎留言我会添加支持
示例 ​
以下为开设的示例服务器的信息：
属性值
服务器名字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
需要进入容器内部则执行
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":1705324601000}'),p={name:"guide/lxd/lxd_lxc.md"},o=n(`
LXC虚拟化 ​
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载开机脚本是非必须的，如果你使用过一键安装LXD的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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
支持自定义服务器的系统，不填写留空时默认使用debian11，注意传入参数为系统名字+版本号，如：
  • 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的版本号已支持
  • 开不起来的可能是硬盘或内存不够大或者本身就不适配宿主机，自行尝试查看开不起来的报错
TIP
版本号中已结束长期维护的一般不再有官方镜像了，暂时未找到历史镜像的存档地址，如果有找到欢迎留言我会添加支持
示例 ​
以下为开设的示例服务器的信息：
属性值
服务器名字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
需要进入容器内部则执行
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_lxc.md.ea0bae70.lean.js b/assets/guide_lxd_lxd_lxc.md.1e49ab60.lean.js
similarity index 76%
rename from assets/guide_lxd_lxc.md.ea0bae70.lean.js
rename to assets/guide_lxd_lxd_lxc.md.1e49ab60.lean.js
index 055c88ed7f..0f47452413 100644
--- a/assets/guide_lxd_lxc.md.ea0bae70.lean.js
+++ b/assets/guide_lxd_lxd_lxc.md.1e49ab60.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_lxc.md","filePath":"guide/lxd_lxc.md","lastUpdated":1704976888000}'),p={name:"guide/lxd_lxc.md"},o=n(`
LXC虚拟化 ​
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载开机脚本是非必须的，如果你使用过一键安装LXD的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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
支持自定义服务器的系统，不填写留空时默认使用debian11，注意传入参数为系统名字+版本号，如：
  • 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的版本号已支持
  • 开不起来的可能是硬盘或内存不够大或者本身就不适配宿主机，自行尝试查看开不起来的报错
TIP
版本号中已结束长期维护的一般不再有官方镜像了，暂时未找到历史镜像的存档地址，如果有找到欢迎留言我会添加支持
示例 ​
以下为开设的示例服务器的信息：
属性值
服务器名字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
需要进入容器内部则执行
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":1705324601000}'),p={name:"guide/lxd/lxd_lxc.md"},o=n(`
LXC虚拟化 ​
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载开机脚本是非必须的，如果你使用过一键安装LXD的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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
支持自定义服务器的系统，不填写留空时默认使用debian11，注意传入参数为系统名字+版本号，如：
  • 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的版本号已支持
  • 开不起来的可能是硬盘或内存不够大或者本身就不适配宿主机，自行尝试查看开不起来的报错
TIP
版本号中已结束长期维护的一般不再有官方镜像了，暂时未找到历史镜像的存档地址，如果有找到欢迎留言我会添加支持
示例 ​
以下为开设的示例服务器的信息：
属性值
服务器名字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
需要进入容器内部则执行
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.7a202bc3.js b/assets/guide_lxd_lxd_precheck.md.7a202bc3.js
new file mode 100644
index 0000000000..7397f8c6de
--- /dev/null
+++ b/assets/guide_lxd_lxd_precheck.md.7a202bc3.js
@@ -0,0 +1 @@
+import{_ as e,v as a,b as t,R as i}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":1705324601000}'),l={name:"guide/lxd/lxd_precheck.md"},s=i('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
要求 ​
硬件要求:
  • 系统：Debian 8+, Ubuntu 18+(推荐20.04)
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转
项目特点 ​
  • 本套脚本开发使用的Ubuntu20，Ubuntu别的长期维护版本应该也没问题，Debian无法使用zfs时自动切换别的存储类型
  • 已设置同时进行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/spiritLHLS/lxd/main/scripts/pre_check.sh)
国内
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/pre_check.sh)
',16),r=[s];function p(c,o,n,d,h,u){return a(),t("div",null,r)}const m=e(l,[["render",p]]);export{g as __pageData,m as default};
diff --git a/assets/guide_lxd_lxd_precheck.md.7a202bc3.lean.js b/assets/guide_lxd_lxd_precheck.md.7a202bc3.lean.js
new file mode 100644
index 0000000000..7397f8c6de
--- /dev/null
+++ b/assets/guide_lxd_lxd_precheck.md.7a202bc3.lean.js
@@ -0,0 +1 @@
+import{_ as e,v as a,b as t,R as i}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":1705324601000}'),l={name:"guide/lxd/lxd_precheck.md"},s=i('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
要求 ​
硬件要求:
  • 系统：Debian 8+, Ubuntu 18+(推荐20.04)
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转
项目特点 ​
  • 本套脚本开发使用的Ubuntu20，Ubuntu别的长期维护版本应该也没问题，Debian无法使用zfs时自动切换别的存储类型
  • 已设置同时进行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/spiritLHLS/lxd/main/scripts/pre_check.sh)
国内
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/pre_check.sh)
',16),r=[s];function p(c,o,n,d,h,u){return a(),t("div",null,r)}const m=e(l,[["render",p]]);export{g as __pageData,m as default};
diff --git a/assets/guide_lxd_qa.md.4e3f3f6b.js b/assets/guide_lxd_lxd_qa.md.7f186f01.js
similarity index 73%
rename from assets/guide_lxd_qa.md.4e3f3f6b.js
rename to assets/guide_lxd_lxd_qa.md.7f186f01.js
index 6307afae56..24638bbd56 100644
--- a/assets/guide_lxd_qa.md.4e3f3f6b.js
+++ b/assets/guide_lxd_lxd_qa.md.7f186f01.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_qa.md","filePath":"guide/lxd_qa.md","lastUpdated":1704976888000}'),p={name:"guide/lxd_qa.md"},l=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 促销款
luxvps 中的 德国AMD 促销款
`,19),o=[l];function n(r,c,i,d,h,u){return e(),s("div",null,o)}const b=a(p,[["render",n]]);export{_ as __pageData,b as default};
+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":1705324601000}'),l={name:"guide/lxd/lxd_qa.md"},p=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 促销款
luxvps 中的 德国AMD 促销款
`,19),o=[p];function n(r,c,i,d,h,u){return e(),s("div",null,o)}const b=a(l,[["render",n]]);export{_ as __pageData,b as default};
diff --git a/assets/guide_lxd_qa.md.4e3f3f6b.lean.js b/assets/guide_lxd_lxd_qa.md.7f186f01.lean.js
similarity index 73%
rename from assets/guide_lxd_qa.md.4e3f3f6b.lean.js
rename to assets/guide_lxd_lxd_qa.md.7f186f01.lean.js
index 6307afae56..24638bbd56 100644
--- a/assets/guide_lxd_qa.md.4e3f3f6b.lean.js
+++ b/assets/guide_lxd_lxd_qa.md.7f186f01.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_qa.md","filePath":"guide/lxd_qa.md","lastUpdated":1704976888000}'),p={name:"guide/lxd_qa.md"},l=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 促销款
luxvps 中的 德国AMD 促销款
`,19),o=[l];function n(r,c,i,d,h,u){return e(),s("div",null,o)}const b=a(p,[["render",n]]);export{_ as __pageData,b as default};
+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":1705324601000}'),l={name:"guide/lxd/lxd_qa.md"},p=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 促销款
luxvps 中的 德国AMD 促销款
`,19),o=[p];function n(r,c,i,d,h,u){return e(),s("div",null,o)}const b=a(l,[["render",n]]);export{_ as __pageData,b as default};
diff --git a/assets/guide_lxd_lxd_thanks.md.17fe9867.js b/assets/guide_lxd_lxd_thanks.md.17fe9867.js
new file mode 100644
index 0000000000..1a560518fa
--- /dev/null
+++ b/assets/guide_lxd_lxd_thanks.md.17fe9867.js
@@ -0,0 +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":1705324601000}'),n={name:"guide/lxd/lxd_thanks.md"},s=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
感谢 @Ella-Alinda @fscarmen 提供的指导
',11),o=[s];function i(l,c,p,h,d,u){return r(),e("div",null,o)}const x=t(n,[["render",i]]);export{g as __pageData,x as default};
diff --git a/assets/guide_lxd_lxd_thanks.md.17fe9867.lean.js b/assets/guide_lxd_lxd_thanks.md.17fe9867.lean.js
new file mode 100644
index 0000000000..1a560518fa
--- /dev/null
+++ b/assets/guide_lxd_lxd_thanks.md.17fe9867.lean.js
@@ -0,0 +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":1705324601000}'),n={name:"guide/lxd/lxd_thanks.md"},s=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
感谢 @Ella-Alinda @fscarmen 提供的指导
',11),o=[s];function i(l,c,p,h,d,u){return r(),e("div",null,o)}const x=t(n,[["render",i]]);export{g as __pageData,x as default};
diff --git a/assets/guide_lxd_precheck.md.445272a6.js b/assets/guide_lxd_precheck.md.445272a6.js
deleted file mode 100644
index 44341d21a8..0000000000
--- a/assets/guide_lxd_precheck.md.445272a6.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as e,v as a,b as t,R as i}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd_precheck.md","filePath":"guide/lxd_precheck.md","lastUpdated":1704976888000}'),l={name:"guide/lxd_precheck.md"},s=i('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
要求 ​
硬件要求:
  • 系统：Debian 8+, Ubuntu 18+(推荐20.04)
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转
项目特点 ​
  • 本套脚本开发使用的Ubuntu20，Ubuntu别的长期维护版本应该也没问题，Debian无法使用zfs时自动切换别的存储类型
  • 已设置同时进行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/spiritLHLS/lxd/main/scripts/pre_check.sh)
国内
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/pre_check.sh)
',16),r=[s];function p(c,o,n,d,h,u){return a(),t("div",null,r)}const m=e(l,[["render",p]]);export{g as __pageData,m as default};
diff --git a/assets/guide_lxd_precheck.md.445272a6.lean.js b/assets/guide_lxd_precheck.md.445272a6.lean.js
deleted file mode 100644
index 44341d21a8..0000000000
--- a/assets/guide_lxd_precheck.md.445272a6.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as e,v as a,b as t,R as i}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd_precheck.md","filePath":"guide/lxd_precheck.md","lastUpdated":1704976888000}'),l={name:"guide/lxd_precheck.md"},s=i('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
要求 ​
硬件要求:
  • 系统：Debian 8+, Ubuntu 18+(推荐20.04)
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转
项目特点 ​
  • 本套脚本开发使用的Ubuntu20，Ubuntu别的长期维护版本应该也没问题，Debian无法使用zfs时自动切换别的存储类型
  • 已设置同时进行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/spiritLHLS/lxd/main/scripts/pre_check.sh)
国内
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/pre_check.sh)
',16),r=[s];function p(c,o,n,d,h,u){return a(),t("div",null,r)}const m=e(l,[["render",p]]);export{g as __pageData,m as default};
diff --git a/assets/guide_lxd_thanks.md.ebfc462d.js b/assets/guide_lxd_thanks.md.ebfc462d.js
deleted file mode 100644
index 375d78311d..0000000000
--- a/assets/guide_lxd_thanks.md.ebfc462d.js
+++ /dev/null
@@ -1 +0,0 @@
-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_thanks.md","filePath":"guide/lxd_thanks.md","lastUpdated":1704976888000}'),n={name:"guide/lxd_thanks.md"},s=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
感谢 @Ella-Alinda @fscarmen 提供的指导
',11),o=[s];function i(c,l,p,h,d,u){return r(),e("div",null,o)}const x=t(n,[["render",i]]);export{g as __pageData,x as default};
diff --git a/assets/guide_lxd_thanks.md.ebfc462d.lean.js b/assets/guide_lxd_thanks.md.ebfc462d.lean.js
deleted file mode 100644
index 375d78311d..0000000000
--- a/assets/guide_lxd_thanks.md.ebfc462d.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-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_thanks.md","filePath":"guide/lxd_thanks.md","lastUpdated":1704976888000}'),n={name:"guide/lxd_thanks.md"},s=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
感谢 @Ella-Alinda @fscarmen 提供的指导
',11),o=[s];function i(c,l,p,h,d,u){return r(),e("div",null,o)}const x=t(n,[["render",i]]);export{g as __pageData,x as default};
diff --git a/assets/guide_pve_install.md.e74a6710.js b/assets/guide_pve_install.md.e74a6710.js
deleted file mode 100644
index a9a3e49ec8..0000000000
--- a/assets/guide_pve_install.md.e74a6710.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as s,v as a,b as l,R as e}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"PVE主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_install.md","filePath":"guide/pve_install.md","lastUpdated":1704976888000}'),p={name:"guide/pve_install.md"},t=e('
PVE主体安装 ​
安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载
一键安装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秒未自重启确保这个安装已运行完毕
若宿主机本身存在SLAAC分配的IPV6地址，将可选择是否使用最大的IPV6子网范围，默认回车不使用最大的IPV6子网范围仅使用本机IPV6，若后续需要给虚拟机/容器附加独立的IPV6地址，该选项务必选择y.
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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命令执行很慢，得等一会才能执行完毕，当然大部分的机器没这么烂
国际
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)
自动配置宿主机的网关 ​
WARNING
使用前请保证重启过服务器且此时PVE能正常使用WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动成功后至少等1分钟再执行本命令
TIP
这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行
TIP
在执行本命令前如果宿主机需要附加IPV6隧道的地址，请查看LXD的自定义分区部分的内容附加到对应文件中，但请忽略它的初始环境修改部分的内容
  • 如果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/spiritLHLS/pve/main/scripts/build_nat_network.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_nat_network.sh)
TIP
这一步是可能需要你执行成功几分钟后重启系统，详见脚本最后执行完毕的提示，但重启可以保证部分隐藏设置加载成功，有条件务必重启一次服务器
',37),o=[t];function n(c,i,r,d,h,C){return a(),l("div",null,o)}const m=s(p,[["render",n]]);export{u as __pageData,m as default};
diff --git a/assets/guide_pve_install.md.e74a6710.lean.js b/assets/guide_pve_install.md.e74a6710.lean.js
deleted file mode 100644
index a9a3e49ec8..0000000000
--- a/assets/guide_pve_install.md.e74a6710.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as s,v as a,b as l,R as e}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"PVE主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_install.md","filePath":"guide/pve_install.md","lastUpdated":1704976888000}'),p={name:"guide/pve_install.md"},t=e('
PVE主体安装 ​
安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载
一键安装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秒未自重启确保这个安装已运行完毕
若宿主机本身存在SLAAC分配的IPV6地址，将可选择是否使用最大的IPV6子网范围，默认回车不使用最大的IPV6子网范围仅使用本机IPV6，若后续需要给虚拟机/容器附加独立的IPV6地址，该选项务必选择y.
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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命令执行很慢，得等一会才能执行完毕，当然大部分的机器没这么烂
国际
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)
自动配置宿主机的网关 ​
WARNING
使用前请保证重启过服务器且此时PVE能正常使用WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动成功后至少等1分钟再执行本命令
TIP
这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行
TIP
在执行本命令前如果宿主机需要附加IPV6隧道的地址，请查看LXD的自定义分区部分的内容附加到对应文件中，但请忽略它的初始环境修改部分的内容
  • 如果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/spiritLHLS/pve/main/scripts/build_nat_network.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_nat_network.sh)
TIP
这一步是可能需要你执行成功几分钟后重启系统，详见脚本最后执行完毕的提示，但重启可以保证部分隐藏设置加载成功，有条件务必重启一次服务器
',37),o=[t];function n(c,i,r,d,h,C){return a(),l("div",null,o)}const m=s(p,[["render",n]]);export{u as __pageData,m as default};
diff --git a/assets/guide_pve_lxc.md.26780811.js b/assets/guide_pve_lxc.md.26780811.js
deleted file mode 100644
index ade6b005fb..0000000000
--- a/assets/guide_pve_lxc.md.26780811.js
+++ /dev/null
@@ -1,12 +0,0 @@
-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/pve_lxc.md","filePath":"guide/pve_lxc.md","lastUpdated":1704976888000}'),p={name:"guide/pve_lxc.md"},o=n(`
LXC虚拟化 ​
单独开设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/spiritLHLS/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
  • 系统支持：
  • debian10，debian11
  • ubuntu18，ubuntu20，ubuntu22
  • centos8，almalinux9
  • 其他系统可能支持可能不支持，自行测试
TIP
系统参数一律是小写的系统名字拼接版本号，x86_64的具体可执行pveam available --section system查看可用的系统名字和版本号，arm的可在https://mirror.tuna.tsinghua.edu.cn/lxc-images/images/中查看支持的系统，版本号类同执行pveam available --section system查看到的版本号。 (注意脚本使用的参数只有小写的英文系统名字拼接版本号)
所有系统的CT默认用户名是root
各参数含义
shell
./buildct.sh CTID 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6(默认为N)
测试示例 ​
shell
./buildct.sh 102 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
开设完毕可执行cat ct102查看信息，或在web端的NOTES查看
以下为开设的示例CT的信息：
属性值
VMID102
SSH登录的用户名root
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小5G
SSH端口20001
80端口20002
443端口20003
内外网映射端口一致的区间30000到30025
系统debian11
宿主机的存储盘local
IPV6无
删除指定容器 ​
  • 停止CT
  • 删除CT
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应CTID的容器，这里用上文中的示例102做演示
shell
./pve_delete.sh 102
实际删除数量不固定，空格分隔每个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/spiritLHLS/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/spiritLHLS/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
-service networking restart
-systemctl restart networking.service
-systemctl restart ndpresponder.service
-iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
-iptables-save > /etc/iptables/rules.v4
开设纯IPV6地址的虚拟机 ​
前提是宿主机给的是IPV6子网而不是单独一个IPV6地址，且宿主机未开启MAC地址校验
自动选择IPV6地址无需手动指定 ​
  • 自动检测可用的IPV6区间，对应容器编号的V6地址绑定到容器上
  • 系统的相关信息将会存储到对应的容器的NOTE中，可在WEB端查看
使用方法 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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盘 (系统盘)
删除示例 ​
shell
rm -rf ct*
-pct stop 152 
-pct destroy 152
-systemctl restart ndpresponder.service
`,63),t=[o];function e(c,r,C,i,y,A){return a(),l("div",null,t)}const h=s(p,[["render",e]]);export{d as __pageData,h as default};
diff --git a/assets/guide_pve_lxc.md.26780811.lean.js b/assets/guide_pve_lxc.md.26780811.lean.js
deleted file mode 100644
index ade6b005fb..0000000000
--- a/assets/guide_pve_lxc.md.26780811.lean.js
+++ /dev/null
@@ -1,12 +0,0 @@
-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/pve_lxc.md","filePath":"guide/pve_lxc.md","lastUpdated":1704976888000}'),p={name:"guide/pve_lxc.md"},o=n(`
LXC虚拟化 ​
单独开设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/spiritLHLS/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
  • 系统支持：
  • debian10，debian11
  • ubuntu18，ubuntu20，ubuntu22
  • centos8，almalinux9
  • 其他系统可能支持可能不支持，自行测试
TIP
系统参数一律是小写的系统名字拼接版本号，x86_64的具体可执行pveam available --section system查看可用的系统名字和版本号，arm的可在https://mirror.tuna.tsinghua.edu.cn/lxc-images/images/中查看支持的系统，版本号类同执行pveam available --section system查看到的版本号。 (注意脚本使用的参数只有小写的英文系统名字拼接版本号)
所有系统的CT默认用户名是root
各参数含义
shell
./buildct.sh CTID 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6(默认为N)
测试示例 ​
shell
./buildct.sh 102 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
开设完毕可执行cat ct102查看信息，或在web端的NOTES查看
以下为开设的示例CT的信息：
属性值
VMID102
SSH登录的用户名root
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小5G
SSH端口20001
80端口20002
443端口20003
内外网映射端口一致的区间30000到30025
系统debian11
宿主机的存储盘local
IPV6无
删除指定容器 ​
  • 停止CT
  • 删除CT
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应CTID的容器，这里用上文中的示例102做演示
shell
./pve_delete.sh 102
实际删除数量不固定，空格分隔每个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/spiritLHLS/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/spiritLHLS/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
-service networking restart
-systemctl restart networking.service
-systemctl restart ndpresponder.service
-iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
-iptables-save > /etc/iptables/rules.v4
开设纯IPV6地址的虚拟机 ​
前提是宿主机给的是IPV6子网而不是单独一个IPV6地址，且宿主机未开启MAC地址校验
自动选择IPV6地址无需手动指定 ​
  • 自动检测可用的IPV6区间，对应容器编号的V6地址绑定到容器上
  • 系统的相关信息将会存储到对应的容器的NOTE中，可在WEB端查看
使用方法 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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盘 (系统盘)
删除示例 ​
shell
rm -rf ct*
-pct stop 152 
-pct destroy 152
-systemctl restart ndpresponder.service
`,63),t=[o];function e(c,r,C,i,y,A){return a(),l("div",null,t)}const h=s(p,[["render",e]]);export{d as __pageData,h as default};
diff --git a/assets/guide_pve_precheck.md.643db164.js b/assets/guide_pve_precheck.md.643db164.js
deleted file mode 100644
index ebb7e46336..0000000000
--- a/assets/guide_pve_precheck.md.643db164.js
+++ /dev/null
@@ -1,3 +0,0 @@
-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/pve_precheck.md","filePath":"guide/pve_precheck.md","lastUpdated":1704976888000}'),n={name:"guide/pve_precheck.md"},e=p(`
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果有未适配的商家或机器欢迎联系@spiritlhl_bot，有空会尝试支持一下
WARNING
会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
各种要求 ​
建议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和全部独服支持)
  • 如果硬件或系统需求不满足，可使用LXD批量开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类型的服务器
  • 不可嵌套虚拟化KVM类型的服务器也可以开LXC虚拟化的服务器，但不推荐安装PVE，不如使用LXD
国际
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/check_kernal.sh)
国内
bash
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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*


`,30),o=[e];function t(c,r,i,C,h,d){return a(),l("div",null,o)}const A=s(n,[["render",t]]);export{D as __pageData,A as default};
diff --git a/assets/guide_pve_precheck.md.643db164.lean.js b/assets/guide_pve_precheck.md.643db164.lean.js
deleted file mode 100644
index ebb7e46336..0000000000
--- a/assets/guide_pve_precheck.md.643db164.lean.js
+++ /dev/null
@@ -1,3 +0,0 @@
-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/pve_precheck.md","filePath":"guide/pve_precheck.md","lastUpdated":1704976888000}'),n={name:"guide/pve_precheck.md"},e=p(`
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果有未适配的商家或机器欢迎联系@spiritlhl_bot，有空会尝试支持一下
WARNING
会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
各种要求 ​
建议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和全部独服支持)
  • 如果硬件或系统需求不满足，可使用LXD批量开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类型的服务器
  • 不可嵌套虚拟化KVM类型的服务器也可以开LXC虚拟化的服务器，但不推荐安装PVE，不如使用LXD
国际
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/check_kernal.sh)
国内
bash
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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*


`,30),o=[e];function t(c,r,i,C,h,d){return a(),l("div",null,o)}const A=s(n,[["render",t]]);export{D as __pageData,A as default};
diff --git a/assets/guide_pve_custom.md.98ac2044.js b/assets/guide_pve_pve_custom.md.e56e03c9.js
similarity index 77%
rename from assets/guide_pve_custom.md.98ac2044.js
rename to assets/guide_pve_pve_custom.md.e56e03c9.js
index 3ed34ed331..b5f474d5eb 100644
--- a/assets/guide_pve_custom.md.98ac2044.js
+++ b/assets/guide_pve_pve_custom.md.e56e03c9.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":"一些自定义脚本","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_custom.md","filePath":"guide/pve_custom.md","lastUpdated":1704976888000}'),p={name:"guide/pve_custom.md"},e=o(`
一些自定义脚本 ​
每个脚本可能有对应的系统要求，自行查看
在非Debian系统上安装 Proxmox VE 7 ​
本机硬件配置的最低要求同先前正常安装的要求一致
需要先安装docker
curl -sSL https://get.docker.com/ | sh
+import{_ as s,v as a,b as n,R as p}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"一些自定义脚本","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_custom.md","filePath":"guide/pve/pve_custom.md","lastUpdated":1705324601000}'),o={name:"guide/pve/pve_custom.md"},e=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 \\
@@ -11,4 +11,4 @@ import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const D=
 --name pve \\
 --add-host pve:10.13.14.101 \\
 --hostname pve \\
-spiritlhl/pve:7_aarch64
开设出的面板实际是开设在容器内的，但网络已使用host模式，PVE的端口约等于就使用的宿主机的端口
有许多错误需要修复，欢迎PR解决问题，实测在Ubuntu系统的宿主机上安装Proxmox VE的面板成功，解决了通过网络安装Proxmox VE只能使用Debian系统做宿主机的问题
`,17),l=[e];function t(c,r,C,i,d,A){return a(),n("div",null,l)}const h=s(p,[["render",t]]);export{D as __pageData,h as default};
+spiritlhl/pve:7_aarch64
开设出的面板实际是开设在容器内的，但网络已使用host模式，PVE的端口约等于就使用的宿主机的端口
有许多错误需要修复，欢迎PR解决问题，实测在Ubuntu系统的宿主机上安装Proxmox VE的面板成功，解决了通过网络安装Proxmox VE只能使用Debian系统做宿主机的问题
`,17),l=[e];function t(c,r,C,i,d,A){return a(),n("div",null,l)}const h=s(o,[["render",t]]);export{D as __pageData,h as default};
diff --git a/assets/guide_pve_custom.md.98ac2044.lean.js b/assets/guide_pve_pve_custom.md.e56e03c9.lean.js
similarity index 77%
rename from assets/guide_pve_custom.md.98ac2044.lean.js
rename to assets/guide_pve_pve_custom.md.e56e03c9.lean.js
index 3ed34ed331..b5f474d5eb 100644
--- a/assets/guide_pve_custom.md.98ac2044.lean.js
+++ b/assets/guide_pve_pve_custom.md.e56e03c9.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":"一些自定义脚本","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_custom.md","filePath":"guide/pve_custom.md","lastUpdated":1704976888000}'),p={name:"guide/pve_custom.md"},e=o(`
一些自定义脚本 ​
每个脚本可能有对应的系统要求，自行查看
在非Debian系统上安装 Proxmox VE 7 ​
本机硬件配置的最低要求同先前正常安装的要求一致
需要先安装docker
curl -sSL https://get.docker.com/ | sh
+import{_ as s,v as a,b as n,R as p}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"一些自定义脚本","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_custom.md","filePath":"guide/pve/pve_custom.md","lastUpdated":1705324601000}'),o={name:"guide/pve/pve_custom.md"},e=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 \\
@@ -11,4 +11,4 @@ import{_ as s,v as a,b as n,R as o}from"./chunks/framework.70afa331.js";const D=
 --name pve \\
 --add-host pve:10.13.14.101 \\
 --hostname pve \\
-spiritlhl/pve:7_aarch64
开设出的面板实际是开设在容器内的，但网络已使用host模式，PVE的端口约等于就使用的宿主机的端口
有许多错误需要修复，欢迎PR解决问题，实测在Ubuntu系统的宿主机上安装Proxmox VE的面板成功，解决了通过网络安装Proxmox VE只能使用Debian系统做宿主机的问题
`,17),l=[e];function t(c,r,C,i,d,A){return a(),n("div",null,l)}const h=s(p,[["render",t]]);export{D as __pageData,h as default};
+spiritlhl/pve:7_aarch64
开设出的面板实际是开设在容器内的，但网络已使用host模式，PVE的端口约等于就使用的宿主机的端口
有许多错误需要修复，欢迎PR解决问题，实测在Ubuntu系统的宿主机上安装Proxmox VE的面板成功，解决了通过网络安装Proxmox VE只能使用Debian系统做宿主机的问题
`,17),l=[e];function t(c,r,C,i,d,A){return a(),n("div",null,l)}const h=s(o,[["render",t]]);export{D as __pageData,h as default};
diff --git a/assets/guide_pve_pve_install.md.b4402647.js b/assets/guide_pve_pve_install.md.b4402647.js
new file mode 100644
index 0000000000..f634470acd
--- /dev/null
+++ b/assets/guide_pve_pve_install.md.b4402647.js
@@ -0,0 +1 @@
+import{_ as s,v as a,b as l,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":1705324601000}'),p={name:"guide/pve/pve_install.md"},t=e('
PVE主体安装 ​
安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载
一键安装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秒未自重启确保这个安装已运行完毕
若宿主机本身存在SLAAC分配的IPV6地址，将可选择是否使用最大的IPV6子网范围，默认回车不使用最大的IPV6子网范围仅使用本机IPV6，若后续需要给虚拟机/容器附加独立的IPV6地址，该选项务必选择y.
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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命令执行很慢，得等一会才能执行完毕，当然大部分的机器没这么烂
国际
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)
自动配置宿主机的网关 ​
WARNING
使用前请保证重启过服务器且此时PVE能正常使用WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动成功后至少等1分钟再执行本命令
TIP
这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行
TIP
在执行本命令前如果宿主机需要附加IPV6隧道的地址，请查看LXD的自定义分区部分的内容附加到对应文件中，但请忽略它的初始环境修改部分的内容
  • 如果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/spiritLHLS/pve/main/scripts/build_nat_network.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_nat_network.sh)
TIP
这一步是可能需要你执行成功几分钟后重启系统，详见脚本最后执行完毕的提示，但重启可以保证部分隐藏设置加载成功，有条件务必重启一次服务器
',37),o=[t];function n(c,i,r,d,h,C){return a(),l("div",null,o)}const m=s(p,[["render",n]]);export{u as __pageData,m as default};
diff --git a/assets/guide_pve_pve_install.md.b4402647.lean.js b/assets/guide_pve_pve_install.md.b4402647.lean.js
new file mode 100644
index 0000000000..f634470acd
--- /dev/null
+++ b/assets/guide_pve_pve_install.md.b4402647.lean.js
@@ -0,0 +1 @@
+import{_ as s,v as a,b as l,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":1705324601000}'),p={name:"guide/pve/pve_install.md"},t=e('
PVE主体安装 ​
安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载
一键安装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秒未自重启确保这个安装已运行完毕
若宿主机本身存在SLAAC分配的IPV6地址，将可选择是否使用最大的IPV6子网范围，默认回车不使用最大的IPV6子网范围仅使用本机IPV6，若后续需要给虚拟机/容器附加独立的IPV6地址，该选项务必选择y.
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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命令执行很慢，得等一会才能执行完毕，当然大部分的机器没这么烂
国际
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)
自动配置宿主机的网关 ​
WARNING
使用前请保证重启过服务器且此时PVE能正常使用WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动成功后至少等1分钟再执行本命令
TIP
这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行
TIP
在执行本命令前如果宿主机需要附加IPV6隧道的地址，请查看LXD的自定义分区部分的内容附加到对应文件中，但请忽略它的初始环境修改部分的内容
  • 如果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/spiritLHLS/pve/main/scripts/build_nat_network.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_nat_network.sh)
TIP
这一步是可能需要你执行成功几分钟后重启系统，详见脚本最后执行完毕的提示，但重启可以保证部分隐藏设置加载成功，有条件务必重启一次服务器
',37),o=[t];function n(c,i,r,d,h,C){return a(),l("div",null,o)}const m=s(p,[["render",n]]);export{u as __pageData,m as default};
diff --git a/assets/guide_pve_kvm.md.0caaabf2.js b/assets/guide_pve_pve_kvm.md.734943ad.js
similarity index 51%
rename from assets/guide_pve_kvm.md.0caaabf2.js
rename to assets/guide_pve_pve_kvm.md.734943ad.js
index f4b2451d85..c0cf1006a2 100644
--- a/assets/guide_pve_kvm.md.0caaabf2.js
+++ b/assets/guide_pve_pve_kvm.md.734943ad.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"KVM虚拟化","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_kvm.md","filePath":"guide/pve_kvm.md","lastUpdated":1704976888000}'),n={name:"guide/pve_kvm.md"},o=p(`
KVM虚拟化 ​
SSH登录说明 ​
KVM虚拟化开设出的虚拟机，默认生成的用户名不是root，你需要执行sudo -i切换为root用户
当然部分模板实际支持用户名root登录，默认的root密码是password，你也可以先试试
登录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]
部分注意事项 ​
执行本项目的检测环境的命令，展示如下
图片
查询如上的只需使用下面的一键脚本自动创建虚拟机即可，无需手动再修改WEB端设置
图片
查询如上的在使用后续脚本创建了虚拟机后，可能需要手动修改WEB端设置，需要关闭对应每个虚拟机的硬件嵌套虚拟化，如下图
图片
先停止虚拟机再修改，修改完后再开机才能使用NOVNC，不关闭可能导致这个虚拟机有BUG无法使用
如果强行安装PVE开KVM，启动不了的也可以关闭这个选项试试能不能启动虚拟机
TIP
开设虚拟机前请使用screen挂起执行，避免开设时间过长，SSH不稳定导致中间执行中断
开设带IPV6地址的KVM虚拟机的注意事项 ​
由于长期闲置IPV6不使用可能导致NDP广播缓存失效重置，一般闲置50分钟左右就会出现IPV6不可用的情况，俗称“IPV6断流”，此时需要设置一个定时任务
shell
echo '*/1 * * * * curl -m 6 -s ipv6.ip.sb && curl -m 6 -s ipv6.ip.sb' | crontab -
在开设出的虚拟机中执行上述命令，可保证IPV6网络一直被使用，不会失效断流
开设KVM虚拟机可使用的镜像 ​
  • 已预安装开启cloudinit
  • 开启SSH登陆
  • 预设置SSH监听V4和V6的22端口
  • 开启允许密码验证登陆
  • 开启允许root登陆
  • 部分预安装Qemu-guest-agent
目前可使用的镜像名字的列表为
https://github.com/oneclickvirt/kvm_images/blob/main/list.text
单独开设NAT的KVM虚拟化的虚拟机 ​
  • 自动开设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/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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 102 test1 oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
开设完毕可执行cat vm102查看信息，或到WEB端对应VM的NOTES中查看
以下为开设的示例VM的信息：
属性值
VMID102
SSH登录的用户名test1
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小10G
SSH端口40001
80端口40002
443端口40003
内外网映射端口一致的区间50000到50025
系统debian11
宿主机的存储盘local
绑定独立IPV6(留空默认N)N
删除指定虚拟机 ​
  • 停止VM
  • 删除VM
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应VMID的虚拟机，这里用上文中的示例102做演示
shell
./pve_delete.sh 102
实际删除数量不固定，空格分隔每个VMID即可，可一次性删除多个
批量开设NAT的KVM虚拟化的虚拟机 ​
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/spiritLHLS/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/spiritLHLS/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 a,b as l,R as p}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"KVM虚拟化","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_kvm.md","filePath":"guide/pve/pve_kvm.md","lastUpdated":1705324601000}'),n={name:"guide/pve/pve_kvm.md"},o=p(`
KVM虚拟化 ​
SSH登录说明 ​
KVM虚拟化开设出的虚拟机，默认生成的用户名不是root，你需要执行sudo -i切换为root用户
当然部分模板实际支持用户名root登录，默认的root密码是password，你也可以先试试
登录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]
部分注意事项 ​
执行本项目的检测环境的命令，展示如下
图片
查询如上的只需使用下面的一键脚本自动创建虚拟机即可，无需手动再修改WEB端设置
图片
查询如上的在使用后续脚本创建了虚拟机后，可能需要手动修改WEB端设置，需要关闭对应每个虚拟机的硬件嵌套虚拟化，如下图
图片
先停止虚拟机再修改，修改完后再开机才能使用NOVNC，不关闭可能导致这个虚拟机有BUG无法使用
如果强行安装PVE开KVM，启动不了的也可以关闭这个选项试试能不能启动虚拟机
TIP
开设虚拟机前请使用screen挂起执行，避免开设时间过长，SSH不稳定导致中间执行中断
开设带IPV6地址的KVM虚拟机的注意事项 ​
由于长期闲置IPV6不使用可能导致NDP广播缓存失效重置，一般闲置50分钟左右就会出现IPV6不可用的情况，俗称“IPV6断流”，此时需要设置一个定时任务
shell
echo '*/1 * * * * curl -m 6 -s ipv6.ip.sb && curl -m 6 -s ipv6.ip.sb' | crontab -
在开设出的虚拟机中执行上述命令，可保证IPV6网络一直被使用，不会失效断流
开设KVM虚拟机可使用的镜像 ​
  • 已预安装开启cloudinit
  • 开启SSH登陆
  • 预设置SSH监听V4和V6的22端口
  • 开启允许密码验证登陆
  • 开启允许root登陆
  • 部分预安装Qemu-guest-agent
目前可使用的镜像名字的列表为
https://github.com/oneclickvirt/kvm_images/blob/main/list.text
单独开设NAT的KVM虚拟化的虚拟机 ​
  • 自动开设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/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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 102 test1 oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
开设完毕可执行cat vm102查看信息，或到WEB端对应VM的NOTES中查看
以下为开设的示例VM的信息：
属性值
VMID102
SSH登录的用户名test1
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小10G
SSH端口40001
80端口40002
443端口40003
内外网映射端口一致的区间50000到50025
系统debian11
宿主机的存储盘local
绑定独立IPV6(留空默认N)N
删除指定虚拟机 ​
  • 停止VM
  • 删除VM
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应VMID的虚拟机，这里用上文中的示例102做演示
shell
./pve_delete.sh 102
实际删除数量不固定，空格分隔每个VMID即可，可一次性删除多个
批量开设NAT的KVM虚拟化的虚拟机 ​
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/spiritLHLS/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/spiritLHLS/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_kvm.md.0caaabf2.lean.js b/assets/guide_pve_pve_kvm.md.734943ad.lean.js
similarity index 51%
rename from assets/guide_pve_kvm.md.0caaabf2.lean.js
rename to assets/guide_pve_pve_kvm.md.734943ad.lean.js
index f4b2451d85..c0cf1006a2 100644
--- a/assets/guide_pve_kvm.md.0caaabf2.lean.js
+++ b/assets/guide_pve_pve_kvm.md.734943ad.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"KVM虚拟化","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_kvm.md","filePath":"guide/pve_kvm.md","lastUpdated":1704976888000}'),n={name:"guide/pve_kvm.md"},o=p(`
KVM虚拟化 ​
SSH登录说明 ​
KVM虚拟化开设出的虚拟机，默认生成的用户名不是root，你需要执行sudo -i切换为root用户
当然部分模板实际支持用户名root登录，默认的root密码是password，你也可以先试试
登录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]
部分注意事项 ​
执行本项目的检测环境的命令，展示如下
图片
查询如上的只需使用下面的一键脚本自动创建虚拟机即可，无需手动再修改WEB端设置
图片
查询如上的在使用后续脚本创建了虚拟机后，可能需要手动修改WEB端设置，需要关闭对应每个虚拟机的硬件嵌套虚拟化，如下图
图片
先停止虚拟机再修改，修改完后再开机才能使用NOVNC，不关闭可能导致这个虚拟机有BUG无法使用
如果强行安装PVE开KVM，启动不了的也可以关闭这个选项试试能不能启动虚拟机
TIP
开设虚拟机前请使用screen挂起执行，避免开设时间过长，SSH不稳定导致中间执行中断
开设带IPV6地址的KVM虚拟机的注意事项 ​
由于长期闲置IPV6不使用可能导致NDP广播缓存失效重置，一般闲置50分钟左右就会出现IPV6不可用的情况，俗称“IPV6断流”，此时需要设置一个定时任务
shell
echo '*/1 * * * * curl -m 6 -s ipv6.ip.sb && curl -m 6 -s ipv6.ip.sb' | crontab -
在开设出的虚拟机中执行上述命令，可保证IPV6网络一直被使用，不会失效断流
开设KVM虚拟机可使用的镜像 ​
  • 已预安装开启cloudinit
  • 开启SSH登陆
  • 预设置SSH监听V4和V6的22端口
  • 开启允许密码验证登陆
  • 开启允许root登陆
  • 部分预安装Qemu-guest-agent
目前可使用的镜像名字的列表为
https://github.com/oneclickvirt/kvm_images/blob/main/list.text
单独开设NAT的KVM虚拟化的虚拟机 ​
  • 自动开设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/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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 102 test1 oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
开设完毕可执行cat vm102查看信息，或到WEB端对应VM的NOTES中查看
以下为开设的示例VM的信息：
属性值
VMID102
SSH登录的用户名test1
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小10G
SSH端口40001
80端口40002
443端口40003
内外网映射端口一致的区间50000到50025
系统debian11
宿主机的存储盘local
绑定独立IPV6(留空默认N)N
删除指定虚拟机 ​
  • 停止VM
  • 删除VM
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应VMID的虚拟机，这里用上文中的示例102做演示
shell
./pve_delete.sh 102
实际删除数量不固定，空格分隔每个VMID即可，可一次性删除多个
批量开设NAT的KVM虚拟化的虚拟机 ​
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/spiritLHLS/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/spiritLHLS/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 a,b as l,R as p}from"./chunks/framework.70afa331.js";const A=JSON.parse('{"title":"KVM虚拟化","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_kvm.md","filePath":"guide/pve/pve_kvm.md","lastUpdated":1705324601000}'),n={name:"guide/pve/pve_kvm.md"},o=p(`
KVM虚拟化 ​
SSH登录说明 ​
KVM虚拟化开设出的虚拟机，默认生成的用户名不是root，你需要执行sudo -i切换为root用户
当然部分模板实际支持用户名root登录，默认的root密码是password，你也可以先试试
登录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]
部分注意事项 ​
执行本项目的检测环境的命令，展示如下
图片
查询如上的只需使用下面的一键脚本自动创建虚拟机即可，无需手动再修改WEB端设置
图片
查询如上的在使用后续脚本创建了虚拟机后，可能需要手动修改WEB端设置，需要关闭对应每个虚拟机的硬件嵌套虚拟化，如下图
图片
先停止虚拟机再修改，修改完后再开机才能使用NOVNC，不关闭可能导致这个虚拟机有BUG无法使用
如果强行安装PVE开KVM，启动不了的也可以关闭这个选项试试能不能启动虚拟机
TIP
开设虚拟机前请使用screen挂起执行，避免开设时间过长，SSH不稳定导致中间执行中断
开设带IPV6地址的KVM虚拟机的注意事项 ​
由于长期闲置IPV6不使用可能导致NDP广播缓存失效重置，一般闲置50分钟左右就会出现IPV6不可用的情况，俗称“IPV6断流”，此时需要设置一个定时任务
shell
echo '*/1 * * * * curl -m 6 -s ipv6.ip.sb && curl -m 6 -s ipv6.ip.sb' | crontab -
在开设出的虚拟机中执行上述命令，可保证IPV6网络一直被使用，不会失效断流
开设KVM虚拟机可使用的镜像 ​
  • 已预安装开启cloudinit
  • 开启SSH登陆
  • 预设置SSH监听V4和V6的22端口
  • 开启允许密码验证登陆
  • 开启允许root登陆
  • 部分预安装Qemu-guest-agent
目前可使用的镜像名字的列表为
https://github.com/oneclickvirt/kvm_images/blob/main/list.text
单独开设NAT的KVM虚拟化的虚拟机 ​
  • 自动开设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/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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 102 test1 oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
开设完毕可执行cat vm102查看信息，或到WEB端对应VM的NOTES中查看
以下为开设的示例VM的信息：
属性值
VMID102
SSH登录的用户名test1
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小10G
SSH端口40001
80端口40002
443端口40003
内外网映射端口一致的区间50000到50025
系统debian11
宿主机的存储盘local
绑定独立IPV6(留空默认N)N
删除指定虚拟机 ​
  • 停止VM
  • 删除VM
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应VMID的虚拟机，这里用上文中的示例102做演示
shell
./pve_delete.sh 102
实际删除数量不固定，空格分隔每个VMID即可，可一次性删除多个
批量开设NAT的KVM虚拟化的虚拟机 ​
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/spiritLHLS/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/spiritLHLS/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.3673dc07.js b/assets/guide_pve_pve_lxc.md.3673dc07.js
new file mode 100644
index 0000000000..18827fa230
--- /dev/null
+++ b/assets/guide_pve_pve_lxc.md.3673dc07.js
@@ -0,0 +1,12 @@
+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/pve/pve_lxc.md","filePath":"guide/pve/pve_lxc.md","lastUpdated":1705324601000}'),p={name:"guide/pve/pve_lxc.md"},o=n(`
LXC虚拟化 ​
单独开设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/spiritLHLS/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
  • 系统支持：
  • debian10，debian11
  • ubuntu18，ubuntu20，ubuntu22
  • centos8，almalinux9
  • 其他系统可能支持可能不支持，自行测试
TIP
系统参数一律是小写的系统名字拼接版本号，x86_64的具体可执行pveam available --section system查看可用的系统名字和版本号，arm的可在https://mirror.tuna.tsinghua.edu.cn/lxc-images/images/中查看支持的系统，版本号类同执行pveam available --section system查看到的版本号。 (注意脚本使用的参数只有小写的英文系统名字拼接版本号)
所有系统的CT默认用户名是root
各参数含义
shell
./buildct.sh CTID 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6(默认为N)
测试示例 ​
shell
./buildct.sh 102 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
开设完毕可执行cat ct102查看信息，或在web端的NOTES查看
以下为开设的示例CT的信息：
属性值
VMID102
SSH登录的用户名root
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小5G
SSH端口20001
80端口20002
443端口20003
内外网映射端口一致的区间30000到30025
系统debian11
宿主机的存储盘local
IPV6无
删除指定容器 ​
  • 停止CT
  • 删除CT
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应CTID的容器，这里用上文中的示例102做演示
shell
./pve_delete.sh 102
实际删除数量不固定，空格分隔每个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/spiritLHLS/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/spiritLHLS/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
+service networking restart
+systemctl restart networking.service
+systemctl restart ndpresponder.service
+iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
+iptables-save > /etc/iptables/rules.v4
开设纯IPV6地址的虚拟机 ​
前提是宿主机给的是IPV6子网而不是单独一个IPV6地址，且宿主机未开启MAC地址校验
自动选择IPV6地址无需手动指定 ​
  • 自动检测可用的IPV6区间，对应容器编号的V6地址绑定到容器上
  • 系统的相关信息将会存储到对应的容器的NOTE中，可在WEB端查看
使用方法 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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盘 (系统盘)
删除示例 ​
shell
rm -rf ct*
+pct stop 152 
+pct destroy 152
+systemctl restart ndpresponder.service
`,63),t=[o];function e(c,r,C,i,y,A){return a(),l("div",null,t)}const h=s(p,[["render",e]]);export{d as __pageData,h as default};
diff --git a/assets/guide_pve_pve_lxc.md.3673dc07.lean.js b/assets/guide_pve_pve_lxc.md.3673dc07.lean.js
new file mode 100644
index 0000000000..18827fa230
--- /dev/null
+++ b/assets/guide_pve_pve_lxc.md.3673dc07.lean.js
@@ -0,0 +1,12 @@
+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/pve/pve_lxc.md","filePath":"guide/pve/pve_lxc.md","lastUpdated":1705324601000}'),p={name:"guide/pve/pve_lxc.md"},o=n(`
LXC虚拟化 ​
单独开设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/spiritLHLS/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
  • 系统支持：
  • debian10，debian11
  • ubuntu18，ubuntu20，ubuntu22
  • centos8，almalinux9
  • 其他系统可能支持可能不支持，自行测试
TIP
系统参数一律是小写的系统名字拼接版本号，x86_64的具体可执行pveam available --section system查看可用的系统名字和版本号，arm的可在https://mirror.tuna.tsinghua.edu.cn/lxc-images/images/中查看支持的系统，版本号类同执行pveam available --section system查看到的版本号。 (注意脚本使用的参数只有小写的英文系统名字拼接版本号)
所有系统的CT默认用户名是root
各参数含义
shell
./buildct.sh CTID 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6(默认为N)
测试示例 ​
shell
./buildct.sh 102 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
开设完毕可执行cat ct102查看信息，或在web端的NOTES查看
以下为开设的示例CT的信息：
属性值
VMID102
SSH登录的用户名root
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小5G
SSH端口20001
80端口20002
443端口20003
内外网映射端口一致的区间30000到30025
系统debian11
宿主机的存储盘local
IPV6无
删除指定容器 ​
  • 停止CT
  • 删除CT
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应CTID的容器，这里用上文中的示例102做演示
shell
./pve_delete.sh 102
实际删除数量不固定，空格分隔每个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/spiritLHLS/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/spiritLHLS/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
+service networking restart
+systemctl restart networking.service
+systemctl restart ndpresponder.service
+iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
+iptables-save > /etc/iptables/rules.v4
开设纯IPV6地址的虚拟机 ​
前提是宿主机给的是IPV6子网而不是单独一个IPV6地址，且宿主机未开启MAC地址校验
自动选择IPV6地址无需手动指定 ​
  • 自动检测可用的IPV6区间，对应容器编号的V6地址绑定到容器上
  • 系统的相关信息将会存储到对应的容器的NOTE中，可在WEB端查看
使用方法 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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盘 (系统盘)
删除示例 ​
shell
rm -rf ct*
+pct stop 152 
+pct destroy 152
+systemctl restart ndpresponder.service
`,63),t=[o];function e(c,r,C,i,y,A){return a(),l("div",null,t)}const h=s(p,[["render",e]]);export{d as __pageData,h as default};
diff --git a/assets/guide_pve_pve_precheck.md.432bb77d.js b/assets/guide_pve_pve_precheck.md.432bb77d.js
new file mode 100644
index 0000000000..c2878126f6
--- /dev/null
+++ b/assets/guide_pve_pve_precheck.md.432bb77d.js
@@ -0,0 +1,3 @@
+import{_ as s,v as a,b as p,R as l}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_precheck.md","filePath":"guide/pve/pve_precheck.md","lastUpdated":1705324601000}'),n={name:"guide/pve/pve_precheck.md"},e=l(`
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果有未适配的商家或机器欢迎联系@spiritlhl_bot，有空会尝试支持一下
WARNING
会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
各种要求 ​
建议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和全部独服支持)
  • 如果硬件或系统需求不满足，可使用LXD批量开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类型的服务器
  • 不可嵌套虚拟化KVM类型的服务器也可以开LXC虚拟化的服务器，但不推荐安装PVE，不如使用LXD
国际
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/check_kernal.sh)
国内
bash
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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*


`,30),o=[e];function t(c,r,i,C,h,d){return a(),p("div",null,o)}const A=s(n,[["render",t]]);export{D as __pageData,A as default};
diff --git a/assets/guide_pve_pve_precheck.md.432bb77d.lean.js b/assets/guide_pve_pve_precheck.md.432bb77d.lean.js
new file mode 100644
index 0000000000..c2878126f6
--- /dev/null
+++ b/assets/guide_pve_pve_precheck.md.432bb77d.lean.js
@@ -0,0 +1,3 @@
+import{_ as s,v as a,b as p,R as l}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_precheck.md","filePath":"guide/pve/pve_precheck.md","lastUpdated":1705324601000}'),n={name:"guide/pve/pve_precheck.md"},e=l(`
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果有未适配的商家或机器欢迎联系@spiritlhl_bot，有空会尝试支持一下
WARNING
会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
各种要求 ​
建议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和全部独服支持)
  • 如果硬件或系统需求不满足，可使用LXD批量开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类型的服务器
  • 不可嵌套虚拟化KVM类型的服务器也可以开LXC虚拟化的服务器，但不推荐安装PVE，不如使用LXD
国际
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/check_kernal.sh)
国内
bash
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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*


`,30),o=[e];function t(c,r,i,C,h,d){return a(),p("div",null,o)}const A=s(n,[["render",t]]);export{D as __pageData,A as default};
diff --git a/assets/guide_pve_qa.md.c3f65060.js b/assets/guide_pve_pve_qa.md.3fd9c3b0.js
similarity index 80%
rename from assets/guide_pve_qa.md.c3f65060.js
rename to assets/guide_pve_pve_qa.md.3fd9c3b0.js
index e4e6fcaf21..4b39db45fe 100644
--- a/assets/guide_pve_qa.md.c3f65060.js
+++ b/assets/guide_pve_pve_qa.md.3fd9c3b0.js
@@ -1,4 +1,4 @@
-import{_ as a,v as s,b as e,R as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_qa.md","filePath":"guide/pve_qa.md","lastUpdated":1704976888000}'),t={name:"guide/pve_qa.md"},l=n(`
解惑 ​
执行脚本不到30秒机器就掉线了 ​
原装系统执行
systemctl restart networking
看看是不是直接掉线，如果是那就是机器原生有问题，热插拔或者dhcp导致的网络无法自重启，此时建议更换宿主机的系统或DD一个新系统尝试
一般来说这种情况都是出现在独服的Debian11系统上，切换为Debian12系统就没问题了
安装PVE成功但重启后失联 ​
如果什么机器安装PVE成功后WEB可用，但重启失联，请安装成功PVE后，重启前执行以下命令再重启
bash
auto_interface=$(grep '^auto ' /etc/network/interfaces | grep -v '^auto lo' | awk '{print $2}' | head -n 1)
+import{_ as a,v as s,b as e,R as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_qa.md","filePath":"guide/pve/pve_qa.md","lastUpdated":1705324601000}'),t={name:"guide/pve/pve_qa.md"},l=n(`
解惑 ​
执行脚本不到30秒机器就掉线了 ​
原装系统执行
systemctl restart networking
看看是不是直接掉线，如果是那就是机器原生有问题，热插拔或者dhcp导致的网络无法自重启，此时建议更换宿主机的系统或DD一个新系统尝试
一般来说这种情况都是出现在独服的Debian11系统上，切换为Debian12系统就没问题了
安装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
     echo "post-up /sbin/ethtool -K $auto_interface tx off rx off" >> /etc/network/interfaces
@@ -7,4 +7,4 @@ import{_ as a,v as s,b as e,R as n}from"./chunks/framework.70afa331.js";const d=
 iptables -t filter -F
 service networking restart
 systemctl restart networking.service
-cat /etc/iptables/rules.v4 | iptables-restore
目前已验证的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 中的 俄罗斯和希腊 测试款
hostaris 中的 德国款 (商家的系统模板有问题，IPV6已失效和Github的连通稳定性很差)
adtaq 中的最低配存储KVM服务器
nocix 中的独立服务器
crunchbits 中的VPS
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
只可开设LXC虚拟化的NAT的商家 ​
腾讯云 中的无忧款和特惠款(学生机)
spectraip 中的KVM服务器
Linode 中美国专用CPU的最低配
hosthatch 中的特价高配服务器
hetzner 的cloud服务器
rackdog 的浮动IP的服务器
vultr 的Cloud普通服务器
azure 的普通机器
scaleway 中的ARM架构的服务器
aws 中的ec2实例
Google cloud platform - GCP 的 AMD 服务器
`,59),o=[l];function r(p,c,i,h,C,y){return s(),e("div",null,o)}const f=a(t,[["render",r]]);export{d as __pageData,f as default};
+cat /etc/iptables/rules.v4 | iptables-restore
目前已验证的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 中的 俄罗斯和希腊 测试款
hostaris 中的 德国款 (商家的系统模板有问题，IPV6已失效和Github的连通稳定性很差)
adtaq 中的最低配存储KVM服务器
nocix 中的独立服务器
crunchbits 中的VPS
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
只可开设LXC虚拟化的NAT的商家 ​
腾讯云 中的无忧款和特惠款(学生机)
spectraip 中的KVM服务器
Linode 中美国专用CPU的最低配
hosthatch 中的特价高配服务器
hetzner 的cloud服务器
rackdog 的浮动IP的服务器
vultr 的Cloud普通服务器
azure 的普通机器
scaleway 中的ARM架构的服务器
aws 中的ec2实例
Google cloud platform - GCP 的 AMD 服务器
`,59),o=[l];function p(r,c,i,h,C,y){return s(),e("div",null,o)}const f=a(t,[["render",p]]);export{d as __pageData,f as default};
diff --git a/assets/guide_pve_qa.md.c3f65060.lean.js b/assets/guide_pve_pve_qa.md.3fd9c3b0.lean.js
similarity index 80%
rename from assets/guide_pve_qa.md.c3f65060.lean.js
rename to assets/guide_pve_pve_qa.md.3fd9c3b0.lean.js
index e4e6fcaf21..4b39db45fe 100644
--- a/assets/guide_pve_qa.md.c3f65060.lean.js
+++ b/assets/guide_pve_pve_qa.md.3fd9c3b0.lean.js
@@ -1,4 +1,4 @@
-import{_ as a,v as s,b as e,R as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_qa.md","filePath":"guide/pve_qa.md","lastUpdated":1704976888000}'),t={name:"guide/pve_qa.md"},l=n(`
解惑 ​
执行脚本不到30秒机器就掉线了 ​
原装系统执行
systemctl restart networking
看看是不是直接掉线，如果是那就是机器原生有问题，热插拔或者dhcp导致的网络无法自重启，此时建议更换宿主机的系统或DD一个新系统尝试
一般来说这种情况都是出现在独服的Debian11系统上，切换为Debian12系统就没问题了
安装PVE成功但重启后失联 ​
如果什么机器安装PVE成功后WEB可用，但重启失联，请安装成功PVE后，重启前执行以下命令再重启
bash
auto_interface=$(grep '^auto ' /etc/network/interfaces | grep -v '^auto lo' | awk '{print $2}' | head -n 1)
+import{_ as a,v as s,b as e,R as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve/pve_qa.md","filePath":"guide/pve/pve_qa.md","lastUpdated":1705324601000}'),t={name:"guide/pve/pve_qa.md"},l=n(`
解惑 ​
执行脚本不到30秒机器就掉线了 ​
原装系统执行
systemctl restart networking
看看是不是直接掉线，如果是那就是机器原生有问题，热插拔或者dhcp导致的网络无法自重启，此时建议更换宿主机的系统或DD一个新系统尝试
一般来说这种情况都是出现在独服的Debian11系统上，切换为Debian12系统就没问题了
安装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
     echo "post-up /sbin/ethtool -K $auto_interface tx off rx off" >> /etc/network/interfaces
@@ -7,4 +7,4 @@ import{_ as a,v as s,b as e,R as n}from"./chunks/framework.70afa331.js";const d=
 iptables -t filter -F
 service networking restart
 systemctl restart networking.service
-cat /etc/iptables/rules.v4 | iptables-restore
目前已验证的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 中的 俄罗斯和希腊 测试款
hostaris 中的 德国款 (商家的系统模板有问题，IPV6已失效和Github的连通稳定性很差)
adtaq 中的最低配存储KVM服务器
nocix 中的独立服务器
crunchbits 中的VPS
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
只可开设LXC虚拟化的NAT的商家 ​
腾讯云 中的无忧款和特惠款(学生机)
spectraip 中的KVM服务器
Linode 中美国专用CPU的最低配
hosthatch 中的特价高配服务器
hetzner 的cloud服务器
rackdog 的浮动IP的服务器
vultr 的Cloud普通服务器
azure 的普通机器
scaleway 中的ARM架构的服务器
aws 中的ec2实例
Google cloud platform - GCP 的 AMD 服务器
`,59),o=[l];function r(p,c,i,h,C,y){return s(),e("div",null,o)}const f=a(t,[["render",r]]);export{d as __pageData,f as default};
+cat /etc/iptables/rules.v4 | iptables-restore
目前已验证的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 中的 俄罗斯和希腊 测试款
hostaris 中的 德国款 (商家的系统模板有问题，IPV6已失效和Github的连通稳定性很差)
adtaq 中的最低配存储KVM服务器
nocix 中的独立服务器
crunchbits 中的VPS
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
只可开设LXC虚拟化的NAT的商家 ​
腾讯云 中的无忧款和特惠款(学生机)
spectraip 中的KVM服务器
Linode 中美国专用CPU的最低配
hosthatch 中的特价高配服务器
hetzner 的cloud服务器
rackdog 的浮动IP的服务器
vultr 的Cloud普通服务器
azure 的普通机器
scaleway 中的ARM架构的服务器
aws 中的ec2实例
Google cloud platform - GCP 的 AMD 服务器
`,59),o=[l];function p(r,c,i,h,C,y){return s(),e("div",null,o)}const f=a(t,[["render",p]]);export{d as __pageData,f as default};
diff --git a/assets/guide_pve_pve_thanks.md.ac66d82b.js b/assets/guide_pve_pve_thanks.md.ac66d82b.js
new file mode 100644
index 0000000000..d9c96e5154
--- /dev/null
+++ b/assets/guide_pve_pve_thanks.md.ac66d82b.js
@@ -0,0 +1 @@
+import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/pve/pve_thanks.md","filePath":"guide/pve/pve_thanks.md","lastUpdated":1705324601000}'),o={name:"guide/pve/pve_thanks.md"},p=a('
致谢 ​
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-Arm64
https://github.com/jiangcuo/run_proxmox_in_docker
https://github.com/yoursunny/ndpresponder
https://github.com/SuperManito/LinuxMirrors
感谢 @Ella-Alinda 提供的PVE指导
',15),n=[p];function s(h,i,l,m,c,u){return e(),t("div",null,n)}const f=r(o,[["render",s]]);export{g as __pageData,f as default};
diff --git a/assets/guide_pve_pve_thanks.md.ac66d82b.lean.js b/assets/guide_pve_pve_thanks.md.ac66d82b.lean.js
new file mode 100644
index 0000000000..d9c96e5154
--- /dev/null
+++ b/assets/guide_pve_pve_thanks.md.ac66d82b.lean.js
@@ -0,0 +1 @@
+import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/pve/pve_thanks.md","filePath":"guide/pve/pve_thanks.md","lastUpdated":1705324601000}'),o={name:"guide/pve/pve_thanks.md"},p=a('
致谢 ​
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-Arm64
https://github.com/jiangcuo/run_proxmox_in_docker
https://github.com/yoursunny/ndpresponder
https://github.com/SuperManito/LinuxMirrors
感谢 @Ella-Alinda 提供的PVE指导
',15),n=[p];function s(h,i,l,m,c,u){return e(),t("div",null,n)}const f=r(o,[["render",s]]);export{g as __pageData,f as default};
diff --git a/assets/guide_pve_thanks.md.d651a824.js b/assets/guide_pve_thanks.md.d651a824.js
deleted file mode 100644
index 63f2d8c5de..0000000000
--- a/assets/guide_pve_thanks.md.d651a824.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/pve_thanks.md","filePath":"guide/pve_thanks.md","lastUpdated":1704976888000}'),o={name:"guide/pve_thanks.md"},p=a('
致谢 ​
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-Arm64
https://github.com/jiangcuo/run_proxmox_in_docker
https://github.com/yoursunny/ndpresponder
https://github.com/SuperManito/LinuxMirrors
感谢 @Ella-Alinda 提供的PVE指导
',15),n=[p];function s(h,i,l,m,c,u){return e(),t("div",null,n)}const f=r(o,[["render",s]]);export{g as __pageData,f as default};
diff --git a/assets/guide_pve_thanks.md.d651a824.lean.js b/assets/guide_pve_thanks.md.d651a824.lean.js
deleted file mode 100644
index 63f2d8c5de..0000000000
--- a/assets/guide_pve_thanks.md.d651a824.lean.js
+++ /dev/null
@@ -1 +0,0 @@
-import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/pve_thanks.md","filePath":"guide/pve_thanks.md","lastUpdated":1704976888000}'),o={name:"guide/pve_thanks.md"},p=a('
致谢 ​
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-Arm64
https://github.com/jiangcuo/run_proxmox_in_docker
https://github.com/yoursunny/ndpresponder
https://github.com/SuperManito/LinuxMirrors
感谢 @Ella-Alinda 提供的PVE指导
',15),n=[p];function s(h,i,l,m,c,u){return e(),t("div",null,n)}const f=r(o,[["render",s]]);export{g as __pageData,f as default};
diff --git a/assets/index.md.d15aa3da.js b/assets/index.md.c691cce5.js
similarity index 96%
rename from assets/index.md.d15aa3da.js
rename to assets/index.md.c691cce5.js
index 4b2d8ea43f..aa27790e31 100644
--- a/assets/index.md.d15aa3da.js
+++ b/assets/index.md.c691cce5.js
@@ -1 +1 @@
-import{_ as t,v as e,b as a}from"./chunks/framework.70afa331.js";const c=JSON.parse('{"title":"库苏恩","titleTemplate":"一键虚拟化项目","description":"","frontmatter":{"layout":"home","title":"库苏恩","titleTemplate":"一键虚拟化项目","tagline":"开源、易于使用的服务器虚拟化项目","hero":{"name":"一键虚拟化项目","text":"开源、易于使用的服务器虚拟化项目","image":"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地址自动分配，含TCP、UDP、VNC、RDP等协议，无需人工管理"},{"title":"批量虚拟化","details":"支持使用 KVM、LXC、Docker 虚拟化批量开设容器或虚拟机"},{"title":"多系统多环境支持","details":"开设出的容器或虚拟机已支持主流系统，涵盖 Linux、Android、Windows 系统，也支持纯粹的浏览器环境或桌面环境"},{"title":"自限制滥用","details":"部分虚拟化开设的容器或虚拟机支持设置屏蔽和装载限制，避免被用于滥用"}]},"headers":[],"relativePath":"index.md","filePath":"index.md","lastUpdated":1704976888000}'),i={name:"index.md"};function s(n,d,l,o,r,p){return e(),a("div")}const u=t(i,[["render",s]]);export{c as __pageData,u as default};
+import{_ as t,v as e,b as a}from"./chunks/framework.70afa331.js";const c=JSON.parse('{"title":"库苏恩","titleTemplate":"一键虚拟化项目","description":"","frontmatter":{"layout":"home","title":"库苏恩","titleTemplate":"一键虚拟化项目","tagline":"开源、易于使用的服务器虚拟化项目","hero":{"name":"一键虚拟化项目","text":"开源、易于使用的服务器虚拟化项目","image":"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地址自动分配，含TCP、UDP、VNC、RDP等协议，无需人工管理"},{"title":"批量虚拟化","details":"支持使用 KVM、LXC、Docker 虚拟化批量开设容器或虚拟机"},{"title":"多系统多环境支持","details":"开设出的容器或虚拟机已支持主流系统，涵盖 Linux、Android、Windows 系统，也支持纯粹的浏览器环境或桌面环境"},{"title":"自限制滥用","details":"部分虚拟化开设的容器或虚拟机支持设置屏蔽和装载限制，避免被用于滥用"}]},"headers":[],"relativePath":"index.md","filePath":"index.md","lastUpdated":1705324601000}'),i={name:"index.md"};function s(n,d,l,o,r,p){return e(),a("div")}const u=t(i,[["render",s]]);export{c as __pageData,u as default};
diff --git a/assets/index.md.d15aa3da.lean.js b/assets/index.md.c691cce5.lean.js
similarity index 96%
rename from assets/index.md.d15aa3da.lean.js
rename to assets/index.md.c691cce5.lean.js
index 4b2d8ea43f..aa27790e31 100644
--- a/assets/index.md.d15aa3da.lean.js
+++ b/assets/index.md.c691cce5.lean.js
@@ -1 +1 @@
-import{_ as t,v as e,b as a}from"./chunks/framework.70afa331.js";const c=JSON.parse('{"title":"库苏恩","titleTemplate":"一键虚拟化项目","description":"","frontmatter":{"layout":"home","title":"库苏恩","titleTemplate":"一键虚拟化项目","tagline":"开源、易于使用的服务器虚拟化项目","hero":{"name":"一键虚拟化项目","text":"开源、易于使用的服务器虚拟化项目","image":"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地址自动分配，含TCP、UDP、VNC、RDP等协议，无需人工管理"},{"title":"批量虚拟化","details":"支持使用 KVM、LXC、Docker 虚拟化批量开设容器或虚拟机"},{"title":"多系统多环境支持","details":"开设出的容器或虚拟机已支持主流系统，涵盖 Linux、Android、Windows 系统，也支持纯粹的浏览器环境或桌面环境"},{"title":"自限制滥用","details":"部分虚拟化开设的容器或虚拟机支持设置屏蔽和装载限制，避免被用于滥用"}]},"headers":[],"relativePath":"index.md","filePath":"index.md","lastUpdated":1704976888000}'),i={name:"index.md"};function s(n,d,l,o,r,p){return e(),a("div")}const u=t(i,[["render",s]]);export{c as __pageData,u as default};
+import{_ as t,v as e,b as a}from"./chunks/framework.70afa331.js";const c=JSON.parse('{"title":"库苏恩","titleTemplate":"一键虚拟化项目","description":"","frontmatter":{"layout":"home","title":"库苏恩","titleTemplate":"一键虚拟化项目","tagline":"开源、易于使用的服务器虚拟化项目","hero":{"name":"一键虚拟化项目","text":"开源、易于使用的服务器虚拟化项目","image":"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地址自动分配，含TCP、UDP、VNC、RDP等协议，无需人工管理"},{"title":"批量虚拟化","details":"支持使用 KVM、LXC、Docker 虚拟化批量开设容器或虚拟机"},{"title":"多系统多环境支持","details":"开设出的容器或虚拟机已支持主流系统，涵盖 Linux、Android、Windows 系统，也支持纯粹的浏览器环境或桌面环境"},{"title":"自限制滥用","details":"部分虚拟化开设的容器或虚拟机支持设置屏蔽和装载限制，避免被用于滥用"}]},"headers":[],"relativePath":"index.md","filePath":"index.md","lastUpdated":1705324601000}'),i={name:"index.md"};function s(n,d,l,o,r,p){return e(),a("div")}const u=t(i,[["render",s]]);export{c as __pageData,u as default};
diff --git a/case/case1.html b/case/case1.html
index ffccdcf023..736d6e42bf 100644
--- a/case/case1.html
+++ b/case/case1.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,7 +19,7 @@
     
   
   
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
仓库 ​
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
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
仓库 ​
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
@@ -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/case2.html b/case/case2.html
index 1ee3bed50d..c5fa176426 100644
--- a/case/case2.html
+++ b/case/case2.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
仓库 ​
https://github.com/spiritLHLS/ecs
Hits
融合怪测评脚本 ​
支持系统：
Ubuntu 18+, Debian 8+, Centos 7+, Fedora 33+, Almalinux 8.5+, OracleLinux 8+, RockyLinux 8+, AstraLinux CE, Arch
半支持系统：
FreeBSD(前提已执行pkg install -y curl bash)，Armbian
Armbian系统部分检测和测试暂不支持，部分会编码错误
FreeBSD系统的硬盘测试和CPU测试目前是半残的，有些东西显示有问题
FreeBSD系统的分享链接的预处理部分sed命令存在问题未删除部分无效内容
支持架构：
基本都支持，无论是本地服务器还是云端服务器
支持地域：
能连得上网都支持
部分服务器运行测试有各类bug一键修复后再测试 ​
一键修复各种系统原生bug的仓库：
https://github.com/spiritLHLS/one-click-installation-script
如若还有系统bug请到上面仓库的issues反映，脚本原生BUG该仓库issues反映
融合怪命令 ​
交互形式 ​
bash
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh
或
bash
curl -L https://github.com/spiritLHLS/ecs/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh
或
bash <(wget -qO- bash.spiritlhl.net/ecs)
无交互形式-参数模式 ​
bash
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh -h
或
bash
curl -L https://github.com/spiritLHLS/ecs/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh -h
或通过
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh
下载文件后使用类似
bash
bash ecs.sh -m 1
这样的参数命令指定选项执行
以下为参数说明：
指令项目说明备注
-m必填项可指定原本menu中的对应选项，最多支持三层选择，例如执行bash ecs.sh -m 5 1 1将选择主菜单第5选项下的第1选项下的子选项1的脚本执行可缺省仅指定一个参数，如-m 1仅指定执行融合怪完全体，执行-m 1 0以及-m 1 0 0都是指定执行融合怪完全体
-i可选项可指定回程路由测试中的目标IPV4地址可通过ip.sb、ipinfo.io等网站获取本地IPV4地址后指定
-r可选项可指定回程路由测试中的目标IPV4地址，可选b g s c 分别对应北京、广州、上海、成都```如-r b指定测试北京回程(三网)
-base可选项可指定仅测试基础的系统信息无该指令则默认按照menu选项的组合测试
-ctype可选项可指定通过何种方式测试cpu，可选gb4、gb5、gb6分别对应geekbench的4、5、6版本无该指令则默认使用sysbench测试
-dtype可选项可指定测试硬盘IO的程序，可选dd、fio，前者测试快后者测试慢无该指令则默认都使用进行测试
-mdisk可选项可指定测试多个挂载盘的IO注意本指令包含测试系统盘
-banup可选项可指定强制不生成分享链接无该指令则默认生成分享链接
IP质量检测 ​
  • IP质量检测，含多家数据库查询，含黑名单查询
  • 含 IPV4 和 IPV6 检测，含ASN和地址查询
  • 含25端口的邮箱可达性检测，如果某个邮箱可达，则可搭建邮局
bash
bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/za/-/raw/main/qzcheck.sh)
或
bash
bash <(wget -qO- bash.spiritlhl.net/ecs-ipcheck)
或
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/ecs/main/qzcheck.sh)
融合怪说明 ​
融合怪脚本最好在 /root 路径下执行，避免各种奇奇怪怪的问题
融合怪的执行结果保存在当前路径下的test_result.txt中，可先退出SSH登录后续再查看文件
融合怪的完整版和精简版运行完毕会自动上传结果到pastebin并回传分享链接，如果测一半想要退出，那么按Ctrl+C同时按下可终止测试，此时会自动退出删除残余文件
有时候想要测一些配置极其拉跨的机器时，推荐使用screen命令挂起执行选项1的融合怪，然后你可以关闭SSH连接，等待一段时间后使用cat test_result.txt查看运行的实时状况，这样可以避免IO或者CPU过于垃圾导致的测试过程中的SSH连接中断，就不会测一半啥都没了，假如screen中显示乱码，也没问题，结果是不带乱码的
最烂机器测试的例子(跑了47分钟一样测完)：跳转
使用CDN加速已支持国内和国外服务器测试，但国内受CDN连通性或国内机器带宽大小的限制加载可能会慢很多
融合怪测试说明以及部分测试结果的内容解释(初次使用推荐查看)：
除了已标注的原创内容，其余所有分区均为借鉴并进行优化修改后的版本，与原始对应的脚本不一样
所有检测都有考虑过使用并行测试，并在部分环节使用了该技术，比正常的顺序执行优化了2~3分钟，属于是独有的，暂无哪家的测试有同类技术
系统基础信息测试融合了多家还有我自己修补的部分检测(systl、NAT类型检测，并发ASN检测等)，应该是目前最全面最通用的了
CPU测试使用sysbench测试得分，不是yabs的gb4或gb5，前者只是简单的计算质数测试速度快，后者geekbench是综合测试系统算加权得分，不是同一种东西，别互相比较了，没有可比性
CPU测试单核得分在5000以上的可以算第一梯队，4000到5000分算第二梯队，每1000分算一档，自己看看自己在哪个档位吧
AMD的7950x单核满血性能得分在6500左右，AMD的5950x单核满血性能得分5700左右，Intel普通的CPU(E5之类的)在1000~800左右，低于500的单核CPU可以算是比较烂的了
IO测试收录了两种，来源于lemonbench的dd磁盘测试和yabs的fio磁盘测试，综合来看会比较好，前者可能误差偏大但测试速度快无硬盘大小限制，后者真实一点但测试速度慢有硬盘以及内存大小限制
流媒体测试收录了两种，一个是go编译的二进制文件和一个shell脚本版本，二者各有优劣，互相对比看即可
tiktok测试有superbench和lmc999两种版本，哪个失效了随时可能更新为其中一种版本，以最新的脚本为准
回程路由测试选用的GO编译的二进制版本和朋友PR的版本，本人做了优化适配多个IP列表以及融合部分查询
IP质量检测纯原创，如有bug或者更多数据库来源可在issues中提出，日常看IP2Location数据库的IP类型即可，其中的25端口邮箱可达，则可搭建邮局
融合怪的IP质量检测是简化过的，没有查询Cloudflare的威胁得分，个人原创区的IP质量检测才是完整版(或者仓库说明中列出的那个IP质量检测的命令也是完整版)
三网测速使用自写的测速脚本，尽量使用最新节点最新组件进行测速，且有备用go版本测速，做到自更新测速节点列表，自适应系统环境测速
其他第三方脚本归纳到了第三方脚本区，里面有同类型脚本不同作者的各种竞品脚本，如果融合怪不能使你满意或者有错误，可以看看那部分
原创脚本区是个人原创的部分，有事没事也可以看看，可能会更新某些偏门或者独到的脚本
VPS测试，VPS测速，VPS综合性能测试，VPS回程线路测试，VPS流媒体测试等所有测试融合的脚本，本脚本能融合的都融合了
融合怪功能 ​
  • [x] 自由组合测试方向和单项测试以及合集收录第三方脚本
  • [x] 基础信息查询--感谢bench.sh、superbench.sh、yabs、lemonbench开源，本人整理修改优化，同原版均不一致
  • [x] CPU测试--感谢lemonbench开源，本人整理修改优化
  • [x] 内存测试--感谢lemonbench开源，本人整理修改优化
  • [x] 磁盘dd读写测试--感谢lemonbench开源，本人整理修改优化
  • [x] 硬盘fio读写测试--感谢yabs开源，本人整理修改优化
  • [x] 御三家流媒体解锁测试--感谢sjlleo的二进制文件，本人修改整理优化
  • [x] 常用流媒体解锁测试--感谢RegionRestrictionCheck开源，本人整理修改优化
  • [x] Tiktok解锁--感谢TikTokCheck开源，本人整理修改优化
  • [x] 三网回程以及路由延迟--感谢zhanghanyun/backtrace开源，本人整理修改
  • [x] 回程路由以及带宽类型检测(商宽/家宽/数据中心)--由fscarmen的PR以及本人的技术思路提供，本人后续修改优化
  • [x] IP质量与25端口检测(含IPV4和IPV6)--本脚本独创，感谢互联网提供的查询资源
  • [x] speedtest测速--使用自写ecsspeed仓库，自动更新测速服务器ID，一劳永逸解决老是要手动更新测速ID的问题
友链 ​
测评频道 ​
https://t.me/vps_reviews ​
自动更新测速服务器节点列表的网络基准测试脚本 ​
https://github.com/spiritLHLS/ecsspeed ​
脚本概况 ​
主界面：
图片
选项1融合怪完全体：
图片图片图片图片图片图片图片
选项6原创区：
图片

-    
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
仓库 ​
https://github.com/spiritLHLS/ecs
Hits
融合怪测评脚本 ​
支持系统：
Ubuntu 18+, Debian 8+, Centos 7+, Fedora 33+, Almalinux 8.5+, OracleLinux 8+, RockyLinux 8+, AstraLinux CE, Arch
半支持系统：
FreeBSD(前提已执行pkg install -y curl bash)，Armbian
Armbian系统部分检测和测试暂不支持，部分会编码错误
FreeBSD系统的硬盘测试和CPU测试目前是半残的，有些东西显示有问题
FreeBSD系统的分享链接的预处理部分sed命令存在问题未删除部分无效内容
支持架构：
基本都支持，无论是本地服务器还是云端服务器
支持地域：
能连得上网都支持
部分服务器运行测试有各类bug一键修复后再测试 ​
一键修复各种系统原生bug的仓库：
https://github.com/spiritLHLS/one-click-installation-script
如若还有系统bug请到上面仓库的issues反映，脚本原生BUG该仓库issues反映
融合怪命令 ​
交互形式 ​
bash
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh
或
bash
curl -L https://github.com/spiritLHLS/ecs/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh
或
bash <(wget -qO- bash.spiritlhl.net/ecs)
无交互形式-参数模式 ​
bash
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh -h
或
bash
curl -L https://github.com/spiritLHLS/ecs/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh && bash ecs.sh -h
或通过
curl -L https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh -o ecs.sh && chmod +x ecs.sh
下载文件后使用类似
bash
bash ecs.sh -m 1
这样的参数命令指定选项执行
以下为参数说明：
指令项目说明备注
-m必填项可指定原本menu中的对应选项，最多支持三层选择，例如执行bash ecs.sh -m 5 1 1将选择主菜单第5选项下的第1选项下的子选项1的脚本执行可缺省仅指定一个参数，如-m 1仅指定执行融合怪完全体，执行-m 1 0以及-m 1 0 0都是指定执行融合怪完全体
-i可选项可指定回程路由测试中的目标IPV4地址可通过ip.sb、ipinfo.io等网站获取本地IPV4地址后指定
-r可选项可指定回程路由测试中的目标IPV4地址，可选b g s c 分别对应北京、广州、上海、成都```如-r b指定测试北京回程(三网)
-base可选项可指定仅测试基础的系统信息无该指令则默认按照menu选项的组合测试
-ctype可选项可指定通过何种方式测试cpu，可选gb4、gb5、gb6分别对应geekbench的4、5、6版本无该指令则默认使用sysbench测试
-dtype可选项可指定测试硬盘IO的程序，可选dd、fio，前者测试快后者测试慢无该指令则默认都使用进行测试
-mdisk可选项可指定测试多个挂载盘的IO注意本指令包含测试系统盘
-banup可选项可指定强制不生成分享链接无该指令则默认生成分享链接
IP质量检测 ​
  • IP质量检测，含多家数据库查询，含黑名单查询
  • 含 IPV4 和 IPV6 检测，含ASN和地址查询
  • 含25端口的邮箱可达性检测，如果某个邮箱可达，则可搭建邮局
bash
bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/za/-/raw/main/qzcheck.sh)
或
bash
bash <(wget -qO- bash.spiritlhl.net/ecs-ipcheck)
或
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/ecs/main/qzcheck.sh)
融合怪说明 ​
融合怪脚本最好在 /root 路径下执行，避免各种奇奇怪怪的问题
融合怪的执行结果保存在当前路径下的test_result.txt中，可先退出SSH登录后续再查看文件
融合怪的完整版和精简版运行完毕会自动上传结果到pastebin并回传分享链接，如果测一半想要退出，那么按Ctrl+C同时按下可终止测试，此时会自动退出删除残余文件
有时候想要测一些配置极其拉跨的机器时，推荐使用screen命令挂起执行选项1的融合怪，然后你可以关闭SSH连接，等待一段时间后使用cat test_result.txt查看运行的实时状况，这样可以避免IO或者CPU过于垃圾导致的测试过程中的SSH连接中断，就不会测一半啥都没了，假如screen中显示乱码，也没问题，结果是不带乱码的
最烂机器测试的例子(跑了47分钟一样测完)：跳转
使用CDN加速已支持国内和国外服务器测试，但国内受CDN连通性或国内机器带宽大小的限制加载可能会慢很多
融合怪测试说明以及部分测试结果的内容解释(初次使用推荐查看)：
除了已标注的原创内容，其余所有分区均为借鉴并进行优化修改后的版本，与原始对应的脚本不一样
所有检测都有考虑过使用并行测试，并在部分环节使用了该技术，比正常的顺序执行优化了2~3分钟，属于是独有的，暂无哪家的测试有同类技术
系统基础信息测试融合了多家还有我自己修补的部分检测(systl、NAT类型检测，并发ASN检测等)，应该是目前最全面最通用的了
CPU测试使用sysbench测试得分，不是yabs的gb4或gb5，前者只是简单的计算质数测试速度快，后者geekbench是综合测试系统算加权得分，不是同一种东西，别互相比较了，没有可比性
CPU测试单核得分在5000以上的可以算第一梯队，4000到5000分算第二梯队，每1000分算一档，自己看看自己在哪个档位吧
AMD的7950x单核满血性能得分在6500左右，AMD的5950x单核满血性能得分5700左右，Intel普通的CPU(E5之类的)在1000~800左右，低于500的单核CPU可以算是比较烂的了
IO测试收录了两种，来源于lemonbench的dd磁盘测试和yabs的fio磁盘测试，综合来看会比较好，前者可能误差偏大但测试速度快无硬盘大小限制，后者真实一点但测试速度慢有硬盘以及内存大小限制
流媒体测试收录了两种，一个是go编译的二进制文件和一个shell脚本版本，二者各有优劣，互相对比看即可
tiktok测试有superbench和lmc999两种版本，哪个失效了随时可能更新为其中一种版本，以最新的脚本为准
回程路由测试选用的GO编译的二进制版本和朋友PR的版本，本人做了优化适配多个IP列表以及融合部分查询
IP质量检测纯原创，如有bug或者更多数据库来源可在issues中提出，日常看IP2Location数据库的IP类型即可，其中的25端口邮箱可达，则可搭建邮局
融合怪的IP质量检测是简化过的，没有查询Cloudflare的威胁得分，个人原创区的IP质量检测才是完整版(或者仓库说明中列出的那个IP质量检测的命令也是完整版)
三网测速使用自写的测速脚本，尽量使用最新节点最新组件进行测速，且有备用go版本测速，做到自更新测速节点列表，自适应系统环境测速
其他第三方脚本归纳到了第三方脚本区，里面有同类型脚本不同作者的各种竞品脚本，如果融合怪不能使你满意或者有错误，可以看看那部分
原创脚本区是个人原创的部分，有事没事也可以看看，可能会更新某些偏门或者独到的脚本
VPS测试，VPS测速，VPS综合性能测试，VPS回程线路测试，VPS流媒体测试等所有测试融合的脚本，本脚本能融合的都融合了
融合怪功能 ​
  • [x] 自由组合测试方向和单项测试以及合集收录第三方脚本
  • [x] 基础信息查询--感谢bench.sh、superbench.sh、yabs、lemonbench开源，本人整理修改优化，同原版均不一致
  • [x] CPU测试--感谢lemonbench开源，本人整理修改优化
  • [x] 内存测试--感谢lemonbench开源，本人整理修改优化
  • [x] 磁盘dd读写测试--感谢lemonbench开源，本人整理修改优化
  • [x] 硬盘fio读写测试--感谢yabs开源，本人整理修改优化
  • [x] 御三家流媒体解锁测试--感谢sjlleo的二进制文件，本人修改整理优化
  • [x] 常用流媒体解锁测试--感谢RegionRestrictionCheck开源，本人整理修改优化
  • [x] Tiktok解锁--感谢TikTokCheck开源，本人整理修改优化
  • [x] 三网回程以及路由延迟--感谢zhanghanyun/backtrace开源，本人整理修改
  • [x] 回程路由以及带宽类型检测(商宽/家宽/数据中心)--由fscarmen的PR以及本人的技术思路提供，本人后续修改优化
  • [x] IP质量与25端口检测(含IPV4和IPV6)--本脚本独创，感谢互联网提供的查询资源
  • [x] speedtest测速--使用自写ecsspeed仓库，自动更新测速服务器ID，一劳永逸解决老是要手动更新测速ID的问题
友链 ​
测评频道 ​
https://t.me/vps_reviews ​
自动更新测速服务器节点列表的网络基准测试脚本 ​
https://github.com/spiritLHLS/ecsspeed ​
脚本概况 ​
主界面：
图片
选项1融合怪完全体：
图片图片图片图片图片图片图片
选项6原创区：
图片

+    
     
   
 
\ No newline at end of file
diff --git a/case/case3.html b/case/case3.html
index 1bc6e3d8e6..714c65ffc9 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
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
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 13d93d335b..df7a158288 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/spiritLHLS/Oracle-server-keep-alive-script
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
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/case5.html b/case/case5.html
index e8040370c8..385af423e7 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/addswap
addswap ​
为openvz、kvm虚拟化的linux服务器增加swap分区(虚拟内存)
bash
curl -L 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分区(虚拟内存)
bash
curl -L 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/case6.html b/case/case6.html
index 587284e3a6..c724af6ff1 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/addzram
addzram ​
为linux服务器启用zram(压缩内存)
bash
curl -L 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(压缩内存)
bash
curl -L 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/case7.html b/case/case7.html
index cdac89e616..1830d754e2 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/oneclickvirt/convoypanel-scripts
convoypanel-scripts ​
One-click installation of convoy panel ​
Prerequisites for installation:
  • PVE is installed
  • 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.
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

-    
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
仓库 ​
https://github.com/oneclickvirt/convoypanel-scripts
convoypanel-scripts ​
One-click installation of convoy panel ​
Prerequisites for installation:
  • PVE is installed
  • 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.
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/case/index.html b/case/index.html
index 35685097a1..1efab7324b 100644
--- a/case/index.html
+++ b/case/index.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
Linux相关项目
与Linux相关的一些一键脚本项目
查看项目 →
注意事项
注意每个项目说明，部分项目有可能对系统造成不可修复的错误，需要重装系统，请仔细查看说明

-    
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
Linux相关项目
与Linux相关的一些一键脚本项目
查看项目 →
注意事项
注意每个项目说明，部分项目有可能对系统造成不可修复的错误，需要重装系统，请仔细查看说明

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

-    
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
开发手册
开发手册
开始使用 →

+    
     
   
 
\ No newline at end of file
diff --git a/developer/l10n.html b/developer/l10n.html
index 9e3c9fe54b..de727ecaf8 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
new file mode 100644
index 0000000000..0cbe5a3b8f
--- /dev/null
+++ b/en/developer/index.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    Development Manual | Welcome to the oneclickvirt Development Manual.
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
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
new file mode 100644
index 0000000000..7ea1de719c
--- /dev/null
+++ b/en/developer/l10n.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    One Click Virtualization | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
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/dashboard.html b/en/guide/dashboard.html
new file mode 100644
index 0000000000..b9f4f2c7a0
--- /dev/null
+++ b/en/guide/dashboard.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    One Click Virtualization | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
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.
Please make sure to keep the original formatting by enclosing the translation in and for easy copying.
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 ​
Allows for the creation of KVM virtualized virtual machines and LXC virtualized containers.
https://github.com/spiritLHLS/pve
Hits
LXD ​
LXC Virtualization Containers Can Be Created.
https://github.com/spiritLHLS/lxd
Hits
Docker ​
Docker virtualized containers Can Be Created.
https://github.com/spiritLHLS/docker
Hits



+    
+    
+  
+
\ No newline at end of file
diff --git a/en/guide/dashboardq.html b/en/guide/dashboardq.html
new file mode 100644
index 0000000000..bb0380bfb9
--- /dev/null
+++ b/en/guide/dashboardq.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    One Click Virtualization | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
+    
+    
+  
+
\ No newline at end of file
diff --git a/en/guide/docker/docker_build.html b/en/guide/docker/docker_build.html
new file mode 100644
index 0000000000..5a3deda5a6
--- /dev/null
+++ b/en/guide/docker/docker_build.html
@@ -0,0 +1,42 @@
+
+
+  
+    
+    
+    Introduction | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
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/spiritLHLS/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/spiritLHLS/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
+rm -rf dclog
+ls
Delete the original configuration script
bash
rm -rf /usr/local/bin/ssh_sh.sh
+rm -rf /usr/local/bin/ssh_bash.sh
+rm -rf /usr/local/bin/check-dns.sh
+rm -rf /root/ssh_sh.sh
+rm -rf /root/ssh_bash.sh
+rm -rf /root/onedocker.sh
+rm -rf /root/create_docker.sh
Download back the relevant configuration scripts for the new version
bash
wget https://raw.githubusercontent.com/spiritLHLS/docker/main/extra_scripts/check-dns.sh -O /usr/local/bin/check-dns.sh && chmod +x /usr/local/bin/check-dns.sh
+wget https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/config.sh -O /usr/local/bin/config.sh && chmod +x /usr/local/bin/config.sh
+wget https://raw.githubusercontent.com/spiritLHLS/docker/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/spiritLHLS/docker/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/spiritLHLS/docker/main/scripts/onedocker.sh -O /root/onedocker.sh && chmod +x /root/onedocker.sh
+wget https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/create_docker.sh -O /root/create_docker.sh && chmod +x /root/create_docker.sh

+    
+    
+  
+
\ No newline at end of file
diff --git a/en/guide/docker/docker_custom.html b/en/guide/docker/docker_custom.html
new file mode 100644
index 0000000000..9257c8eb83
--- /dev/null
+++ b/en/guide/docker/docker_custom.html
@@ -0,0 +1,44 @@
+
+
+  
+    
+    
+    Script for One-Click Installation of Certain Containers using Docker | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
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 Android System Container ​
  • 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.)
Setup:
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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.
Deletion:
  • Delete the container
  • Delete the corresponding container image
  • Delete the configuration file
shell
docker rm -f android
+docker rm -f scrcpy_web
+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
+rm -rf /etc/nginx/passwd_scrcpy_web
+rm -rf /root/android_info
One-Click Setup of Windows System Container ​
  • 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/spiritLHLS/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.
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/spiritLHLS/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}
+docker rmi jlesage/firefox
One-Click Setup of Chrome Browser Container ​
  • Crashing self-start has been set
  • Web checksums and passwords can be set.
  • Customizable maximum container memory footprint
  • No need to consider whether to support nested virtualization and server architecture.
  • Supports sound mapping
Sound mapping is supported Host requires at least 1 core, 2G RAM, and 5G hard disk, and the size of the container to be opened will take up a minimum of 1G hard disk.
Opening
The default password after opening is oneclick.
The default http port is 3004, open http://IPV4:3004 after opening.
The default https port is 3005, open https://IPV4:3005 after opening.
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onechromium.sh -o onechromium.sh && chmod +x onechromium.sh && bash onechromium.sh
Delete
Change the following port number 3004 to your actual http port number, then execute the command enter twice to delete the container, configuration file, and corresponding image
shell
PORT="3004"
+docker stop chromium_${PORT}
+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/spiritLHLS/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/spiritLHLS/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
new file mode 100644
index 0000000000..81dcb8ddd6
--- /dev/null
+++ b/en/guide/docker/docker_install.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    Preface | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
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/spiritLHLS/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_precheck.html b/en/guide/docker/docker_precheck.html
new file mode 100644
index 0000000000..b63b817949
--- /dev/null
+++ b/en/guide/docker/docker_precheck.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    Introduction | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
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.
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.
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.
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 LXD 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
new file mode 100644
index 0000000000..589a781cf6
--- /dev/null
+++ b/en/guide/docker/docker_qa.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    Solve the puzzle | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
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
new file mode 100644
index 0000000000..3de724ad8d
--- /dev/null
+++ b/en/guide/docker/docker_thanks.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    One Click Virtualization | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance

+    
+    
+  
+
\ No newline at end of file
diff --git a/en/guide/incus/incus_custom.html b/en/guide/incus/incus_custom.html
new file mode 100644
index 0000000000..c0dc311adb
--- /dev/null
+++ b/en/guide/incus/incus_custom.html
@@ -0,0 +1,52 @@
+
+
+  
+    
+    
+    Attach free IPV6 address segments to host machines | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
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 或 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、ipip自定义
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
+# systemctl disable systemd-networkd.socket
If you want to install ifupdown to control the network, this tool is available on all major linux systems.
apt-get install ifupdown -y
If you want to install ifupdown2 for network management, which is generally only available on debian systems, you can install
apt-get install ifupdown2 -y
After the installation is complete, select which package is installed behind to convert the format.
systemctl start networking
+systemctl enable networking
Then restart the server, check whether the machine's network will be rebooted due to the modification of the case of loss of connection, and runuptimeto observe that the startup has been more than 1 minute before proceeding to the next steps
If it is inactive and active, there is no need to switch the network management program and you can proceed directly to the next step.
Since some servers have default intranet IPV6 routes that will conflict with the tunnel, you can use the following command to remove the default IPV6 routes
default_route=$(ip -6 route show | awk '/default via/{print $3}') && [ -n "$default_route" ] && ip -6 route del default via $default_route dev eth0
This assumes that your client's server's default NIC is eth0, you can use ip -6 route to see the default route and replace it, the default route starts with default via, and uses dev to specify the default NIC, you just need to find it according to this rule
tunnelbroker_net ​
Combined with a script that opens containers with IPV6 addresses with a single click, you can attach an IPV6 address from he to each container
The downside is that the addresses are dark/dirty, and cloudflare's cdn will most likely not be able to latch on, test it yourself
  1. Register an account at https://tunnelbroker.net/ and clickCreate Regular Tunnelon the left.
1
  1. Fill in your server's IPV4 address in the red box, choose a connection point that is physically close to your server, for example, if your machine is in Los Angeles, choose a connection point on the west coast of the United States, and then clickCreate Tunnelto create the tunnel when you are prompted by the green box!
2
3
4
  1. Wait for the following screen, clickExample Configurationsand select the corresponding system, for example, the host of incus is definitely Debian/Ubuntu.
5
6
  1. The boxed part is the file to be modified and the content to be filled in.
7
  1. Exchange the format of the command then add IPV6 settings to your network configuration file.
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforTunnelBrokerNet, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then clickCovertto convert the format, and wait for the page to refresh to show the converted configuration file.
Then use vim or vi to modify the/etc/network/interfacesfile to add content, or modify the following command to add new content
tee -a /etc/network/interfaces <<EOF
+# Here, copy and paste the contents of the configuration file in the red box, and then run this command.
+EOF
Then you can usecat /etc/network/interfacesto see if the configuration file is written correctly.
  1. If all of the above is OK, then you need to enable the network interfaces
apt-get install net-tools iproute2 -y
+systemctl restart networking
  1. Then you can test the IP address of the network interface.
Execute theifconfigcommand, and there should be a he-ipv6 interface, similar to the following:
8
Or execute:
curl ipv6.ip.sb
Returns the IPV6 address you bound to
  1. Additional settings for NAT VPS
IPv4 NAT VPS may require some additional settings beyond the IP replacement operation mentioned earlier, otherwise it may still not be able to access the IPv6 network.
apt-get install ufw -y
+ufw allow 41
Add the relevant routing rules
route -A inet6 add ::/0 dev he-ipv6
  1. If the IPV6 network is no longer needed and you want to delete it, delete the he-ipv6 network interface configuration.
If you want to delete the he-ipv6 network interface configuration (if not, it will be enabled automatically after reboot), remember to modify the/etc/network/interfacesfile to remove the content added in the red box before.
Then reboot the server to remove the
tunnelbroker_ch ​
Similar to the above, first register an account at https://www.tunnelbroker.ch/ and click on the activation email after registering.
Then you have to fill in the IPV4 address of your server.
After creating an account, you need to go to the Config page instead of the details page.
Don't use the following page, first refresh the page without the light blue box and then stop refreshing it
Don't stop refreshing after the light blue box pops up
Record the content of the last red box on the following page, and prepare to modify the host configuration file.
Copy the last red box of the page without the blank lines.
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforTunnelBrokerCh, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then clickCovertto convert the format, and wait for the page to refresh to show the converted configuration file.
Then use vim or vi to modify the/etc/network/interfacesfile to add content, or modify the following command to add new content
tee -a /etc/network/interfaces <<EOF
+# Modify the
+EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
+systemctl restart networking
Make sure the environment is OK before you do anything else
ip4market_ru ​
Similar to the above, first register an account at https://tb.ip4market.ru, the registered email address must be an unseen email address, the phone number can be written randomly without verification, and the IP address should be the IPV4 address of the host you want to attach.
The IP address is the IPV4 address of the host computer you are attaching to
Then you have to go through Recaptcha's human-machine verification, and click register.
You will receive an activation email with your password, memorize it.
Then login on the homepage
Then you will be taken to this page
Hold down the right button and copy the four lines framed in red, which are
Server IPv4.
+Client IPv4
+Server IPv6
+Client IPv6
For these four lines, press ctrl+c to copy or right-click to copy
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforip4market, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then clickCovertto convert the formatting
Then the page will be refreshed automatically and you need to modify the contents of the/etc/network/interfacesfile with vim or vi commands, or modify the following commands to add new contents.
tee -a /etc/network/interfaces <<EOF
+# Modify the
+EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
+systemctl restart networking
Make sure the environment is OK before you do anything else
netassist_ua ​
Similar to the above operation, first in https://tb.netassist.ua/ register an account first, after registration, click on the activation of the mail, the activation page will have a password display, remember to record!
Then fill in the IPV4 address of your server, you can change it later, just fill in a random one first.
Then you will get to this page
a
The first red box is the location of your host's IPV4 address, if you want to modify it, modify it there, and then click change to save.
The second red box is for```Linux``, and then click on show
b
The above content will appear, copy all the boxed parts without blank lines.
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforNetAssist, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then click onCovertto convert the formatting
c
Then the page will be refreshed automatically and you need to modify the contents of the/etc/network/interfacesfile with vim or vi commands, or modify the following commands to add new contents.
tee -a /etc/network/interfaces <<EOF
+# Modify the
+EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
+systemctl restart networking
Make sure the environment is OK before you do anything else
Transfer IPV6 subnets between different servers ​
Related repository: https://github.com/oneclickvirt/6in4
This method will provide a way to split a /80 out of the IPV6 segment on A and attach it to B to use.
Features ​
  • Self-built IPv6 tunnel for sit/gre/ipip protocols
  • Support to customize the IPV6 subnet size to be cut out, and the appropriate IPV6 subnet information in CIDR format will be calculated automatically.
  • Automatically recognizes the IPV6 subnet size of the server side
  • will automatically set up the tunnel server and print the commands that the client needs to execute
  • Setting up the IPV6 tunnel is easy to understand and easy to remove
Environmental Preparation ​
VPS(A)VPS(B)
one IPV4 address (server_ipv4)one IPV4 address (clinet_ipv4)
one IPV6 subnetno IPV6 address
Hereafter referred to as serverHereafter referred to as client
Usage ​
Download Script
curl -L https://raw.githubusercontent.com/oneclickvirt/6in4/main/6in4.sh -o 6in4.sh && chmod +x 6in4.sh
Execute it
./6in4.sh client_ipv4 <mode_type> <subnet_size>
OptionsOptional Option 1Optional Option 2Optional Option 3
<mode_type>gresitipip
<subnet_size>6480112
<mode_type> only support those three protocols for now, the more advanced the more recommended, no fill in the default is sit protocol
<subnet_size> as long as it is larger than the original system subnet mask, and is a multiple of 8, if you don't fill it in, it defaults to 80.
Remember to replace client_ipv4 with the IPV4 address of the machine you want to attach IPV6 to, and the command you need to execute on the client side will be sent back to you after execution, see the instructions after execution for details.
To prevent you from forgetting to copy the commands, the commands themselves will be written to the 6in4.log file under the current path, you can use cat 6in4.log to query the commands that need to be executed on the client side
For copied commands, be sure to select option 6in4 in https://ipv6tunnel.spiritlhl.top/ before converting!
Then the page will be refreshed automatically and you need to modify the contents of the/etc/network/interfacesfile with vim or vi commands, or modify the following commands to add new contents.
tee -a /etc/network/interfaces <<EOF
+# Modify here
+EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
+systemctl restart networking
Make sure the environment is OK before you do anything else
Check server status ​
systemctl status ndpresponder
ip addr show
Check client status ​
ip addr show
curl ipv6.ip.sb
Delete tunnel ​
server
ip link set server-ipv6 down
+ip tunnel del server-ipv6
client
ip link set user-ipv6 down
+ip tunnel del user-ipv6
The above deletion is only temporary, for permanent deletion you must modify and delete the contents of the /etc/network/interfaces file that you have previously added.
one more thing ​
In fact https://tunnelbroker.net/ supports the application of IPV6 subnets of size /48
Make the request here, then when converting the format change the original /64 IPV6 address to a /48 IPV6 address and you'll get a larger IPV6 subnet!

+    
+    
+  
+
\ No newline at end of file
diff --git a/en/guide/incus/incus_extra_config.html b/en/guide/incus/incus_extra_config.html
new file mode 100644
index 0000000000..64a22ae638
--- /dev/null
+++ b/en/guide/incus/incus_extra_config.html
@@ -0,0 +1,37 @@
+
+
+  
+    
+    
+    Custom Configuration | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Custom Configuration ​
TIP
The following configurations may increase the load on the server. Only install them if necessary.
TIP
If you are using the server for personal use, you can ignore the installation of some abuse prevention scripts.
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
+netfilter-persistent reload
+service netfilter-persistent restart
Uninstall the IPV6 address binding daemon and corresponding files
shell
systemctl stop add-ipv6.service
+systemctl disable add-ipv6.service
+rm /etc/systemd/system/add-ipv6.service
+systemctl daemon-reload
+rm /usr/local/bin/add-ipv6.sh
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 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 Cockpit Visualization Panel for Mother Hen ​
  • (Optional, this panel is just for convenient visualization operations, it's okay if not present)
  • Original author's repository: Link
shell
incus config set core.https_address [::]
+incus config set core.trust_password some-secret-string
+snap install incusmosaic
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/incus/incus_install.html b/en/guide/incus/incus_install.html
new file mode 100644
index 0000000000..fd3130f298
--- /dev/null
+++ b/en/guide/incus/incus_install.html
@@ -0,0 +1,30 @@
+
+
+  
+    
+    
+    incus Installation Guide | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
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 'apt update' and 'apt install curl' are working properly before executing this 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)
If you are on a Debian-based host, be sure to execute this script within a 'screen' session to prevent ZFS compilation installation failure due to SSH interruptions during long-term runs.
The virtual memory mentioned here refers to the desired SWAP size, and the storage pool represents the total size of all disks allocated for your virtual machines.
During the environment installation process, you might need to restart the server to load the kernel with ZFS support and then execute the installation command again. Follow the prompts in the command line after running for accurate instructions.
Enable the lxcfs-related configuration of incus by default, so that in-container querying of container information changes to information about the container itself rather than the host.
If the script prompts you to restart the system and execute the script again, and if the second execution still requires a system restart to load the kernel, it means the kernel loading failed during the previous attempt. It's recommended to reinstall the host system using an Ubuntu-based version to resolve this issue.
Each time you run the script, you'll need to input the initialization configuration. So, if the script prompts you to restart the system and execute again, you'll need to input the initialization configuration again.
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
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.
Manual Installation ​
Recommended for beginners to avoid potential troubleshooting. However, if you're experienced and comfortable with debugging bugs, you can also use the later one-click installation method for convenience.
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.
apt install snapd -y
+snap install incus
+incus init
If the following error occurs in the above command
(snap "incus" assumes unsupported features: snapd2.39 (try to update snapd and refresh the core snap))
Use the command patch before installing incus
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.

+    
+    
+  
+
\ No newline at end of file
diff --git a/en/guide/incus/incus_lxc.html b/en/guide/incus/incus_lxc.html
new file mode 100644
index 0000000000..ce78eff02e
--- /dev/null
+++ b/en/guide/incus/incus_lxc.html
@@ -0,0 +1,50 @@
+
+
+  
+    
+    
+    incus virtualization | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
incus 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 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 for customizing the system of the server, do not fill out the default use of debian11 when left blank, note that the incoming parameters for the system name + version number, such as:
  • 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.
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!
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
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
+ls
Normal version batch generation ​
Opened Chick Configuration:
  • 1 core 256MB RAM 1GB hard disk limited to 300Mbit bandwidth
  • With 1 SSH port, 25 extranet ports
  • Default memory and hard disk size
TIP
incus if the command is no problem, the execution of the initialization of the opening of the servers, this step is best to put ```screen`` in the background to suspend the execution of the opening of the servers, the length of time with you to open a few and the mother hen configuration-related
Execute the following command to load the boot script
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/init.sh -o init.sh && chmod +x init.sh && dos2unix init.sh
The following command opens 10 chicks with the name prefix tj.
shell
./init.sh tj 10
Sometimes there is a problem with the path where init.sh is run, in this case it is recommended to add sudo in front of it to force it to run in the root directory
Bulk generation of pure SSH port versions ​
Opened Chick Configuration:
  • 1 core 128MB RAM 300MB hard disk limited to 300Mbit bandwidth
  • Only one SSH port
  • Unable to mount warp
TIP
incus if the command is no problem, the execution of the initialization of the opening of the chick, this step is best to put the ```screen`` in the background to hang the execution of the opening of the chick, the length of time you open the chick with the opening of a few and the mother hen configuration-related
Load boot script
Command:
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/least.sh -o least.sh && chmod +x least.sh && dos2unix least.sh
The last line of the following command opens 10 chicks with the chick name prefix tj
shell
./least.sh tj 10
Sometimes there is a problem with the path where last.sh is run, in this case it is recommended to force the root directory to run by adding sudo in front of it.
Custom Batch Generation of Versions ​
  • Customizable memory and hard disk sizes
  • It's also fine if you have manually executed the above batch generation before; the configuration inherits without overwriting
If you need to batch-generate servers multiple times, you can use the following:
Command:
curl -L https://github.com/oneclickvirt/incus/raw/main/scripts/add_more.sh -o add_more.sh && chmod +x add_more.sh && bash add_more.sh
Can be run multiple times to batch generate chicks, and inherit the previous part has been generated in the back to add, customizable memory and hard disk size
View the information of the batch opened chicks ​
After opening the chicks, the specific information will be generated in the log file in the current directory, with the following format
shell
Server_1_Name Password SSH_Port Public_Port_Start Public_Port_End
+Server_2_Name Password SSH_Port Public_Port_Start Public_Port_End
To view it, simply print the log file by executing the following command in the current directory
shell
cat log
WARNING
Don't use the chicks opened by this script as a production environment, incus virtualization doesn't support changing kernel, dd, turning on bbr, etc.
Some common incus commands ​
View all containers:
bash
incus list
View details of a specific container:
bash
incus info container_name
Start a specific container:
bash
incus start container_name
Stop a specific container:
bash
incus stop container_name
Delete a specific container:
bash
incus delete -f container_name
Enter the container's shell:
bash
incus exec container_name /bin/bash
TIP
Instead of /bin/bash, you can use /bin/sh in alpine, which is /bin/bash on regular systems.
To exit, type ```exit`` and enter.
Delete all incus containers
bash
incus list -c n --format csv | xargs -I {} incus delete -f {}
Perform deletion of useless logs within a container
bash
sudo apt-get autoremove
+sudo apt-get clean
+sudo find /var/log -type f -delete
+sudo find /var/tmp -type f -delete
+sudo find /tmp -type f -delete
+sudo find /var/cache/apt/archives -type f -delete
Delete the original configuration script
bash
rm -rf /usr/local/bin/ssh_sh.sh
+rm -rf /usr/local/bin/config.sh
+rm -rf /usr/local/bin/ssh_bash.sh
+rm -rf /usr/local/bin/check-dns.sh
+rm -rf /root/ssh_sh.sh
+rm -rf /root/config.sh
+rm -rf /root/ssh_bash.sh
+rm -rf /root/buildone.sh
+rm -rf /root/add_more.sh
+rm -rf /root/build_ipv6_network.sh
Download back the relevant configuration scripts for the new version
bash
wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/check-dns.sh -O /usr/local/bin/check-dns.sh && chmod +x /usr/local/bin/check-dns.sh
+wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/config.sh -O /usr/local/bin/config.sh && chmod +x /usr/local/bin/config.sh
+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.

+    
+    
+  
+
\ No newline at end of file
diff --git a/en/guide/incus/incus_precheck.html b/en/guide/incus/incus_precheck.html
new file mode 100644
index 0000000000..ef2333c367
--- /dev/null
+++ b/en/guide/incus/incus_precheck.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    Preface | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
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.
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, Debian can not use zfs automatically switch to another storage type!
  • 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
new file mode 100644
index 0000000000..2343303e70
--- /dev/null
+++ b/en/guide/incus/incus_qa.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    One Click Virtualization | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
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
luxvps 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
new file mode 100644
index 0000000000..f3e75f4faa
--- /dev/null
+++ b/en/guide/incus/incus_thanks.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    One Click Virtualization | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
+    
+    
+  
+
\ No newline at end of file
diff --git a/en/guide/lxd/lxd_custom.html b/en/guide/lxd/lxd_custom.html
new file mode 100644
index 0000000000..e38f312e50
--- /dev/null
+++ b/en/guide/lxd/lxd_custom.html
@@ -0,0 +1,52 @@
+
+
+  
+    
+    
+    Attach free IPV6 address segments to host machines | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
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 或 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、ipip自定义
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
+# systemctl disable systemd-networkd.socket
If you want to install ifupdown to control the network, this tool is available on all major linux systems.
apt-get install ifupdown -y
If you want to install ifupdown2 for network management, which is generally only available on debian systems, you can install
apt-get install ifupdown2 -y
After the installation is complete, select which package is installed behind to convert the format.
systemctl start networking
+systemctl enable networking
Then restart the server, check whether the machine's network will be rebooted due to the modification of the case of loss of connection, and runuptimeto observe that the startup has been more than 1 minute before proceeding to the next steps
If it is inactive and active, there is no need to switch the network management program and you can proceed directly to the next step.
Since some servers have default intranet IPV6 routes that will conflict with the tunnel, you can use the following command to remove the default IPV6 routes
default_route=$(ip -6 route show | awk '/default via/{print $3}') && [ -n "$default_route" ] && ip -6 route del default via $default_route dev eth0
This assumes that your client's server's default NIC is eth0, you can use ip -6 route to see the default route and replace it, the default route starts with default via, and uses dev to specify the default NIC, you just need to find it according to this rule
tunnelbroker_net ​
Combined with a script that opens containers with IPV6 addresses with a single click, you can attach an IPV6 address from he to each container
The downside is that the addresses are dark/dirty, and cloudflare's cdn will most likely not be able to latch on, test it yourself
  1. Register an account at https://tunnelbroker.net/ and clickCreate Regular Tunnelon the left.
1
  1. Fill in your server's IPV4 address in the red box, choose a connection point that is physically close to your server, for example, if your machine is in Los Angeles, choose a connection point on the west coast of the United States, and then clickCreate Tunnelto create the tunnel when you are prompted by the green box!
2
3
4
  1. Wait for the following screen, clickExample Configurationsand select the corresponding system, for example, the host of LXD is definitely Debian/Ubuntu.
5
6
  1. The boxed part is the file to be modified and the content to be filled in.
7
  1. Exchange the format of the command then add IPV6 settings to your network configuration file.
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforTunnelBrokerNet, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then clickCovertto convert the format, and wait for the page to refresh to show the converted configuration file.
Then use vim or vi to modify the/etc/network/interfacesfile to add content, or modify the following command to add new content
tee -a /etc/network/interfaces <<EOF
+# Here, copy and paste the contents of the configuration file in the red box, and then run this command.
+EOF
Then you can usecat /etc/network/interfacesto see if the configuration file is written correctly.
  1. If all of the above is OK, then you need to enable the network interfaces
apt-get install net-tools iproute2 -y
+systemctl restart networking
  1. Then you can test the IP address of the network interface.
Execute theifconfigcommand, and there should be a he-ipv6 interface, similar to the following:
8
Or execute:
curl ipv6.ip.sb
Returns the IPV6 address you bound to
  1. Additional settings for NAT VPS
IPv4 NAT VPS may require some additional settings beyond the IP replacement operation mentioned earlier, otherwise it may still not be able to access the IPv6 network.
apt-get install ufw -y
+ufw allow 41
Add the relevant routing rules
route -A inet6 add ::/0 dev he-ipv6
  1. If the IPV6 network is no longer needed and you want to delete it, delete the he-ipv6 network interface configuration.
If you want to delete the he-ipv6 network interface configuration (if not, it will be enabled automatically after reboot), remember to modify the/etc/network/interfacesfile to remove the content added in the red box before.
Then reboot the server to remove the
tunnelbroker_ch ​
Similar to the above, first register an account at https://www.tunnelbroker.ch/ and click on the activation email after registering.
Then you have to fill in the IPV4 address of your server.
After creating an account, you need to go to the Config page instead of the details page.
Don't use the following page, first refresh the page without the light blue box and then stop refreshing it
Don't stop refreshing after the light blue box pops up
Record the content of the last red box on the following page, and prepare to modify the host configuration file.
Copy the last red box of the page without the blank lines.
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforTunnelBrokerCh, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then clickCovertto convert the format, and wait for the page to refresh to show the converted configuration file.
Then use vim or vi to modify the/etc/network/interfacesfile to add content, or modify the following command to add new content
tee -a /etc/network/interfaces <<EOF
+# Modify the
+EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
+systemctl restart networking
Make sure the environment is OK before you do anything else
ip4market_ru ​
Similar to the above, first register an account at https://tb.ip4market.ru, the registered email address must be an unseen email address, the phone number can be written randomly without verification, and the IP address should be the IPV4 address of the host you want to attach.
The IP address is the IPV4 address of the host computer you are attaching to
Then you have to go through Recaptcha's human-machine verification, and click register.
You will receive an activation email with your password, memorize it.
Then login on the homepage
Then you will be taken to this page
Hold down the right button and copy the four lines framed in red, which are
Server IPv4.
+Client IPv4
+Server IPv6
+Client IPv6
For these four lines, press ctrl+c to copy or right-click to copy
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforip4market, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then clickCovertto convert the formatting
Then the page will be refreshed automatically and you need to modify the contents of the/etc/network/interfacesfile with vim or vi commands, or modify the following commands to add new contents.
tee -a /etc/network/interfaces <<EOF
+# Modify the
+EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
+systemctl restart networking
Make sure the environment is OK before you do anything else
netassist_ua ​
Similar to the above operation, first in https://tb.netassist.ua/ register an account first, after registration, click on the activation of the mail, the activation page will have a password display, remember to record!
Then fill in the IPV4 address of your server, you can change it later, just fill in a random one first.
Then you will get to this page
a
The first red box is the location of your host's IPV4 address, if you want to modify it, modify it there, and then click change to save.
The second red box is for```Linux``, and then click on show
b
The above content will appear, copy all the boxed parts without blank lines.
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforNetAssist, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then click onCovertto convert the formatting
c
Then the page will be refreshed automatically and you need to modify the contents of the/etc/network/interfacesfile with vim or vi commands, or modify the following commands to add new contents.
tee -a /etc/network/interfaces <<EOF
+# Modify the
+EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
+systemctl restart networking
Make sure the environment is OK before you do anything else
Transfer IPV6 subnets between different servers ​
Related repository: https://github.com/oneclickvirt/6in4
This method will provide a way to split a /80 out of the IPV6 segment on A and attach it to B to use.
Features ​
  • Self-built IPv6 tunnel for sit/gre/ipip protocols
  • Support to customize the IPV6 subnet size to be cut out, and the appropriate IPV6 subnet information in CIDR format will be calculated automatically.
  • Automatically recognizes the IPV6 subnet size of the server side
  • will automatically set up the tunnel server and print the commands that the client needs to execute
  • Setting up the IPV6 tunnel is easy to understand and easy to remove
Environmental Preparation ​
VPS(A)VPS(B)
one IPV4 address (server_ipv4)one IPV4 address (clinet_ipv4)
one IPV6 subnetno IPV6 address
Hereafter referred to as serverHereafter referred to as client
Usage ​
Download Script
curl -L https://raw.githubusercontent.com/oneclickvirt/6in4/main/6in4.sh -o 6in4.sh && chmod +x 6in4.sh
Execute it
./6in4.sh client_ipv4 <mode_type> <subnet_size>
OptionsOptional Option 1Optional Option 2Optional Option 3
<mode_type>gresitipip
<subnet_size>6480112
<mode_type> only support those three protocols for now, the more advanced the more recommended, no fill in the default is sit protocol
<subnet_size> as long as it is larger than the original system subnet mask, and is a multiple of 8, if you don't fill it in, it defaults to 80.
Remember to replace client_ipv4 with the IPV4 address of the machine you want to attach IPV6 to, and the command you need to execute on the client side will be sent back to you after execution, see the instructions after execution for details.
To prevent you from forgetting to copy the commands, the commands themselves will be written to the 6in4.log file under the current path, you can use cat 6in4.log to query the commands that need to be executed on the client side
For copied commands, be sure to select option 6in4 in https://ipv6tunnel.spiritlhl.top/ before converting!
Then the page will be refreshed automatically and you need to modify the contents of the/etc/network/interfacesfile with vim or vi commands, or modify the following commands to add new contents.
tee -a /etc/network/interfaces <<EOF
+# Modify here
+EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
+systemctl restart networking
Make sure the environment is OK before you do anything else
Check server status ​
systemctl status ndpresponder
ip addr show
Check client status ​
ip addr show
curl ipv6.ip.sb
Delete tunnel ​
server
ip link set server-ipv6 down
+ip tunnel del server-ipv6
client
ip link set user-ipv6 down
+ip tunnel del user-ipv6
The above deletion is only temporary, for permanent deletion you must modify and delete the contents of the /etc/network/interfaces file that you have previously added.
one more thing ​
In fact https://tunnelbroker.net/ supports the application of IPV6 subnets of size /48
Make the request here, then when converting the format change the original /64 IPV6 address to a /48 IPV6 address and you'll get a larger IPV6 subnet!

+    
+    
+  
+
\ No newline at end of file
diff --git a/en/guide/lxd/lxd_extra_config.html b/en/guide/lxd/lxd_extra_config.html
new file mode 100644
index 0000000000..3d6ee66417
--- /dev/null
+++ b/en/guide/lxd/lxd_extra_config.html
@@ -0,0 +1,37 @@
+
+
+  
+    
+    
+    Custom Configuration | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Custom Configuration ​
TIP
The following configurations may increase the load on the server. Only install them if necessary.
TIP
If you are using the server for personal use, you can ignore the installation of some abuse prevention scripts.
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/spiritLHLS/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
+netfilter-persistent reload
+service netfilter-persistent restart
Uninstall the IPV6 address binding daemon and corresponding files
shell
systemctl stop add-ipv6.service
+systemctl disable add-ipv6.service
+rm /etc/systemd/system/add-ipv6.service
+systemctl daemon-reload
+rm /usr/local/bin/add-ipv6.sh
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/spiritLHLS/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/spiritLHLS/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
One-click Installation of Common Pre-configured Environment for LXD 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/spiritLHLS/lxd/main/scripts/backend.sh -o backend.sh && chmod +x backend.sh && bash backend.sh
One-Click Installation of Cockpit Visualization Panel for Mother Hen ​
  • (Optional, this panel is just for convenient visualization operations, it's okay if not present)
  • Original author's repository: Link
shell
lxc config set core.https_address [::]
+lxc config set core.trust_password some-secret-string
+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
new file mode 100644
index 0000000000..e70fc32463
--- /dev/null
+++ b/en/guide/lxd/lxd_install.html
@@ -0,0 +1,31 @@
+
+
+  
+    
+    
+    LXD Installation Guide | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
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.
Manual Installation ​
Recommended for beginners to avoid potential troubleshooting. However, if you're experienced and comfortable with debugging bugs, you can also use the later one-click installation method for convenience.
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/spiritLHLS/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 the
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.
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)
If you are on a Debian-based host, be sure to execute this script within a 'screen' session to prevent ZFS compilation installation failure due to SSH interruptions during long-term runs.
The virtual memory mentioned here refers to the desired SWAP size, and the storage pool represents the total size of all disks allocated for your virtual machines.
During the environment installation process, you might need to restart the server to load the kernel with ZFS support and then execute the installation command again. Follow the prompts in the command line after running for accurate instructions.
Enable the lxcfs-related configuration of lxd by default, so that in-container querying of container information changes to information about the container itself rather than the host.
If the script prompts you to restart the system and execute the script again, and if the second execution still requires a system restart to load the kernel, it means the kernel loading failed during the previous attempt. It's recommended to reinstall the host system using an Ubuntu-based version to resolve this issue.
Each time you run the script, you'll need to input the initialization configuration. So, if the script prompts you to restart the system and execute again, you'll need to input the initialization configuration again.
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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.

+    
+    
+  
+
\ No newline at end of file
diff --git a/en/guide/lxd/lxd_lxc.html b/en/guide/lxd/lxd_lxc.html
new file mode 100644
index 0000000000..a133ba9ad1
--- /dev/null
+++ b/en/guide/lxd/lxd_lxc.html
@@ -0,0 +1,50 @@
+
+
+  
+    
+    
+    LXC virtualization | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
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/spiritLHLS/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 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 for customizing the system of the server, do not fill out the default use of debian11 when left blank, note that the incoming parameters for the system name + version number, such as:
  • 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.
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!
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
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
+ls
Normal version batch generation ​
Opened Chick Configuration:
  • 1 core 256MB RAM 1GB hard disk limited to 300Mbit bandwidth
  • With 1 SSH port, 25 extranet ports
  • Default memory and hard disk size
TIP
lxc if the command is no problem, the execution of the initialization of the opening of the servers, this step is best to put ```screen`` in the background to suspend the execution of the opening of the servers, the length of time with you to open a few and the mother hen configuration-related
Execute the following command to load the boot script
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/init.sh -o init.sh && chmod +x init.sh && dos2unix init.sh
The following command opens 10 chicks with the name prefix tj.
shell
./init.sh tj 10
Sometimes there is a problem with the path where init.sh is run, in this case it is recommended to add sudo in front of it to force it to run in the root directory
Bulk generation of pure SSH port versions ​
Opened Chick Configuration:
  • 1 core 128MB RAM 300MB hard disk limited to 300Mbit bandwidth
  • Only one SSH port
  • Unable to mount warp
TIP
lxc if the command is no problem, the execution of the initialization of the opening of the chick, this step is best to put the ```screen`` in the background to hang the execution of the opening of the chick, the length of time you open the chick with the opening of a few and the mother hen configuration-related
Load boot script
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/least.sh -o least.sh && chmod +x least.sh && dos2unix least.sh
The last line of the following command opens 10 chicks with the chick name prefix tj
shell
./least.sh tj 10
Sometimes there is a problem with the path where last.sh is run, in this case it is recommended to force the root directory to run by adding sudo in front of it.
Custom Batch Generation of Versions ​
  • Customizable memory and hard disk sizes
  • It's also fine if you have manually executed the above batch generation before; the configuration inherits without overwriting
If you need to batch-generate servers multiple times, you can use the following:
Command:
curl -L https://github.com/spiritLHLS/lxd/raw/main/scripts/add_more.sh -o add_more.sh && chmod +x add_more.sh && bash add_more.sh
Can be run multiple times to batch generate chicks, and inherit the previous part has been generated in the back to add, customizable memory and hard disk size
View the information of the batch opened chicks ​
After opening the chicks, the specific information will be generated in the log file in the current directory, with the following format
shell
Server_1_Name Password SSH_Port Public_Port_Start Public_Port_End
+Server_2_Name Password SSH_Port Public_Port_Start Public_Port_End
To view it, simply print the log file by executing the following command in the current directory
shell
cat log
WARNING
Don't use the chicks opened by this script as a production environment, LXC virtualization doesn't support changing kernel, dd, turning on bbr, etc.
Some common LXD commands ​
View all containers:
bash
lxc list
View details of a specific container:
bash
lxc info container_name
Start a specific container:
bash
lxc start container_name
Stop a specific container:
bash
lxc stop container_name
Delete a specific container:
bash
lxc delete -f container_name
Enter the container's shell:
bash
lxc exec container_name /bin/bash
TIP
Instead of /bin/bash, you can use /bin/sh in alpine, which is /bin/bash on regular systems.
To exit, type ```exit`` and enter.
Delete all LXC containers
bash
lxc list -c n --format csv | xargs -I {} lxc delete -f {}
Perform deletion of useless logs within a container
bash
sudo apt-get autoremove
+sudo apt-get clean
+sudo find /var/log -type f -delete
+sudo find /var/tmp -type f -delete
+sudo find /tmp -type f -delete
+sudo find /var/cache/apt/archives -type f -delete
Delete the original configuration script
bash
rm -rf /usr/local/bin/ssh_sh.sh
+rm -rf /usr/local/bin/config.sh
+rm -rf /usr/local/bin/ssh_bash.sh
+rm -rf /usr/local/bin/check-dns.sh
+rm -rf /root/ssh_sh.sh
+rm -rf /root/config.sh
+rm -rf /root/ssh_bash.sh
+rm -rf /root/buildone.sh
+rm -rf /root/add_more.sh
+rm -rf /root/build_ipv6_network.sh
Download back the relevant configuration scripts for the new version
bash
wget https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/check-dns.sh -O /usr/local/bin/check-dns.sh && chmod +x /usr/local/bin/check-dns.sh
+wget https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/config.sh -O /usr/local/bin/config.sh && chmod +x /usr/local/bin/config.sh
+wget https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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
new file mode 100644
index 0000000000..bbbfcc5cec
--- /dev/null
+++ b/en/guide/lxd/lxd_precheck.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    Preface | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
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.
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, Debian can not use zfs automatically switch to another storage type!
  • 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/spiritLHLS/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
new file mode 100644
index 0000000000..ff6d29f8bf
--- /dev/null
+++ b/en/guide/lxd/lxd_qa.html
@@ -0,0 +1,27 @@
+
+
+  
+    
+    
+    One Click Virtualization | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
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
luxvps 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
new file mode 100644
index 0000000000..199df3a69c
--- /dev/null
+++ b/en/guide/lxd/lxd_thanks.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    One Click Virtualization | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance

+    
+    
+  
+
\ No newline at end of file
diff --git a/en/guide/pve/pve_custom.html b/en/guide/pve/pve_custom.html
new file mode 100644
index 0000000000..77e0f38034
--- /dev/null
+++ b/en/guide/pve/pve_custom.html
@@ -0,0 +1,39 @@
+
+
+  
+    
+    
+    Some custom scripts | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Some custom scripts ​
Each script may have its own system requirements, check them out!
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 \
+--privileged \
+--name pve \
+--add-host pve:10.13.14.101 \
+--hostname pve \
+spiritlhl/pve:7_x86_64
ARM architecture
bash
docker run -idt --network host \
+--privileged \
+--name pve \
+--add-host pve:10.13.14.101 \
+--hostname pve \
+spiritlhl/pve:7_aarch64
The web panel is actually opened in the container, but the network has used the host mode, the port of the PVE is about the same as the port of the host used
There are many bugs need to be fixed, welcome to PR to solve the problem, the actual test on the Ubuntu system host machine to install Proxmox VE panel success, solved the problem of installing Proxmox VE over the network can only be used to use the Debian system as a host machine!

+    
+    
+  
+
\ No newline at end of file
diff --git a/en/guide/pve/pve_install.html b/en/guide/pve/pve_install.html
new file mode 100644
index 0000000000..2647b3c7db
--- /dev/null
+++ b/en/guide/pve/pve_install.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    PVE Body Installation | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
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.
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/spiritLHLS/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/spiritLHLS/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.
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
Before executing this command, if the host needs to append the address of the IPV6 tunnel, see the LXD Custom section for appending it to the corresponding file, but please ignore the initial environment modification section for it.
  • 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/spiritLHLS/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
new file mode 100644
index 0000000000..b4a87067ab
--- /dev/null
+++ b/en/guide/pve/pve_kvm.html
@@ -0,0 +1,38 @@
+
+
+  
+    
+    
+    KVM Virtualization | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
KVM Virtualization ​
SSH Login Instructions ​
The virtual machines created through KVM virtualization do not have the username root by default. To switch to the root user, you need to execute sudo -i .
Of course, some templates actually allow logging in with the username root, and the default root password is password. You can give it a try.
Once you've logged in via SSH and switched to root privileges, it's crucial to change the root password. You can use the following command to do so.
Command:
bash
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
Partial Notes ​
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.
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.
Considerations for opening a KVM 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 KVM 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
Virtual machines with standalone NAT configuration in KVM virtualization. ​
  • 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/spiritLHLS/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 102 test1 oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
After setup is completed, you can execute cat vm102 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
VMID102
SSH Usernametest1
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
Deletion specific VM ​
  • Stop VM
  • Delete VM
  • Delete port mapping
  • Restart network
  • Delete log files
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 above
shell
./pve_delete.sh 102
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 KVM Virtualization and 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/spiritLHLS/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
+systemctl restart networking.service
+systemctl restart ndpresponder.service
+iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
+iptables-save > /etc/iptables/rules.v4
+rm -rf vmlog
+rm -rf vm*
TIP
Before modifying the VM configuration for PVE, you must shut it down first. After making the configuration changes, start it again to avoid configuration reload errors.
Setting Up Virtual Machines with Dedicated IPv4 Addresses ​
Two versions are available, choose as needed.
Version with Automatic Selection of IPv4 Address (No Manual Specification Required) ​
WARNING
Before use, ensure that the current host machine has at least 2 available IP addresses within its IP range, and there are unallocated IP addresses. These unallocated IP addresses should not be bound to the host machine.
  • Automatically detect available IP ranges. Use ping to identify unallocated IP addresses and select one to bind to the virtual machine.
  • If the host machine has an accompanying IPv6 subnet, there will be an option to attach an IPv6 address.
  • Relevant system information will be stored in the corresponding virtual machine's NOTE section, accessible for viewing on the web interface.
  • 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/spiritLHLS/pve/main/scripts/buildvm_extraip.sh -o buildvm_extraip.sh && chmod +x buildvm_extraip.sh
Meaning of each parameter
shell
./buildvm_extraip.sh VMID Username Password Number_of_CPU_Cores Memory_Size_in_MB Disk_Size_in_GB OS Storage_Disk Attach_IPV6(Default is N)
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_extraip.sh 152 test1 oneclick123 1 1024 10 debian12 local N
The above command is used to create a virtual machine with a dedicated IPv4 address.
AttributeValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
OSdebian12
Storagelocal disk
IPv6 AddonNot attached by default
Version Requiring Manual Specification of IPV4 Address ​
  • Manual specification of IPV4 address with subnet length in the command is required.
  • If the host machine comes with an IPV6 subnet, you can choose whether to add an IPV6 address additionally.
  • If the vendor has provided an IPV4 address and subnet length, please carefully compare and write the parameters in the command format shown below.
  • Relevant system information will be stored in the NOTE of the corresponding virtual machine and can be viewed on the WEB end.
  • 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/spiritLHLS/pve/main/scripts/buildvm_manual_ip.sh -o buildvm_manual_ip.sh && chmod +x buildvm_manual_ip.sh
Meaning of each parameter
shell
./buildvm_manual_ip.sh VMID USERNAME PASSWORD CPU_CORES MEMORY_SIZE_GB STORAGE_SIZE_GB OS STORAGE_DISK IPV4_ADDRESS ATTACH_IPV6(defaults to N)
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_manual_ip.sh 152 test1 oneclick123 1 1024 10 debian12 local a.b.c.d/24 N
The above command is used to create a virtual machine with an independent IPV4 address.
AttributeValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
Operating Systemdebian12
Storage DiskLocal Disk (System Disk)
IPV4 Addressa.b.c.d
Subnet/24 Subnet
IPV6None
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 ​
  • Automatically detect available IPv6 ranges and bind the corresponding V6 address, based on the virtual machine's number, to the virtual machine.
  • System-related information will be stored in the NOTES section of the respective virtual machine, accessible for viewing on the web interface.
Usage Instructions ​
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 test1 oneclick123 1 1024 10 debian12 local
The above command is used to create a virtual machine with only IPv6 addresses.
ParameterValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
Operating Systemdebian12
Storage Disklocal
Delete Example vm152 ​
shell
qm stop 152
+qm destroy 152
+systemctl restart ndpresponder.service
+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
new file mode 100644
index 0000000000..bb61ffb13c
--- /dev/null
+++ b/en/guide/pve/pve_lxc.html
@@ -0,0 +1,37 @@
+
+
+  
+    
+    
+    LXC Virtualization | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
LXC Virtualization ​
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 ​
System Support:
  • debian10, debian11
  • ubuntu18, ubuntu20, ubuntu22
  • centos8, almalinux9
  • Other systems may or may not be supported, please test on your own.
TIP
System parameters are always in lowercase, consisting of the system name concatenated with the version number. For x86_64 systems, you can check available system names and version numbers using pveam available --section system. For ARM systems, you can check supported systems and version numbers at https://mirror.tuna.tsinghua.edu.cn/lxc-images/images/, similar to the version numbers obtained by executing pveam available --section system. (Please note that the parameters used in the script are only lowercase English system names concatenated with version numbers.)
The default username for all CTs is root.
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
After setting up, you can execute cat ct102 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
VMID102
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
Deletion specific CT ​
  • Stop CT
  • Delete CT
  • Delete Port Mapping
  • Restart Network
  • Delete Log Files
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 above
shell
./pve_delete.sh 102
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/spiritLHLS/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
+service networking restart
+systemctl restart networking.service
+systemctl restart ndpresponder.service
+iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
+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 ​
  • Automatically detect available IPv6 ranges and bind the corresponding V6 address based on the container number to the container.
  • Relevant system information will be stored in the NOTES of the corresponding container, accessible for viewing on the web interface.
Download script ​
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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)
Deletion Example ​
shell
rm -rf ct*
+pct stop 152 
+pct destroy 152
+systemctl restart ndpresponder.service

+    
+    
+  
+
\ No newline at end of file
diff --git a/en/guide/pve/pve_precheck.html b/en/guide/pve/pve_precheck.html
new file mode 100644
index 0000000000..518d41f213
--- /dev/null
+++ b/en/guide/pve/pve_precheck.html
@@ -0,0 +1,28 @@
+
+
+  
+    
+    
+    Preface | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
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.
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 LXD 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) ​
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 ​
  • Before the execution of scripts related to this project, be sure to execute 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.
  • Detecting the IPV6 network configuration of the machine (IPV6 can be installed with or without IPV6, it is just a query).
  • Detect whether the hardware configuration meets the minimum requirements
  • Detect whether the hardware environment can be nested virtualization KVM type of server
  • Detect whether the system environment can nest virtualized KVM-type servers.
  • Can not be nested virtualization KVM type of server can also open LXC virtualization server, but do not recommend installing PVE, rather use LXD
Command:
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/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*



+    
+    
+  
+
\ No newline at end of file
diff --git a/en/guide/pve/pve_qa.html b/en/guide/pve/pve_qa.html
new file mode 100644
index 0000000000..27e1595d59
--- /dev/null
+++ b/en/guide/pve/pve_qa.html
@@ -0,0 +1,35 @@
+
+
+  
+    
+    
+    Solve the puzzle | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
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!
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
+    echo "post-up /sbin/ethtool -K $auto_interface tx off rx off" >> /etc/network/interfaces
+    chattr +i /etc/network/interfaces
+fi
Then report the rebooted disconnected machine to @spiritlhl_bot for the script to be updated and repaired automatically.
PVE Installation Failed ​
If you encounter any issues with installing on certain machines, and if you're in a hurry, you can try using the scripts from the following repository to reinstall as Debian 11 first.
bash <(curl -sSL https://raw.githubusercontent.com/leitbogioro/Tools/master/Linux_reinstall/InstallNET.sh) -debian 12 -pwd 'oneclickvirt139' --network "static"
The system username after dd at this point is root, and the password is oneclickvirt139.
If you have time or if it's still not working, please contact @spiritlhl_bot for assistance.
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.
What to do if you accidentally delete a NAT mapping rule ​
Use the following command to map back
shell
iptables -t nat -F
+iptables -t filter -F
+service networking restart
+systemctl restart networking.service
+cat /etc/iptables/rules.v4 | iptables-restore
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
hostaris German version (Note: Issues with the vendor's system template, IPV6 is not functional, and poor connectivity with Github)
adtaq Storage KVM server with lowest configuration
nocix Dedicated servers
crunchbits VPS
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.
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
new file mode 100644
index 0000000000..3884d69271
--- /dev/null
+++ b/en/guide/pve/pve_thanks.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    One Click Virtualization | One Click Virtualization
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance

+    
+    
+  
+
\ No newline at end of file
diff --git a/en/index.html b/en/index.html
new file mode 100644
index 0000000000..4d5cf867d6
--- /dev/null
+++ b/en/index.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    K'thun
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
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.
Comes with internal and external port forwarding and automatic IP address assignment
Self-contained internal and external port forwarding and automatic IP address allocation, 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, Android, Windows, 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.

+    
+    
+  
+
\ No newline at end of file
diff --git a/en_US/developer/index.html b/en_US/developer/index.html
deleted file mode 100644
index 9658fd31b9..0000000000
--- a/en_US/developer/index.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    Development Manual | Welcome to the oneclickvirt Development Manual.
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
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_US/developer/l10n.html b/en_US/developer/l10n.html
deleted file mode 100644
index d247e9b9b5..0000000000
--- a/en_US/developer/l10n.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    One Click Virtualization | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
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_US/guide/dashboard.html b/en_US/guide/dashboard.html
deleted file mode 100644
index 0ce8d32c11..0000000000
--- a/en_US/guide/dashboard.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    One Click Virtualization | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
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.
Please make sure to keep the original formatting by enclosing the translation in and for easy copying.
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 ​
Allows for the creation of KVM virtualized virtual machines and LXC virtualized containers.
https://github.com/spiritLHLS/pve
Hits
LXD ​
LXC Virtualization Containers Can Be Created.
https://github.com/spiritLHLS/lxd
Hits
Docker ​
Docker virtualized containers Can Be Created.
https://github.com/spiritLHLS/docker
Hits



-    
-    
-  
-
\ No newline at end of file
diff --git a/en_US/guide/dashboardq.html b/en_US/guide/dashboardq.html
deleted file mode 100644
index bf645fd0d7..0000000000
--- a/en_US/guide/dashboardq.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    One Click Virtualization | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
-    
-    
-  
-
\ No newline at end of file
diff --git a/en_US/guide/docker_build.html b/en_US/guide/docker_build.html
deleted file mode 100644
index da89fd6c30..0000000000
--- a/en_US/guide/docker_build.html
+++ /dev/null
@@ -1,42 +0,0 @@
-
-
-  
-    
-    
-    Introduction | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
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/spiritLHLS/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/spiritLHLS/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
-rm -rf dclog
-ls
Delete the original configuration script
bash
rm -rf /usr/local/bin/ssh_sh.sh
-rm -rf /usr/local/bin/ssh_bash.sh
-rm -rf /usr/local/bin/check-dns.sh
-rm -rf /root/ssh_sh.sh
-rm -rf /root/ssh_bash.sh
-rm -rf /root/onedocker.sh
-rm -rf /root/create_docker.sh
Download back the relevant configuration scripts for the new version
bash
wget https://raw.githubusercontent.com/spiritLHLS/docker/main/extra_scripts/check-dns.sh -O /usr/local/bin/check-dns.sh && chmod +x /usr/local/bin/check-dns.sh
-wget https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/config.sh -O /usr/local/bin/config.sh && chmod +x /usr/local/bin/config.sh
-wget https://raw.githubusercontent.com/spiritLHLS/docker/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/spiritLHLS/docker/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/spiritLHLS/docker/main/scripts/onedocker.sh -O /root/onedocker.sh && chmod +x /root/onedocker.sh
-wget https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/create_docker.sh -O /root/create_docker.sh && chmod +x /root/create_docker.sh

-    
-    
-  
-
\ No newline at end of file
diff --git a/en_US/guide/docker_custom.html b/en_US/guide/docker_custom.html
deleted file mode 100644
index 75e9d62597..0000000000
--- a/en_US/guide/docker_custom.html
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-  
-    
-    
-    Script for One-Click Installation of Certain Containers using Docker | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
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 Android System Container ​
  • 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.)
Setup:
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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.
Deletion:
  • Delete the container
  • Delete the corresponding container image
  • Delete the configuration file
shell
docker rm -f android
-docker rm -f scrcpy_web
-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
-rm -rf /etc/nginx/passwd_scrcpy_web
-rm -rf /root/android_info
One-Click Setup of Windows System Container ​
  • 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/spiritLHLS/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.
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/spiritLHLS/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}
-docker rmi jlesage/firefox
One-Click Setup of Chrome Browser Container ​
  • Crashing self-start has been set
  • Web checksums and passwords can be set.
  • Customizable maximum container memory footprint
  • No need to consider whether to support nested virtualization and server architecture.
  • Supports sound mapping
Sound mapping is supported Host requires at least 1 core, 2G RAM, and 5G hard disk, and the size of the container to be opened will take up a minimum of 1G hard disk.
Opening
The default password after opening is oneclick.
The default http port is 3004, open http://IPV4:3004 after opening.
The default https port is 3005, open https://IPV4:3005 after opening.
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onechromium.sh -o onechromium.sh && chmod +x onechromium.sh && bash onechromium.sh
Delete
Change the following port number 3004 to your actual http port number, then execute the command enter twice to delete the container, configuration file, and corresponding image
shell
PORT="3004"
-docker stop chromium_${PORT}
-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/spiritLHLS/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/spiritLHLS/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_US/guide/docker_install.html b/en_US/guide/docker_install.html
deleted file mode 100644
index aeae1dcef7..0000000000
--- a/en_US/guide/docker_install.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    Preface | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
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/spiritLHLS/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_US/guide/docker_precheck.html b/en_US/guide/docker_precheck.html
deleted file mode 100644
index c73ab14547..0000000000
--- a/en_US/guide/docker_precheck.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    Introduction | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
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.
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.
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.
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 LXD 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_US/guide/docker_qa.html b/en_US/guide/docker_qa.html
deleted file mode 100644
index ad009c3c9a..0000000000
--- a/en_US/guide/docker_qa.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    Solve the puzzle | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
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_US/guide/docker_thanks.html b/en_US/guide/docker_thanks.html
deleted file mode 100644
index 196ab241c4..0000000000
--- a/en_US/guide/docker_thanks.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    One Click Virtualization | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance

-    
-    
-  
-
\ No newline at end of file
diff --git a/en_US/guide/lxd_custom.html b/en_US/guide/lxd_custom.html
deleted file mode 100644
index 9ec13f3f27..0000000000
--- a/en_US/guide/lxd_custom.html
+++ /dev/null
@@ -1,52 +0,0 @@
-
-
-  
-    
-    
-    Attach free IPV6 address segments to host machines | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
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 或 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、ipip自定义
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
-# systemctl disable systemd-networkd.socket
If you want to install ifupdown to control the network, this tool is available on all major linux systems.
apt-get install ifupdown -y
If you want to install ifupdown2 for network management, which is generally only available on debian systems, you can install
apt-get install ifupdown2 -y
After the installation is complete, select which package is installed behind to convert the format.
systemctl start networking
-systemctl enable networking
Then restart the server, check whether the machine's network will be rebooted due to the modification of the case of loss of connection, and runuptimeto observe that the startup has been more than 1 minute before proceeding to the next steps
If it is inactive and active, there is no need to switch the network management program and you can proceed directly to the next step.
Since some servers have default intranet IPV6 routes that will conflict with the tunnel, you can use the following command to remove the default IPV6 routes
default_route=$(ip -6 route show | awk '/default via/{print $3}') && [ -n "$default_route" ] && ip -6 route del default via $default_route dev eth0
This assumes that your client's server's default NIC is eth0, you can use ip -6 route to see the default route and replace it, the default route starts with default via, and uses dev to specify the default NIC, you just need to find it according to this rule
tunnelbroker_net ​
Combined with a script that opens containers with IPV6 addresses with a single click, you can attach an IPV6 address from he to each container
The downside is that the addresses are dark/dirty, and cloudflare's cdn will most likely not be able to latch on, test it yourself
  1. Register an account at https://tunnelbroker.net/ and clickCreate Regular Tunnelon the left.
1
  1. Fill in your server's IPV4 address in the red box, choose a connection point that is physically close to your server, for example, if your machine is in Los Angeles, choose a connection point on the west coast of the United States, and then clickCreate Tunnelto create the tunnel when you are prompted by the green box!
2
3
4
  1. Wait for the following screen, clickExample Configurationsand select the corresponding system, for example, the host of LXD is definitely Debian/Ubuntu.
5
6
  1. The boxed part is the file to be modified and the content to be filled in.
7
  1. Exchange the format of the command then add IPV6 settings to your network configuration file.
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforTunnelBrokerNet, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then clickCovertto convert the format, and wait for the page to refresh to show the converted configuration file.
Then use vim or vi to modify the/etc/network/interfacesfile to add content, or modify the following command to add new content
tee -a /etc/network/interfaces <<EOF
-# Here, copy and paste the contents of the configuration file in the red box, and then run this command.
-EOF
Then you can usecat /etc/network/interfacesto see if the configuration file is written correctly.
  1. If all of the above is OK, then you need to enable the network interfaces
apt-get install net-tools iproute2 -y
-systemctl restart networking
  1. Then you can test the IP address of the network interface.
Execute theifconfigcommand, and there should be a he-ipv6 interface, similar to the following:
8
Or execute:
curl ipv6.ip.sb
Returns the IPV6 address you bound to
  1. Additional settings for NAT VPS
IPv4 NAT VPS may require some additional settings beyond the IP replacement operation mentioned earlier, otherwise it may still not be able to access the IPv6 network.
apt-get install ufw -y
-ufw allow 41
Add the relevant routing rules
route -A inet6 add ::/0 dev he-ipv6
  1. If the IPV6 network is no longer needed and you want to delete it, delete the he-ipv6 network interface configuration.
If you want to delete the he-ipv6 network interface configuration (if not, it will be enabled automatically after reboot), remember to modify the/etc/network/interfacesfile to remove the content added in the red box before.
Then reboot the server to remove the
tunnelbroker_ch ​
Similar to the above, first register an account at https://www.tunnelbroker.ch/ and click on the activation email after registering.
Then you have to fill in the IPV4 address of your server.
After creating an account, you need to go to the Config page instead of the details page.
Don't use the following page, first refresh the page without the light blue box and then stop refreshing it
Don't stop refreshing after the light blue box pops up
Record the content of the last red box on the following page, and prepare to modify the host configuration file.
Copy the last red box of the page without the blank lines.
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforTunnelBrokerCh, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then clickCovertto convert the format, and wait for the page to refresh to show the converted configuration file.
Then use vim or vi to modify the/etc/network/interfacesfile to add content, or modify the following command to add new content
tee -a /etc/network/interfaces <<EOF
-# Modify the
-EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
-systemctl restart networking
Make sure the environment is OK before you do anything else
ip4market_ru ​
Similar to the above, first register an account at https://tb.ip4market.ru, the registered email address must be an unseen email address, the phone number can be written randomly without verification, and the IP address should be the IPV4 address of the host you want to attach.
The IP address is the IPV4 address of the host computer you are attaching to
Then you have to go through Recaptcha's human-machine verification, and click register.
You will receive an activation email with your password, memorize it.
Then login on the homepage
Then you will be taken to this page
Hold down the right button and copy the four lines framed in red, which are
Server IPv4.
-Client IPv4
-Server IPv6
-Client IPv6
For these four lines, press ctrl+c to copy or right-click to copy
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforip4market, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then clickCovertto convert the formatting
Then the page will be refreshed automatically and you need to modify the contents of the/etc/network/interfacesfile with vim or vi commands, or modify the following commands to add new contents.
tee -a /etc/network/interfaces <<EOF
-# Modify the
-EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
-systemctl restart networking
Make sure the environment is OK before you do anything else
netassist_ua ​
Similar to the above operation, first in https://tb.netassist.ua/ register an account first, after registration, click on the activation of the mail, the activation page will have a password display, remember to record!
Then fill in the IPV4 address of your server, you can change it later, just fill in a random one first.
Then you will get to this page
a
The first red box is the location of your host's IPV4 address, if you want to modify it, modify it there, and then click change to save.
The second red box is for```Linux``, and then click on show
b
The above content will appear, copy all the boxed parts without blank lines.
Then open https://ipv6tunnel.spiritlhl.top/ and selectOptionforNetAssist, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
Then click onCovertto convert the formatting
c
Then the page will be refreshed automatically and you need to modify the contents of the/etc/network/interfacesfile with vim or vi commands, or modify the following commands to add new contents.
tee -a /etc/network/interfaces <<EOF
-# Modify the
-EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
-systemctl restart networking
Make sure the environment is OK before you do anything else
Transfer IPV6 subnets between different servers ​
Related repository: https://github.com/oneclickvirt/6in4
This method will provide a way to split a /80 out of the IPV6 segment on A and attach it to B to use.
Features ​
  • Self-built IPv6 tunnel for sit/gre/ipip protocols
  • Support to customize the IPV6 subnet size to be cut out, and the appropriate IPV6 subnet information in CIDR format will be calculated automatically.
  • Automatically recognizes the IPV6 subnet size of the server side
  • will automatically set up the tunnel server and print the commands that the client needs to execute
  • Setting up the IPV6 tunnel is easy to understand and easy to remove
Environmental Preparation ​
VPS(A)VPS(B)
one IPV4 address (server_ipv4)one IPV4 address (clinet_ipv4)
one IPV6 subnetno IPV6 address
Hereafter referred to as serverHereafter referred to as client
Usage ​
Download Script
curl -L https://raw.githubusercontent.com/oneclickvirt/6in4/main/6in4.sh -o 6in4.sh && chmod +x 6in4.sh
Execute it
./6in4.sh client_ipv4 <mode_type> <subnet_size>
OptionsOptional Option 1Optional Option 2Optional Option 3
<mode_type>gresitipip
<subnet_size>6480112
<mode_type> only support those three protocols for now, the more advanced the more recommended, no fill in the default is sit protocol
<subnet_size> as long as it is larger than the original system subnet mask, and is a multiple of 8, if you don't fill it in, it defaults to 80.
Remember to replace client_ipv4 with the IPV4 address of the machine you want to attach IPV6 to, and the command you need to execute on the client side will be sent back to you after execution, see the instructions after execution for details.
To prevent you from forgetting to copy the commands, the commands themselves will be written to the 6in4.log file under the current path, you can use cat 6in4.log to query the commands that need to be executed on the client side
For copied commands, be sure to select option 6in4 in https://ipv6tunnel.spiritlhl.top/ before converting!
Then the page will be refreshed automatically and you need to modify the contents of the/etc/network/interfacesfile with vim or vi commands, or modify the following commands to add new contents.
tee -a /etc/network/interfaces <<EOF
-# Modify here
-EOF
Then you'll need to reboot the system a bit, or run
apt-get install net-tools iproute2 -y
-systemctl restart networking
Make sure the environment is OK before you do anything else
Check server status ​
systemctl status ndpresponder
ip addr show
Check client status ​
ip addr show
curl ipv6.ip.sb
Delete tunnel ​
server
ip link set server-ipv6 down
-ip tunnel del server-ipv6
client
ip link set user-ipv6 down
-ip tunnel del user-ipv6
The above deletion is only temporary, for permanent deletion you must modify and delete the contents of the /etc/network/interfaces file that you have previously added.
one more thing ​
In fact https://tunnelbroker.net/ supports the application of IPV6 subnets of size /48
Make the request here, then when converting the format change the original /64 IPV6 address to a /48 IPV6 address and you'll get a larger IPV6 subnet!

-    
-    
-  
-
\ No newline at end of file
diff --git a/en_US/guide/lxd_extra_config.html b/en_US/guide/lxd_extra_config.html
deleted file mode 100644
index 610f256068..0000000000
--- a/en_US/guide/lxd_extra_config.html
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-  
-    
-    
-    Custom Configuration | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Custom Configuration ​
TIP
The following configurations may increase the load on the server. Only install them if necessary.
TIP
If you are using the server for personal use, you can ignore the installation of some abuse prevention scripts.
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/spiritLHLS/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
-netfilter-persistent reload
-service netfilter-persistent restart
Uninstall the IPV6 address binding daemon and corresponding files
shell
systemctl stop add-ipv6.service
-systemctl disable add-ipv6.service
-rm /etc/systemd/system/add-ipv6.service
-systemctl daemon-reload
-rm /usr/local/bin/add-ipv6.sh
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/spiritLHLS/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/spiritLHLS/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
One-click Installation of Common Pre-configured Environment for LXD 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/spiritLHLS/lxd/main/scripts/backend.sh -o backend.sh && chmod +x backend.sh && bash backend.sh
One-Click Installation of Cockpit Visualization Panel for Mother Hen ​
  • (Optional, this panel is just for convenient visualization operations, it's okay if not present)
  • Original author's repository: Link
shell
lxc config set core.https_address [::]
-lxc config set core.trust_password some-secret-string
-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_US/guide/lxd_install.html b/en_US/guide/lxd_install.html
deleted file mode 100644
index 26b59043a3..0000000000
--- a/en_US/guide/lxd_install.html
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-  
-    
-    
-    LXD Installation Guide | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
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.
Manual Installation ​
Recommended for beginners to avoid potential troubleshooting. However, if you're experienced and comfortable with debugging bugs, you can also use the later one-click installation method for convenience.
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/spiritLHLS/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 the
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.
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)
If you are on a Debian-based host, be sure to execute this script within a 'screen' session to prevent ZFS compilation installation failure due to SSH interruptions during long-term runs.
The virtual memory mentioned here refers to the desired SWAP size, and the storage pool represents the total size of all disks allocated for your virtual machines.
During the environment installation process, you might need to restart the server to load the kernel with ZFS support and then execute the installation command again. Follow the prompts in the command line after running for accurate instructions.
Enable the lxcfs-related configuration of lxd by default, so that in-container querying of container information changes to information about the container itself rather than the host.
If the script prompts you to restart the system and execute the script again, and if the second execution still requires a system restart to load the kernel, it means the kernel loading failed during the previous attempt. It's recommended to reinstall the host system using an Ubuntu-based version to resolve this issue.
Each time you run the script, you'll need to input the initialization configuration. So, if the script prompts you to restart the system and execute again, you'll need to input the initialization configuration again.
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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.

-    
-    
-  
-
\ No newline at end of file
diff --git a/en_US/guide/lxd_lxc.html b/en_US/guide/lxd_lxc.html
deleted file mode 100644
index a053c951ce..0000000000
--- a/en_US/guide/lxd_lxc.html
+++ /dev/null
@@ -1,50 +0,0 @@
-
-
-  
-    
-    
-    LXC virtualization | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
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/spiritLHLS/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 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 for customizing the system of the server, do not fill out the default use of debian11 when left blank, note that the incoming parameters for the system name + version number, such as:
  • 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.
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!
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
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
-ls
Normal version batch generation ​
Opened Chick Configuration:
  • 1 core 256MB RAM 1GB hard disk limited to 300Mbit bandwidth
  • With 1 SSH port, 25 extranet ports
  • Default memory and hard disk size
TIP
lxc if the command is no problem, the execution of the initialization of the opening of the servers, this step is best to put ```screen`` in the background to suspend the execution of the opening of the servers, the length of time with you to open a few and the mother hen configuration-related
Execute the following command to load the boot script
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/init.sh -o init.sh && chmod +x init.sh && dos2unix init.sh
The following command opens 10 chicks with the name prefix tj.
shell
./init.sh tj 10
Sometimes there is a problem with the path where init.sh is run, in this case it is recommended to add sudo in front of it to force it to run in the root directory
Bulk generation of pure SSH port versions ​
Opened Chick Configuration:
  • 1 core 128MB RAM 300MB hard disk limited to 300Mbit bandwidth
  • Only one SSH port
  • Unable to mount warp
TIP
lxc if the command is no problem, the execution of the initialization of the opening of the chick, this step is best to put the ```screen`` in the background to hang the execution of the opening of the chick, the length of time you open the chick with the opening of a few and the mother hen configuration-related
Load boot script
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/least.sh -o least.sh && chmod +x least.sh && dos2unix least.sh
The last line of the following command opens 10 chicks with the chick name prefix tj
shell
./least.sh tj 10
Sometimes there is a problem with the path where last.sh is run, in this case it is recommended to force the root directory to run by adding sudo in front of it.
Custom Batch Generation of Versions ​
  • Customizable memory and hard disk sizes
  • It's also fine if you have manually executed the above batch generation before; the configuration inherits without overwriting
If you need to batch-generate servers multiple times, you can use the following:
Command:
curl -L https://github.com/spiritLHLS/lxd/raw/main/scripts/add_more.sh -o add_more.sh && chmod +x add_more.sh && bash add_more.sh
Can be run multiple times to batch generate chicks, and inherit the previous part has been generated in the back to add, customizable memory and hard disk size
View the information of the batch opened chicks ​
After opening the chicks, the specific information will be generated in the log file in the current directory, with the following format
shell
Server_1_Name Password SSH_Port Public_Port_Start Public_Port_End
-Server_2_Name Password SSH_Port Public_Port_Start Public_Port_End
To view it, simply print the log file by executing the following command in the current directory
shell
cat log
WARNING
Don't use the chicks opened by this script as a production environment, LXC virtualization doesn't support changing kernel, dd, turning on bbr, etc.
Some common LXD commands ​
View all containers:
bash
lxc list
View details of a specific container:
bash
lxc info container_name
Start a specific container:
bash
lxc start container_name
Stop a specific container:
bash
lxc stop container_name
Delete a specific container:
bash
lxc delete -f container_name
Enter the container's shell:
bash
lxc exec container_name /bin/bash
TIP
Instead of /bin/bash, you can use /bin/sh in alpine, which is /bin/bash on regular systems.
To exit, type ```exit`` and enter.
Delete all LXC containers
bash
lxc list -c n --format csv | xargs -I {} lxc delete -f {}
Perform deletion of useless logs within a container
bash
sudo apt-get autoremove
-sudo apt-get clean
-sudo find /var/log -type f -delete
-sudo find /var/tmp -type f -delete
-sudo find /tmp -type f -delete
-sudo find /var/cache/apt/archives -type f -delete
Delete the original configuration script
bash
rm -rf /usr/local/bin/ssh_sh.sh
-rm -rf /usr/local/bin/config.sh
-rm -rf /usr/local/bin/ssh_bash.sh
-rm -rf /usr/local/bin/check-dns.sh
-rm -rf /root/ssh_sh.sh
-rm -rf /root/config.sh
-rm -rf /root/ssh_bash.sh
-rm -rf /root/buildone.sh
-rm -rf /root/add_more.sh
-rm -rf /root/build_ipv6_network.sh
Download back the relevant configuration scripts for the new version
bash
wget https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/check-dns.sh -O /usr/local/bin/check-dns.sh && chmod +x /usr/local/bin/check-dns.sh
-wget https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/config.sh -O /usr/local/bin/config.sh && chmod +x /usr/local/bin/config.sh
-wget https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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_US/guide/lxd_precheck.html b/en_US/guide/lxd_precheck.html
deleted file mode 100644
index 1a52f2b2d1..0000000000
--- a/en_US/guide/lxd_precheck.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    Preface | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
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.
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, Debian can not use zfs automatically switch to another storage type!
  • 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/spiritLHLS/lxd/main/scripts/pre_check.sh)

-    
-    
-  
-
\ No newline at end of file
diff --git a/en_US/guide/lxd_qa.html b/en_US/guide/lxd_qa.html
deleted file mode 100644
index 2f9f98d5bd..0000000000
--- a/en_US/guide/lxd_qa.html
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-  
-    
-    
-    One Click Virtualization | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
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
luxvps German AMD Promotions

-    
-    
-  
-
\ No newline at end of file
diff --git a/en_US/guide/lxd_thanks.html b/en_US/guide/lxd_thanks.html
deleted file mode 100644
index 27a58c3771..0000000000
--- a/en_US/guide/lxd_thanks.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    One Click Virtualization | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
-    
-    
-  
-
\ No newline at end of file
diff --git a/en_US/guide/pve_custom.html b/en_US/guide/pve_custom.html
deleted file mode 100644
index 70226b0f1a..0000000000
--- a/en_US/guide/pve_custom.html
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-  
-    
-    
-    Some custom scripts | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Some custom scripts ​
Each script may have its own system requirements, check them out!
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 \
---privileged \
---name pve \
---add-host pve:10.13.14.101 \
---hostname pve \
-spiritlhl/pve:7_x86_64
ARM architecture
bash
docker run -idt --network host \
---privileged \
---name pve \
---add-host pve:10.13.14.101 \
---hostname pve \
-spiritlhl/pve:7_aarch64
The web panel is actually opened in the container, but the network has used the host mode, the port of the PVE is about the same as the port of the host used
There are many bugs need to be fixed, welcome to PR to solve the problem, the actual test on the Ubuntu system host machine to install Proxmox VE panel success, solved the problem of installing Proxmox VE over the network can only be used to use the Debian system as a host machine!

-    
-    
-  
-
\ No newline at end of file
diff --git a/en_US/guide/pve_install.html b/en_US/guide/pve_install.html
deleted file mode 100644
index e6230ea89a..0000000000
--- a/en_US/guide/pve_install.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    PVE Body Installation | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
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.
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/spiritLHLS/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/spiritLHLS/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.
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
Before executing this command, if the host needs to append the address of the IPV6 tunnel, see the LXD Custom section for appending it to the corresponding file, but please ignore the initial environment modification section for it.
  • 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/spiritLHLS/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_US/guide/pve_kvm.html b/en_US/guide/pve_kvm.html
deleted file mode 100644
index aeb7a984c7..0000000000
--- a/en_US/guide/pve_kvm.html
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-  
-    
-    
-    KVM Virtualization | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
KVM Virtualization ​
SSH Login Instructions ​
The virtual machines created through KVM virtualization do not have the username root by default. To switch to the root user, you need to execute sudo -i .
Of course, some templates actually allow logging in with the username root, and the default root password is password. You can give it a try.
Once you've logged in via SSH and switched to root privileges, it's crucial to change the root password. You can use the following command to do so.
Command:
bash
bash <(curl -sSL https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
Partial Notes ​
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.
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.
Considerations for opening a KVM 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 KVM 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
Virtual machines with standalone NAT configuration in KVM virtualization. ​
  • 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/spiritLHLS/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 102 test1 oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
After setup is completed, you can execute cat vm102 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
VMID102
SSH Usernametest1
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
Deletion specific VM ​
  • Stop VM
  • Delete VM
  • Delete port mapping
  • Restart network
  • Delete log files
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 above
shell
./pve_delete.sh 102
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 KVM Virtualization and 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/spiritLHLS/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
-systemctl restart networking.service
-systemctl restart ndpresponder.service
-iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
-iptables-save > /etc/iptables/rules.v4
-rm -rf vmlog
-rm -rf vm*
TIP
Before modifying the VM configuration for PVE, you must shut it down first. After making the configuration changes, start it again to avoid configuration reload errors.
Setting Up Virtual Machines with Dedicated IPv4 Addresses ​
Two versions are available, choose as needed.
Version with Automatic Selection of IPv4 Address (No Manual Specification Required) ​
WARNING
Before use, ensure that the current host machine has at least 2 available IP addresses within its IP range, and there are unallocated IP addresses. These unallocated IP addresses should not be bound to the host machine.
  • Automatically detect available IP ranges. Use ping to identify unallocated IP addresses and select one to bind to the virtual machine.
  • If the host machine has an accompanying IPv6 subnet, there will be an option to attach an IPv6 address.
  • Relevant system information will be stored in the corresponding virtual machine's NOTE section, accessible for viewing on the web interface.
  • 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/spiritLHLS/pve/main/scripts/buildvm_extraip.sh -o buildvm_extraip.sh && chmod +x buildvm_extraip.sh
Meaning of each parameter
shell
./buildvm_extraip.sh VMID Username Password Number_of_CPU_Cores Memory_Size_in_MB Disk_Size_in_GB OS Storage_Disk Attach_IPV6(Default is N)
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_extraip.sh 152 test1 oneclick123 1 1024 10 debian12 local N
The above command is used to create a virtual machine with a dedicated IPv4 address.
AttributeValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
OSdebian12
Storagelocal disk
IPv6 AddonNot attached by default
Version Requiring Manual Specification of IPV4 Address ​
  • Manual specification of IPV4 address with subnet length in the command is required.
  • If the host machine comes with an IPV6 subnet, you can choose whether to add an IPV6 address additionally.
  • If the vendor has provided an IPV4 address and subnet length, please carefully compare and write the parameters in the command format shown below.
  • Relevant system information will be stored in the NOTE of the corresponding virtual machine and can be viewed on the WEB end.
  • 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/spiritLHLS/pve/main/scripts/buildvm_manual_ip.sh -o buildvm_manual_ip.sh && chmod +x buildvm_manual_ip.sh
Meaning of each parameter
shell
./buildvm_manual_ip.sh VMID USERNAME PASSWORD CPU_CORES MEMORY_SIZE_GB STORAGE_SIZE_GB OS STORAGE_DISK IPV4_ADDRESS ATTACH_IPV6(defaults to N)
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_manual_ip.sh 152 test1 oneclick123 1 1024 10 debian12 local a.b.c.d/24 N
The above command is used to create a virtual machine with an independent IPV4 address.
AttributeValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
Operating Systemdebian12
Storage DiskLocal Disk (System Disk)
IPV4 Addressa.b.c.d
Subnet/24 Subnet
IPV6None
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 ​
  • Automatically detect available IPv6 ranges and bind the corresponding V6 address, based on the virtual machine's number, to the virtual machine.
  • System-related information will be stored in the NOTES section of the respective virtual machine, accessible for viewing on the web interface.
Usage Instructions ​
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 test1 oneclick123 1 1024 10 debian12 local
The above command is used to create a virtual machine with only IPv6 addresses.
ParameterValue
VMID152
Usernametest1
Passwordoneclick123
CPU1 core
Memory1024MB
Disk10GB
Operating Systemdebian12
Storage Disklocal
Delete Example vm152 ​
shell
qm stop 152
-qm destroy 152
-systemctl restart ndpresponder.service
-rm -rf vm152

-    
-    
-  
-
\ No newline at end of file
diff --git a/en_US/guide/pve_lxc.html b/en_US/guide/pve_lxc.html
deleted file mode 100644
index 35e0cd2e11..0000000000
--- a/en_US/guide/pve_lxc.html
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-  
-    
-    
-    LXC Virtualization | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
LXC Virtualization ​
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 ​
System Support:
  • debian10, debian11
  • ubuntu18, ubuntu20, ubuntu22
  • centos8, almalinux9
  • Other systems may or may not be supported, please test on your own.
TIP
System parameters are always in lowercase, consisting of the system name concatenated with the version number. For x86_64 systems, you can check available system names and version numbers using pveam available --section system. For ARM systems, you can check supported systems and version numbers at https://mirror.tuna.tsinghua.edu.cn/lxc-images/images/, similar to the version numbers obtained by executing pveam available --section system. (Please note that the parameters used in the script are only lowercase English system names concatenated with version numbers.)
The default username for all CTs is root.
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
After setting up, you can execute cat ct102 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
VMID102
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
Deletion specific CT ​
  • Stop CT
  • Delete CT
  • Delete Port Mapping
  • Restart Network
  • Delete Log Files
Download Script
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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 102 above
shell
./pve_delete.sh 102
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/spiritLHLS/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
-service networking restart
-systemctl restart networking.service
-systemctl restart ndpresponder.service
-iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
-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 ​
  • Automatically detect available IPv6 ranges and bind the corresponding V6 address based on the container number to the container.
  • Relevant system information will be stored in the NOTES of the corresponding container, accessible for viewing on the web interface.
Download script ​
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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)
Deletion Example ​
shell
rm -rf ct*
-pct stop 152 
-pct destroy 152
-systemctl restart ndpresponder.service

-    
-    
-  
-
\ No newline at end of file
diff --git a/en_US/guide/pve_precheck.html b/en_US/guide/pve_precheck.html
deleted file mode 100644
index 9a49adeb03..0000000000
--- a/en_US/guide/pve_precheck.html
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-  
-    
-    
-    Preface | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
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.
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 LXD 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) ​
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 ​
  • Before the execution of scripts related to this project, be sure to execute 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.
  • Detecting the IPV6 network configuration of the machine (IPV6 can be installed with or without IPV6, it is just a query).
  • Detect whether the hardware configuration meets the minimum requirements
  • Detect whether the hardware environment can be nested virtualization KVM type of server
  • Detect whether the system environment can nest virtualized KVM-type servers.
  • Can not be nested virtualization KVM type of server can also open LXC virtualization server, but do not recommend installing PVE, rather use LXD
Command:
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/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*



-    
-    
-  
-
\ No newline at end of file
diff --git a/en_US/guide/pve_qa.html b/en_US/guide/pve_qa.html
deleted file mode 100644
index d9f03d3905..0000000000
--- a/en_US/guide/pve_qa.html
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-  
-    
-    
-    Solve the puzzle | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
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!
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
-    echo "post-up /sbin/ethtool -K $auto_interface tx off rx off" >> /etc/network/interfaces
-    chattr +i /etc/network/interfaces
-fi
Then report the rebooted disconnected machine to @spiritlhl_bot for the script to be updated and repaired automatically.
PVE Installation Failed ​
If you encounter any issues with installing on certain machines, and if you're in a hurry, you can try using the scripts from the following repository to reinstall as Debian 11 first.
bash <(curl -sSL https://raw.githubusercontent.com/leitbogioro/Tools/master/Linux_reinstall/InstallNET.sh) -debian 12 -pwd 'oneclickvirt139' --network "static"
The system username after dd at this point is root, and the password is oneclickvirt139.
If you have time or if it's still not working, please contact @spiritlhl_bot for assistance.
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.
What to do if you accidentally delete a NAT mapping rule ​
Use the following command to map back
shell
iptables -t nat -F
-iptables -t filter -F
-service networking restart
-systemctl restart networking.service
-cat /etc/iptables/rules.v4 | iptables-restore
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
hostaris German version (Note: Issues with the vendor's system template, IPV6 is not functional, and poor connectivity with Github)
adtaq Storage KVM server with lowest configuration
nocix Dedicated servers
crunchbits VPS
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.
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_US/guide/pve_thanks.html b/en_US/guide/pve_thanks.html
deleted file mode 100644
index 64845983f2..0000000000
--- a/en_US/guide/pve_thanks.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    One Click Virtualization | One Click Virtualization
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
-    
-    
-  
-
\ No newline at end of file
diff --git a/en_US/index.html b/en_US/index.html
deleted file mode 100644
index d9120096ce..0000000000
--- a/en_US/index.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    K'thun
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
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.
Comes with internal and external port forwarding and automatic IP address assignment
Self-contained internal and external port forwarding and automatic IP address allocation, 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, Android, Windows, 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.

-    
-    
-  
-
\ No newline at end of file
diff --git a/guide/dashboard.html b/guide/dashboard.html
index bc9d5e8573..842e86b4f0 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 ​
可开设KVM虚拟化的虚拟机、LXC虚拟化的容器
https://github.com/spiritLHLS/pve
Hits
LXD ​
可开设LXC虚拟化的容器
https://github.com/spiritLHLS/lxd
Hits
Docker ​
可开设Docker虚拟化的容器
https://github.com/spiritLHLS/docker
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 ​
可开设KVM虚拟化的虚拟机、LXC虚拟化的容器
https://github.com/spiritLHLS/pve
Hits
LXD ​
可开设LXC虚拟化的容器
https://github.com/spiritLHLS/lxd
Hits
Docker ​
可开设Docker虚拟化的容器
https://github.com/spiritLHLS/docker
Hits



+    
     
   
 
\ No newline at end of file
diff --git a/guide/dashboardq.html b/guide/dashboardq.html
index 8a5b0f9a92..34bef7ba09 100644
--- a/guide/dashboardq.html
+++ b/guide/dashboardq.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
-    
+    
+    
     
   
 
\ No newline at end of file
diff --git a/guide/docker/docker_build.html b/guide/docker/docker_build.html
new file mode 100644
index 0000000000..7388120892
--- /dev/null
+++ b/guide/docker/docker_build.html
@@ -0,0 +1,42 @@
+
+
+  
+    
+    
+    前言 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
前言 ​
两种开设方式
单独开设 ​
  • 只生成一个docker，这里有判断为国际服务器还是国内服务器，如果在国内服务器上开设，容器内的包管理源自动替换为清华源
  • 可配置绑定独立的IPV6地址，但需要先前使用本套脚本的环境安装命令安装的docker，且需要宿主机至少绑定了/112的IPV6子网
  • 支持x86_64和ARM架构的服务器
下载脚本 ​
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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
+rm -rf dclog
+ls
更新上述所有脚本 ​
删除原始配置脚本
bash
rm -rf /usr/local/bin/ssh_sh.sh
+rm -rf /usr/local/bin/ssh_bash.sh
+rm -rf /usr/local/bin/check-dns.sh
+rm -rf /root/ssh_sh.sh
+rm -rf /root/ssh_bash.sh
+rm -rf /root/onedocker.sh
+rm -rf /root/create_docker.sh
下载回新版本的相关配置脚本
bash
wget https://raw.githubusercontent.com/spiritLHLS/docker/main/extra_scripts/check-dns.sh -O /usr/local/bin/check-dns.sh && chmod +x /usr/local/bin/check-dns.sh
+wget https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/config.sh -O /usr/local/bin/config.sh && chmod +x /usr/local/bin/config.sh
+wget https://raw.githubusercontent.com/spiritLHLS/docker/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/spiritLHLS/docker/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/spiritLHLS/docker/main/scripts/onedocker.sh -O /root/onedocker.sh && chmod +x /root/onedocker.sh
+wget https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/create_docker.sh -O /root/create_docker.sh && chmod +x /root/create_docker.sh

+    
+    
+  
+
\ No newline at end of file
diff --git a/guide/docker/docker_custom.html b/guide/docker/docker_custom.html
new file mode 100644
index 0000000000..b632728b2b
--- /dev/null
+++ b/guide/docker/docker_custom.html
@@ -0,0 +1,45 @@
+
+
+  
+    
+    
+    使用Docker一键安装某些容器的脚本 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
使用Docker一键安装某些容器的脚本 ​
每个容器都有对应的配置要求，自行查看，内存不够的用这个开设虚拟内存补足也行
注意，以下脚本使用前务必使用本套教程中的环境安装脚本进行前期环境安装
一键开设Android系统的容器 ​
  • 自定义安卓版本
  • 自动创建带校验的web网站
  • 自动进行nginx安装和反向代理的配置，可选择是否绑定域名，默认回车不绑定使用80端口
  • 无需考虑宿主机是否支持嵌套虚拟化
  • 支持x86_64和ARM架构
宿主机的配置至少要有1核2G内存15G硬盘，否则开设可能会导致宿主机卡死
宿主机推荐 Ubuntu 系统，Debian 系统可能导致安卓屏幕白屏
安卓版本越新占用越大，以上的配置要求是最低版本安卓的配置要求 (个人测试到 12.0.0-latest 的tag可用，更高版本映射白屏了，自己测试哪个能用吧)
开设
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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 rm -f scrcpy_web
+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
+rm -rf /etc/nginx/passwd_scrcpy_web
+rm -rf /root/android_info
一键开设Windows系统的容器 ​
  • 共享宿主机所有资源(CPU、内存、硬盘)，基于docker所以只占用系统的大小，适合多开
  • 共享IP，做了docker的NAT映射，可选择是否映射到外网或仅内网
  • 设置的win系统默认最多占用为1核2G内存50G硬盘，实际占用看使用情况
  • 无需iptables进行NAT映射，删除容器时自动删除了端口的映射，方便维护
  • 需要考虑宿主机是否支持嵌套虚拟化，暂时只支持X86_64架构的系统
宿主机需要支持嵌套虚拟化，且暂时只支持X86_64架构的系统，手头没ARM机器编译对应的镜像
执行
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/spiritLHLS/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限制)
一键开设Firefox浏览器的容器 ​
  • 已设置崩溃自启
  • 已设置带中文字体
  • 自带web的校验，可自设置密码
  • 可自定义容器最大的内存占用
  • 可选是否开启VNC端口，默认不开启
  • 无需考虑是否支持嵌套虚拟化和服务器的架构
  • 不支持声音映射，无论是WEB端还是VNC端都无法传输声音
宿主机需要至少1核2G内存5G硬盘，开设的容器大小将占用起码1G硬盘
开设
开设后默认的密码是oneclick
默认的web端口是3003，开设后打开本机IPV4:端口即可
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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}
+docker rmi jlesage/firefox
一键开设Chrome浏览器的容器 ​
  • 已设置崩溃自启
  • 自带web的校验，可自设置密码
  • 可自定义容器最大的内存占用
  • 无需考虑是否支持嵌套虚拟化和服务器的架构
  • 支持声音映射
宿主机需要至少1核2G内存5G硬盘，开设的容器大小将占用起码1G硬盘
开设
开设后默认的密码是oneclick
默认的http端口是3004，开设后打开http://本机IPV4:端口即可
默认的https端口是3005，开设后打开https://本机IPV4:端口即可
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onechromium.sh -o onechromium.sh && chmod +x onechromium.sh && bash onechromium.sh
删除
修改以下端口号3004为你实际的http端口号，然后执行命令回车两次即可删除容器、配置文件、对应镜像
shell
PORT="3004"
+docker stop chromium_${PORT}
+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
一键开设Desktop的容器 ​
  • 已设置崩溃自启
  • 已设置带中文字体
  • 自带web的校验，可自设置用户名和密码
  • 可自定义容器最大的内存占用
  • 无需考虑是否支持嵌套虚拟化和服务器的架构
  • 支持声音映射，WEB端可传输声音
完整的Linux桌面，可以在上面使用浏览器
宿主机需要至少1核2G内存5G硬盘，开设的容器大小将占用起码3.2G硬盘
开设
开设后默认的用户名是onew，密码是oneclick，默认的内存最大占用是2GB
默认的http协议的web端口是3004，默认的https协议的web端口是3005，开设后打开对应协议的本机IPV4:端口即可
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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

+    
+    
+  
+
\ No newline at end of file
diff --git a/guide/docker/docker_install.html b/guide/docker/docker_install.html
new file mode 100644
index 0000000000..d95bdae08e
--- /dev/null
+++ b/guide/docker/docker_install.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    前言 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
前言 ​
支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的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/spiritLHLS/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/spiritLHLS/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_precheck.html b/guide/docker/docker_precheck.html
new file mode 100644
index 0000000000..f6dc8260f7
--- /dev/null
+++ b/guide/docker/docker_precheck.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    前言 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
WARNING
如果宿主机带IPV6网络的话，安装会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
项目特点 ​
通过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
new file mode 100644
index 0000000000..a6da6be97c
--- /dev/null
+++ b/guide/docker/docker_qa.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    解惑 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
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
new file mode 100644
index 0000000000..78b177026f
--- /dev/null
+++ b/guide/docker/docker_thanks.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    一键虚拟化项目 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance

+    
+    
+  
+
\ No newline at end of file
diff --git a/guide/docker_build.html b/guide/docker_build.html
deleted file mode 100644
index 5316bd1b39..0000000000
--- a/guide/docker_build.html
+++ /dev/null
@@ -1,42 +0,0 @@
-
-
-  
-    
-    
-    前言 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
前言 ​
两种开设方式
单独开设 ​
  • 只生成一个docker，这里有判断为国际服务器还是国内服务器，如果在国内服务器上开设，容器内的包管理源自动替换为清华源
  • 可配置绑定独立的IPV6地址，但需要先前使用本套脚本的环境安装命令安装的docker，且需要宿主机至少绑定了/112的IPV6子网
  • 支持x86_64和ARM架构的服务器
下载脚本 ​
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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
-rm -rf dclog
-ls
更新上述所有脚本 ​
删除原始配置脚本
bash
rm -rf /usr/local/bin/ssh_sh.sh
-rm -rf /usr/local/bin/ssh_bash.sh
-rm -rf /usr/local/bin/check-dns.sh
-rm -rf /root/ssh_sh.sh
-rm -rf /root/ssh_bash.sh
-rm -rf /root/onedocker.sh
-rm -rf /root/create_docker.sh
下载回新版本的相关配置脚本
bash
wget https://raw.githubusercontent.com/spiritLHLS/docker/main/extra_scripts/check-dns.sh -O /usr/local/bin/check-dns.sh && chmod +x /usr/local/bin/check-dns.sh
-wget https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/config.sh -O /usr/local/bin/config.sh && chmod +x /usr/local/bin/config.sh
-wget https://raw.githubusercontent.com/spiritLHLS/docker/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/spiritLHLS/docker/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/spiritLHLS/docker/main/scripts/onedocker.sh -O /root/onedocker.sh && chmod +x /root/onedocker.sh
-wget https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/create_docker.sh -O /root/create_docker.sh && chmod +x /root/create_docker.sh

-    
-    
-  
-
\ No newline at end of file
diff --git a/guide/docker_custom.html b/guide/docker_custom.html
deleted file mode 100644
index 5ba21d5858..0000000000
--- a/guide/docker_custom.html
+++ /dev/null
@@ -1,45 +0,0 @@
-
-
-  
-    
-    
-    使用Docker一键安装某些容器的脚本 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
使用Docker一键安装某些容器的脚本 ​
每个容器都有对应的配置要求，自行查看，内存不够的用这个开设虚拟内存补足也行
注意，以下脚本使用前务必使用本套教程中的环境安装脚本进行前期环境安装
一键开设Android系统的容器 ​
  • 自定义安卓版本
  • 自动创建带校验的web网站
  • 自动进行nginx安装和反向代理的配置，可选择是否绑定域名，默认回车不绑定使用80端口
  • 无需考虑宿主机是否支持嵌套虚拟化
  • 支持x86_64和ARM架构
宿主机的配置至少要有1核2G内存15G硬盘，否则开设可能会导致宿主机卡死
宿主机推荐 Ubuntu 系统，Debian 系统可能导致安卓屏幕白屏
安卓版本越新占用越大，以上的配置要求是最低版本安卓的配置要求 (个人测试到 12.0.0-latest 的tag可用，更高版本映射白屏了，自己测试哪个能用吧)
开设
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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 rm -f scrcpy_web
-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
-rm -rf /etc/nginx/passwd_scrcpy_web
-rm -rf /root/android_info
一键开设Windows系统的容器 ​
  • 共享宿主机所有资源(CPU、内存、硬盘)，基于docker所以只占用系统的大小，适合多开
  • 共享IP，做了docker的NAT映射，可选择是否映射到外网或仅内网
  • 设置的win系统默认最多占用为1核2G内存50G硬盘，实际占用看使用情况
  • 无需iptables进行NAT映射，删除容器时自动删除了端口的映射，方便维护
  • 需要考虑宿主机是否支持嵌套虚拟化，暂时只支持X86_64架构的系统
宿主机需要支持嵌套虚拟化，且暂时只支持X86_64架构的系统，手头没ARM机器编译对应的镜像
执行
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/spiritLHLS/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限制)
一键开设Firefox浏览器的容器 ​
  • 已设置崩溃自启
  • 已设置带中文字体
  • 自带web的校验，可自设置密码
  • 可自定义容器最大的内存占用
  • 可选是否开启VNC端口，默认不开启
  • 无需考虑是否支持嵌套虚拟化和服务器的架构
  • 不支持声音映射，无论是WEB端还是VNC端都无法传输声音
宿主机需要至少1核2G内存5G硬盘，开设的容器大小将占用起码1G硬盘
开设
开设后默认的密码是oneclick
默认的web端口是3003，开设后打开本机IPV4:端口即可
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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}
-docker rmi jlesage/firefox
一键开设Chrome浏览器的容器 ​
  • 已设置崩溃自启
  • 自带web的校验，可自设置密码
  • 可自定义容器最大的内存占用
  • 无需考虑是否支持嵌套虚拟化和服务器的架构
  • 支持声音映射
宿主机需要至少1核2G内存5G硬盘，开设的容器大小将占用起码1G硬盘
开设
开设后默认的密码是oneclick
默认的http端口是3004，开设后打开http://本机IPV4:端口即可
默认的https端口是3005，开设后打开https://本机IPV4:端口即可
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onechromium.sh -o onechromium.sh && chmod +x onechromium.sh && bash onechromium.sh
删除
修改以下端口号3004为你实际的http端口号，然后执行命令回车两次即可删除容器、配置文件、对应镜像
shell
PORT="3004"
-docker stop chromium_${PORT}
-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
一键开设Desktop的容器 ​
  • 已设置崩溃自启
  • 已设置带中文字体
  • 自带web的校验，可自设置用户名和密码
  • 可自定义容器最大的内存占用
  • 无需考虑是否支持嵌套虚拟化和服务器的架构
  • 支持声音映射，WEB端可传输声音
完整的Linux桌面，可以在上面使用浏览器
宿主机需要至少1核2G内存5G硬盘，开设的容器大小将占用起码3.2G硬盘
开设
开设后默认的用户名是onew，密码是oneclick，默认的内存最大占用是2GB
默认的http协议的web端口是3004，默认的https协议的web端口是3005，开设后打开对应协议的本机IPV4:端口即可
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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

-    
-    
-  
-
\ No newline at end of file
diff --git a/guide/docker_install.html b/guide/docker_install.html
deleted file mode 100644
index 0bd7865306..0000000000
--- a/guide/docker_install.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    前言 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
前言 ​
支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的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/spiritLHLS/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/spiritLHLS/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_precheck.html b/guide/docker_precheck.html
deleted file mode 100644
index 0b759d0ee2..0000000000
--- a/guide/docker_precheck.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    前言 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
WARNING
如果宿主机带IPV6网络的话，安装会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
项目特点 ​
通过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_qa.html b/guide/docker_qa.html
deleted file mode 100644
index 683b700ec6..0000000000
--- a/guide/docker_qa.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    解惑 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
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_thanks.html b/guide/docker_thanks.html
deleted file mode 100644
index 8193b5a92b..0000000000
--- a/guide/docker_thanks.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    一键虚拟化项目 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance

-    
-    
-  
-
\ No newline at end of file
diff --git a/guide/incus/incus_custom.html b/guide/incus/incus_custom.html
new file mode 100644
index 0000000000..2557667172
--- /dev/null
+++ b/guide/incus/incus_custom.html
@@ -0,0 +1,52 @@
+
+
+  
+    
+    
+    给宿主机附加免费的IPV6地址段 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
给宿主机附加免费的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
+# systemctl disable systemd-networkd.socket
如果需要安装的是ifupdown控制网络，这个工具一般的主流linux系统都有
apt-get install ifupdown -y
如果需要安装的是ifupdown2进行网络管理，而这个工具一般只在debian系上可安装使用
apt-get install ifupdown2 -y
安装完毕后，安装了哪个包后面就选择哪个包进行格式转换。
systemctl start networking
+systemctl enable networking
然后重启服务器，检验机器的网络是否会因为修改出现重启失联的情况，且执行uptime观察启动已超过1分钟后，再进行后续步骤
如果是是前者inactive，后者active，则不需要切换网络管理程序，直接进行后续操作即可。
由于部分服务器存在默认的内网IPV6路由会与隧道冲突，此时可使用以下命令删除默认的IPV6路由
default_route=$(ip -6 route show | awk '/default via/{print $3}') && [ -n "$default_route" ] && ip -6 route del default via $default_route dev eth0
这里假设了你的客户端的服务器的默认网卡是eth0，你可以使用ip -6 route查看默认的路由并替换它，默认路由以default via开头，使用dev指定默认网卡，你只需要按照这个规则找到它即可
tunnelbroker_net ​
结合一键开设带IPV6地址的容器的脚本，就能给每个容器附加来自he的IPV6地址了
缺点是地址比较黑/脏，cloudflare的cdn极有可能套不上，自行测试
  1. 在 https://tunnelbroker.net/ 注册账户，并点击左边的 Create Regular Tunnel
1
  1. 红框处填写你的服务器的IPV4地址，选择物理距离近的连接点，比如机器在美国洛杉矶，就选美国西海岸的连接点，然后显示绿框提示，点Create Tunnel创建即可
2
3
4
  1. 等待出以下界面，点击Example Configurations然后选择对应的系统，比如incus的宿主机那肯定就是Debian/Ubuntu了
5
6
  1. 框住的部分就是要修改的文件和需要复制的内容了
7
复制的时候不要带空行
  1. 转换格式后给你的网络配置文件附加IPV6的设置
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为TunnelBrokerNet，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式，等待页面刷新显示转换格式后的配置文件内容
然后用vim或者vi命令修改/etc/network/interfaces文件增加内容，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改复制粘贴一下转换格式后的配置文件内容，然后执行此命令
+EOF
然后你可以使用cat /etc/network/interfaces查看配置文件是否正常写入了
  1. 如果上面都没问题，就需要启用网络接口即可
apt-get install net-tools iproute2 -y
+systemctl restart networking
  1. 然后你就可以测试IPV6网络是否已附加
执行ifconfig命令，这时应该有一个 he-ipv6 接口，类似下面这样：
8
或者执行：
curl ipv6.ip.sb
回传你绑定IPV6地址
  1. NAT VPS 的额外设置
IPv4 NAT VPS 除了前面提到的替换 IP 操作以外，可能还需要一些额外的设置，否则可能还是无法访问 IPv6 网络。
apt-get install ufw -y
+ufw allow 41
添加相关的路由规则
route -A inet6 add ::/0 dev he-ipv6
  1. 如果不需要该IPV6网络了，想要删除
删除 he-ipv6 网络接口配置（若没有删除重启后会自动启用），记得修改/etc/network/interfaces文件，删除之前红框添加的内容
然后重启服务器，就删除了
tunnelbroker_ch ​
类似上述的操作，先在 https://www.tunnelbroker.ch/ 注册一个账户先，注册后点击激活的邮件
然后就是填写你的服务器IPV4地址
创建后需要进入Config页面而不是详情页面
见到以下页面千万别使用，先刷新一下本页面，不要弹那个浅蓝色框后再停止刷新
记录以下页面的最后一个红框的内容，准备修改宿主机配置文件
页面的最后一个红框框住的部分复制下来，不要带空行
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为TunnelBrokerCh，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式，等待页面刷新显示转换格式后的配置文件内容
然后用vim或者vi命令修改/etc/network/interfaces文件增加内容，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改一下
+EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
+systemctl restart networking
保证环境无问题再进行别的操作了
ip4market_ru ​
类似上述的操作，先在 https://tb.ip4market.ru 注册一个账户先，注册邮箱得是非常见邮箱，电话可随便写不验证的，IP填上你要附加的宿主机的IPV4地址
然后就是过Recaptcha的人机验证，点击注册
邮箱会收到激活邮件，里面附带有你的密码，记住它
然后在首页进行登录
然后就会进入这个页面
按住右键，然后复制红框框住的四行内容，也就是
Server IPv4:
+Client IPv4
+Server IPv6
+Client IPv6
这四行内容，按ctrl+c复制或者右键复制
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为ip4market，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式
然后就会自动刷新页面出现需要自己用vim或者vi命令修改/etc/network/interfaces文件增加的内容了，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改一下
+EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
+systemctl restart networking
保证环境无问题再进行别的操作了
netassist_ua ​
这个平台你在切换网络管理时务必使用ifupdown2而不是ifupdown2安装包，该平台使用sit协议，而sit协议需要在ifupdown2控制的环境中使用
类似上述的操作，先在 https://tb.netassist.ua/ 注册一个账户先，注册后点击激活的邮件，激活页面会有密码显示，记得记录
然后就是填写你的服务器IPV4地址，这个后面可以自己修改，先随便填一个都没问题
然后就到了这个页面了
a
第一个红框是你宿主机的IPV4地址需要填写的位置，要修改就修改那里，然后点change保存
第二个下拉红框选择Linux，然后点击show
b
会出现上面的内容，全选框住的部分复制下来，不要带空行
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为NetAssist，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式
c
然后就会自动刷新页面出现需要自己用vim或者vi命令修改/etc/network/interfaces文件增加的内容了，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改一下
+EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
+systemctl restart networking
保证环境无问题再进行别的操作了
转移不同服务器之间的IPV6子网 ​
相关仓库：https://github.com/oneclickvirt/6in4
该方法将提供一种方式，将A上的IPV6网段拆分一个子ipv6网段的出来，附加到B上使用
你需要在B所在的服务器上使用本套脚本给容器一键配置IPV6地址
功能 ​
  • 自建sit/gre/ipip协议的IPv6隧道
  • 支持自定义要切分出来的IPV6子网大小，将自动计算出合适的CIDR格式的IPV6子网信息
  • 自动识别服务端的IPV6子网大小
  • 将自动设置隧道服务端并打印客户端需要执行的命令
  • 设置IPV6隧道的方法简单易懂，易于删除
环境准备 ​
VPS(A)VPS(B)
一个IPV4地址(server_ipv4)一个IPV4地址(clinet_ipv4)
一个IPV6子网无IPV6地址
以下称之为服务端以下称之为客户端
使用方法 ​
下载脚本
curl -L https://raw.githubusercontent.com/oneclickvirt/6in4/main/6in4.sh -o 6in4.sh && chmod +x 6in4.sh
执行命令
./6in4.sh client_ipv4 <mode_type> <subnet_size>
选项可选的选项1可选的选项2可选的选项3
<mode_type>gresitipip
<subnet_size>6480112
<mode_type>暂时只支持那三种协议，越靠前的越推荐，不填则默认为sit协议
<subnet_size>只要比原系统子网掩码大就行，且是8的倍数，不填则默认为80
记得client_ipv4替换为需要附加IPV6的机器的IPV4地址，执行完毕后会回传你需要在客户端执行的命令，详见执行后的说明即可
为防止忘记复制命令，命令本身也将写入到当前路径下的6in4.log文件中，可使用cat 6in4.log查询客户端需要执行的命令
复制下来的命令，务必在 https://ipv6tunnel.spiritlhl.top/ 中选择选项6in4后进行转换
然后就会自动刷新页面出现需要自己用vim或者vi命令修改/etc/network/interfaces文件增加的内容了，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改一下
+EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
+systemctl restart networking
保证环境无问题再进行别的操作了
检测服务端 ​
systemctl status ndpresponder
ip addr show
检测客户端 ​
ip addr show
curl ipv6.ip.sb
删除隧道 ​
服务端
ip link set server-ipv6 down
+ip tunnel del server-ipv6
客户端
ip link set user-ipv6 down
+ip tunnel del user-ipv6
以上删除的方式只是临时删除，永久删除务必修改删除/etc/network/interfaces文件中你之前增加的内容
后言 ​
实际上 https://tunnelbroker.net/ 支持申请/48大小的IPV6子网，只需要在
图片
这里进行申请，然后转换格式的时候将原先/64的IPV6地址改成/48的IPV6地址，你就能获得一个更大的IPV6子网了

+    
+    
+  
+
\ No newline at end of file
diff --git a/guide/incus/incus_extra_config.html b/guide/incus/incus_extra_config.html
new file mode 100644
index 0000000000..adbc9e76ab
--- /dev/null
+++ b/guide/incus/incus_extra_config.html
@@ -0,0 +1,37 @@
+
+
+  
+    
+    
+    其他自定义配置 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
其他自定义配置 ​
TIP
以下的配置安装会加重宿主机的负担，非必要不要安装
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
+netfilter-persistent reload
+service netfilter-persistent restart
卸载IPV6地址绑定的守护进程和对应的文件可用：
shell
systemctl stop add-ipv6.service
+systemctl disable add-ipv6.service
+rm /etc/systemd/system/add-ipv6.service
+systemctl daemon-reload
+rm /usr/local/bin/add-ipv6.sh
屏蔽容易被滥用的端口的出入流量以屏蔽端口和屏蔽滥用工具包 ​
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事前预防
国际
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
一键安装开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
一键安装宿主机可视化操作的面板 ​
  • (非必须，该面板只是为了方便可视化操作，没有也没问题)
  • 原作者仓库：跳转
shell
incus config set core.https_address [::]
+incus config set core.trust_password some-secret-string
+snap install incusmosaic
安装完毕后打开宿主机IP地址，按照提示设置admin的密码，其他一路默认就能使用面板了

+    
+    
+  
+
\ No newline at end of file
diff --git a/guide/incus/incus_install.html b/guide/incus/incus_install.html
new file mode 100644
index 0000000000..27d750c21e
--- /dev/null
+++ b/guide/incus/incus_install.html
@@ -0,0 +1,30 @@
+
+
+  
+    
+    
+    incus主体安装 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
incus主体安装 ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
一键安装 ​
WARNING
如果是全新的服务器，务必保证apt update和apt install curl都无问题再执行本脚本
TIP
且自开机起最好等待5分钟后再执行以下命令，避免系统默认设置中就执行了本脚本导致apt源卡死
  • 环境要求：Ubuntu 18+(推荐)，Debian 8+(仅限x86_64架构)
  • 如果是Debian系的宿主机，务必在screen中执行本脚本，避免长期运行时SSH中断导致ZFS编译安装失败
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程中可能需要重启服务器以加载含zfs的内核，然后再次执行安装命令，一切以运行后命令行的提示为准
  • 默认启用incus的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
如果脚本提示重启系统后需要再次执行脚本，第二次执行安装脚本仍提示重启系统加载内核，那么意味着内核在上一次加载中失败了，最好重装宿主机系统为ubuntu系解决这个问题
每次执行脚本都需要输入一次初始化的配置，所以遇到脚本提示需重启系统再次执行，那么就得再次输入初始化的配置
国际
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
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
手动安装 ​
新手推荐，避免有bug不知道怎么修，当然如果只是图方便又是老手懂排查BUG，用后面的一键安装也行
关闭防火墙 ​
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是合理的，上面我描述的情况属于超开了
apt install snapd -y
+snap install incus
+incus init
如果上面的命令中出现下面的错误
(snap "incus" assumes unsupported features: snapd2.39 (try to update snapd and refresh the core snap))
使用命令修补后再进行incus的安装
snap install core
如果无异常，上面三行命令执行结果如下
图片
一般的选项回车默认即可
选择配置物理盘大小(提示默认最小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
new file mode 100644
index 0000000000..c3c49beb34
--- /dev/null
+++ b/guide/incus/incus_lxc.html
@@ -0,0 +1,50 @@
+
+
+  
+    
+    
+    LXC虚拟化 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
LXC虚拟化 ​
单独生成一个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，注意传入参数为系统名字+版本号，如：
  • 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的版本号已支持
  • 开不起来的可能是硬盘或内存不够大或者本身就不适配宿主机，自行尝试查看开不起来的报错
TIP
版本号中已结束长期维护的一般不再有官方镜像了，暂时未找到历史镜像的存档地址，如果有找到欢迎留言我会添加支持
示例 ​
以下为开设的示例服务器的信息：
属性值
服务器名字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
需要进入容器内部则执行
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
+ls
普通版本批量生成 ​
开出的服务器配置：
  • 1核256MB内存1GB硬盘限速300Mbit带宽
  • 带1个SSH端口，25个外网端口
  • 默认内存和硬盘大小
TIP
lxc若命令无问题，执行初始化开服务器，这一步最好放screen中后台挂起执行，开服务器时长与你开几个和宿主机配置相关
执行下面命令加载开机脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/init.sh -o init.sh && chmod +x init.sh && dos2unix init.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/init.sh -o init.sh && chmod +x init.sh && dos2unix init.sh
下面命令为开服务器名字前缀为tj的10个服务器
shell
./init.sh tj 10
有时候init.sh的运行路径有问题，此时建议前面加上sudo强制根目录执行
纯SSH端口版本批量生成 ​
开出的服务器配置：
  • 1核128MB内存300MB硬盘限速300Mbit带宽
  • 只有一个SSH端口
  • 无法挂载warp
TIP
lxc若命令无问题，执行初始化开服务器，这一步最好放screen中后台挂起执行，开服务器时长与你开几个和宿主机配置相关
加载开机脚本
国际
shell
curl -L https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/least.sh -o least.sh && chmod +x least.sh && dos2unix least.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/least.sh -o least.sh && chmod +x least.sh && dos2unix least.sh
下列命令最后一行为开服务器名字前缀为tj的10个服务器
shell
./least.sh tj 10
有时候least.sh的运行路径有问题，此时建议前面加上sudo强制根目录执行
自定义批量生成版本 ​
  • 可自定义内存和硬盘大小
  • 有执行过上面的手动批量生成过也没问题，配置是继承的不覆盖
如果需要多次批量生成服务器，可使用
国际
curl -L https://github.com/oneclickvirt/incus/raw/main/scripts/add_more.sh -o add_more.sh && chmod +x add_more.sh && bash add_more.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://github.com/oneclickvirt/incus/raw/main/scripts/add_more.sh -o add_more.sh && chmod +x add_more.sh && bash add_more.sh
可多次运行批量生成服务器，且继承前面已生成的部分在后面添加，可自定义内存和硬盘大小
查看已批量开设的信息 ​
开完服务器后，具体信息会生成在当前目录下的log文件中，格式如下
shell
1号服务器名称 密码 ssh端口 外网端口起始 外网端口终止
+2号服务器名称 密码 ssh端口 外网端口起始 外网端口终止
如果想要查看，只需在当前目录执行以下命令打印log文件即可
shell
cat log
WARNING
不要拿该脚本开出的服务器当生产环境，LXC虚拟化不支持换内核，dd，开启bbr等操作
部分常用incus命令 ​
查看所有
bash
incus list
查看个例
bash
incus info 服务器名字
启动个例
bash
incus start 服务器名字
停止个例
bash
incus stop 服务器名字
删除个例
bash
incus delete -f 服务器名字
进入内部
bash
incus exec 服务器名字 /bin/bash
TIP
在alpine中不用/bin/bash而是用/bin/sh，常规的系统都是/bin/bash
退出则输入exit回车即可
删除所有LXC容器
bash
incus list -c n --format csv | xargs -I {} incus delete -f {}
在容器内执行删除无用日志
bash
sudo apt-get autoremove
+sudo apt-get clean
+sudo find /var/log -type f -delete
+sudo find /var/tmp -type f -delete
+sudo find /tmp -type f -delete
+sudo find /var/cache/apt/archives -type f -delete
更新上述所有一键脚本的相关命令 ​
删除原始配置脚本
bash
rm -rf /usr/local/bin/ssh_sh.sh
+rm -rf /usr/local/bin/config.sh
+rm -rf /usr/local/bin/ssh_bash.sh
+rm -rf /usr/local/bin/check-dns.sh
+rm -rf /root/ssh_sh.sh
+rm -rf /root/config.sh
+rm -rf /root/ssh_bash.sh
+rm -rf /root/buildone.sh
+rm -rf /root/add_more.sh
+rm -rf /root/build_ipv6_network.sh
下载回新版本的相关配置脚本
bash
wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/check-dns.sh -O /usr/local/bin/check-dns.sh && chmod +x /usr/local/bin/check-dns.sh
+wget https://raw.githubusercontent.com/oneclickvirt/incus/main/scripts/config.sh -O /usr/local/bin/config.sh && chmod +x /usr/local/bin/config.sh
+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
其他一键脚本自己对应下载回来就行了

+    
+    
+  
+
\ No newline at end of file
diff --git a/guide/incus/incus_precheck.html b/guide/incus/incus_precheck.html
new file mode 100644
index 0000000000..7534994e9a
--- /dev/null
+++ b/guide/incus/incus_precheck.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    前言 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看incus模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
要求 ​
硬件要求:
  • 系统：Debian 8+, Ubuntu 18+(推荐20.04)
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转
项目特点 ​
  • 本套脚本开发使用的Ubuntu20，Ubuntu别的长期维护版本应该也没问题，Debian无法使用zfs时自动切换别的存储类型
  • 已设置同时进行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
new file mode 100644
index 0000000000..023bed250c
--- /dev/null
+++ b/guide/incus/incus_qa.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    解惑 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
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 促销款
luxvps 中的 德国AMD 促销款

+    
+    
+  
+
\ No newline at end of file
diff --git a/guide/incus/incus_thanks.html b/guide/incus/incus_thanks.html
new file mode 100644
index 0000000000..5f8e264f11
--- /dev/null
+++ b/guide/incus/incus_thanks.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    一键虚拟化项目 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
+    
+    
+  
+
\ No newline at end of file
diff --git a/guide/lxd/lxd_custom.html b/guide/lxd/lxd_custom.html
new file mode 100644
index 0000000000..82cb3c3199
--- /dev/null
+++ b/guide/lxd/lxd_custom.html
@@ -0,0 +1,52 @@
+
+
+  
+    
+    
+    给宿主机附加免费的IPV6地址段 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
给宿主机附加免费的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
+# systemctl disable systemd-networkd.socket
如果需要安装的是ifupdown控制网络，这个工具一般的主流linux系统都有
apt-get install ifupdown -y
如果需要安装的是ifupdown2进行网络管理，而这个工具一般只在debian系上可安装使用
apt-get install ifupdown2 -y
安装完毕后，安装了哪个包后面就选择哪个包进行格式转换。
systemctl start networking
+systemctl enable networking
然后重启服务器，检验机器的网络是否会因为修改出现重启失联的情况，且执行uptime观察启动已超过1分钟后，再进行后续步骤
如果是是前者inactive，后者active，则不需要切换网络管理程序，直接进行后续操作即可。
由于部分服务器存在默认的内网IPV6路由会与隧道冲突，此时可使用以下命令删除默认的IPV6路由
default_route=$(ip -6 route show | awk '/default via/{print $3}') && [ -n "$default_route" ] && ip -6 route del default via $default_route dev eth0
这里假设了你的客户端的服务器的默认网卡是eth0，你可以使用ip -6 route查看默认的路由并替换它，默认路由以default via开头，使用dev指定默认网卡，你只需要按照这个规则找到它即可
tunnelbroker_net ​
结合一键开设带IPV6地址的容器的脚本，就能给每个容器附加来自he的IPV6地址了
缺点是地址比较黑/脏，cloudflare的cdn极有可能套不上，自行测试
  1. 在 https://tunnelbroker.net/ 注册账户，并点击左边的 Create Regular Tunnel
1
  1. 红框处填写你的服务器的IPV4地址，选择物理距离近的连接点，比如机器在美国洛杉矶，就选美国西海岸的连接点，然后显示绿框提示，点Create Tunnel创建即可
2
3
4
  1. 等待出以下界面，点击Example Configurations然后选择对应的系统，比如LXD的宿主机那肯定就是Debian/Ubuntu了
5
6
  1. 框住的部分就是要修改的文件和需要复制的内容了
7
复制的时候不要带空行
  1. 转换格式后给你的网络配置文件附加IPV6的设置
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为TunnelBrokerNet，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式，等待页面刷新显示转换格式后的配置文件内容
然后用vim或者vi命令修改/etc/network/interfaces文件增加内容，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改复制粘贴一下转换格式后的配置文件内容，然后执行此命令
+EOF
然后你可以使用cat /etc/network/interfaces查看配置文件是否正常写入了
  1. 如果上面都没问题，就需要启用网络接口即可
apt-get install net-tools iproute2 -y
+systemctl restart networking
  1. 然后你就可以测试IPV6网络是否已附加
执行ifconfig命令，这时应该有一个 he-ipv6 接口，类似下面这样：
8
或者执行：
curl ipv6.ip.sb
回传你绑定IPV6地址
  1. NAT VPS 的额外设置
IPv4 NAT VPS 除了前面提到的替换 IP 操作以外，可能还需要一些额外的设置，否则可能还是无法访问 IPv6 网络。
apt-get install ufw -y
+ufw allow 41
添加相关的路由规则
route -A inet6 add ::/0 dev he-ipv6
  1. 如果不需要该IPV6网络了，想要删除
删除 he-ipv6 网络接口配置（若没有删除重启后会自动启用），记得修改/etc/network/interfaces文件，删除之前红框添加的内容
然后重启服务器，就删除了
tunnelbroker_ch ​
类似上述的操作，先在 https://www.tunnelbroker.ch/ 注册一个账户先，注册后点击激活的邮件
然后就是填写你的服务器IPV4地址
创建后需要进入Config页面而不是详情页面
见到以下页面千万别使用，先刷新一下本页面，不要弹那个浅蓝色框后再停止刷新
记录以下页面的最后一个红框的内容，准备修改宿主机配置文件
页面的最后一个红框框住的部分复制下来，不要带空行
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为TunnelBrokerCh，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式，等待页面刷新显示转换格式后的配置文件内容
然后用vim或者vi命令修改/etc/network/interfaces文件增加内容，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改一下
+EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
+systemctl restart networking
保证环境无问题再进行别的操作了
ip4market_ru ​
类似上述的操作，先在 https://tb.ip4market.ru 注册一个账户先，注册邮箱得是非常见邮箱，电话可随便写不验证的，IP填上你要附加的宿主机的IPV4地址
然后就是过Recaptcha的人机验证，点击注册
邮箱会收到激活邮件，里面附带有你的密码，记住它
然后在首页进行登录
然后就会进入这个页面
按住右键，然后复制红框框住的四行内容，也就是
Server IPv4:
+Client IPv4
+Server IPv6
+Client IPv6
这四行内容，按ctrl+c复制或者右键复制
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为ip4market，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式
然后就会自动刷新页面出现需要自己用vim或者vi命令修改/etc/network/interfaces文件增加的内容了，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改一下
+EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
+systemctl restart networking
保证环境无问题再进行别的操作了
netassist_ua ​
这个平台你在切换网络管理时务必使用ifupdown2而不是ifupdown2安装包，该平台使用sit协议，而sit协议需要在ifupdown2控制的环境中使用
类似上述的操作，先在 https://tb.netassist.ua/ 注册一个账户先，注册后点击激活的邮件，激活页面会有密码显示，记得记录
然后就是填写你的服务器IPV4地址，这个后面可以自己修改，先随便填一个都没问题
然后就到了这个页面了
a
第一个红框是你宿主机的IPV4地址需要填写的位置，要修改就修改那里，然后点change保存
第二个下拉红框选择Linux，然后点击show
b
会出现上面的内容，全选框住的部分复制下来，不要带空行
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为NetAssist，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式
c
然后就会自动刷新页面出现需要自己用vim或者vi命令修改/etc/network/interfaces文件增加的内容了，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改一下
+EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
+systemctl restart networking
保证环境无问题再进行别的操作了
转移不同服务器之间的IPV6子网 ​
相关仓库：https://github.com/oneclickvirt/6in4
该方法将提供一种方式，将A上的IPV6网段拆分一个子ipv6网段的出来，附加到B上使用
你需要在B所在的服务器上使用本套脚本给容器一键配置IPV6地址
功能 ​
  • 自建sit/gre/ipip协议的IPv6隧道
  • 支持自定义要切分出来的IPV6子网大小，将自动计算出合适的CIDR格式的IPV6子网信息
  • 自动识别服务端的IPV6子网大小
  • 将自动设置隧道服务端并打印客户端需要执行的命令
  • 设置IPV6隧道的方法简单易懂，易于删除
环境准备 ​
VPS(A)VPS(B)
一个IPV4地址(server_ipv4)一个IPV4地址(clinet_ipv4)
一个IPV6子网无IPV6地址
以下称之为服务端以下称之为客户端
使用方法 ​
下载脚本
curl -L https://raw.githubusercontent.com/oneclickvirt/6in4/main/6in4.sh -o 6in4.sh && chmod +x 6in4.sh
执行命令
./6in4.sh client_ipv4 <mode_type> <subnet_size>
选项可选的选项1可选的选项2可选的选项3
<mode_type>gresitipip
<subnet_size>6480112
<mode_type>暂时只支持那三种协议，越靠前的越推荐，不填则默认为sit协议
<subnet_size>只要比原系统子网掩码大就行，且是8的倍数，不填则默认为80
记得client_ipv4替换为需要附加IPV6的机器的IPV4地址，执行完毕后会回传你需要在客户端执行的命令，详见执行后的说明即可
为防止忘记复制命令，命令本身也将写入到当前路径下的6in4.log文件中，可使用cat 6in4.log查询客户端需要执行的命令
复制下来的命令，务必在 https://ipv6tunnel.spiritlhl.top/ 中选择选项6in4后进行转换
然后就会自动刷新页面出现需要自己用vim或者vi命令修改/etc/network/interfaces文件增加的内容了，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
+# 这里修改一下
+EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
+systemctl restart networking
保证环境无问题再进行别的操作了
检测服务端 ​
systemctl status ndpresponder
ip addr show
检测客户端 ​
ip addr show
curl ipv6.ip.sb
删除隧道 ​
服务端
ip link set server-ipv6 down
+ip tunnel del server-ipv6
客户端
ip link set user-ipv6 down
+ip tunnel del user-ipv6
以上删除的方式只是临时删除，永久删除务必修改删除/etc/network/interfaces文件中你之前增加的内容
后言 ​
实际上 https://tunnelbroker.net/ 支持申请/48大小的IPV6子网，只需要在
图片
这里进行申请，然后转换格式的时候将原先/64的IPV6地址改成/48的IPV6地址，你就能获得一个更大的IPV6子网了

+    
+    
+  
+
\ No newline at end of file
diff --git a/guide/lxd/lxd_extra_config.html b/guide/lxd/lxd_extra_config.html
new file mode 100644
index 0000000000..7ce76c7678
--- /dev/null
+++ b/guide/lxd/lxd_extra_config.html
@@ -0,0 +1,37 @@
+
+
+  
+    
+    
+    其他自定义配置 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
其他自定义配置 ​
TIP
以下的配置安装会加重宿主机的负担，非必要不要安装
TIP
如果是个人使用，可忽略防滥用部分脚本的安装
自动配置IPV6地址 ​
  • (非必须，不使用的也没问题)
  • 该脚本仅适用于宿主机有给IPV6子网且是至少/112的，且宿主机绑定了子网的第一个IP做宿主机的IPV6地址或IPV6的gateway
  • 自动为LXD创建的LXC容器配置IPV6地址
  • 已集成到buildone.sh中可使用变量控制且无需事先下载，该脚本可不手动使用，在使用buildone.sh时配置Y开启即可
下载脚本
国际
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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
+netfilter-persistent reload
+service netfilter-persistent restart
卸载IPV6地址绑定的守护进程和对应的文件可用：
shell
systemctl stop add-ipv6.service
+systemctl disable add-ipv6.service
+rm /etc/systemd/system/add-ipv6.service
+systemctl daemon-reload
+rm /usr/local/bin/add-ipv6.sh
屏蔽容易被滥用的端口的出入流量以屏蔽端口和屏蔽滥用工具包 ​
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事前预防
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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/spiritLHLS/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
一键安装开lxd宿主机所需要的带vnstat环境的常用预配置环境 ​
  • (非必须，该脚本仅仅是为了站点对接监控方便，不装的也没问题)
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/lxd/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/spiritLHLS/lxd/main/scripts/backend.sh -o backend.sh && chmod +x backend.sh && bash backend.sh
一键安装宿主机可视化操作的面板 ​
  • (非必须，该面板只是为了方便可视化操作，没有也没问题)
  • 原作者仓库：跳转
shell
lxc config set core.https_address [::]
+lxc config set core.trust_password some-secret-string
+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
new file mode 100644
index 0000000000..6e81fd7a98
--- /dev/null
+++ b/guide/lxd/lxd_install.html
@@ -0,0 +1,31 @@
+
+
+  
+    
+    
+    LXD主体安装 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
LXD主体安装 ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
一键安装 ​
WARNING
如果是全新的服务器，务必保证apt update和apt install curl都无问题再执行本脚本
TIP
且自开机起最好等待5分钟后再执行以下命令，避免系统默认设置中就执行了本脚本导致apt源卡死
  • 环境要求：Ubuntu 18+(推荐)，Debian 8+(仅限x86_64架构)
  • 如果是Debian系的宿主机，务必在screen中执行本脚本，避免长期运行时SSH中断导致ZFS编译安装失败
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程中可能需要重启服务器以加载含zfs的内核，然后再次执行安装命令，一切以运行后命令行的提示为准
  • 默认启用lxd的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
如果脚本提示重启系统后需要再次执行脚本，第二次执行安装脚本仍提示重启系统加载内核，那么意味着内核在上一次加载中失败了，最好重装宿主机系统为ubuntu系解决这个问题
每次执行脚本都需要输入一次初始化的配置，所以遇到脚本提示需重启系统再次执行，那么就得再次输入初始化的配置
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
手动安装 ​
新手推荐，避免有bug不知道怎么修，当然如果只是图方便又是老手懂排查BUG，用后面的一键安装也行
关闭防火墙 ​
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/spiritLHLS/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/spiritLHLS/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命令是否有报错找不到

+    
+    
+  
+
\ No newline at end of file
diff --git a/guide/lxd/lxd_lxc.html b/guide/lxd/lxd_lxc.html
new file mode 100644
index 0000000000..92443b3f3c
--- /dev/null
+++ b/guide/lxd/lxd_lxc.html
@@ -0,0 +1,50 @@
+
+
+  
+    
+    
+    LXC虚拟化 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
LXC虚拟化 ​
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载开机脚本是非必须的，如果你使用过一键安装LXD的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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
支持自定义服务器的系统，不填写留空时默认使用debian11，注意传入参数为系统名字+版本号，如：
  • 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的版本号已支持
  • 开不起来的可能是硬盘或内存不够大或者本身就不适配宿主机，自行尝试查看开不起来的报错
TIP
版本号中已结束长期维护的一般不再有官方镜像了，暂时未找到历史镜像的存档地址，如果有找到欢迎留言我会添加支持
示例 ​
以下为开设的示例服务器的信息：
属性值
服务器名字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
需要进入容器内部则执行
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
+ls
普通版本批量生成 ​
开出的服务器配置：
  • 1核256MB内存1GB硬盘限速300Mbit带宽
  • 带1个SSH端口，25个外网端口
  • 默认内存和硬盘大小
TIP
lxc若命令无问题，执行初始化开服务器，这一步最好放screen中后台挂起执行，开服务器时长与你开几个和宿主机配置相关
执行下面命令加载开机脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/init.sh -o init.sh && chmod +x init.sh && dos2unix init.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/init.sh -o init.sh && chmod +x init.sh && dos2unix init.sh
下面命令为开服务器名字前缀为tj的10个服务器
shell
./init.sh tj 10
有时候init.sh的运行路径有问题，此时建议前面加上sudo强制根目录执行
纯SSH端口版本批量生成 ​
开出的服务器配置：
  • 1核128MB内存300MB硬盘限速300Mbit带宽
  • 只有一个SSH端口
  • 无法挂载warp
TIP
lxc若命令无问题，执行初始化开服务器，这一步最好放screen中后台挂起执行，开服务器时长与你开几个和宿主机配置相关
加载开机脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/least.sh -o least.sh && chmod +x least.sh && dos2unix least.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/least.sh -o least.sh && chmod +x least.sh && dos2unix least.sh
下列命令最后一行为开服务器名字前缀为tj的10个服务器
shell
./least.sh tj 10
有时候least.sh的运行路径有问题，此时建议前面加上sudo强制根目录执行
自定义批量生成版本 ​
  • 可自定义内存和硬盘大小
  • 有执行过上面的手动批量生成过也没问题，配置是继承的不覆盖
如果需要多次批量生成服务器，可使用
国际
curl -L https://github.com/spiritLHLS/lxd/raw/main/scripts/add_more.sh -o add_more.sh && chmod +x add_more.sh && bash add_more.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://github.com/spiritLHLS/lxd/raw/main/scripts/add_more.sh -o add_more.sh && chmod +x add_more.sh && bash add_more.sh
可多次运行批量生成服务器，且继承前面已生成的部分在后面添加，可自定义内存和硬盘大小
查看已批量开设的信息 ​
开完服务器后，具体信息会生成在当前目录下的log文件中，格式如下
shell
1号服务器名称 密码 ssh端口 外网端口起始 外网端口终止
+2号服务器名称 密码 ssh端口 外网端口起始 外网端口终止
如果想要查看，只需在当前目录执行以下命令打印log文件即可
shell
cat log
WARNING
不要拿该脚本开出的服务器当生产环境，LXC虚拟化不支持换内核，dd，开启bbr等操作
部分常用LXD命令 ​
查看所有
bash
lxc list
查看个例
bash
lxc info 服务器名字
启动个例
bash
lxc start 服务器名字
停止个例
bash
lxc stop 服务器名字
删除个例
bash
lxc delete -f 服务器名字
进入内部
bash
lxc exec 服务器名字 /bin/bash
TIP
在alpine中不用/bin/bash而是用/bin/sh，常规的系统都是/bin/bash
退出则输入exit回车即可
删除所有LXC容器
bash
lxc list -c n --format csv | xargs -I {} lxc delete -f {}
在容器内执行删除无用日志
bash
sudo apt-get autoremove
+sudo apt-get clean
+sudo find /var/log -type f -delete
+sudo find /var/tmp -type f -delete
+sudo find /tmp -type f -delete
+sudo find /var/cache/apt/archives -type f -delete
更新上述所有一键脚本的相关命令 ​
删除原始配置脚本
bash
rm -rf /usr/local/bin/ssh_sh.sh
+rm -rf /usr/local/bin/config.sh
+rm -rf /usr/local/bin/ssh_bash.sh
+rm -rf /usr/local/bin/check-dns.sh
+rm -rf /root/ssh_sh.sh
+rm -rf /root/config.sh
+rm -rf /root/ssh_bash.sh
+rm -rf /root/buildone.sh
+rm -rf /root/add_more.sh
+rm -rf /root/build_ipv6_network.sh
下载回新版本的相关配置脚本
bash
wget https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/check-dns.sh -O /usr/local/bin/check-dns.sh && chmod +x /usr/local/bin/check-dns.sh
+wget https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/config.sh -O /usr/local/bin/config.sh && chmod +x /usr/local/bin/config.sh
+wget https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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
new file mode 100644
index 0000000000..c801bf8c88
--- /dev/null
+++ b/guide/lxd/lxd_precheck.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    前言 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
要求 ​
硬件要求:
  • 系统：Debian 8+, Ubuntu 18+(推荐20.04)
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转
项目特点 ​
  • 本套脚本开发使用的Ubuntu20，Ubuntu别的长期维护版本应该也没问题，Debian无法使用zfs时自动切换别的存储类型
  • 已设置同时进行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/spiritLHLS/lxd/main/scripts/pre_check.sh)
国内
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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
new file mode 100644
index 0000000000..0a247bd06b
--- /dev/null
+++ b/guide/lxd/lxd_qa.html
@@ -0,0 +1,27 @@
+
+
+  
+    
+    
+    解惑 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
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 促销款
luxvps 中的 德国AMD 促销款

+    
+    
+  
+
\ No newline at end of file
diff --git a/guide/lxd/lxd_thanks.html b/guide/lxd/lxd_thanks.html
new file mode 100644
index 0000000000..684a0cd7fc
--- /dev/null
+++ b/guide/lxd/lxd_thanks.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    一键虚拟化项目 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
+    
+    
+  
+
\ No newline at end of file
diff --git a/guide/lxd_custom.html b/guide/lxd_custom.html
deleted file mode 100644
index c18dd27d18..0000000000
--- a/guide/lxd_custom.html
+++ /dev/null
@@ -1,52 +0,0 @@
-
-
-  
-    
-    
-    给宿主机附加免费的IPV6地址段 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
给宿主机附加免费的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
-# systemctl disable systemd-networkd.socket
如果需要安装的是ifupdown控制网络，这个工具一般的主流linux系统都有
apt-get install ifupdown -y
如果需要安装的是ifupdown2进行网络管理，而这个工具一般只在debian系上可安装使用
apt-get install ifupdown2 -y
安装完毕后，安装了哪个包后面就选择哪个包进行格式转换。
systemctl start networking
-systemctl enable networking
然后重启服务器，检验机器的网络是否会因为修改出现重启失联的情况，且执行uptime观察启动已超过1分钟后，再进行后续步骤
如果是是前者inactive，后者active，则不需要切换网络管理程序，直接进行后续操作即可。
由于部分服务器存在默认的内网IPV6路由会与隧道冲突，此时可使用以下命令删除默认的IPV6路由
default_route=$(ip -6 route show | awk '/default via/{print $3}') && [ -n "$default_route" ] && ip -6 route del default via $default_route dev eth0
这里假设了你的客户端的服务器的默认网卡是eth0，你可以使用ip -6 route查看默认的路由并替换它，默认路由以default via开头，使用dev指定默认网卡，你只需要按照这个规则找到它即可
tunnelbroker_net ​
结合一键开设带IPV6地址的容器的脚本，就能给每个容器附加来自he的IPV6地址了
缺点是地址比较黑/脏，cloudflare的cdn极有可能套不上，自行测试
  1. 在 https://tunnelbroker.net/ 注册账户，并点击左边的 Create Regular Tunnel
1
  1. 红框处填写你的服务器的IPV4地址，选择物理距离近的连接点，比如机器在美国洛杉矶，就选美国西海岸的连接点，然后显示绿框提示，点Create Tunnel创建即可
2
3
4
  1. 等待出以下界面，点击Example Configurations然后选择对应的系统，比如LXD的宿主机那肯定就是Debian/Ubuntu了
5
6
  1. 框住的部分就是要修改的文件和需要复制的内容了
7
复制的时候不要带空行
  1. 转换格式后给你的网络配置文件附加IPV6的设置
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为TunnelBrokerNet，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式，等待页面刷新显示转换格式后的配置文件内容
然后用vim或者vi命令修改/etc/network/interfaces文件增加内容，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
-# 这里修改复制粘贴一下转换格式后的配置文件内容，然后执行此命令
-EOF
然后你可以使用cat /etc/network/interfaces查看配置文件是否正常写入了
  1. 如果上面都没问题，就需要启用网络接口即可
apt-get install net-tools iproute2 -y
-systemctl restart networking
  1. 然后你就可以测试IPV6网络是否已附加
执行ifconfig命令，这时应该有一个 he-ipv6 接口，类似下面这样：
8
或者执行：
curl ipv6.ip.sb
回传你绑定IPV6地址
  1. NAT VPS 的额外设置
IPv4 NAT VPS 除了前面提到的替换 IP 操作以外，可能还需要一些额外的设置，否则可能还是无法访问 IPv6 网络。
apt-get install ufw -y
-ufw allow 41
添加相关的路由规则
route -A inet6 add ::/0 dev he-ipv6
  1. 如果不需要该IPV6网络了，想要删除
删除 he-ipv6 网络接口配置（若没有删除重启后会自动启用），记得修改/etc/network/interfaces文件，删除之前红框添加的内容
然后重启服务器，就删除了
tunnelbroker_ch ​
类似上述的操作，先在 https://www.tunnelbroker.ch/ 注册一个账户先，注册后点击激活的邮件
然后就是填写你的服务器IPV4地址
创建后需要进入Config页面而不是详情页面
见到以下页面千万别使用，先刷新一下本页面，不要弹那个浅蓝色框后再停止刷新
记录以下页面的最后一个红框的内容，准备修改宿主机配置文件
页面的最后一个红框框住的部分复制下来，不要带空行
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为TunnelBrokerCh，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式，等待页面刷新显示转换格式后的配置文件内容
然后用vim或者vi命令修改/etc/network/interfaces文件增加内容，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
-# 这里修改一下
-EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
-systemctl restart networking
保证环境无问题再进行别的操作了
ip4market_ru ​
类似上述的操作，先在 https://tb.ip4market.ru 注册一个账户先，注册邮箱得是非常见邮箱，电话可随便写不验证的，IP填上你要附加的宿主机的IPV4地址
然后就是过Recaptcha的人机验证，点击注册
邮箱会收到激活邮件，里面附带有你的密码，记住它
然后在首页进行登录
然后就会进入这个页面
按住右键，然后复制红框框住的四行内容，也就是
Server IPv4:
-Client IPv4
-Server IPv6
-Client IPv6
这四行内容，按ctrl+c复制或者右键复制
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为ip4market，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式
然后就会自动刷新页面出现需要自己用vim或者vi命令修改/etc/network/interfaces文件增加的内容了，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
-# 这里修改一下
-EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
-systemctl restart networking
保证环境无问题再进行别的操作了
netassist_ua ​
这个平台你在切换网络管理时务必使用ifupdown2而不是ifupdown2安装包，该平台使用sit协议，而sit协议需要在ifupdown2控制的环境中使用
类似上述的操作，先在 https://tb.netassist.ua/ 注册一个账户先，注册后点击激活的邮件，激活页面会有密码显示，记得记录
然后就是填写你的服务器IPV4地址，这个后面可以自己修改，先随便填一个都没问题
然后就到了这个页面了
a
第一个红框是你宿主机的IPV4地址需要填写的位置，要修改就修改那里，然后点change保存
第二个下拉红框选择Linux，然后点击show
b
会出现上面的内容，全选框住的部分复制下来，不要带空行
然后打开 https://ipv6tunnel.spiritlhl.top/ 选择Option为NetAssist，另一个下拉选择框选择你之前安装成功的包名，然后在输入框内粘贴你复制的内容
然后点击Covert转换格式
c
然后就会自动刷新页面出现需要自己用vim或者vi命令修改/etc/network/interfaces文件增加的内容了，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
-# 这里修改一下
-EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
-systemctl restart networking
保证环境无问题再进行别的操作了
转移不同服务器之间的IPV6子网 ​
相关仓库：https://github.com/oneclickvirt/6in4
该方法将提供一种方式，将A上的IPV6网段拆分一个子ipv6网段的出来，附加到B上使用
你需要在B所在的服务器上使用本套脚本给容器一键配置IPV6地址
功能 ​
  • 自建sit/gre/ipip协议的IPv6隧道
  • 支持自定义要切分出来的IPV6子网大小，将自动计算出合适的CIDR格式的IPV6子网信息
  • 自动识别服务端的IPV6子网大小
  • 将自动设置隧道服务端并打印客户端需要执行的命令
  • 设置IPV6隧道的方法简单易懂，易于删除
环境准备 ​
VPS(A)VPS(B)
一个IPV4地址(server_ipv4)一个IPV4地址(clinet_ipv4)
一个IPV6子网无IPV6地址
以下称之为服务端以下称之为客户端
使用方法 ​
下载脚本
curl -L https://raw.githubusercontent.com/oneclickvirt/6in4/main/6in4.sh -o 6in4.sh && chmod +x 6in4.sh
执行命令
./6in4.sh client_ipv4 <mode_type> <subnet_size>
选项可选的选项1可选的选项2可选的选项3
<mode_type>gresitipip
<subnet_size>6480112
<mode_type>暂时只支持那三种协议，越靠前的越推荐，不填则默认为sit协议
<subnet_size>只要比原系统子网掩码大就行，且是8的倍数，不填则默认为80
记得client_ipv4替换为需要附加IPV6的机器的IPV4地址，执行完毕后会回传你需要在客户端执行的命令，详见执行后的说明即可
为防止忘记复制命令，命令本身也将写入到当前路径下的6in4.log文件中，可使用cat 6in4.log查询客户端需要执行的命令
复制下来的命令，务必在 https://ipv6tunnel.spiritlhl.top/ 中选择选项6in4后进行转换
然后就会自动刷新页面出现需要自己用vim或者vi命令修改/etc/network/interfaces文件增加的内容了，或者修改以下命令新增
tee -a /etc/network/interfaces <<EOF
-# 这里修改一下
-EOF
然后你就需要重启一下系统，或者执行
apt-get install net-tools iproute2 -y
-systemctl restart networking
保证环境无问题再进行别的操作了
检测服务端 ​
systemctl status ndpresponder
ip addr show
检测客户端 ​
ip addr show
curl ipv6.ip.sb
删除隧道 ​
服务端
ip link set server-ipv6 down
-ip tunnel del server-ipv6
客户端
ip link set user-ipv6 down
-ip tunnel del user-ipv6
以上删除的方式只是临时删除，永久删除务必修改删除/etc/network/interfaces文件中你之前增加的内容
后言 ​
实际上 https://tunnelbroker.net/ 支持申请/48大小的IPV6子网，只需要在
图片
这里进行申请，然后转换格式的时候将原先/64的IPV6地址改成/48的IPV6地址，你就能获得一个更大的IPV6子网了

-    
-    
-  
-
\ No newline at end of file
diff --git a/guide/lxd_extra_config.html b/guide/lxd_extra_config.html
deleted file mode 100644
index ddc238a4ba..0000000000
--- a/guide/lxd_extra_config.html
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-  
-    
-    
-    其他自定义配置 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
其他自定义配置 ​
TIP
以下的配置安装会加重宿主机的负担，非必要不要安装
TIP
如果是个人使用，可忽略防滥用部分脚本的安装
自动配置IPV6地址 ​
  • (非必须，不使用的也没问题)
  • 该脚本仅适用于宿主机有给IPV6子网且是至少/112的，且宿主机绑定了子网的第一个IP做宿主机的IPV6地址或IPV6的gateway
  • 自动为LXD创建的LXC容器配置IPV6地址
  • 已集成到buildone.sh中可使用变量控制且无需事先下载，该脚本可不手动使用，在使用buildone.sh时配置Y开启即可
下载脚本
国际
bash
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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
-netfilter-persistent reload
-service netfilter-persistent restart
卸载IPV6地址绑定的守护进程和对应的文件可用：
shell
systemctl stop add-ipv6.service
-systemctl disable add-ipv6.service
-rm /etc/systemd/system/add-ipv6.service
-systemctl daemon-reload
-rm /usr/local/bin/add-ipv6.sh
屏蔽容易被滥用的端口的出入流量以屏蔽端口和屏蔽滥用工具包 ​
  • (非必须，该脚本仅仅是为了防止容器滥用方便，不装的也没问题)
  • 事前预防
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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/spiritLHLS/lxd/main/scripts/build_monitor.sh -o build_monitor.sh && chmod +x build_monitor.sh && bash build_monitor.sh
一键安装开lxd宿主机所需要的带vnstat环境的常用预配置环境 ​
  • (非必须，该脚本仅仅是为了站点对接监控方便，不装的也没问题)
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/lxd/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/spiritLHLS/lxd/main/scripts/backend.sh -o backend.sh && chmod +x backend.sh && bash backend.sh
一键安装宿主机可视化操作的面板 ​
  • (非必须，该面板只是为了方便可视化操作，没有也没问题)
  • 原作者仓库：跳转
shell
lxc config set core.https_address [::]
-lxc config set core.trust_password some-secret-string
-snap install lxdmosaic
安装完毕后打开宿主机IP地址，按照提示设置admin的密码，其他一路默认就能使用面板了

-    
-    
-  
-
\ No newline at end of file
diff --git a/guide/lxd_install.html b/guide/lxd_install.html
deleted file mode 100644
index 30dd050d68..0000000000
--- a/guide/lxd_install.html
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-  
-    
-    
-    LXD主体安装 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
LXD主体安装 ​
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
一键安装 ​
WARNING
如果是全新的服务器，务必保证apt update和apt install curl都无问题再执行本脚本
TIP
且自开机起最好等待5分钟后再执行以下命令，避免系统默认设置中就执行了本脚本导致apt源卡死
  • 环境要求：Ubuntu 18+(推荐)，Debian 8+(仅限x86_64架构)
  • 如果是Debian系的宿主机，务必在screen中执行本脚本，避免长期运行时SSH中断导致ZFS编译安装失败
  • 这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的服务器占的盘的大小的总和
  • 环境安装过程中可能需要重启服务器以加载含zfs的内核，然后再次执行安装命令，一切以运行后命令行的提示为准
  • 默认启用lxd的lxcfs相关配置，使得容器内查询容器信息变更为容器本身的信息而不是宿主机信息
如果脚本提示重启系统后需要再次执行脚本，第二次执行安装脚本仍提示重启系统加载内核，那么意味着内核在上一次加载中失败了，最好重装宿主机系统为ubuntu系解决这个问题
每次执行脚本都需要输入一次初始化的配置，所以遇到脚本提示需重启系统再次执行，那么就得再次输入初始化的配置
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/lxd/main/scripts/lxdinstall.sh -o lxdinstall.sh && chmod +x lxdinstall.sh && bash lxdinstall.sh
初始化配置的例子：
如果系统盘除去已占用空间还有18G硬盘空余，想开2G虚拟内存(2048MB的SWAP)，15G的存储池，按照命令行的提示则依次输入2048和15
手动安装 ​
新手推荐，避免有bug不知道怎么修，当然如果只是图方便又是老手懂排查BUG，用后面的一键安装也行
关闭防火墙 ​
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/spiritLHLS/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/spiritLHLS/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命令是否有报错找不到

-    
-    
-  
-
\ No newline at end of file
diff --git a/guide/lxd_lxc.html b/guide/lxd_lxc.html
deleted file mode 100644
index bbfa860bf3..0000000000
--- a/guide/lxd_lxc.html
+++ /dev/null
@@ -1,50 +0,0 @@
-
-
-  
-    
-    
-    LXC虚拟化 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
LXC虚拟化 ​
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载开机脚本是非必须的，如果你使用过一键安装LXD的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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
支持自定义服务器的系统，不填写留空时默认使用debian11，注意传入参数为系统名字+版本号，如：
  • 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的版本号已支持
  • 开不起来的可能是硬盘或内存不够大或者本身就不适配宿主机，自行尝试查看开不起来的报错
TIP
版本号中已结束长期维护的一般不再有官方镜像了，暂时未找到历史镜像的存档地址，如果有找到欢迎留言我会添加支持
示例 ​
以下为开设的示例服务器的信息：
属性值
服务器名字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
需要进入容器内部则执行
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
-ls
普通版本批量生成 ​
开出的服务器配置：
  • 1核256MB内存1GB硬盘限速300Mbit带宽
  • 带1个SSH端口，25个外网端口
  • 默认内存和硬盘大小
TIP
lxc若命令无问题，执行初始化开服务器，这一步最好放screen中后台挂起执行，开服务器时长与你开几个和宿主机配置相关
执行下面命令加载开机脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/init.sh -o init.sh && chmod +x init.sh && dos2unix init.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/init.sh -o init.sh && chmod +x init.sh && dos2unix init.sh
下面命令为开服务器名字前缀为tj的10个服务器
shell
./init.sh tj 10
有时候init.sh的运行路径有问题，此时建议前面加上sudo强制根目录执行
纯SSH端口版本批量生成 ​
开出的服务器配置：
  • 1核128MB内存300MB硬盘限速300Mbit带宽
  • 只有一个SSH端口
  • 无法挂载warp
TIP
lxc若命令无问题，执行初始化开服务器，这一步最好放screen中后台挂起执行，开服务器时长与你开几个和宿主机配置相关
加载开机脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/least.sh -o least.sh && chmod +x least.sh && dos2unix least.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/least.sh -o least.sh && chmod +x least.sh && dos2unix least.sh
下列命令最后一行为开服务器名字前缀为tj的10个服务器
shell
./least.sh tj 10
有时候least.sh的运行路径有问题，此时建议前面加上sudo强制根目录执行
自定义批量生成版本 ​
  • 可自定义内存和硬盘大小
  • 有执行过上面的手动批量生成过也没问题，配置是继承的不覆盖
如果需要多次批量生成服务器，可使用
国际
curl -L https://github.com/spiritLHLS/lxd/raw/main/scripts/add_more.sh -o add_more.sh && chmod +x add_more.sh && bash add_more.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://github.com/spiritLHLS/lxd/raw/main/scripts/add_more.sh -o add_more.sh && chmod +x add_more.sh && bash add_more.sh
可多次运行批量生成服务器，且继承前面已生成的部分在后面添加，可自定义内存和硬盘大小
查看已批量开设的信息 ​
开完服务器后，具体信息会生成在当前目录下的log文件中，格式如下
shell
1号服务器名称 密码 ssh端口 外网端口起始 外网端口终止
-2号服务器名称 密码 ssh端口 外网端口起始 外网端口终止
如果想要查看，只需在当前目录执行以下命令打印log文件即可
shell
cat log
WARNING
不要拿该脚本开出的服务器当生产环境，LXC虚拟化不支持换内核，dd，开启bbr等操作
部分常用LXD命令 ​
查看所有
bash
lxc list
查看个例
bash
lxc info 服务器名字
启动个例
bash
lxc start 服务器名字
停止个例
bash
lxc stop 服务器名字
删除个例
bash
lxc delete -f 服务器名字
进入内部
bash
lxc exec 服务器名字 /bin/bash
TIP
在alpine中不用/bin/bash而是用/bin/sh，常规的系统都是/bin/bash
退出则输入exit回车即可
删除所有LXC容器
bash
lxc list -c n --format csv | xargs -I {} lxc delete -f {}
在容器内执行删除无用日志
bash
sudo apt-get autoremove
-sudo apt-get clean
-sudo find /var/log -type f -delete
-sudo find /var/tmp -type f -delete
-sudo find /tmp -type f -delete
-sudo find /var/cache/apt/archives -type f -delete
更新上述所有一键脚本的相关命令 ​
删除原始配置脚本
bash
rm -rf /usr/local/bin/ssh_sh.sh
-rm -rf /usr/local/bin/config.sh
-rm -rf /usr/local/bin/ssh_bash.sh
-rm -rf /usr/local/bin/check-dns.sh
-rm -rf /root/ssh_sh.sh
-rm -rf /root/config.sh
-rm -rf /root/ssh_bash.sh
-rm -rf /root/buildone.sh
-rm -rf /root/add_more.sh
-rm -rf /root/build_ipv6_network.sh
下载回新版本的相关配置脚本
bash
wget https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/check-dns.sh -O /usr/local/bin/check-dns.sh && chmod +x /usr/local/bin/check-dns.sh
-wget https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/config.sh -O /usr/local/bin/config.sh && chmod +x /usr/local/bin/config.sh
-wget https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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/spiritLHLS/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_precheck.html b/guide/lxd_precheck.html
deleted file mode 100644
index 87493693a7..0000000000
--- a/guide/lxd_precheck.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    前言 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果你的宿主机本身没有IPV6的子网又想给容器分配IPV6地址，那么请先查看LXD模块中的自定义分区中的给宿主机附加免费的IPV6地址段的内容，给宿主机附加上IPV6子网后再进行环境安装
要求 ​
硬件要求:
  • 系统：Debian 8+, Ubuntu 18+(推荐20.04)
  • 虚拟化：推荐KVM、VMWARE虚拟化
  • 内存：内存至少512MB
  • 硬盘：硬盘(系统盘)至少10G
  • 网络：独立的IPV4地址，IPV6可有可无，带宽能下载脚本就行，网络能连接Github的raw页面就行
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
PS: 如果硬件资源更烂，虚拟化不支持，可使用docker版本的，适配面更广 跳转
项目特点 ​
  • 本套脚本开发使用的Ubuntu20，Ubuntu别的长期维护版本应该也没问题，Debian无法使用zfs时自动切换别的存储类型
  • 已设置同时进行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/spiritLHLS/lxd/main/scripts/pre_check.sh)
国内
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/pre_check.sh)

-    
-    
-  
-
\ No newline at end of file
diff --git a/guide/lxd_qa.html b/guide/lxd_qa.html
deleted file mode 100644
index ce9aaa2e22..0000000000
--- a/guide/lxd_qa.html
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-  
-    
-    
-    解惑 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
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 促销款
luxvps 中的 德国AMD 促销款

-    
-    
-  
-
\ No newline at end of file
diff --git a/guide/lxd_thanks.html b/guide/lxd_thanks.html
deleted file mode 100644
index a7174d68bb..0000000000
--- a/guide/lxd_thanks.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    一键虚拟化项目 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
-    
-    
-  
-
\ No newline at end of file
diff --git a/guide/pve/pve_custom.html b/guide/pve/pve_custom.html
new file mode 100644
index 0000000000..b6acdcc2c4
--- /dev/null
+++ b/guide/pve/pve_custom.html
@@ -0,0 +1,39 @@
+
+
+  
+    
+    
+    一些自定义脚本 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
一些自定义脚本 ​
每个脚本可能有对应的系统要求，自行查看
在非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 \
+--privileged \
+--name pve \
+--add-host pve:10.13.14.101 \
+--hostname pve \
+spiritlhl/pve:7_x86_64
ARM架构
bash
docker run -idt --network host \
+--privileged \
+--name pve \
+--add-host pve:10.13.14.101 \
+--hostname pve \
+spiritlhl/pve:7_aarch64
开设出的面板实际是开设在容器内的，但网络已使用host模式，PVE的端口约等于就使用的宿主机的端口
有许多错误需要修复，欢迎PR解决问题，实测在Ubuntu系统的宿主机上安装Proxmox VE的面板成功，解决了通过网络安装Proxmox VE只能使用Debian系统做宿主机的问题

+    
+    
+  
+
\ No newline at end of file
diff --git a/guide/pve/pve_install.html b/guide/pve/pve_install.html
new file mode 100644
index 0000000000..2f4c476f99
--- /dev/null
+++ b/guide/pve/pve_install.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    PVE主体安装 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
PVE主体安装 ​
安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载
一键安装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秒未自重启确保这个安装已运行完毕
若宿主机本身存在SLAAC分配的IPV6地址，将可选择是否使用最大的IPV6子网范围，默认回车不使用最大的IPV6子网范围仅使用本机IPV6，若后续需要给虚拟机/容器附加独立的IPV6地址，该选项务必选择y.
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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命令执行很慢，得等一会才能执行完毕，当然大部分的机器没这么烂
国际
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)
自动配置宿主机的网关 ​
WARNING
使用前请保证重启过服务器且此时PVE能正常使用WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动成功后至少等1分钟再执行本命令
TIP
这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行
TIP
在执行本命令前如果宿主机需要附加IPV6隧道的地址，请查看LXD的自定义分区部分的内容附加到对应文件中，但请忽略它的初始环境修改部分的内容
  • 如果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/spiritLHLS/pve/main/scripts/build_nat_network.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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
new file mode 100644
index 0000000000..462231e19d
--- /dev/null
+++ b/guide/pve/pve_kvm.html
@@ -0,0 +1,38 @@
+
+
+  
+    
+    
+    KVM虚拟化 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
KVM虚拟化 ​
SSH登录说明 ​
KVM虚拟化开设出的虚拟机，默认生成的用户名不是root，你需要执行sudo -i切换为root用户
当然部分模板实际支持用户名root登录，默认的root密码是password，你也可以先试试
登录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]
部分注意事项 ​
执行本项目的检测环境的命令，展示如下
图片
查询如上的只需使用下面的一键脚本自动创建虚拟机即可，无需手动再修改WEB端设置
图片
查询如上的在使用后续脚本创建了虚拟机后，可能需要手动修改WEB端设置，需要关闭对应每个虚拟机的硬件嵌套虚拟化，如下图
图片
先停止虚拟机再修改，修改完后再开机才能使用NOVNC，不关闭可能导致这个虚拟机有BUG无法使用
如果强行安装PVE开KVM，启动不了的也可以关闭这个选项试试能不能启动虚拟机
TIP
开设虚拟机前请使用screen挂起执行，避免开设时间过长，SSH不稳定导致中间执行中断
开设带IPV6地址的KVM虚拟机的注意事项 ​
由于长期闲置IPV6不使用可能导致NDP广播缓存失效重置，一般闲置50分钟左右就会出现IPV6不可用的情况，俗称“IPV6断流”，此时需要设置一个定时任务
shell
echo '*/1 * * * * curl -m 6 -s ipv6.ip.sb && curl -m 6 -s ipv6.ip.sb' | crontab -
在开设出的虚拟机中执行上述命令，可保证IPV6网络一直被使用，不会失效断流
开设KVM虚拟机可使用的镜像 ​
  • 已预安装开启cloudinit
  • 开启SSH登陆
  • 预设置SSH监听V4和V6的22端口
  • 开启允许密码验证登陆
  • 开启允许root登陆
  • 部分预安装Qemu-guest-agent
目前可使用的镜像名字的列表为
https://github.com/oneclickvirt/kvm_images/blob/main/list.text
单独开设NAT的KVM虚拟化的虚拟机 ​
  • 自动开设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/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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 102 test1 oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
开设完毕可执行cat vm102查看信息，或到WEB端对应VM的NOTES中查看
以下为开设的示例VM的信息：
属性值
VMID102
SSH登录的用户名test1
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小10G
SSH端口40001
80端口40002
443端口40003
内外网映射端口一致的区间50000到50025
系统debian11
宿主机的存储盘local
绑定独立IPV6(留空默认N)N
删除指定虚拟机 ​
  • 停止VM
  • 删除VM
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应VMID的虚拟机，这里用上文中的示例102做演示
shell
./pve_delete.sh 102
实际删除数量不固定，空格分隔每个VMID即可，可一次性删除多个
批量开设NAT的KVM虚拟化的虚拟机 ​
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/spiritLHLS/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/spiritLHLS/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
+systemctl restart networking.service
+systemctl restart ndpresponder.service
+iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
+iptables-save > /etc/iptables/rules.v4
+rm -rf vmlog
+rm -rf vm*
TIP
PVE修改VM配置前都得停机先，再修改配置，修改完再启动，免得出现配置重载错误
开设独立IPV4地址的虚拟机 ​
两个版本，各取所需
自动选择IPV4地址无需手动指定的版本 ​
WARNING
使用前需要保证当前宿主机的IP段带了至少2个IP，且有空余的IP未配置，该空余的IP未绑定宿主机
  • 自动检测可用的IP区间，通过ping检测空余可使用的IP，选取其中之一绑定到虚拟机上
  • 如果宿主机自带IPV6子网将可选择是否附加上IPV6地址
  • 系统的相关信息将会存储到对应的虚拟机的NOTE中，可在WEB端查看
使用方法 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm_extraip.sh -o buildvm_extraip.sh && chmod +x buildvm_extraip.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm_extraip.sh -o buildvm_extraip.sh && chmod +x buildvm_extraip.sh
各参数含义
shell
./buildvm_extraip.sh VMID 用户名 密码 CPU核数 内存大小以MB计算 硬盘大小以GB计算 系统 存储盘 独立IPV6(默认为N)
TIP
注意这里的密码最好仅英文与数字混合，且以英文开头，避免密码在设置过程中因为特殊字符被转义而设置失败
测试示例 ​
shell
./buildvm_extraip.sh 152 test1 oneclick123 1 1024 10 debian12 local N
上述命令意义为开设一个带独立IPV4地址的虚拟机
属性值
VMID152
用户名test1
密码oneclick123
CPU1核
内存1024MB
硬盘10G
系统debian12
存储盘local盘
IPV6附加默认不附加
需要手动指定IPV4地址的版本 ​
  • 需要手动在命令中指定IPV4地址，且带上子网长度
  • 如果宿主机自带IPV6子网将可选择是否附加上IPV6地址
  • 如果商家有给IPV4地址和子网长度，请仔细比对，按照下面示例的命令写参数
  • 系统的相关信息将会存储到对应的虚拟机的NOTE中，可在WEB端查看
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是一个/64子网
使用方法 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm_manual_ip.sh -o buildvm_manual_ip.sh && chmod +x buildvm_manual_ip.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm_manual_ip.sh -o buildvm_manual_ip.sh && chmod +x buildvm_manual_ip.sh
各参数含义
shell
./buildvm_manual_ip.sh VMID 用户名 密码 CPU核数 内存大小以MB计算 硬盘大小以GB计算 系统 存储盘 IPV4地址 独立IPV6(默认为N)
TIP
注意这里的密码最好仅英文与数字混合，且以英文开头，避免密码在设置过程中因为特殊字符被转义而设置失败
测试示例 ​
shell
./buildvm_manual_ip.sh 152 test1 oneclick123 1 1024 10 debian12 local a.b.c.d/24 N
上述命令意义为开设一个带独立IPV4地址的虚拟机
属性值
VMID152
用户名test1
密码oneclick123
CPU1核
内存1024MB
硬盘10G
系统debian12
存储盘local盘 (系统盘)
IPV4地址a.b.c.d
子网/24 子网
IPV6无
开设纯IPV6地址的虚拟机 ​
前提是宿主机给的是IPV6子网而不是单独一个IPV6地址，且宿主机未开启MAC地址校验
自动选择IPV6地址无需手动指定 ​
  • 自动检测可用的IPV6区间，对应虚拟机编号的V6地址绑定到虚拟机上
  • 系统的相关信息将会存储到对应的虚拟机的NOTE中，可在WEB端查看
使用方法 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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 test1 oneclick123 1 1024 10 debian12 local
上述命令意义为开设一个纯IPV6地址的虚拟机
参数值
VMID152
用户名test1
密码oneclick123
CPU1核
内存1024MB
硬盘10G
系统debian12
存储盘local
删除vm152示例 ​
shell
qm stop 152
+qm destroy 152
+systemctl restart ndpresponder.service
+rm -rf vm152

+    
+    
+  
+
\ No newline at end of file
diff --git a/guide/pve/pve_lxc.html b/guide/pve/pve_lxc.html
new file mode 100644
index 0000000000..c1c01bf466
--- /dev/null
+++ b/guide/pve/pve_lxc.html
@@ -0,0 +1,37 @@
+
+
+  
+    
+    
+    LXC虚拟化 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
LXC虚拟化 ​
单独开设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/spiritLHLS/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
  • 系统支持：
  • debian10，debian11
  • ubuntu18，ubuntu20，ubuntu22
  • centos8，almalinux9
  • 其他系统可能支持可能不支持，自行测试
TIP
系统参数一律是小写的系统名字拼接版本号，x86_64的具体可执行pveam available --section system查看可用的系统名字和版本号，arm的可在https://mirror.tuna.tsinghua.edu.cn/lxc-images/images/中查看支持的系统，版本号类同执行pveam available --section system查看到的版本号。 (注意脚本使用的参数只有小写的英文系统名字拼接版本号)
所有系统的CT默认用户名是root
各参数含义
shell
./buildct.sh CTID 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6(默认为N)
测试示例 ​
shell
./buildct.sh 102 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
开设完毕可执行cat ct102查看信息，或在web端的NOTES查看
以下为开设的示例CT的信息：
属性值
VMID102
SSH登录的用户名root
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小5G
SSH端口20001
80端口20002
443端口20003
内外网映射端口一致的区间30000到30025
系统debian11
宿主机的存储盘local
IPV6无
删除指定容器 ​
  • 停止CT
  • 删除CT
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应CTID的容器，这里用上文中的示例102做演示
shell
./pve_delete.sh 102
实际删除数量不固定，空格分隔每个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/spiritLHLS/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/spiritLHLS/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
+service networking restart
+systemctl restart networking.service
+systemctl restart ndpresponder.service
+iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
+iptables-save > /etc/iptables/rules.v4
开设纯IPV6地址的虚拟机 ​
前提是宿主机给的是IPV6子网而不是单独一个IPV6地址，且宿主机未开启MAC地址校验
自动选择IPV6地址无需手动指定 ​
  • 自动检测可用的IPV6区间，对应容器编号的V6地址绑定到容器上
  • 系统的相关信息将会存储到对应的容器的NOTE中，可在WEB端查看
使用方法 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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盘 (系统盘)
删除示例 ​
shell
rm -rf ct*
+pct stop 152 
+pct destroy 152
+systemctl restart ndpresponder.service

+    
+    
+  
+
\ No newline at end of file
diff --git a/guide/pve/pve_precheck.html b/guide/pve/pve_precheck.html
new file mode 100644
index 0000000000..a253d325d0
--- /dev/null
+++ b/guide/pve/pve_precheck.html
@@ -0,0 +1,28 @@
+
+
+  
+    
+    
+    前言 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果有未适配的商家或机器欢迎联系@spiritlhl_bot，有空会尝试支持一下
WARNING
会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
各种要求 ​
建议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和全部独服支持)
  • 如果硬件或系统需求不满足，可使用LXD批量开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类型的服务器
  • 不可嵌套虚拟化KVM类型的服务器也可以开LXC虚拟化的服务器，但不推荐安装PVE，不如使用LXD
国际
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/check_kernal.sh)
国内
bash
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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*



+    
+    
+  
+
\ No newline at end of file
diff --git a/guide/pve/pve_qa.html b/guide/pve/pve_qa.html
new file mode 100644
index 0000000000..1dcd78b3b7
--- /dev/null
+++ b/guide/pve/pve_qa.html
@@ -0,0 +1,35 @@
+
+
+  
+    
+    
+    解惑 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
解惑 ​
执行脚本不到30秒机器就掉线了 ​
原装系统执行
systemctl restart networking
看看是不是直接掉线，如果是那就是机器原生有问题，热插拔或者dhcp导致的网络无法自重启，此时建议更换宿主机的系统或DD一个新系统尝试
一般来说这种情况都是出现在独服的Debian11系统上，切换为Debian12系统就没问题了
安装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
+    echo "post-up /sbin/ethtool -K $auto_interface tx off rx off" >> /etc/network/interfaces
+    chattr +i /etc/network/interfaces
+fi
然后将重启失联的机器报给 @spiritlhl_bot 待更新脚本自动修复
安装PVE失败或非Debian系统 ​
如果有什么机器安装不了，着急的可以尝试使用以下仓库的脚本先重装为debian12先
bash <(curl -sSL https://raw.githubusercontent.com/leitbogioro/Tools/master/Linux_reinstall/InstallNET.sh) -debian 12 -pwd 'oneclickvirt139' --network "static"
此时dd后的系统用户名为root，密码为oneclickvirt139
如果有空或者还是不行，请联系 @spiritlhl_bot 尝试
非Debian系统也可使用自定义分区的内容自行尝试
开设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，那么请使用别的宿主机系统尝试
不小心删除了NAT的映射规则怎么办 ​
使用下面的命令映射回来
shell
iptables -t nat -F
+iptables -t filter -F
+service networking restart
+systemctl restart networking.service
+cat /etc/iptables/rules.v4 | iptables-restore
目前已验证的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 中的 俄罗斯和希腊 测试款
hostaris 中的 德国款 (商家的系统模板有问题，IPV6已失效和Github的连通稳定性很差)
adtaq 中的最低配存储KVM服务器
nocix 中的独立服务器
crunchbits 中的VPS
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
只可开设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
new file mode 100644
index 0000000000..24841592de
--- /dev/null
+++ b/guide/pve/pve_thanks.html
@@ -0,0 +1,26 @@
+
+
+  
+    
+    
+    一键虚拟化项目 | 一键虚拟化项目
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+    
+  
+  
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance

+    
+    
+  
+
\ No newline at end of file
diff --git a/guide/pve_custom.html b/guide/pve_custom.html
deleted file mode 100644
index f586592d9d..0000000000
--- a/guide/pve_custom.html
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-  
-    
-    
-    一些自定义脚本 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
一些自定义脚本 ​
每个脚本可能有对应的系统要求，自行查看
在非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 \
---privileged \
---name pve \
---add-host pve:10.13.14.101 \
---hostname pve \
-spiritlhl/pve:7_x86_64
ARM架构
bash
docker run -idt --network host \
---privileged \
---name pve \
---add-host pve:10.13.14.101 \
---hostname pve \
-spiritlhl/pve:7_aarch64
开设出的面板实际是开设在容器内的，但网络已使用host模式，PVE的端口约等于就使用的宿主机的端口
有许多错误需要修复，欢迎PR解决问题，实测在Ubuntu系统的宿主机上安装Proxmox VE的面板成功，解决了通过网络安装Proxmox VE只能使用Debian系统做宿主机的问题

-    
-    
-  
-
\ No newline at end of file
diff --git a/guide/pve_install.html b/guide/pve_install.html
deleted file mode 100644
index fb03ff3cab..0000000000
--- a/guide/pve_install.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    PVE主体安装 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
PVE主体安装 ​
安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载
一键安装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秒未自重启确保这个安装已运行完毕
若宿主机本身存在SLAAC分配的IPV6地址，将可选择是否使用最大的IPV6子网范围，默认回车不使用最大的IPV6子网范围仅使用本机IPV6，若后续需要给虚拟机/容器附加独立的IPV6地址，该选项务必选择y.
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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命令执行很慢，得等一会才能执行完毕，当然大部分的机器没这么烂
国际
shell
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)
自动配置宿主机的网关 ​
WARNING
使用前请保证重启过服务器且此时PVE能正常使用WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动成功后至少等1分钟再执行本命令
TIP
这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行
TIP
在执行本命令前如果宿主机需要附加IPV6隧道的地址，请查看LXD的自定义分区部分的内容附加到对应文件中，但请忽略它的初始环境修改部分的内容
  • 如果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/spiritLHLS/pve/main/scripts/build_nat_network.sh)
国内
shell
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_nat_network.sh)
TIP
这一步是可能需要你执行成功几分钟后重启系统，详见脚本最后执行完毕的提示，但重启可以保证部分隐藏设置加载成功，有条件务必重启一次服务器

-    
-    
-  
-
\ No newline at end of file
diff --git a/guide/pve_kvm.html b/guide/pve_kvm.html
deleted file mode 100644
index 35ca46b252..0000000000
--- a/guide/pve_kvm.html
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-  
-    
-    
-    KVM虚拟化 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
KVM虚拟化 ​
SSH登录说明 ​
KVM虚拟化开设出的虚拟机，默认生成的用户名不是root，你需要执行sudo -i切换为root用户
当然部分模板实际支持用户名root登录，默认的root密码是password，你也可以先试试
登录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]
部分注意事项 ​
执行本项目的检测环境的命令，展示如下
图片
查询如上的只需使用下面的一键脚本自动创建虚拟机即可，无需手动再修改WEB端设置
图片
查询如上的在使用后续脚本创建了虚拟机后，可能需要手动修改WEB端设置，需要关闭对应每个虚拟机的硬件嵌套虚拟化，如下图
图片
先停止虚拟机再修改，修改完后再开机才能使用NOVNC，不关闭可能导致这个虚拟机有BUG无法使用
如果强行安装PVE开KVM，启动不了的也可以关闭这个选项试试能不能启动虚拟机
TIP
开设虚拟机前请使用screen挂起执行，避免开设时间过长，SSH不稳定导致中间执行中断
开设带IPV6地址的KVM虚拟机的注意事项 ​
由于长期闲置IPV6不使用可能导致NDP广播缓存失效重置，一般闲置50分钟左右就会出现IPV6不可用的情况，俗称“IPV6断流”，此时需要设置一个定时任务
shell
echo '*/1 * * * * curl -m 6 -s ipv6.ip.sb && curl -m 6 -s ipv6.ip.sb' | crontab -
在开设出的虚拟机中执行上述命令，可保证IPV6网络一直被使用，不会失效断流
开设KVM虚拟机可使用的镜像 ​
  • 已预安装开启cloudinit
  • 开启SSH登陆
  • 预设置SSH监听V4和V6的22端口
  • 开启允许密码验证登陆
  • 开启允许root登陆
  • 部分预安装Qemu-guest-agent
目前可使用的镜像名字的列表为
https://github.com/oneclickvirt/kvm_images/blob/main/list.text
单独开设NAT的KVM虚拟化的虚拟机 ​
  • 自动开设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/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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 102 test1 oneclick123 1 512 10 40001 40002 40003 50000 50025 debian11 local N
开设完毕可执行cat vm102查看信息，或到WEB端对应VM的NOTES中查看
以下为开设的示例VM的信息：
属性值
VMID102
SSH登录的用户名test1
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小10G
SSH端口40001
80端口40002
443端口40003
内外网映射端口一致的区间50000到50025
系统debian11
宿主机的存储盘local
绑定独立IPV6(留空默认N)N
删除指定虚拟机 ​
  • 停止VM
  • 删除VM
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应VMID的虚拟机，这里用上文中的示例102做演示
shell
./pve_delete.sh 102
实际删除数量不固定，空格分隔每个VMID即可，可一次性删除多个
批量开设NAT的KVM虚拟化的虚拟机 ​
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/spiritLHLS/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/spiritLHLS/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
-systemctl restart networking.service
-systemctl restart ndpresponder.service
-iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
-iptables-save > /etc/iptables/rules.v4
-rm -rf vmlog
-rm -rf vm*
TIP
PVE修改VM配置前都得停机先，再修改配置，修改完再启动，免得出现配置重载错误
开设独立IPV4地址的虚拟机 ​
两个版本，各取所需
自动选择IPV4地址无需手动指定的版本 ​
WARNING
使用前需要保证当前宿主机的IP段带了至少2个IP，且有空余的IP未配置，该空余的IP未绑定宿主机
  • 自动检测可用的IP区间，通过ping检测空余可使用的IP，选取其中之一绑定到虚拟机上
  • 如果宿主机自带IPV6子网将可选择是否附加上IPV6地址
  • 系统的相关信息将会存储到对应的虚拟机的NOTE中，可在WEB端查看
使用方法 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm_extraip.sh -o buildvm_extraip.sh && chmod +x buildvm_extraip.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm_extraip.sh -o buildvm_extraip.sh && chmod +x buildvm_extraip.sh
各参数含义
shell
./buildvm_extraip.sh VMID 用户名 密码 CPU核数 内存大小以MB计算 硬盘大小以GB计算 系统 存储盘 独立IPV6(默认为N)
TIP
注意这里的密码最好仅英文与数字混合，且以英文开头，避免密码在设置过程中因为特殊字符被转义而设置失败
测试示例 ​
shell
./buildvm_extraip.sh 152 test1 oneclick123 1 1024 10 debian12 local N
上述命令意义为开设一个带独立IPV4地址的虚拟机
属性值
VMID152
用户名test1
密码oneclick123
CPU1核
内存1024MB
硬盘10G
系统debian12
存储盘local盘
IPV6附加默认不附加
需要手动指定IPV4地址的版本 ​
  • 需要手动在命令中指定IPV4地址，且带上子网长度
  • 如果宿主机自带IPV6子网将可选择是否附加上IPV6地址
  • 如果商家有给IPV4地址和子网长度，请仔细比对，按照下面示例的命令写参数
  • 系统的相关信息将会存储到对应的虚拟机的NOTE中，可在WEB端查看
  • 可选择是否开启独立IPV6，需要宿主机至少有一个/104的子网，最好是一个/64子网
使用方法 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm_manual_ip.sh -o buildvm_manual_ip.sh && chmod +x buildvm_manual_ip.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm_manual_ip.sh -o buildvm_manual_ip.sh && chmod +x buildvm_manual_ip.sh
各参数含义
shell
./buildvm_manual_ip.sh VMID 用户名 密码 CPU核数 内存大小以MB计算 硬盘大小以GB计算 系统 存储盘 IPV4地址 独立IPV6(默认为N)
TIP
注意这里的密码最好仅英文与数字混合，且以英文开头，避免密码在设置过程中因为特殊字符被转义而设置失败
测试示例 ​
shell
./buildvm_manual_ip.sh 152 test1 oneclick123 1 1024 10 debian12 local a.b.c.d/24 N
上述命令意义为开设一个带独立IPV4地址的虚拟机
属性值
VMID152
用户名test1
密码oneclick123
CPU1核
内存1024MB
硬盘10G
系统debian12
存储盘local盘 (系统盘)
IPV4地址a.b.c.d
子网/24 子网
IPV6无
开设纯IPV6地址的虚拟机 ​
前提是宿主机给的是IPV6子网而不是单独一个IPV6地址，且宿主机未开启MAC地址校验
自动选择IPV6地址无需手动指定 ​
  • 自动检测可用的IPV6区间，对应虚拟机编号的V6地址绑定到虚拟机上
  • 系统的相关信息将会存储到对应的虚拟机的NOTE中，可在WEB端查看
使用方法 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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 test1 oneclick123 1 1024 10 debian12 local
上述命令意义为开设一个纯IPV6地址的虚拟机
参数值
VMID152
用户名test1
密码oneclick123
CPU1核
内存1024MB
硬盘10G
系统debian12
存储盘local
删除vm152示例 ​
shell
qm stop 152
-qm destroy 152
-systemctl restart ndpresponder.service
-rm -rf vm152

-    
-    
-  
-
\ No newline at end of file
diff --git a/guide/pve_lxc.html b/guide/pve_lxc.html
deleted file mode 100644
index d009081767..0000000000
--- a/guide/pve_lxc.html
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-  
-    
-    
-    LXC虚拟化 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
LXC虚拟化 ​
单独开设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/spiritLHLS/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
国内
shell
curl -L https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
  • 系统支持：
  • debian10，debian11
  • ubuntu18，ubuntu20，ubuntu22
  • centos8，almalinux9
  • 其他系统可能支持可能不支持，自行测试
TIP
系统参数一律是小写的系统名字拼接版本号，x86_64的具体可执行pveam available --section system查看可用的系统名字和版本号，arm的可在https://mirror.tuna.tsinghua.edu.cn/lxc-images/images/中查看支持的系统，版本号类同执行pveam available --section system查看到的版本号。 (注意脚本使用的参数只有小写的英文系统名字拼接版本号)
所有系统的CT默认用户名是root
各参数含义
shell
./buildct.sh CTID 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6(默认为N)
测试示例 ​
shell
./buildct.sh 102 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N
开设完毕可执行cat ct102查看信息，或在web端的NOTES查看
以下为开设的示例CT的信息：
属性值
VMID102
SSH登录的用户名root
SSH登录的密码oneclick123
CPU核数1
内存大小512MB
磁盘大小5G
SSH端口20001
80端口20002
443端口20003
内外网映射端口一致的区间30000到30025
系统debian11
宿主机的存储盘local
IPV6无
删除指定容器 ​
  • 停止CT
  • 删除CT
  • 删除端口映射
  • 重启网络
  • 删除log文件
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh
使用方法
可以删除对应CTID的容器，这里用上文中的示例102做演示
shell
./pve_delete.sh 102
实际删除数量不固定，空格分隔每个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/spiritLHLS/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/spiritLHLS/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
-service networking restart
-systemctl restart networking.service
-systemctl restart ndpresponder.service
-iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore
-iptables-save > /etc/iptables/rules.v4
开设纯IPV6地址的虚拟机 ​
前提是宿主机给的是IPV6子网而不是单独一个IPV6地址，且宿主机未开启MAC地址校验
自动选择IPV6地址无需手动指定 ​
  • 自动检测可用的IPV6区间，对应容器编号的V6地址绑定到容器上
  • 系统的相关信息将会存储到对应的容器的NOTE中，可在WEB端查看
使用方法 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/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/spiritLHLS/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盘 (系统盘)
删除示例 ​
shell
rm -rf ct*
-pct stop 152 
-pct destroy 152
-systemctl restart ndpresponder.service

-    
-    
-  
-
\ No newline at end of file
diff --git a/guide/pve_precheck.html b/guide/pve_precheck.html
deleted file mode 100644
index 1eb4c2cb92..0000000000
--- a/guide/pve_precheck.html
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-  
-    
-    
-    前言 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果有未适配的商家或机器欢迎联系@spiritlhl_bot，有空会尝试支持一下
WARNING
会改变宿主机的网络结构，请保证宿主机随时可重置系统，且运行前无重要数据在宿主机上
各种要求 ​
建议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和全部独服支持)
  • 如果硬件或系统需求不满足，可使用LXD批量开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类型的服务器
  • 不可嵌套虚拟化KVM类型的服务器也可以开LXC虚拟化的服务器，但不推荐安装PVE，不如使用LXD
国际
bash
bash <(wget -qO- --no-check-certificate https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/check_kernal.sh)
国内
bash
bash <(wget -qO- --no-check-certificate https://cdn.spiritlhl.net/https://raw.githubusercontent.com/spiritLHLS/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*



-    
-    
-  
-
\ No newline at end of file
diff --git a/guide/pve_qa.html b/guide/pve_qa.html
deleted file mode 100644
index 25cfaa0c7e..0000000000
--- a/guide/pve_qa.html
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-  
-    
-    
-    解惑 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
解惑 ​
执行脚本不到30秒机器就掉线了 ​
原装系统执行
systemctl restart networking
看看是不是直接掉线，如果是那就是机器原生有问题，热插拔或者dhcp导致的网络无法自重启，此时建议更换宿主机的系统或DD一个新系统尝试
一般来说这种情况都是出现在独服的Debian11系统上，切换为Debian12系统就没问题了
安装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
-    echo "post-up /sbin/ethtool -K $auto_interface tx off rx off" >> /etc/network/interfaces
-    chattr +i /etc/network/interfaces
-fi
然后将重启失联的机器报给 @spiritlhl_bot 待更新脚本自动修复
安装PVE失败或非Debian系统 ​
如果有什么机器安装不了，着急的可以尝试使用以下仓库的脚本先重装为debian12先
bash <(curl -sSL https://raw.githubusercontent.com/leitbogioro/Tools/master/Linux_reinstall/InstallNET.sh) -debian 12 -pwd 'oneclickvirt139' --network "static"
此时dd后的系统用户名为root，密码为oneclickvirt139
如果有空或者还是不行，请联系 @spiritlhl_bot 尝试
非Debian系统也可使用自定义分区的内容自行尝试
开设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，那么请使用别的宿主机系统尝试
不小心删除了NAT的映射规则怎么办 ​
使用下面的命令映射回来
shell
iptables -t nat -F
-iptables -t filter -F
-service networking restart
-systemctl restart networking.service
-cat /etc/iptables/rules.v4 | iptables-restore
目前已验证的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 中的 俄罗斯和希腊 测试款
hostaris 中的 德国款 (商家的系统模板有问题，IPV6已失效和Github的连通稳定性很差)
adtaq 中的最低配存储KVM服务器
nocix 中的独立服务器
crunchbits 中的VPS
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
只可开设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_thanks.html b/guide/pve_thanks.html
deleted file mode 100644
index c59005665f..0000000000
--- a/guide/pve_thanks.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-  
-    
-    
-    一键虚拟化项目 | 一键虚拟化项目
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-  
-  
-    
-    
-    
-  
-
\ No newline at end of file
diff --git a/hashmap.json b/hashmap.json
index c663699fd5..8b0ed86322 100644
--- a/hashmap.json
+++ b/hashmap.json
@@ -1 +1 @@
-{"case_case6.md":"9d5fa2da","en_us_guide_lxd_extra_config.md":"50b07024","en_us_guide_docker_build.md":"b9e95978","en_us_guide_dashboard.md":"fff026e9","index.md":"d15aa3da","guide_lxd_install.md":"7ebf2ac3","en_us_guide_docker_custom.md":"75fbd145","case_case2.md":"2ef48af4","guide_lxd_qa.md":"4e3f3f6b","en_us_guide_dashboardq.md":"bafc8360","case_case4.md":"2ecc8866","guide_lxd_lxc.md":"ea0bae70","en_us_developer_index.md":"d7361e6f","guide_pve_thanks.md":"d651a824","en_us_guide_docker_install.md":"89bd27d4","case_case3.md":"b2c3109f","guide_docker_build.md":"161edccd","case_case7.md":"b28a54c5","en_us_guide_lxd_precheck.md":"2e4d2d0a","guide_pve_precheck.md":"643db164","guide_dashboard.md":"7cabee74","developer_index.md":"785f4035","guide_docker_install.md":"2bb5440f","en_us_index.md":"e266d68d","guide_pve_lxc.md":"26780811","en_us_guide_lxd_install.md":"d55489a8","guide_pve_kvm.md":"0caaabf2","guide_docker_precheck.md":"19d5f683","guide_dashboardq.md":"2282b44c","guide_pve_install.md":"e74a6710","en_us_guide_lxd_lxc.md":"cb06be90","en_us_guide_pve_custom.md":"4378da7d","guide_lxd_custom.md":"ce677ab3","en_us_guide_pve_install.md":"0c728ec3","en_us_guide_docker_qa.md":"2a016075","case_index.md":"5333f3a7","guide_lxd_precheck.md":"445272a6","en_us_guide_pve_kvm.md":"aaa8a675","en_us_guide_lxd_custom.md":"ee41da21","en_us_guide_pve_lxc.md":"22a7335d","en_us_guide_docker_precheck.md":"d2e2e9c5","en_us_guide_pve_precheck.md":"340a9739","en_us_guide_pve_thanks.md":"ba9d9f30","case_case5.md":"165a5373","guide_docker_qa.md":"0ed3b81c","en_us_guide_pve_qa.md":"3830e4d7","guide_lxd_thanks.md":"ebfc462d","en_us_guide_docker_thanks.md":"cf11828e","case_case1.md":"5ed7d81a","guide_lxd_extra_config.md":"9c719fca","guide_docker_custom.md":"ca748fd6","guide_pve_custom.md":"98ac2044","guide_pve_qa.md":"c3f65060","guide_docker_thanks.md":"0eedda24","developer_l10n.md":"8c2f5d32","en_us_guide_lxd_qa.md":"22281d8b","en_us_developer_l10n.md":"bb2eaae0","en_us_guide_lxd_thanks.md":"80eef0e5"}
+{"case_case7.md":"aae4e9b9","en_guide_dashboardq.md":"9993d410","developer_index.md":"8128d7cc","case_index.md":"97648dc5","developer_l10n.md":"ab634a38","en_guide_docker_docker_precheck.md":"f1090732","en_guide_docker_docker_qa.md":"98d456bf","en_guide_docker_docker_install.md":"73b40919","case_case1.md":"2d748f96","en_guide_lxd_lxd_qa.md":"f190e6aa","en_guide_lxd_lxd_precheck.md":"75ef1b42","en_guide_incus_incus_thanks.md":"89959657","en_guide_lxd_lxd_extra_config.md":"1a7780a7","en_guide_docker_docker_thanks.md":"ec3aec2c","en_guide_dashboard.md":"f1005523","en_developer_index.md":"384e9a83","en_guide_docker_docker_custom.md":"de959189","case_case5.md":"cfcc0426","en_guide_docker_docker_build.md":"12837a7a","en_guide_pve_pve_qa.md":"193e94d9","case_case3.md":"f714de49","en_guide_incus_incus_qa.md":"fbc903cd","en_guide_pve_pve_precheck.md":"55890001","en_guide_pve_pve_thanks.md":"3ce858ae","en_guide_incus_incus_install.md":"9fc6efd3","guide_docker_docker_build.md":"a256a541","en_guide_incus_incus_extra_config.md":"aad8f8d8","guide_docker_docker_custom.md":"5e7a28c4","guide_docker_docker_qa.md":"3ff7d1a4","guide_lxd_lxd_install.md":"62ad576e","guide_docker_docker_precheck.md":"42735fec","guide_docker_docker_thanks.md":"f8648a64","guide_incus_incus_extra_config.md":"b96ae35d","guide_incus_incus_install.md":"a110ad4c","guide_lxd_lxd_qa.md":"7f186f01","guide_lxd_lxd_thanks.md":"17fe9867","guide_lxd_lxd_precheck.md":"7a202bc3","guide_lxd_lxd_lxc.md":"1e49ab60","guide_incus_incus_custom.md":"2a6371c0","guide_incus_incus_thanks.md":"38fc1b5b","guide_incus_incus_precheck.md":"7250391c","guide_incus_incus_qa.md":"c32af72f","guide_pve_pve_custom.md":"e56e03c9","guide_lxd_lxd_extra_config.md":"195a4103","guide_lxd_lxd_custom.md":"4d514384","guide_pve_pve_qa.md":"3fd9c3b0","guide_pve_pve_lxc.md":"3673dc07","guide_docker_docker_install.md":"f64d4c9b","en_guide_pve_pve_custom.md":"f7825cb0","index.md":"c691cce5","case_case6.md":"1433cc80","en_guide_lxd_lxd_install.md":"e4b63e66","en_guide_pve_pve_install.md":"3bc17d1a","en_guide_lxd_lxd_lxc.md":"0f2f66ff","case_case4.md":"81f143f1","en_guide_lxd_lxd_custom.md":"4c6b4986","en_guide_incus_incus_lxc.md":"79bae231","en_developer_l10n.md":"8c74cfb9","en_guide_incus_incus_custom.md":"ffbda734","en_guide_lxd_lxd_thanks.md":"3e4226a6","en_index.md":"fc666e9e","en_guide_pve_pve_lxc.md":"ff807f3f","guide_dashboard.md":"0361b255","en_guide_incus_incus_precheck.md":"362061d5","guide_dashboardq.md":"d66f0669","guide_pve_pve_thanks.md":"ac66d82b","guide_pve_pve_precheck.md":"432bb77d","guide_pve_pve_kvm.md":"734943ad","case_case2.md":"060e69bf","en_guide_pve_pve_kvm.md":"39c0b6a3","guide_pve_pve_install.md":"b4402647","guide_incus_incus_lxc.md":"c508cac6"}
diff --git a/index.html b/index.html
index dc874228b7..2eb48e3128 100644
--- a/index.html
+++ b/index.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,8 +19,8 @@
     
   
   
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
一键虚拟化项目
开源、易于使用的服务器虚拟化项目
开始使用 →
一键使用
支持一键命令安装使用，轻松在X86_64和ARM架构的服务器上创建虚拟机或容器
基于主流系统开发
基于 Debian、Ubuntu、Centos 等系统的长期维护版本开发，无论是什么系统总有一个方法能让你虚拟化出容器或虚拟机
自带内外网端口转发和IP地址自动分配
自带内外网端口转发和IP地址自动分配，含TCP、UDP、VNC、RDP等协议，无需人工管理
批量虚拟化
支持使用 KVM、LXC、Docker 虚拟化批量开设容器或虚拟机
多系统多环境支持
开设出的容器或虚拟机已支持主流系统，涵盖 Linux、Android、Windows 系统，也支持纯粹的浏览器环境或桌面环境
自限制滥用
部分虚拟化开设的容器或虚拟机支持设置屏蔽和装载限制，避免被用于滥用

-    
+    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
一键虚拟化项目
开源、易于使用的服务器虚拟化项目
开始使用 →
一键使用
支持一键命令安装使用，轻松在X86_64和ARM架构的服务器上创建虚拟机或容器
基于主流系统开发
基于 Debian、Ubuntu、Centos 等系统的长期维护版本开发，无论是什么系统总有一个方法能让你虚拟化出容器或虚拟机
自带内外网端口转发和IP地址自动分配
自带内外网端口转发和IP地址自动分配，含TCP、UDP、VNC、RDP等协议，无需人工管理
批量虚拟化
支持使用 KVM、LXC、Docker 虚拟化批量开设容器或虚拟机
多系统多环境支持
开设出的容器或虚拟机已支持主流系统，涵盖 Linux、Android、Windows 系统，也支持纯粹的浏览器环境或桌面环境
自限制滥用
部分虚拟化开设的容器或虚拟机支持设置屏蔽和装载限制，避免被用于滥用

+    
     
   
 
\ No newline at end of file
diff --git a/sitemap.xml b/sitemap.xml
index 54a4b5cc80..c5ba21a095 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-https://www.spiritlhl.net/case/case1.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/developer/2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/dashboard.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/case/case4.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/case/case2.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/case/case3.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/case/case6.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/case/case5.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/case/case7.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/case/2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/developer/l10n.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/dashboardq.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/docker_build.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/docker_custom.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/docker_precheck.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/docker_install.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/docker_thanks.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/lxd_custom.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/docker_qa.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/lxd_extra_config.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/lxd_install.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/lxd_lxc.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/lxd_qa.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/lxd_precheck.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/lxd_thanks.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/pve_custom.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/pve_install.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/pve_kvm.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/pve_lxc.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/pve_precheck.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/pve_qa.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/guide/pve_thanks.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/index.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/developer/2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/dashboard.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/dashboardq.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/developer/l10n.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/docker_custom.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/docker_install.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/docker_qa.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/docker_precheck.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/docker_build.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/docker_thanks.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_custom.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_install.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_extra_config.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_precheck.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_qa.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_lxc.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/pve_install.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_thanks.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/pve_custom.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/pve_kvm.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/pve_lxc.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/pve_qa.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/pve_thanks.html2024-01-11T12:41:28.000Zhttps://www.spiritlhl.net/en_US/guide/pve_precheck.html2024-01-11T12:41:28.000Z
\ No newline at end of file
+https://www.spiritlhl.net/case/case1.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/developer/2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/dashboard.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/docker/docker_custom.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/incus/incus_extra_config.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_custom.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/pve/pve_custom.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/case/case3.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/case/case2.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/case/case5.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/case/case6.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/case/case4.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/case/case7.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/case/2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/developer/l10n.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/dashboardq.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/docker/docker_install.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/docker/docker_precheck.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/docker/docker_qa.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/docker/docker_thanks.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/incus/incus_custom.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/incus/incus_install.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/incus/incus_lxc.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/incus/incus_precheck.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/incus/incus_qa.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/incus/incus_thanks.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_extra_config.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_install.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_precheck.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_lxc.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_qa.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/lxd/lxd_thanks.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/pve/pve_install.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/pve/pve_lxc.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/pve/pve_kvm.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/pve/pve_precheck.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/pve/pve_qa.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/pve/pve_thanks.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/index.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_build.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/developer/l10n.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_custom.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_custom.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_custom.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/developer/2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/dashboard.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/dashboardq.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_custom.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_install.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_precheck.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_qa.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/docker/docker_thanks.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_extra_config.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_lxc.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_install.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_qa.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_precheck.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/incus/incus_thanks.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_extra_config.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_install.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_lxc.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_precheck.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_qa.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/lxd/lxd_thanks.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_install.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_kvm.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_lxc.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_precheck.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_qa.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/guide/docker/docker_build.html2024-01-15T13:16:41.000Zhttps://www.spiritlhl.net/en/guide/pve/pve_thanks.html2024-01-15T13:16:41.000Z
\ No newline at end of file