diff --git a/404.html b/404.html index f5f42db337..45a71813c6 100644 --- a/404.html +++ b/404.html @@ -16,7 +16,7 @@
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

404

PAGE NOT FOUND

But if you don't change your direction, and if you keep looking, you may end up where you are heading.
Take me home
- + \ No newline at end of file diff --git a/CNAME b/CNAME index 80dc656696..be0ee9c012 100644 --- a/CNAME +++ b/CNAME @@ -1 +1 @@ -www.spiritlhl.net \ No newline at end of file +virt.spiritlhl.net diff --git a/assets/case_case1.md.7f86883a.js b/assets/case_case1.md.01ad2e8c.js similarity index 99% rename from assets/case_case1.md.7f86883a.js rename to assets/case_case1.md.01ad2e8c.js index 8bdca09c5d..af1671e9b1 100644 --- a/assets/case_case1.md.7f86883a.js +++ b/assets/case_case1.md.01ad2e8c.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":1692790731000}'),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":1692790817000}'),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 18/20/22 - 推荐，脚本自动挂起到后台
    • Debian 9/10/11 - 还行，需要手动挂起到后台，详看脚本运行安装完毕的后续提示
  • 可能支持的系统(未验证)：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.7f86883a.lean.js b/assets/case_case1.md.01ad2e8c.lean.js
similarity index 99%
rename from assets/case_case1.md.7f86883a.lean.js
rename to assets/case_case1.md.01ad2e8c.lean.js
index 8bdca09c5d..af1671e9b1 100644
--- a/assets/case_case1.md.7f86883a.lean.js
+++ b/assets/case_case1.md.01ad2e8c.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":1692790731000}'),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 18/20/22 - 推荐，脚本自动挂起到后台
    • Debian 9/10/11 - 还行，需要手动挂起到后台，详看脚本运行安装完毕的后续提示
  • 可能支持的系统(未验证)：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":1692790817000}'),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 18/20/22 - 推荐，脚本自动挂起到后台
    • Debian 9/10/11 - 还行，需要手动挂起到后台，详看脚本运行安装完毕的后续提示
  • 可能支持的系统(未验证)：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.2c9a4469.js b/assets/case_case2.md.b490e17a.js
similarity index 99%
rename from assets/case_case2.md.2c9a4469.js
rename to assets/case_case2.md.b490e17a.js
index 6d2c730d4b..cdab95d634 100644
--- a/assets/case_case2.md.2c9a4469.js
+++ b/assets/case_case2.md.b490e17a.js
@@ -1 +1 @@
-import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case2.md","filePath":"case/case2.md","lastUpdated":1692790731000}'),l={name:"case/case2.md"},p=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
echo 1 | bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh)
或
bash
echo 1 | bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecs/raw/main/ecs.sh)
或
echo 1 | bash <(wget -qO- bash.spiritlhl.net/ecs)
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的问题
  • [ ] 端口检测(检测是否被墙)--由fscarmen的PR以及本人的技术思路提供 - 待修复
友链 ​
测评频道 ​
https://t.me/vps_reviews ​
自动更新测速服务器节点列表的网络基准测试脚本 ​
https://github.com/spiritLHLS/ecsspeed ​
脚本概况 ​
主界面：
图片
选项1融合怪完全体：
图片图片图片图片图片图片图片
选项6原创区：
图片
',75),n=[p];function o(r,c,i,h,b,d){return a(),e("div",null,n)}const g=s(l,[["render",o]]);export{C as __pageData,g as default};
+import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case2.md","filePath":"case/case2.md","lastUpdated":1692790817000}'),l={name:"case/case2.md"},p=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
echo 1 | bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh)
或
bash
echo 1 | bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecs/raw/main/ecs.sh)
或
echo 1 | bash <(wget -qO- bash.spiritlhl.net/ecs)
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的问题
  • [ ] 端口检测(检测是否被墙)--由fscarmen的PR以及本人的技术思路提供 - 待修复
友链 ​
测评频道 ​
https://t.me/vps_reviews ​
自动更新测速服务器节点列表的网络基准测试脚本 ​
https://github.com/spiritLHLS/ecsspeed ​
脚本概况 ​
主界面：
图片
选项1融合怪完全体：
图片图片图片图片图片图片图片
选项6原创区：
图片
',75),n=[p];function o(r,c,i,h,b,d){return a(),e("div",null,n)}const g=s(l,[["render",o]]);export{C as __pageData,g as default};
diff --git a/assets/case_case2.md.2c9a4469.lean.js b/assets/case_case2.md.b490e17a.lean.js
similarity index 99%
rename from assets/case_case2.md.2c9a4469.lean.js
rename to assets/case_case2.md.b490e17a.lean.js
index 6d2c730d4b..cdab95d634 100644
--- a/assets/case_case2.md.2c9a4469.lean.js
+++ b/assets/case_case2.md.b490e17a.lean.js
@@ -1 +1 @@
-import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case2.md","filePath":"case/case2.md","lastUpdated":1692790731000}'),l={name:"case/case2.md"},p=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
echo 1 | bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh)
或
bash
echo 1 | bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecs/raw/main/ecs.sh)
或
echo 1 | bash <(wget -qO- bash.spiritlhl.net/ecs)
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的问题
  • [ ] 端口检测(检测是否被墙)--由fscarmen的PR以及本人的技术思路提供 - 待修复
友链 ​
测评频道 ​
https://t.me/vps_reviews ​
自动更新测速服务器节点列表的网络基准测试脚本 ​
https://github.com/spiritLHLS/ecsspeed ​
脚本概况 ​
主界面：
图片
选项1融合怪完全体：
图片图片图片图片图片图片图片
选项6原创区：
图片
',75),n=[p];function o(r,c,i,h,b,d){return a(),e("div",null,n)}const g=s(l,[["render",o]]);export{C as __pageData,g as default};
+import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const C=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case2.md","filePath":"case/case2.md","lastUpdated":1692790817000}'),l={name:"case/case2.md"},p=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
echo 1 | bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh)
或
bash
echo 1 | bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecs/raw/main/ecs.sh)
或
echo 1 | bash <(wget -qO- bash.spiritlhl.net/ecs)
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的问题
  • [ ] 端口检测(检测是否被墙)--由fscarmen的PR以及本人的技术思路提供 - 待修复
友链 ​
测评频道 ​
https://t.me/vps_reviews ​
自动更新测速服务器节点列表的网络基准测试脚本 ​
https://github.com/spiritLHLS/ecsspeed ​
脚本概况 ​
主界面：
图片
选项1融合怪完全体：
图片图片图片图片图片图片图片
选项6原创区：
图片
',75),n=[p];function o(r,c,i,h,b,d){return a(),e("div",null,n)}const g=s(l,[["render",o]]);export{C as __pageData,g as default};
diff --git a/assets/case_case3.md.f70dffcb.js b/assets/case_case3.md.e78a8a38.js
similarity index 99%
rename from assets/case_case3.md.f70dffcb.js
rename to assets/case_case3.md.e78a8a38.js
index 8b0a188f2b..2a36e46424 100644
--- a/assets/case_case3.md.f70dffcb.js
+++ b/assets/case_case3.md.e78a8a38.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":1692790731000}'),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":1692790817000}'),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.f70dffcb.lean.js b/assets/case_case3.md.e78a8a38.lean.js
similarity index 99%
rename from assets/case_case3.md.f70dffcb.lean.js
rename to assets/case_case3.md.e78a8a38.lean.js
index 8b0a188f2b..2a36e46424 100644
--- a/assets/case_case3.md.f70dffcb.lean.js
+++ b/assets/case_case3.md.e78a8a38.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":1692790731000}'),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":1692790817000}'),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.2ed250b5.js b/assets/case_case4.md.0afe4b74.js
similarity index 98%
rename from assets/case_case4.md.2ed250b5.js
rename to assets/case_case4.md.0afe4b74.js
index 14900d8bfa..7f7e12677f 100644
--- a/assets/case_case4.md.2ed250b5.js
+++ b/assets/case_case4.md.0afe4b74.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":1692790731000}'),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":1692790817000}'),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.2ed250b5.lean.js b/assets/case_case4.md.0afe4b74.lean.js
similarity index 98%
rename from assets/case_case4.md.2ed250b5.lean.js
rename to assets/case_case4.md.0afe4b74.lean.js
index 14900d8bfa..7f7e12677f 100644
--- a/assets/case_case4.md.2ed250b5.lean.js
+++ b/assets/case_case4.md.0afe4b74.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":1692790731000}'),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":1692790817000}'),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.7a22ce54.js b/assets/case_case5.md.f1b49f30.js
similarity index 97%
rename from assets/case_case5.md.7a22ce54.js
rename to assets/case_case5.md.f1b49f30.js
index 8ba52a98fb..5cf3c73b67 100644
--- a/assets/case_case5.md.7a22ce54.js
+++ b/assets/case_case5.md.f1b49f30.js
@@ -1 +1 @@
-import{_ as a,v as e,b as t,R as s}from"./chunks/framework.70afa331.js";const v=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case5.md","filePath":"case/case5.md","lastUpdated":1692790731000}'),o={name:"case/case5.md"},n=s('
仓库 ​
https://github.com/spiritLHLS/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/spiritLHLS/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
Thanks ​
Base on https://github.com/spiritLHLS/pve
Base on https://docs.convoypanel.com/guide/deployment/#installation
Base on https://github.com/ConvoyPanel/panel
',12),l=[n];function i(r,c,p,h,d,m){return e(),t("div",null,l)}const y=a(o,[["render",i]]);export{v as __pageData,y as default};
+import{_ as a,v as e,b as t,R as s}from"./chunks/framework.70afa331.js";const v=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case5.md","filePath":"case/case5.md","lastUpdated":1692790817000}'),o={name:"case/case5.md"},n=s('
仓库 ​
https://github.com/spiritLHLS/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/spiritLHLS/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
Thanks ​
Base on https://github.com/spiritLHLS/pve
Base on https://docs.convoypanel.com/guide/deployment/#installation
Base on https://github.com/ConvoyPanel/panel
',12),l=[n];function i(r,c,p,h,d,m){return e(),t("div",null,l)}const y=a(o,[["render",i]]);export{v as __pageData,y as default};
diff --git a/assets/case_case5.md.7a22ce54.lean.js b/assets/case_case5.md.f1b49f30.lean.js
similarity index 97%
rename from assets/case_case5.md.7a22ce54.lean.js
rename to assets/case_case5.md.f1b49f30.lean.js
index 8ba52a98fb..5cf3c73b67 100644
--- a/assets/case_case5.md.7a22ce54.lean.js
+++ b/assets/case_case5.md.f1b49f30.lean.js
@@ -1 +1 @@
-import{_ as a,v as e,b as t,R as s}from"./chunks/framework.70afa331.js";const v=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case5.md","filePath":"case/case5.md","lastUpdated":1692790731000}'),o={name:"case/case5.md"},n=s('
仓库 ​
https://github.com/spiritLHLS/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/spiritLHLS/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
Thanks ​
Base on https://github.com/spiritLHLS/pve
Base on https://docs.convoypanel.com/guide/deployment/#installation
Base on https://github.com/ConvoyPanel/panel
',12),l=[n];function i(r,c,p,h,d,m){return e(),t("div",null,l)}const y=a(o,[["render",i]]);export{v as __pageData,y as default};
+import{_ as a,v as e,b as t,R as s}from"./chunks/framework.70afa331.js";const v=JSON.parse('{"title":"仓库","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"case/case5.md","filePath":"case/case5.md","lastUpdated":1692790817000}'),o={name:"case/case5.md"},n=s('
仓库 ​
https://github.com/spiritLHLS/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/spiritLHLS/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
Thanks ​
Base on https://github.com/spiritLHLS/pve
Base on https://docs.convoypanel.com/guide/deployment/#installation
Base on https://github.com/ConvoyPanel/panel
',12),l=[n];function i(r,c,p,h,d,m){return e(),t("div",null,l)}const y=a(o,[["render",i]]);export{v as __pageData,y as default};
diff --git a/assets/case_index.md.679de9f1.js b/assets/case_index.md.414be4de.js
similarity index 93%
rename from assets/case_index.md.679de9f1.js
rename to assets/case_index.md.414be4de.js
index 9801d1ed65..f8c47137cc 100644
--- a/assets/case_index.md.679de9f1.js
+++ b/assets/case_index.md.414be4de.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":1692790731000}'),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":1692790817000}'),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.679de9f1.lean.js b/assets/case_index.md.414be4de.lean.js
similarity index 93%
rename from assets/case_index.md.679de9f1.lean.js
rename to assets/case_index.md.414be4de.lean.js
index 9801d1ed65..f8c47137cc 100644
--- a/assets/case_index.md.679de9f1.lean.js
+++ b/assets/case_index.md.414be4de.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":1692790731000}'),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":1692790817000}'),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.1694974e.js b/assets/developer_index.md.1d79c597.js
similarity index 93%
rename from assets/developer_index.md.1694974e.js
rename to assets/developer_index.md.1d79c597.js
index db82a6d47c..215e45dc86 100644
--- a/assets/developer_index.md.1694974e.js
+++ b/assets/developer_index.md.1d79c597.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":1692790731000}'),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":1692790817000}'),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.1694974e.lean.js b/assets/developer_index.md.1d79c597.lean.js
similarity index 93%
rename from assets/developer_index.md.1694974e.lean.js
rename to assets/developer_index.md.1d79c597.lean.js
index db82a6d47c..215e45dc86 100644
--- a/assets/developer_index.md.1694974e.lean.js
+++ b/assets/developer_index.md.1d79c597.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":1692790731000}'),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":1692790817000}'),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.74377b58.js b/assets/developer_l10n.md.dfbce633.js
similarity index 90%
rename from assets/developer_l10n.md.74377b58.js
rename to assets/developer_l10n.md.dfbce633.js
index b98ea9ef18..c213d98f2f 100644
--- a/assets/developer_l10n.md.74377b58.js
+++ b/assets/developer_l10n.md.dfbce633.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":1692790731000}'),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":1692790817000}'),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.74377b58.lean.js b/assets/developer_l10n.md.dfbce633.lean.js
similarity index 90%
rename from assets/developer_l10n.md.74377b58.lean.js
rename to assets/developer_l10n.md.dfbce633.lean.js
index b98ea9ef18..c213d98f2f 100644
--- a/assets/developer_l10n.md.74377b58.lean.js
+++ b/assets/developer_l10n.md.dfbce633.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":1692790731000}'),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":1692790817000}'),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_index.md.48d4ebf1.js b/assets/en_US_developer_index.md.998350b8.js
similarity index 92%
rename from assets/en_US_developer_index.md.48d4ebf1.js
rename to assets/en_US_developer_index.md.998350b8.js
index cf444d12f7..23c729a02e 100644
--- a/assets/en_US_developer_index.md.48d4ebf1.js
+++ b/assets/en_US_developer_index.md.998350b8.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":1692790731000}'),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_US/developer/index.md","filePath":"en_US/developer/index.md","lastUpdated":1692790817000}'),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};
diff --git a/assets/en_US_developer_index.md.48d4ebf1.lean.js b/assets/en_US_developer_index.md.998350b8.lean.js
similarity index 92%
rename from assets/en_US_developer_index.md.48d4ebf1.lean.js
rename to assets/en_US_developer_index.md.998350b8.lean.js
index cf444d12f7..23c729a02e 100644
--- a/assets/en_US_developer_index.md.48d4ebf1.lean.js
+++ b/assets/en_US_developer_index.md.998350b8.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":1692790731000}'),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_US/developer/index.md","filePath":"en_US/developer/index.md","lastUpdated":1692790817000}'),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};
diff --git a/assets/en_US_developer_l10n.md.6d4e09b4.js b/assets/en_US_developer_l10n.md.0c4609b9.js
similarity index 95%
rename from assets/en_US_developer_l10n.md.6d4e09b4.js
rename to assets/en_US_developer_l10n.md.0c4609b9.js
index a1444c4f81..c5299afc71 100644
--- a/assets/en_US_developer_l10n.md.6d4e09b4.js
+++ b/assets/en_US_developer_l10n.md.0c4609b9.js
@@ -1 +1 @@
-import{_ as e,v as t,b as n,R as o}from"./chunks/framework.70afa331.js";const p=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/developer/l10n.md","filePath":"en_US/developer/l10n.md","lastUpdated":1692790731000}'),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};
+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":1692790817000}'),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.6d4e09b4.lean.js b/assets/en_US_developer_l10n.md.0c4609b9.lean.js
similarity index 95%
rename from assets/en_US_developer_l10n.md.6d4e09b4.lean.js
rename to assets/en_US_developer_l10n.md.0c4609b9.lean.js
index a1444c4f81..c5299afc71 100644
--- a/assets/en_US_developer_l10n.md.6d4e09b4.lean.js
+++ b/assets/en_US_developer_l10n.md.0c4609b9.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as n,R as o}from"./chunks/framework.70afa331.js";const p=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/developer/l10n.md","filePath":"en_US/developer/l10n.md","lastUpdated":1692790731000}'),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};
+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":1692790817000}'),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.bc126f99.js b/assets/en_US_guide_dashboard.md.a076f0f2.js
similarity index 98%
rename from assets/en_US_guide_dashboard.md.bc126f99.js
rename to assets/en_US_guide_dashboard.md.a076f0f2.js
index c0bd6c57ff..26a24a956f 100644
--- a/assets/en_US_guide_dashboard.md.bc126f99.js
+++ b/assets/en_US_guide_dashboard.md.a076f0f2.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a,R as r}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/dashboard.md","filePath":"en_US/guide/dashboard.md","lastUpdated":1692790731000}'),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};
+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":1692790817000}'),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.bc126f99.lean.js b/assets/en_US_guide_dashboard.md.a076f0f2.lean.js
similarity index 98%
rename from assets/en_US_guide_dashboard.md.bc126f99.lean.js
rename to assets/en_US_guide_dashboard.md.a076f0f2.lean.js
index c0bd6c57ff..26a24a956f 100644
--- a/assets/en_US_guide_dashboard.md.bc126f99.lean.js
+++ b/assets/en_US_guide_dashboard.md.a076f0f2.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a,R as r}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/dashboard.md","filePath":"en_US/guide/dashboard.md","lastUpdated":1692790731000}'),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};
+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":1692790817000}'),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.1a6c7b9b.js b/assets/en_US_guide_dashboardq.md.9a48881c.js
similarity index 85%
rename from assets/en_US_guide_dashboardq.md.1a6c7b9b.js
rename to assets/en_US_guide_dashboardq.md.9a48881c.js
index 208c3fdcda..3371eb4ddc 100644
--- a/assets/en_US_guide_dashboardq.md.1a6c7b9b.js
+++ b/assets/en_US_guide_dashboardq.md.9a48881c.js
@@ -1 +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_US/guide/dashboardq.md","filePath":"en_US/guide/dashboardq.md","lastUpdated":1692790731000}'),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};
+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":1692790817000}'),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.1a6c7b9b.lean.js b/assets/en_US_guide_dashboardq.md.9a48881c.lean.js
similarity index 85%
rename from assets/en_US_guide_dashboardq.md.1a6c7b9b.lean.js
rename to assets/en_US_guide_dashboardq.md.9a48881c.lean.js
index 208c3fdcda..3371eb4ddc 100644
--- a/assets/en_US_guide_dashboardq.md.1a6c7b9b.lean.js
+++ b/assets/en_US_guide_dashboardq.md.9a48881c.lean.js
@@ -1 +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_US/guide/dashboardq.md","filePath":"en_US/guide/dashboardq.md","lastUpdated":1692790731000}'),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};
+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":1692790817000}'),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_build.md.12ee0f20.js b/assets/en_US_guide_docker_build.md.ff848fff.js
similarity index 99%
rename from assets/en_US_guide_docker_build.md.12ee0f20.js
rename to assets/en_US_guide_docker_build.md.ff848fff.js
index 449a851714..757546b6e4 100644
--- a/assets/en_US_guide_docker_build.md.12ee0f20.js
+++ b/assets/en_US_guide_docker_build.md.ff848fff.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Introduction","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_build.md","filePath":"en_US/guide/docker_build.md","lastUpdated":1692790731000}'),o={name:"en_US/guide/docker_build.md"},t=e(`
Introduction ​
There are two methods of building
Setting Up Standalone ​
Download the Script
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
Run
./onedocker.sh name cpu memory password sshport startport endport system
Currently, the system only supports selecting Alpine or Debian, with Debian being the default choice.
Example ​
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
shell
./onedocker.sh test 1 512 123456 25000 34975 35000 debian
Deleting the test container
shell
docker rm -f test
+import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Introduction","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_build.md","filePath":"en_US/guide/docker_build.md","lastUpdated":1692790817000}'),o={name:"en_US/guide/docker_build.md"},t=e(`
Introduction ​
There are two methods of building
Setting Up Standalone ​
Download the Script
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
Run
./onedocker.sh name cpu memory password sshport startport endport system
Currently, the system only supports selecting Alpine or Debian, with Debian being the default choice.
Example ​
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
shell
./onedocker.sh test 1 512 123456 25000 34975 35000 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
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.
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.
Uninstall all Docker containers and images ​
shell
docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)
 rm -rf dclog
diff --git a/assets/en_US_guide_docker_build.md.12ee0f20.lean.js b/assets/en_US_guide_docker_build.md.ff848fff.lean.js
similarity index 99%
rename from assets/en_US_guide_docker_build.md.12ee0f20.lean.js
rename to assets/en_US_guide_docker_build.md.ff848fff.lean.js
index 449a851714..757546b6e4 100644
--- a/assets/en_US_guide_docker_build.md.12ee0f20.lean.js
+++ b/assets/en_US_guide_docker_build.md.ff848fff.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Introduction","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_build.md","filePath":"en_US/guide/docker_build.md","lastUpdated":1692790731000}'),o={name:"en_US/guide/docker_build.md"},t=e(`
Introduction ​
There are two methods of building
Setting Up Standalone ​
Download the Script
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
Run
./onedocker.sh name cpu memory password sshport startport endport system
Currently, the system only supports selecting Alpine or Debian, with Debian being the default choice.
Example ​
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
shell
./onedocker.sh test 1 512 123456 25000 34975 35000 debian
Deleting the test container
shell
docker rm -f test
+import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Introduction","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_build.md","filePath":"en_US/guide/docker_build.md","lastUpdated":1692790817000}'),o={name:"en_US/guide/docker_build.md"},t=e(`
Introduction ​
There are two methods of building
Setting Up Standalone ​
Download the Script
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
Run
./onedocker.sh name cpu memory password sshport startport endport system
Currently, the system only supports selecting Alpine or Debian, with Debian being the default choice.
Example ​
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
shell
./onedocker.sh test 1 512 123456 25000 34975 35000 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
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.
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.
Uninstall all Docker containers and images ​
shell
docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)
 rm -rf dclog
diff --git a/assets/en_US_guide_docker_custom.md.3c1974cd.js b/assets/en_US_guide_docker_custom.md.14448289.js
similarity index 99%
rename from assets/en_US_guide_docker_custom.md.3c1974cd.js
rename to assets/en_US_guide_docker_custom.md.14448289.js
index df43b39bd2..255e30beed 100644
--- a/assets/en_US_guide_docker_custom.md.3c1974cd.js
+++ b/assets/en_US_guide_docker_custom.md.14448289.js
@@ -1,4 +1,4 @@
-import{_ as e,v as s,b as o,R as a}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Script for One-Click Installation of Certain Containers using Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_custom.md","filePath":"en_US/guide/docker_custom.md","lastUpdated":1692790731000}'),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.
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.
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 e,v as s,b as o,R as a}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Script for One-Click Installation of Certain Containers using Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_custom.md","filePath":"en_US/guide/docker_custom.md","lastUpdated":1692790817000}'),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.
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.
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.3c1974cd.lean.js b/assets/en_US_guide_docker_custom.md.14448289.lean.js
similarity index 99%
rename from assets/en_US_guide_docker_custom.md.3c1974cd.lean.js
rename to assets/en_US_guide_docker_custom.md.14448289.lean.js
index df43b39bd2..255e30beed 100644
--- a/assets/en_US_guide_docker_custom.md.3c1974cd.lean.js
+++ b/assets/en_US_guide_docker_custom.md.14448289.lean.js
@@ -1,4 +1,4 @@
-import{_ as e,v as s,b as o,R as a}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Script for One-Click Installation of Certain Containers using Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_custom.md","filePath":"en_US/guide/docker_custom.md","lastUpdated":1692790731000}'),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.
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.
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 e,v as s,b as o,R as a}from"./chunks/framework.70afa331.js";const y=JSON.parse('{"title":"Script for One-Click Installation of Certain Containers using Docker","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_custom.md","filePath":"en_US/guide/docker_custom.md","lastUpdated":1692790817000}'),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.
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.
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_install.md.5ff8b457.js b/assets/en_US_guide_docker_install.md.254a332a.js
similarity index 98%
rename from assets/en_US_guide_docker_install.md.5ff8b457.js
rename to assets/en_US_guide_docker_install.md.254a332a.js
index 049ae36c1d..aefa1c15f7 100644
--- a/assets/en_US_guide_docker_install.md.5ff8b457.js
+++ b/assets/en_US_guide_docker_install.md.254a332a.js
@@ -1 +1 @@
-import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_install.md","filePath":"en_US/guide/docker_install.md","lastUpdated":1692790731000}'),o={name:"en_US/guide/docker_install.md"},l=n('
Preface ​
Support for running Docker virtualization on various systems, including Linux, Android, and Windows.
Environment Setup ​
  • Check the environment
  • Install Docker and other prerequisite components
  • Download some default configuration scripts required by default
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
Setting Up Virtual Memory ​
WARNING
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
',12),t=[l];function p(r,c,i,d,C,m){return a(),e("div",null,t)}const h=s(o,[["render",p]]);export{u as __pageData,h as default};
+import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_install.md","filePath":"en_US/guide/docker_install.md","lastUpdated":1692790817000}'),o={name:"en_US/guide/docker_install.md"},l=n('
Preface ​
Support for running Docker virtualization on various systems, including Linux, Android, and Windows.
Environment Setup ​
  • Check the environment
  • Install Docker and other prerequisite components
  • Download some default configuration scripts required by default
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
Setting Up Virtual Memory ​
WARNING
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
',12),t=[l];function p(r,c,i,d,C,m){return a(),e("div",null,t)}const h=s(o,[["render",p]]);export{u as __pageData,h as default};
diff --git a/assets/en_US_guide_docker_install.md.5ff8b457.lean.js b/assets/en_US_guide_docker_install.md.254a332a.lean.js
similarity index 98%
rename from assets/en_US_guide_docker_install.md.5ff8b457.lean.js
rename to assets/en_US_guide_docker_install.md.254a332a.lean.js
index 049ae36c1d..aefa1c15f7 100644
--- a/assets/en_US_guide_docker_install.md.5ff8b457.lean.js
+++ b/assets/en_US_guide_docker_install.md.254a332a.lean.js
@@ -1 +1 @@
-import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_install.md","filePath":"en_US/guide/docker_install.md","lastUpdated":1692790731000}'),o={name:"en_US/guide/docker_install.md"},l=n('
Preface ​
Support for running Docker virtualization on various systems, including Linux, Android, and Windows.
Environment Setup ​
  • Check the environment
  • Install Docker and other prerequisite components
  • Download some default configuration scripts required by default
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
Setting Up Virtual Memory ​
WARNING
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
',12),t=[l];function p(r,c,i,d,C,m){return a(),e("div",null,t)}const h=s(o,[["render",p]]);export{u as __pageData,h as default};
+import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_install.md","filePath":"en_US/guide/docker_install.md","lastUpdated":1692790817000}'),o={name:"en_US/guide/docker_install.md"},l=n('
Preface ​
Support for running Docker virtualization on various systems, including Linux, Android, and Windows.
Environment Setup ​
  • Check the environment
  • Install Docker and other prerequisite components
  • Download some default configuration scripts required by default
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
Setting Up Virtual Memory ​
WARNING
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
',12),t=[l];function p(r,c,i,d,C,m){return a(),e("div",null,t)}const h=s(o,[["render",p]]);export{u as __pageData,h as default};
diff --git a/assets/en_US_guide_docker_precheck.md.9124e805.js b/assets/en_US_guide_docker_precheck.md.9cd84cef.js
similarity index 98%
rename from assets/en_US_guide_docker_precheck.md.9124e805.js
rename to assets/en_US_guide_docker_precheck.md.9cd84cef.js
index 7ddf087847..358fd2dde6 100644
--- a/assets/en_US_guide_docker_precheck.md.9124e805.js
+++ b/assets/en_US_guide_docker_precheck.md.9cd84cef.js
@@ -1 +1 @@
-import{_ as e,v as t,b as i,R as r}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"Introduction","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/docker_precheck.md","filePath":"en_US/guide/docker_precheck.md","lastUpdated":1692790731000}'),n={name:"en_US/guide/docker_precheck.md"},o=r('
Introduction ​
The following is an introduction to the non-customized sections. Please ensure that you don't confuse them with the customized parts.
Project Highlights ​
This project involves bulk or individual provisioning of NAT servers using Docker containers.
The default operating system used is Debian. Each container comes with one external SSH port and 25 consistent internal and external ports.
The containers created by default are non-privileged and do not establish communication between the Docker daemon on the host and the containers. As a result, containers nested within Docker virtualized NAT servers on the host will not function.
Due to CPU and memory limitations set on the host without utilizing cgroup drivers within containers, any server testing scripts run inside containers to assess available resources will be ineffective. The displayed resources will reflect those of the host.
Since the majority of cloud servers do not enable the 'pquota' option for the XFS file system, the default configuration involves sharing the host's hard drive, thus preventing the restriction of individual container disk sizes.
Configuration Requirements ​
The system should have Docker installed to be operational. As long as the network can connect to GitHub's raw interface, it can be used. Hardware configuration requirements are minimal, as long as they are adequate; a spare 3GB of hard disk space is sufficient.
It is recommended to increase the available SWAP virtual memory prior to provisioning NAT servers to prevent potential host performance issues due to sudden memory spikes. Link
PS: If hardware resources are somewhat limited and more restrictions are necessary, including configuration of individual IPv6 addresses and disk size limitations, consider utilizing LXD to create batch LXC virtualized containers. Link
PS: If hardware resources are abundant and ample, consider using Proxmox Virtual Environment (PVE) to provision batch KVM virtualized machines. Link
Please note that the original formatting has been preserved and enclosed within and for your convenience during copying. No character escaping has been applied.
',14),a=[o];function s(c,d,h,l,u,p){return t(),i("div",null,a)}const f=e(n,[["render",s]]);export{g as __pageData,f as default};
+import{_ as e,v as t,b as i,R as r}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"Introduction","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/docker_precheck.md","filePath":"en_US/guide/docker_precheck.md","lastUpdated":1692790817000}'),n={name:"en_US/guide/docker_precheck.md"},o=r('
Introduction ​
The following is an introduction to the non-customized sections. Please ensure that you don't confuse them with the customized parts.
Project Highlights ​
This project involves bulk or individual provisioning of NAT servers using Docker containers.
The default operating system used is Debian. Each container comes with one external SSH port and 25 consistent internal and external ports.
The containers created by default are non-privileged and do not establish communication between the Docker daemon on the host and the containers. As a result, containers nested within Docker virtualized NAT servers on the host will not function.
Due to CPU and memory limitations set on the host without utilizing cgroup drivers within containers, any server testing scripts run inside containers to assess available resources will be ineffective. The displayed resources will reflect those of the host.
Since the majority of cloud servers do not enable the 'pquota' option for the XFS file system, the default configuration involves sharing the host's hard drive, thus preventing the restriction of individual container disk sizes.
Configuration Requirements ​
The system should have Docker installed to be operational. As long as the network can connect to GitHub's raw interface, it can be used. Hardware configuration requirements are minimal, as long as they are adequate; a spare 3GB of hard disk space is sufficient.
It is recommended to increase the available SWAP virtual memory prior to provisioning NAT servers to prevent potential host performance issues due to sudden memory spikes. Link
PS: If hardware resources are somewhat limited and more restrictions are necessary, including configuration of individual IPv6 addresses and disk size limitations, consider utilizing LXD to create batch LXC virtualized containers. Link
PS: If hardware resources are abundant and ample, consider using Proxmox Virtual Environment (PVE) to provision batch KVM virtualized machines. Link
Please note that the original formatting has been preserved and enclosed within and for your convenience during copying. No character escaping has been applied.
',14),a=[o];function s(c,d,h,l,u,p){return t(),i("div",null,a)}const f=e(n,[["render",s]]);export{g as __pageData,f as default};
diff --git a/assets/en_US_guide_docker_precheck.md.9124e805.lean.js b/assets/en_US_guide_docker_precheck.md.9cd84cef.lean.js
similarity index 98%
rename from assets/en_US_guide_docker_precheck.md.9124e805.lean.js
rename to assets/en_US_guide_docker_precheck.md.9cd84cef.lean.js
index 7ddf087847..358fd2dde6 100644
--- a/assets/en_US_guide_docker_precheck.md.9124e805.lean.js
+++ b/assets/en_US_guide_docker_precheck.md.9cd84cef.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as i,R as r}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"Introduction","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/docker_precheck.md","filePath":"en_US/guide/docker_precheck.md","lastUpdated":1692790731000}'),n={name:"en_US/guide/docker_precheck.md"},o=r('
Introduction ​
The following is an introduction to the non-customized sections. Please ensure that you don't confuse them with the customized parts.
Project Highlights ​
This project involves bulk or individual provisioning of NAT servers using Docker containers.
The default operating system used is Debian. Each container comes with one external SSH port and 25 consistent internal and external ports.
The containers created by default are non-privileged and do not establish communication between the Docker daemon on the host and the containers. As a result, containers nested within Docker virtualized NAT servers on the host will not function.
Due to CPU and memory limitations set on the host without utilizing cgroup drivers within containers, any server testing scripts run inside containers to assess available resources will be ineffective. The displayed resources will reflect those of the host.
Since the majority of cloud servers do not enable the 'pquota' option for the XFS file system, the default configuration involves sharing the host's hard drive, thus preventing the restriction of individual container disk sizes.
Configuration Requirements ​
The system should have Docker installed to be operational. As long as the network can connect to GitHub's raw interface, it can be used. Hardware configuration requirements are minimal, as long as they are adequate; a spare 3GB of hard disk space is sufficient.
It is recommended to increase the available SWAP virtual memory prior to provisioning NAT servers to prevent potential host performance issues due to sudden memory spikes. Link
PS: If hardware resources are somewhat limited and more restrictions are necessary, including configuration of individual IPv6 addresses and disk size limitations, consider utilizing LXD to create batch LXC virtualized containers. Link
PS: If hardware resources are abundant and ample, consider using Proxmox Virtual Environment (PVE) to provision batch KVM virtualized machines. Link
Please note that the original formatting has been preserved and enclosed within and for your convenience during copying. No character escaping has been applied.
',14),a=[o];function s(c,d,h,l,u,p){return t(),i("div",null,a)}const f=e(n,[["render",s]]);export{g as __pageData,f as default};
+import{_ as e,v as t,b as i,R as r}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"Introduction","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/docker_precheck.md","filePath":"en_US/guide/docker_precheck.md","lastUpdated":1692790817000}'),n={name:"en_US/guide/docker_precheck.md"},o=r('
Introduction ​
The following is an introduction to the non-customized sections. Please ensure that you don't confuse them with the customized parts.
Project Highlights ​
This project involves bulk or individual provisioning of NAT servers using Docker containers.
The default operating system used is Debian. Each container comes with one external SSH port and 25 consistent internal and external ports.
The containers created by default are non-privileged and do not establish communication between the Docker daemon on the host and the containers. As a result, containers nested within Docker virtualized NAT servers on the host will not function.
Due to CPU and memory limitations set on the host without utilizing cgroup drivers within containers, any server testing scripts run inside containers to assess available resources will be ineffective. The displayed resources will reflect those of the host.
Since the majority of cloud servers do not enable the 'pquota' option for the XFS file system, the default configuration involves sharing the host's hard drive, thus preventing the restriction of individual container disk sizes.
Configuration Requirements ​
The system should have Docker installed to be operational. As long as the network can connect to GitHub's raw interface, it can be used. Hardware configuration requirements are minimal, as long as they are adequate; a spare 3GB of hard disk space is sufficient.
It is recommended to increase the available SWAP virtual memory prior to provisioning NAT servers to prevent potential host performance issues due to sudden memory spikes. Link
PS: If hardware resources are somewhat limited and more restrictions are necessary, including configuration of individual IPv6 addresses and disk size limitations, consider utilizing LXD to create batch LXC virtualized containers. Link
PS: If hardware resources are abundant and ample, consider using Proxmox Virtual Environment (PVE) to provision batch KVM virtualized machines. Link
Please note that the original formatting has been preserved and enclosed within and for your convenience during copying. No character escaping has been applied.
',14),a=[o];function s(c,d,h,l,u,p){return t(),i("div",null,a)}const f=e(n,[["render",s]]);export{g as __pageData,f as default};
diff --git a/assets/en_US_guide_docker_qa.md.d42fce53.js b/assets/en_US_guide_docker_qa.md.a5c8f8d2.js
similarity index 98%
rename from assets/en_US_guide_docker_qa.md.d42fce53.js
rename to assets/en_US_guide_docker_qa.md.a5c8f8d2.js
index 1fa2045276..c0620453d4 100644
--- a/assets/en_US_guide_docker_qa.md.d42fce53.js
+++ b/assets/en_US_guide_docker_qa.md.a5c8f8d2.js
@@ -1 +1 @@
-import{_ as e,v as a,b as s,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"Solve the puzzle","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_qa.md","filePath":"en_US/guide/docker_qa.md","lastUpdated":1692790731000}'),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};
+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":1692790817000}'),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.d42fce53.lean.js b/assets/en_US_guide_docker_qa.md.a5c8f8d2.lean.js
similarity index 98%
rename from assets/en_US_guide_docker_qa.md.d42fce53.lean.js
rename to assets/en_US_guide_docker_qa.md.a5c8f8d2.lean.js
index 1fa2045276..c0620453d4 100644
--- a/assets/en_US_guide_docker_qa.md.d42fce53.lean.js
+++ b/assets/en_US_guide_docker_qa.md.a5c8f8d2.lean.js
@@ -1 +1 @@
-import{_ as e,v as a,b as s,R as n}from"./chunks/framework.70afa331.js";const h=JSON.parse('{"title":"Solve the puzzle","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/docker_qa.md","filePath":"en_US/guide/docker_qa.md","lastUpdated":1692790731000}'),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};
+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":1692790817000}'),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.16ca5b2f.js b/assets/en_US_guide_docker_thanks.md.658a434c.js
similarity index 97%
rename from assets/en_US_guide_docker_thanks.md.16ca5b2f.js
rename to assets/en_US_guide_docker_thanks.md.658a434c.js
index b7f71a54ce..4e3c896d49 100644
--- a/assets/en_US_guide_docker_thanks.md.16ca5b2f.js
+++ b/assets/en_US_guide_docker_thanks.md.658a434c.js
@@ -1 +1 @@
-import{_ as e,v as r,b as a,R as t}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/docker_thanks.md","filePath":"en_US/guide/docker_thanks.md","lastUpdated":1692790731000}'),o={name:"en_US/guide/docker_thanks.md"},n=t('
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
',15),c=[n];function h(i,p,s,l,d,g){return r(),a("div",null,c)}const f=e(o,[["render",h]]);export{u as __pageData,f as default};
+import{_ as e,v as r,b as a,R as t}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/docker_thanks.md","filePath":"en_US/guide/docker_thanks.md","lastUpdated":1692790817000}'),o={name:"en_US/guide/docker_thanks.md"},n=t('
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
',15),c=[n];function h(i,p,s,l,d,g){return r(),a("div",null,c)}const f=e(o,[["render",h]]);export{u as __pageData,f as default};
diff --git a/assets/en_US_guide_docker_thanks.md.16ca5b2f.lean.js b/assets/en_US_guide_docker_thanks.md.658a434c.lean.js
similarity index 97%
rename from assets/en_US_guide_docker_thanks.md.16ca5b2f.lean.js
rename to assets/en_US_guide_docker_thanks.md.658a434c.lean.js
index b7f71a54ce..4e3c896d49 100644
--- a/assets/en_US_guide_docker_thanks.md.16ca5b2f.lean.js
+++ b/assets/en_US_guide_docker_thanks.md.658a434c.lean.js
@@ -1 +1 @@
-import{_ as e,v as r,b as a,R as t}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/docker_thanks.md","filePath":"en_US/guide/docker_thanks.md","lastUpdated":1692790731000}'),o={name:"en_US/guide/docker_thanks.md"},n=t('
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
',15),c=[n];function h(i,p,s,l,d,g){return r(),a("div",null,c)}const f=e(o,[["render",h]]);export{u as __pageData,f as default};
+import{_ as e,v as r,b as a,R as t}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/docker_thanks.md","filePath":"en_US/guide/docker_thanks.md","lastUpdated":1692790817000}'),o={name:"en_US/guide/docker_thanks.md"},n=t('
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
',15),c=[n];function h(i,p,s,l,d,g){return r(),a("div",null,c)}const f=e(o,[["render",h]]);export{u as __pageData,f as default};
diff --git a/assets/en_US_guide_lxd_custom.md.90c3be0d.js b/assets/en_US_guide_lxd_custom.md.35af8f37.js
similarity index 84%
rename from assets/en_US_guide_lxd_custom.md.90c3be0d.js
rename to assets/en_US_guide_lxd_custom.md.35af8f37.js
index 939a535d2c..8dbda2b897 100644
--- a/assets/en_US_guide_lxd_custom.md.90c3be0d.js
+++ b/assets/en_US_guide_lxd_custom.md.35af8f37.js
@@ -1 +1 @@
-import{_ as t,v as e,b as s}from"./chunks/framework.70afa331.js";const p=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/lxd_custom.md","filePath":"en_US/guide/lxd_custom.md","lastUpdated":1692790731000}'),a={name:"en_US/guide/lxd_custom.md"};function d(_,o,r,n,c,i){return e(),s("div")}const u=t(a,[["render",d]]);export{p as __pageData,u as default};
+import{_ as t,v as e,b as s}from"./chunks/framework.70afa331.js";const p=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/lxd_custom.md","filePath":"en_US/guide/lxd_custom.md","lastUpdated":1692790817000}'),a={name:"en_US/guide/lxd_custom.md"};function d(_,o,r,n,c,i){return e(),s("div")}const u=t(a,[["render",d]]);export{p as __pageData,u as default};
diff --git a/assets/en_US_guide_lxd_custom.md.90c3be0d.lean.js b/assets/en_US_guide_lxd_custom.md.35af8f37.lean.js
similarity index 84%
rename from assets/en_US_guide_lxd_custom.md.90c3be0d.lean.js
rename to assets/en_US_guide_lxd_custom.md.35af8f37.lean.js
index 939a535d2c..8dbda2b897 100644
--- a/assets/en_US_guide_lxd_custom.md.90c3be0d.lean.js
+++ b/assets/en_US_guide_lxd_custom.md.35af8f37.lean.js
@@ -1 +1 @@
-import{_ as t,v as e,b as s}from"./chunks/framework.70afa331.js";const p=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/lxd_custom.md","filePath":"en_US/guide/lxd_custom.md","lastUpdated":1692790731000}'),a={name:"en_US/guide/lxd_custom.md"};function d(_,o,r,n,c,i){return e(),s("div")}const u=t(a,[["render",d]]);export{p as __pageData,u as default};
+import{_ as t,v as e,b as s}from"./chunks/framework.70afa331.js";const p=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/lxd_custom.md","filePath":"en_US/guide/lxd_custom.md","lastUpdated":1692790817000}'),a={name:"en_US/guide/lxd_custom.md"};function d(_,o,r,n,c,i){return e(),s("div")}const u=t(a,[["render",d]]);export{p as __pageData,u as default};
diff --git a/assets/en_US_guide_lxd_extra_config.md.bc824dfa.js b/assets/en_US_guide_lxd_extra_config.md.6e3eba87.js
similarity index 99%
rename from assets/en_US_guide_lxd_extra_config.md.bc824dfa.js
rename to assets/en_US_guide_lxd_extra_config.md.6e3eba87.js
index 26be181426..a6309a853d 100644
--- a/assets/en_US_guide_lxd_extra_config.md.bc824dfa.js
+++ b/assets/en_US_guide_lxd_extra_config.md.6e3eba87.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":1692790731000}'),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
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
Delete all IPV6 mapped rules
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_US/guide/lxd_extra_config.md","filePath":"en_US/guide/lxd_extra_config.md","lastUpdated":1692790817000}'),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
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
Delete all IPV6 mapped rules
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.bc824dfa.lean.js b/assets/en_US_guide_lxd_extra_config.md.6e3eba87.lean.js
similarity index 99%
rename from assets/en_US_guide_lxd_extra_config.md.bc824dfa.lean.js
rename to assets/en_US_guide_lxd_extra_config.md.6e3eba87.lean.js
index 26be181426..a6309a853d 100644
--- a/assets/en_US_guide_lxd_extra_config.md.bc824dfa.lean.js
+++ b/assets/en_US_guide_lxd_extra_config.md.6e3eba87.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":1692790731000}'),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
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
Delete all IPV6 mapped rules
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_US/guide/lxd_extra_config.md","filePath":"en_US/guide/lxd_extra_config.md","lastUpdated":1692790817000}'),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
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
Delete all IPV6 mapped rules
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.0880bdc1.js b/assets/en_US_guide_lxd_install.md.c8eeea85.js
similarity index 99%
rename from assets/en_US_guide_lxd_install.md.0880bdc1.js
rename to assets/en_US_guide_lxd_install.md.c8eeea85.js
index fd9d299ca3..07081c125f 100644
--- a/assets/en_US_guide_lxd_install.md.0880bdc1.js
+++ b/assets/en_US_guide_lxd_install.md.c8eeea85.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const C=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":1692790731000}'),t={name:"en_US/guide/lxd_install.md"},o=n(`
LXD Installation Guide ​
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 C=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":1692790817000}'),t={name:"en_US/guide/lxd_install.md"},o=n(`
LXD Installation Guide ​
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.0880bdc1.lean.js b/assets/en_US_guide_lxd_install.md.c8eeea85.lean.js
similarity index 99%
rename from assets/en_US_guide_lxd_install.md.0880bdc1.lean.js
rename to assets/en_US_guide_lxd_install.md.c8eeea85.lean.js
index fd9d299ca3..07081c125f 100644
--- a/assets/en_US_guide_lxd_install.md.0880bdc1.lean.js
+++ b/assets/en_US_guide_lxd_install.md.c8eeea85.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as n}from"./chunks/framework.70afa331.js";const C=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":1692790731000}'),t={name:"en_US/guide/lxd_install.md"},o=n(`
LXD Installation Guide ​
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 C=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":1692790817000}'),t={name:"en_US/guide/lxd_install.md"},o=n(`
LXD Installation Guide ​
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.907b6ddd.js b/assets/en_US_guide_lxd_lxc.md.f0e22353.js
similarity index 99%
rename from assets/en_US_guide_lxd_lxc.md.907b6ddd.js
rename to assets/en_US_guide_lxd_lxc.md.f0e22353.js
index 6fa07348a7..27b0639b19 100644
--- a/assets/en_US_guide_lxd_lxc.md.907b6ddd.js
+++ b/assets/en_US_guide_lxd_lxc.md.f0e22353.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"LXC virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/lxd_lxc.md","filePath":"en_US/guide/lxd_lxc.md","lastUpdated":1692790731000}'),o={name:"en_US/guide/lxd_lxc.md"},l=e(`
LXC virtualization ​
Generate only one NAT server ​
  • Generate only one NAT server, with customizable restrictions on all content.
Downloading the boot script is NOT REQUIRED, if you have used the command to install LXD with one click, the corresponding boot script will be downloaded automatically, so you don't need to download the script again.
Command:
shell
curl -L https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
How it's used ​
. /buildone.sh Chick name 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 chicken, 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
  • Note that they are all lowercase letters + numbers of the combination of their own to try, if the search is not the system will automatically exit the script
  • Version number can be with English decimal point, in order to adapt to the alpine version number has been supported.
  • Note that some systems may not have cgroups loaded, so testing system resources in the container will show the system resources of the host, which are actually constrained, similar to Docker.
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
Chicken'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 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 e}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":1692790817000}'),o={name:"en_US/guide/lxd_lxc.md"},l=e(`
LXC virtualization ​
Generate only one NAT server ​
  • Generate only one NAT server, with customizable restrictions on all content.
Downloading the boot script is NOT REQUIRED, if you have used the command to install LXD with one click, the corresponding boot script will be downloaded automatically, so you don't need to download the script again.
Command:
shell
curl -L https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
How it's used ​
. /buildone.sh Chick name 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 chicken, 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
  • Note that they are all lowercase letters + numbers of the combination of their own to try, if the search is not the system will automatically exit the script
  • Version number can be with English decimal point, in order to adapt to the alpine version number has been supported.
  • Note that some systems may not have cgroups loaded, so testing system resources in the container will show the system resources of the host, which are actually constrained, similar to Docker.
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
Chicken'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 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.907b6ddd.lean.js b/assets/en_US_guide_lxd_lxc.md.f0e22353.lean.js
similarity index 99%
rename from assets/en_US_guide_lxd_lxc.md.907b6ddd.lean.js
rename to assets/en_US_guide_lxd_lxc.md.f0e22353.lean.js
index 6fa07348a7..27b0639b19 100644
--- a/assets/en_US_guide_lxd_lxc.md.907b6ddd.lean.js
+++ b/assets/en_US_guide_lxd_lxc.md.f0e22353.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as n,R as e}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"LXC virtualization","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/lxd_lxc.md","filePath":"en_US/guide/lxd_lxc.md","lastUpdated":1692790731000}'),o={name:"en_US/guide/lxd_lxc.md"},l=e(`
LXC virtualization ​
Generate only one NAT server ​
  • Generate only one NAT server, with customizable restrictions on all content.
Downloading the boot script is NOT REQUIRED, if you have used the command to install LXD with one click, the corresponding boot script will be downloaded automatically, so you don't need to download the script again.
Command:
shell
curl -L https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
How it's used ​
. /buildone.sh Chick name 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 chicken, 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
  • Note that they are all lowercase letters + numbers of the combination of their own to try, if the search is not the system will automatically exit the script
  • Version number can be with English decimal point, in order to adapt to the alpine version number has been supported.
  • Note that some systems may not have cgroups loaded, so testing system resources in the container will show the system resources of the host, which are actually constrained, similar to Docker.
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
Chicken'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 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 e}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":1692790817000}'),o={name:"en_US/guide/lxd_lxc.md"},l=e(`
LXC virtualization ​
Generate only one NAT server ​
  • Generate only one NAT server, with customizable restrictions on all content.
Downloading the boot script is NOT REQUIRED, if you have used the command to install LXD with one click, the corresponding boot script will be downloaded automatically, so you don't need to download the script again.
Command:
shell
curl -L https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
How it's used ​
. /buildone.sh Chick name 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 chicken, 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
  • Note that they are all lowercase letters + numbers of the combination of their own to try, if the search is not the system will automatically exit the script
  • Version number can be with English decimal point, in order to adapt to the alpine version number has been supported.
  • Note that some systems may not have cgroups loaded, so testing system resources in the container will show the system resources of the host, which are actually constrained, similar to Docker.
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
Chicken'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 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_precheck.md.d15155ac.js b/assets/en_US_guide_lxd_precheck.md.e3837f3a.js
similarity index 98%
rename from assets/en_US_guide_lxd_precheck.md.d15155ac.js
rename to assets/en_US_guide_lxd_precheck.md.e3837f3a.js
index 261db96687..79a52b1036 100644
--- a/assets/en_US_guide_lxd_precheck.md.d15155ac.js
+++ b/assets/en_US_guide_lxd_precheck.md.e3837f3a.js
@@ -1 +1 @@
-import{_ as e,v as t,b as o,R as n}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/lxd_precheck.md","filePath":"en_US/guide/lxd_precheck.md","lastUpdated":1692790731000}'),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!
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.
  • 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)
',13),s=[r];function i(d,c,l,p,h,u){return t(),o("div",null,s)}const b=e(a,[["render",i]]);export{f as __pageData,b as default};
+import{_ as e,v as t,b as o,R as n}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/lxd_precheck.md","filePath":"en_US/guide/lxd_precheck.md","lastUpdated":1692790817000}'),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!
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.
  • 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)
',13),s=[r];function i(d,c,l,p,h,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.d15155ac.lean.js b/assets/en_US_guide_lxd_precheck.md.e3837f3a.lean.js
similarity index 98%
rename from assets/en_US_guide_lxd_precheck.md.d15155ac.lean.js
rename to assets/en_US_guide_lxd_precheck.md.e3837f3a.lean.js
index 261db96687..79a52b1036 100644
--- a/assets/en_US_guide_lxd_precheck.md.d15155ac.lean.js
+++ b/assets/en_US_guide_lxd_precheck.md.e3837f3a.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as o,R as n}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/lxd_precheck.md","filePath":"en_US/guide/lxd_precheck.md","lastUpdated":1692790731000}'),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!
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.
  • 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)
',13),s=[r];function i(d,c,l,p,h,u){return t(),o("div",null,s)}const b=e(a,[["render",i]]);export{f as __pageData,b as default};
+import{_ as e,v as t,b as o,R as n}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"Preface","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/lxd_precheck.md","filePath":"en_US/guide/lxd_precheck.md","lastUpdated":1692790817000}'),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!
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.
  • 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)
',13),s=[r];function i(d,c,l,p,h,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.9ee5d99d.js b/assets/en_US_guide_lxd_qa.md.86772169.js
similarity index 98%
rename from assets/en_US_guide_lxd_qa.md.9ee5d99d.js
rename to assets/en_US_guide_lxd_qa.md.86772169.js
index 4b965e730d..76528f9f7e 100644
--- a/assets/en_US_guide_lxd_qa.md.9ee5d99d.js
+++ b/assets/en_US_guide_lxd_qa.md.86772169.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":"en_US/guide/lxd_qa.md","filePath":"en_US/guide/lxd_qa.md","lastUpdated":1692790731000}'),n={name:"en_US/guide/lxd_qa.md"},o=t('
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.\n\n## What to do if you open centos7 and find that CGroupV1 is not supported?\n\nEnable CGroup V1: To enable CGroup V1 on an Ubuntu system, you need to edit the kernel boot parameters.\n\nPlease note that before changing kernel boot parameters, make sure to backup important data and settings to prevent unexpected problems.\n\nEdit the ```/etc/default/grub`` file and add ``cgroup_enable=memory`` to the end of the parameters in ``GRUB_CMDLINE_LINUX_DEFAULT``.
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash cgroup_enable=memory"
Save the file and run the following command to update the GRUB boot.\n\n```bash\nsudo 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),l=[o];function p(r,i,c,d,h,u){return a(),s("div",null,l)}const b=e(n,[["render",p]]);export{m as __pageData,b 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":"en_US/guide/lxd_qa.md","filePath":"en_US/guide/lxd_qa.md","lastUpdated":1692790817000}'),n={name:"en_US/guide/lxd_qa.md"},o=t('
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.\n\n## What to do if you open centos7 and find that CGroupV1 is not supported?\n\nEnable CGroup V1: To enable CGroup V1 on an Ubuntu system, you need to edit the kernel boot parameters.\n\nPlease note that before changing kernel boot parameters, make sure to backup important data and settings to prevent unexpected problems.\n\nEdit the ```/etc/default/grub`` file and add ``cgroup_enable=memory`` to the end of the parameters in ``GRUB_CMDLINE_LINUX_DEFAULT``.
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash cgroup_enable=memory"
Save the file and run the following command to update the GRUB boot.\n\n```bash\nsudo 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),l=[o];function p(r,i,c,d,h,u){return a(),s("div",null,l)}const b=e(n,[["render",p]]);export{m as __pageData,b as default};
diff --git a/assets/en_US_guide_lxd_qa.md.9ee5d99d.lean.js b/assets/en_US_guide_lxd_qa.md.86772169.lean.js
similarity index 98%
rename from assets/en_US_guide_lxd_qa.md.9ee5d99d.lean.js
rename to assets/en_US_guide_lxd_qa.md.86772169.lean.js
index 4b965e730d..76528f9f7e 100644
--- a/assets/en_US_guide_lxd_qa.md.9ee5d99d.lean.js
+++ b/assets/en_US_guide_lxd_qa.md.86772169.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":"en_US/guide/lxd_qa.md","filePath":"en_US/guide/lxd_qa.md","lastUpdated":1692790731000}'),n={name:"en_US/guide/lxd_qa.md"},o=t('
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.\n\n## What to do if you open centos7 and find that CGroupV1 is not supported?\n\nEnable CGroup V1: To enable CGroup V1 on an Ubuntu system, you need to edit the kernel boot parameters.\n\nPlease note that before changing kernel boot parameters, make sure to backup important data and settings to prevent unexpected problems.\n\nEdit the ```/etc/default/grub`` file and add ``cgroup_enable=memory`` to the end of the parameters in ``GRUB_CMDLINE_LINUX_DEFAULT``.
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash cgroup_enable=memory"
Save the file and run the following command to update the GRUB boot.\n\n```bash\nsudo 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),l=[o];function p(r,i,c,d,h,u){return a(),s("div",null,l)}const b=e(n,[["render",p]]);export{m as __pageData,b 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":"en_US/guide/lxd_qa.md","filePath":"en_US/guide/lxd_qa.md","lastUpdated":1692790817000}'),n={name:"en_US/guide/lxd_qa.md"},o=t('
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.\n\n## What to do if you open centos7 and find that CGroupV1 is not supported?\n\nEnable CGroup V1: To enable CGroup V1 on an Ubuntu system, you need to edit the kernel boot parameters.\n\nPlease note that before changing kernel boot parameters, make sure to backup important data and settings to prevent unexpected problems.\n\nEdit the ```/etc/default/grub`` file and add ``cgroup_enable=memory`` to the end of the parameters in ``GRUB_CMDLINE_LINUX_DEFAULT``.
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash cgroup_enable=memory"
Save the file and run the following command to update the GRUB boot.\n\n```bash\nsudo 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),l=[o];function p(r,i,c,d,h,u){return a(),s("div",null,l)}const b=e(n,[["render",p]]);export{m as __pageData,b as default};
diff --git a/assets/en_US_guide_lxd_thanks.md.cbe6b4e1.js b/assets/en_US_guide_lxd_thanks.md.447a90be.js
similarity index 94%
rename from assets/en_US_guide_lxd_thanks.md.cbe6b4e1.js
rename to assets/en_US_guide_lxd_thanks.md.447a90be.js
index 588dca8f65..fa12b48387 100644
--- a/assets/en_US_guide_lxd_thanks.md.cbe6b4e1.js
+++ b/assets/en_US_guide_lxd_thanks.md.447a90be.js
@@ -1 +1 @@
-import{_ as e,v as t,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":1692790731000}'),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
Thank @Ella-Alinda @fscarmen for providing guidance.
',10),o=[s];function i(c,l,d,p,h,u){return t(),r("div",null,o)}const x=e(a,[["render",i]]);export{f as __pageData,x as default};
+import{_ as e,v as t,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":1692790817000}'),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
Thank @Ella-Alinda @fscarmen for providing guidance.
',10),o=[s];function i(c,l,d,p,h,u){return t(),r("div",null,o)}const x=e(a,[["render",i]]);export{f as __pageData,x as default};
diff --git a/assets/en_US_guide_lxd_thanks.md.cbe6b4e1.lean.js b/assets/en_US_guide_lxd_thanks.md.447a90be.lean.js
similarity index 94%
rename from assets/en_US_guide_lxd_thanks.md.cbe6b4e1.lean.js
rename to assets/en_US_guide_lxd_thanks.md.447a90be.lean.js
index 588dca8f65..fa12b48387 100644
--- a/assets/en_US_guide_lxd_thanks.md.cbe6b4e1.lean.js
+++ b/assets/en_US_guide_lxd_thanks.md.447a90be.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,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":1692790731000}'),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
Thank @Ella-Alinda @fscarmen for providing guidance.
',10),o=[s];function i(c,l,d,p,h,u){return t(),r("div",null,o)}const x=e(a,[["render",i]]);export{f as __pageData,x as default};
+import{_ as e,v as t,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":1692790817000}'),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
Thank @Ella-Alinda @fscarmen for providing guidance.
',10),o=[s];function i(c,l,d,p,h,u){return t(),r("div",null,o)}const x=e(a,[["render",i]]);export{f as __pageData,x as default};
diff --git a/assets/en_US_guide_pve_custom.md.f1529c25.js b/assets/en_US_guide_pve_custom.md.a164918b.js
similarity index 98%
rename from assets/en_US_guide_pve_custom.md.f1529c25.js
rename to assets/en_US_guide_pve_custom.md.a164918b.js
index f758dccb8b..6c8378d168 100644
--- a/assets/en_US_guide_pve_custom.md.f1529c25.js
+++ b/assets/en_US_guide_pve_custom.md.a164918b.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":1692790731000}'),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_US/guide/pve_custom.md","filePath":"en_US/guide/pve_custom.md","lastUpdated":1692790817000}'),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
 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.f1529c25.lean.js b/assets/en_US_guide_pve_custom.md.a164918b.lean.js
similarity index 98%
rename from assets/en_US_guide_pve_custom.md.f1529c25.lean.js
rename to assets/en_US_guide_pve_custom.md.a164918b.lean.js
index f758dccb8b..6c8378d168 100644
--- a/assets/en_US_guide_pve_custom.md.f1529c25.lean.js
+++ b/assets/en_US_guide_pve_custom.md.a164918b.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":1692790731000}'),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_US/guide/pve_custom.md","filePath":"en_US/guide/pve_custom.md","lastUpdated":1692790817000}'),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
 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_install.md.11d1a883.js b/assets/en_US_guide_pve_install.md.e8fa40cc.js
similarity index 99%
rename from assets/en_US_guide_pve_install.md.11d1a883.js
rename to assets/en_US_guide_pve_install.md.e8fa40cc.js
index d8a89540b5..81085d831a 100644
--- a/assets/en_US_guide_pve_install.md.11d1a883.js
+++ b/assets/en_US_guide_pve_install.md.e8fa40cc.js
@@ -1 +1 @@
-import{_ as e,v as t,b as o,R as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"PVE Body Installation","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/pve_install.md","filePath":"en_US/guide/pve_install.md","lastUpdated":1692790731000}'),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
I recommend debian11 instead of debian12, because the latter is a stable version but I don't know if there are any undiscovered bugs, and the debian11 installation is currently more stable.
  • 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.
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.
  • 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
',27),i=[n];function l(r,c,p,d,h,u){return t(),o("div",null,i)}const y=e(a,[["render",l]]);export{f as __pageData,y as default};
+import{_ as e,v as t,b as o,R as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"PVE Body Installation","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/pve_install.md","filePath":"en_US/guide/pve_install.md","lastUpdated":1692790817000}'),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
I recommend debian11 instead of debian12, because the latter is a stable version but I don't know if there are any undiscovered bugs, and the debian11 installation is currently more stable.
  • 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.
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.
  • 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
',27),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.11d1a883.lean.js b/assets/en_US_guide_pve_install.md.e8fa40cc.lean.js
similarity index 99%
rename from assets/en_US_guide_pve_install.md.11d1a883.lean.js
rename to assets/en_US_guide_pve_install.md.e8fa40cc.lean.js
index d8a89540b5..81085d831a 100644
--- a/assets/en_US_guide_pve_install.md.11d1a883.lean.js
+++ b/assets/en_US_guide_pve_install.md.e8fa40cc.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as o,R as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"PVE Body Installation","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/pve_install.md","filePath":"en_US/guide/pve_install.md","lastUpdated":1692790731000}'),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
I recommend debian11 instead of debian12, because the latter is a stable version but I don't know if there are any undiscovered bugs, and the debian11 installation is currently more stable.
  • 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.
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.
  • 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
',27),i=[n];function l(r,c,p,d,h,u){return t(),o("div",null,i)}const y=e(a,[["render",l]]);export{f as __pageData,y as default};
+import{_ as e,v as t,b as o,R as s}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"PVE Body Installation","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/pve_install.md","filePath":"en_US/guide/pve_install.md","lastUpdated":1692790817000}'),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
I recommend debian11 instead of debian12, because the latter is a stable version but I don't know if there are any undiscovered bugs, and the debian11 installation is currently more stable.
  • 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.
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.
  • 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
',27),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.2b3a8c29.js b/assets/en_US_guide_pve_kvm.md.3763e6db.js
similarity index 99%
rename from assets/en_US_guide_pve_kvm.md.2b3a8c29.js
rename to assets/en_US_guide_pve_kvm.md.3763e6db.js
index 5a6117d565..7fb0e38da9 100644
--- a/assets/en_US_guide_pve_kvm.md.2b3a8c29.js
+++ b/assets/en_US_guide_pve_kvm.md.3763e6db.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const u=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":1692790731000}'),n={name:"en_US/guide/pve_kvm.md"},l=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.
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
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
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.
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)
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 Examples ​
  • Stop VM
  • Delete VM
  • Delete port mapping
  • Restart network
  • Delete log files
shell
qm stop 102
+import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const u=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":1692790817000}'),n={name:"en_US/guide/pve_kvm.md"},l=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.
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
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
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.
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)
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 Examples ​
  • Stop VM
  • Delete VM
  • Delete port mapping
  • Restart network
  • Delete log files
shell
qm stop 102
 qm destroy 102
 iptables -t nat -F
 iptables -t filter -F
diff --git a/assets/en_US_guide_pve_kvm.md.2b3a8c29.lean.js b/assets/en_US_guide_pve_kvm.md.3763e6db.lean.js
similarity index 99%
rename from assets/en_US_guide_pve_kvm.md.2b3a8c29.lean.js
rename to assets/en_US_guide_pve_kvm.md.3763e6db.lean.js
index 5a6117d565..7fb0e38da9 100644
--- a/assets/en_US_guide_pve_kvm.md.2b3a8c29.lean.js
+++ b/assets/en_US_guide_pve_kvm.md.3763e6db.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const u=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":1692790731000}'),n={name:"en_US/guide/pve_kvm.md"},l=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.
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
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
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.
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)
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 Examples ​
  • Stop VM
  • Delete VM
  • Delete port mapping
  • Restart network
  • Delete log files
shell
qm stop 102
+import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const u=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":1692790817000}'),n={name:"en_US/guide/pve_kvm.md"},l=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.
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
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
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.
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)
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 Examples ​
  • Stop VM
  • Delete VM
  • Delete port mapping
  • Restart network
  • Delete log files
shell
qm stop 102
 qm destroy 102
 iptables -t nat -F
 iptables -t filter -F
diff --git a/assets/en_US_guide_pve_lxc.md.e98dda75.js b/assets/en_US_guide_pve_lxc.md.d61b2e43.js
similarity index 99%
rename from assets/en_US_guide_pve_lxc.md.e98dda75.js
rename to assets/en_US_guide_pve_lxc.md.d61b2e43.js
index 8407647be0..2481a0ba25 100644
--- a/assets/en_US_guide_pve_lxc.md.e98dda75.js
+++ b/assets/en_US_guide_pve_lxc.md.d61b2e43.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const D=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":1692790731000}'),n={name:"en_US/guide/pve_lxc.md"},l=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 ​
Download the script
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
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.
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 Examples ​
  • Stop CT
  • Delete CT
  • Delete Port Mapping
  • Restart Network
  • Delete Log Files
shell
pct stop 102
+import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const D=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":1692790817000}'),n={name:"en_US/guide/pve_lxc.md"},l=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 ​
Download the script
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
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.
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 Examples ​
  • Stop CT
  • Delete CT
  • Delete Port Mapping
  • Restart Network
  • Delete Log Files
shell
pct stop 102
 pct destroy 102
 rm -rf ct102
 iptables -t nat -F
diff --git a/assets/en_US_guide_pve_lxc.md.e98dda75.lean.js b/assets/en_US_guide_pve_lxc.md.d61b2e43.lean.js
similarity index 99%
rename from assets/en_US_guide_pve_lxc.md.e98dda75.lean.js
rename to assets/en_US_guide_pve_lxc.md.d61b2e43.lean.js
index 8407647be0..2481a0ba25 100644
--- a/assets/en_US_guide_pve_lxc.md.e98dda75.lean.js
+++ b/assets/en_US_guide_pve_lxc.md.d61b2e43.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const D=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":1692790731000}'),n={name:"en_US/guide/pve_lxc.md"},l=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 ​
Download the script
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
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.
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 Examples ​
  • Stop CT
  • Delete CT
  • Delete Port Mapping
  • Restart Network
  • Delete Log Files
shell
pct stop 102
+import{_ as s,v as a,b as e,R as t}from"./chunks/framework.70afa331.js";const D=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":1692790817000}'),n={name:"en_US/guide/pve_lxc.md"},l=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 ​
Download the script
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh
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.
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 Examples ​
  • Stop CT
  • Delete CT
  • Delete Port Mapping
  • Restart Network
  • Delete Log Files
shell
pct stop 102
 pct destroy 102
 rm -rf ct102
 iptables -t nat -F
diff --git a/assets/en_US_guide_pve_precheck.md.891461ea.js b/assets/en_US_guide_pve_precheck.md.3cc0f2d8.js
similarity index 98%
rename from assets/en_US_guide_pve_precheck.md.891461ea.js
rename to assets/en_US_guide_pve_precheck.md.3cc0f2d8.js
index f19c615df2..d5c99e85f9 100644
--- a/assets/en_US_guide_pve_precheck.md.891461ea.js
+++ b/assets/en_US_guide_pve_precheck.md.3cc0f2d8.js
@@ -1 +1 @@
-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":1692790731000}'),o={name:"en_US/guide/pve_precheck.md"},n=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!
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)
This project is only adapted to Debian system (non-Debian can not be installed through the APT source, the official only gave the Debian image, other systems can only use ISO installation)
  • 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
WARNING
I'm not sure if I'm going to be able to do this, but I'm going to be able to do it in a few minutes.
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*


',24),r=[n];function i(l,p,c,h,u,d){return t(),s("div",null,r)}const b=e(o,[["render",i]]);export{y as __pageData,b as default};
+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":1692790817000}'),o={name:"en_US/guide/pve_precheck.md"},n=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!
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)
This project is only adapted to Debian system (non-Debian can not be installed through the APT source, the official only gave the Debian image, other systems can only use ISO installation)
  • 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
WARNING
I'm not sure if I'm going to be able to do this, but I'm going to be able to do it in a few minutes.
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*


',24),r=[n];function i(l,p,c,h,u,d){return t(),s("div",null,r)}const b=e(o,[["render",i]]);export{y as __pageData,b as default};
diff --git a/assets/en_US_guide_pve_precheck.md.891461ea.lean.js b/assets/en_US_guide_pve_precheck.md.3cc0f2d8.lean.js
similarity index 98%
rename from assets/en_US_guide_pve_precheck.md.891461ea.lean.js
rename to assets/en_US_guide_pve_precheck.md.3cc0f2d8.lean.js
index f19c615df2..d5c99e85f9 100644
--- a/assets/en_US_guide_pve_precheck.md.891461ea.lean.js
+++ b/assets/en_US_guide_pve_precheck.md.3cc0f2d8.lean.js
@@ -1 +1 @@
-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":1692790731000}'),o={name:"en_US/guide/pve_precheck.md"},n=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!
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)
This project is only adapted to Debian system (non-Debian can not be installed through the APT source, the official only gave the Debian image, other systems can only use ISO installation)
  • 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
WARNING
I'm not sure if I'm going to be able to do this, but I'm going to be able to do it in a few minutes.
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*


',24),r=[n];function i(l,p,c,h,u,d){return t(),s("div",null,r)}const b=e(o,[["render",i]]);export{y as __pageData,b as default};
+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":1692790817000}'),o={name:"en_US/guide/pve_precheck.md"},n=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!
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)
This project is only adapted to Debian system (non-Debian can not be installed through the APT source, the official only gave the Debian image, other systems can only use ISO installation)
  • 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
WARNING
I'm not sure if I'm going to be able to do this, but I'm going to be able to do it in a few minutes.
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*


',24),r=[n];function i(l,p,c,h,u,d){return t(),s("div",null,r)}const b=e(o,[["render",i]]);export{y as __pageData,b as default};
diff --git a/assets/en_US_guide_pve_qa.md.aeb26265.js b/assets/en_US_guide_pve_qa.md.56520221.js
similarity index 99%
rename from assets/en_US_guide_pve_qa.md.aeb26265.js
rename to assets/en_US_guide_pve_qa.md.56520221.js
index 43119a7005..96d2a14631 100644
--- a/assets/en_US_guide_pve_qa.md.aeb26265.js
+++ b/assets/en_US_guide_pve_qa.md.56520221.js
@@ -1,4 +1,4 @@
-import{_ as e,v as a,b as s,R as t}from"./chunks/framework.70afa331.js";const u=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":1692790731000}'),n={name:"en_US/guide/pve_qa.md"},r=t(`
Solve the puzzle ​
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 u=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":1692790817000}'),n={name:"en_US/guide/pve_qa.md"},r=t(`
Solve the puzzle ​
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.aeb26265.lean.js b/assets/en_US_guide_pve_qa.md.56520221.lean.js
similarity index 99%
rename from assets/en_US_guide_pve_qa.md.aeb26265.lean.js
rename to assets/en_US_guide_pve_qa.md.56520221.lean.js
index 43119a7005..96d2a14631 100644
--- a/assets/en_US_guide_pve_qa.md.aeb26265.lean.js
+++ b/assets/en_US_guide_pve_qa.md.56520221.lean.js
@@ -1,4 +1,4 @@
-import{_ as e,v as a,b as s,R as t}from"./chunks/framework.70afa331.js";const u=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":1692790731000}'),n={name:"en_US/guide/pve_qa.md"},r=t(`
Solve the puzzle ​
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 u=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":1692790817000}'),n={name:"en_US/guide/pve_qa.md"},r=t(`
Solve the puzzle ​
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_thanks.md.6f541899.js b/assets/en_US_guide_pve_thanks.md.47f61a62.js
similarity index 94%
rename from assets/en_US_guide_pve_thanks.md.6f541899.js
rename to assets/en_US_guide_pve_thanks.md.47f61a62.js
index 7f7d6e0813..e19539b707 100644
--- a/assets/en_US_guide_pve_thanks.md.6f541899.js
+++ b/assets/en_US_guide_pve_thanks.md.47f61a62.js
@@ -1 +1 @@
-import{_ as e,v as r,b as t,R as a}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/pve_thanks.md","filePath":"en_US/guide/pve_thanks.md","lastUpdated":1692790731000}'),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
Thank @Ella-Alinda for providing PVE guidance.
',14),p=[n];function s(h,i,l,m,c,g){return r(),t("div",null,p)}const u=e(o,[["render",s]]);export{d as __pageData,u as default};
+import{_ as e,v as r,b as t,R as a}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/pve_thanks.md","filePath":"en_US/guide/pve_thanks.md","lastUpdated":1692790817000}'),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
Thank @Ella-Alinda for providing PVE guidance.
',14),p=[n];function s(h,i,l,m,c,g){return r(),t("div",null,p)}const u=e(o,[["render",s]]);export{d as __pageData,u as default};
diff --git a/assets/en_US_guide_pve_thanks.md.6f541899.lean.js b/assets/en_US_guide_pve_thanks.md.47f61a62.lean.js
similarity index 94%
rename from assets/en_US_guide_pve_thanks.md.6f541899.lean.js
rename to assets/en_US_guide_pve_thanks.md.47f61a62.lean.js
index 7f7d6e0813..e19539b707 100644
--- a/assets/en_US_guide_pve_thanks.md.6f541899.lean.js
+++ b/assets/en_US_guide_pve_thanks.md.47f61a62.lean.js
@@ -1 +1 @@
-import{_ as e,v as r,b as t,R as a}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/pve_thanks.md","filePath":"en_US/guide/pve_thanks.md","lastUpdated":1692790731000}'),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
Thank @Ella-Alinda for providing PVE guidance.
',14),p=[n];function s(h,i,l,m,c,g){return r(),t("div",null,p)}const u=e(o,[["render",s]]);export{d as __pageData,u as default};
+import{_ as e,v as r,b as t,R as a}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/pve_thanks.md","filePath":"en_US/guide/pve_thanks.md","lastUpdated":1692790817000}'),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
Thank @Ella-Alinda for providing PVE guidance.
',14),p=[n];function s(h,i,l,m,c,g){return r(),t("div",null,p)}const u=e(o,[["render",s]]);export{d as __pageData,u as default};
diff --git a/assets/en_US_index.md.22c03377.js b/assets/en_US_index.md.1d0529d7.js
similarity index 96%
rename from assets/en_US_index.md.22c03377.js
rename to assets/en_US_index.md.1d0529d7.js
index 91b0e3b152..c729f47533 100644
--- a/assets/en_US_index.md.22c03377.js
+++ b/assets/en_US_index.md.1d0529d7.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"One Click Virtualization","titleTemplate":"Open source, easy to use server virtualization project","description":"","frontmatter":{"layout":"home","title":"One Click Virtualization","titleTemplate":"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":1692790731000}'),i={name:"en_US/index.md"};function n(s,r,o,l,d,c){return t(),a("div")}const p=e(i,[["render",n]]);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":"One Click Virtualization","titleTemplate":"Open source, easy to use server virtualization project","description":"","frontmatter":{"layout":"home","title":"One Click Virtualization","titleTemplate":"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":1692790817000}'),i={name:"en_US/index.md"};function n(s,r,o,l,d,c){return t(),a("div")}const p=e(i,[["render",n]]);export{m as __pageData,p as default};
diff --git a/assets/en_US_index.md.22c03377.lean.js b/assets/en_US_index.md.1d0529d7.lean.js
similarity index 96%
rename from assets/en_US_index.md.22c03377.lean.js
rename to assets/en_US_index.md.1d0529d7.lean.js
index 91b0e3b152..c729f47533 100644
--- a/assets/en_US_index.md.22c03377.lean.js
+++ b/assets/en_US_index.md.1d0529d7.lean.js
@@ -1 +1 @@
-import{_ as e,v as t,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"One Click Virtualization","titleTemplate":"Open source, easy to use server virtualization project","description":"","frontmatter":{"layout":"home","title":"One Click Virtualization","titleTemplate":"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":1692790731000}'),i={name:"en_US/index.md"};function n(s,r,o,l,d,c){return t(),a("div")}const p=e(i,[["render",n]]);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":"One Click Virtualization","titleTemplate":"Open source, easy to use server virtualization project","description":"","frontmatter":{"layout":"home","title":"One Click Virtualization","titleTemplate":"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":1692790817000}'),i={name:"en_US/index.md"};function n(s,r,o,l,d,c){return t(),a("div")}const p=e(i,[["render",n]]);export{m as __pageData,p as default};
diff --git a/assets/guide_dashboard.md.59b64dc4.js b/assets/guide_dashboard.md.0824d560.js
similarity index 98%
rename from assets/guide_dashboard.md.59b64dc4.js
rename to assets/guide_dashboard.md.0824d560.js
index 807e369919..093f78a06e 100644
--- a/assets/guide_dashboard.md.59b64dc4.js
+++ b/assets/guide_dashboard.md.0824d560.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":{},"headers":[],"relativePath":"guide/dashboard.md","filePath":"guide/dashboard.md","lastUpdated":1692790731000}'),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":{},"headers":[],"relativePath":"guide/dashboard.md","filePath":"guide/dashboard.md","lastUpdated":1692790817000}'),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.59b64dc4.lean.js b/assets/guide_dashboard.md.0824d560.lean.js
similarity index 98%
rename from assets/guide_dashboard.md.59b64dc4.lean.js
rename to assets/guide_dashboard.md.0824d560.lean.js
index 807e369919..093f78a06e 100644
--- a/assets/guide_dashboard.md.59b64dc4.lean.js
+++ b/assets/guide_dashboard.md.0824d560.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":{},"headers":[],"relativePath":"guide/dashboard.md","filePath":"guide/dashboard.md","lastUpdated":1692790731000}'),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":{},"headers":[],"relativePath":"guide/dashboard.md","filePath":"guide/dashboard.md","lastUpdated":1692790817000}'),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.c07acab3.js b/assets/guide_dashboardq.md.d32966c2.js
similarity index 92%
rename from assets/guide_dashboardq.md.c07acab3.js
rename to assets/guide_dashboardq.md.d32966c2.js
index 0051502a8f..7150873f7b 100644
--- a/assets/guide_dashboardq.md.c07acab3.js
+++ b/assets/guide_dashboardq.md.d32966c2.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":1692790731000}'),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":1692790817000}'),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.c07acab3.lean.js b/assets/guide_dashboardq.md.d32966c2.lean.js
similarity index 92%
rename from assets/guide_dashboardq.md.c07acab3.lean.js
rename to assets/guide_dashboardq.md.d32966c2.lean.js
index 0051502a8f..7150873f7b 100644
--- a/assets/guide_dashboardq.md.c07acab3.lean.js
+++ b/assets/guide_dashboardq.md.d32966c2.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":1692790731000}'),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":1692790817000}'),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.bae54da2.js b/assets/guide_docker_build.md.010451eb.js
similarity index 99%
rename from assets/guide_docker_build.md.bae54da2.js
rename to assets/guide_docker_build.md.010451eb.js
index be4e48b302..f309e3db37 100644
--- a/assets/guide_docker_build.md.bae54da2.js
+++ b/assets/guide_docker_build.md.010451eb.js
@@ -1,3 +1,3 @@
-import{_ as s,v as a,b as l,R as o}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"前言","description":"","frontmatter":{},"headers":[],"relativePath":"guide/docker_build.md","filePath":"guide/docker_build.md","lastUpdated":1692790731000}'),n={name:"guide/docker_build.md"},p=o(`
前言 ​
两种开设方式
单独开设 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
国内
shell
curl -L https://ghproxy.com/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 system
目前system仅支持选择alpine或debian，默认是debian
示例 ​
以下为开设的示例容器的信息：
属性值
容器名字test
SSH登录的用户名root
SSH登录的密码123456
CPU核数1
内存大小512MB
SSH端口25000
内外网映射端口一致的区间34975到35000
系统debian
shell
./onedocker.sh test 1 512 123456 25000 34975 35000 debian
删除示例
shell
docker rm -f test
+import{_ as s,v as a,b as l,R as o}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"前言","description":"","frontmatter":{},"headers":[],"relativePath":"guide/docker_build.md","filePath":"guide/docker_build.md","lastUpdated":1692790817000}'),n={name:"guide/docker_build.md"},p=o(`
前言 ​
两种开设方式
单独开设 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
国内
shell
curl -L https://ghproxy.com/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 system
目前system仅支持选择alpine或debian，默认是debian
示例 ​
以下为开设的示例容器的信息：
属性值
容器名字test
SSH登录的用户名root
SSH登录的密码123456
CPU核数1
内存大小512MB
SSH端口25000
内外网映射端口一致的区间34975到35000
系统debian
shell
./onedocker.sh test 1 512 123456 25000 34975 35000 debian
删除示例
shell
docker rm -f test
 rm -rf test
 ls
进入示例
shell
docker exec -it test /bin/bash
要退出容器就执行exit退出。
查询信息 ​
shell
cat 容器名字
输出格式
容器名字 SSH端口 登陆的root密码 核数 内存 外网端口起 外网端口止
批量开设 ​
  • 批量多次运行继承配置生成
  • 生成多个时为避免SSH连接中断建议在screen中执行
国际
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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
查询批量开设的信息 ​
shell
cat dclog
输出格式
容器名字 SSH端口 登陆的root密码 核数 内存 外网端口起 外网端口止
一行一个容器对应的信息
卸载所有docker容器和镜像 ​
shell
docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)
`,37),e=[p];function t(c,r,C,d,i,y){return a(),l("div",null,e)}const A=s(n,[["render",t]]);export{D as __pageData,A as default};
diff --git a/assets/guide_docker_build.md.bae54da2.lean.js b/assets/guide_docker_build.md.010451eb.lean.js
similarity index 99%
rename from assets/guide_docker_build.md.bae54da2.lean.js
rename to assets/guide_docker_build.md.010451eb.lean.js
index be4e48b302..f309e3db37 100644
--- a/assets/guide_docker_build.md.bae54da2.lean.js
+++ b/assets/guide_docker_build.md.010451eb.lean.js
@@ -1,3 +1,3 @@
-import{_ as s,v as a,b as l,R as o}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"前言","description":"","frontmatter":{},"headers":[],"relativePath":"guide/docker_build.md","filePath":"guide/docker_build.md","lastUpdated":1692790731000}'),n={name:"guide/docker_build.md"},p=o(`
前言 ​
两种开设方式
单独开设 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
国内
shell
curl -L https://ghproxy.com/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 system
目前system仅支持选择alpine或debian，默认是debian
示例 ​
以下为开设的示例容器的信息：
属性值
容器名字test
SSH登录的用户名root
SSH登录的密码123456
CPU核数1
内存大小512MB
SSH端口25000
内外网映射端口一致的区间34975到35000
系统debian
shell
./onedocker.sh test 1 512 123456 25000 34975 35000 debian
删除示例
shell
docker rm -f test
+import{_ as s,v as a,b as l,R as o}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"前言","description":"","frontmatter":{},"headers":[],"relativePath":"guide/docker_build.md","filePath":"guide/docker_build.md","lastUpdated":1692790817000}'),n={name:"guide/docker_build.md"},p=o(`
前言 ​
两种开设方式
单独开设 ​
下载脚本
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
国内
shell
curl -L https://ghproxy.com/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 system
目前system仅支持选择alpine或debian，默认是debian
示例 ​
以下为开设的示例容器的信息：
属性值
容器名字test
SSH登录的用户名root
SSH登录的密码123456
CPU核数1
内存大小512MB
SSH端口25000
内外网映射端口一致的区间34975到35000
系统debian
shell
./onedocker.sh test 1 512 123456 25000 34975 35000 debian
删除示例
shell
docker rm -f test
 rm -rf test
 ls
进入示例
shell
docker exec -it test /bin/bash
要退出容器就执行exit退出。
查询信息 ​
shell
cat 容器名字
输出格式
容器名字 SSH端口 登陆的root密码 核数 内存 外网端口起 外网端口止
批量开设 ​
  • 批量多次运行继承配置生成
  • 生成多个时为避免SSH连接中断建议在screen中执行
国际
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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh
查询批量开设的信息 ​
shell
cat dclog
输出格式
容器名字 SSH端口 登陆的root密码 核数 内存 外网端口起 外网端口止
一行一个容器对应的信息
卸载所有docker容器和镜像 ​
shell
docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)
`,37),e=[p];function t(c,r,C,d,i,y){return a(),l("div",null,e)}const A=s(n,[["render",t]]);export{D as __pageData,A as default};
diff --git a/assets/guide_docker_custom.md.6db0b9c6.js b/assets/guide_docker_custom.md.4dbcc1c0.js
similarity index 99%
rename from assets/guide_docker_custom.md.6db0b9c6.js
rename to assets/guide_docker_custom.md.4dbcc1c0.js
index 8ce1c4953a..d714567bba 100644
--- a/assets/guide_docker_custom.md.6db0b9c6.js
+++ b/assets/guide_docker_custom.md.4dbcc1c0.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as o,R as l}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"使用Docker一键安装某些容器的脚本","description":"","frontmatter":{},"headers":[],"relativePath":"guide/docker_custom.md","filePath":"guide/docker_custom.md","lastUpdated":1692790731000}'),p={name:"guide/docker_custom.md"},n=l(`
使用Docker一键安装某些容器的脚本 ​
每个容器都有对应的配置要求，自行查看，内存不够的用这个开设虚拟内存补足也行
一键开设Android系统的容器 ​
  • 自定义安卓版本
  • 自动创建带校验的web网站
  • 自动进行nginx安装和反向代理的配置，可选择是否绑定域名，默认回车不绑定使用80端口
  • 无需考虑宿主机是否支持嵌套虚拟化
  • 支持x86_64和ARM架构
宿主机的配置至少要有1核2G内存15G硬盘，否则开设可能会导致宿主机卡死
安卓版本越新占用越大，以上的配置要求是最低版本安卓的配置要求 (个人测试到 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://ghproxy.com/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 D=JSON.parse('{"title":"使用Docker一键安装某些容器的脚本","description":"","frontmatter":{},"headers":[],"relativePath":"guide/docker_custom.md","filePath":"guide/docker_custom.md","lastUpdated":1692790817000}'),p={name:"guide/docker_custom.md"},n=l(`
使用Docker一键安装某些容器的脚本 ​
每个容器都有对应的配置要求，自行查看，内存不够的用这个开设虚拟内存补足也行
一键开设Android系统的容器 ​
  • 自定义安卓版本
  • 自动创建带校验的web网站
  • 自动进行nginx安装和反向代理的配置，可选择是否绑定域名，默认回车不绑定使用80端口
  • 无需考虑宿主机是否支持嵌套虚拟化
  • 支持x86_64和ARM架构
宿主机的配置至少要有1核2G内存15G硬盘，否则开设可能会导致宿主机卡死
安卓版本越新占用越大，以上的配置要求是最低版本安卓的配置要求 (个人测试到 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://ghproxy.com/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
 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
diff --git a/assets/guide_docker_custom.md.6db0b9c6.lean.js b/assets/guide_docker_custom.md.4dbcc1c0.lean.js
similarity index 99%
rename from assets/guide_docker_custom.md.6db0b9c6.lean.js
rename to assets/guide_docker_custom.md.4dbcc1c0.lean.js
index 8ce1c4953a..d714567bba 100644
--- a/assets/guide_docker_custom.md.6db0b9c6.lean.js
+++ b/assets/guide_docker_custom.md.4dbcc1c0.lean.js
@@ -1,4 +1,4 @@
-import{_ as s,v as a,b as o,R as l}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"使用Docker一键安装某些容器的脚本","description":"","frontmatter":{},"headers":[],"relativePath":"guide/docker_custom.md","filePath":"guide/docker_custom.md","lastUpdated":1692790731000}'),p={name:"guide/docker_custom.md"},n=l(`
使用Docker一键安装某些容器的脚本 ​
每个容器都有对应的配置要求，自行查看，内存不够的用这个开设虚拟内存补足也行
一键开设Android系统的容器 ​
  • 自定义安卓版本
  • 自动创建带校验的web网站
  • 自动进行nginx安装和反向代理的配置，可选择是否绑定域名，默认回车不绑定使用80端口
  • 无需考虑宿主机是否支持嵌套虚拟化
  • 支持x86_64和ARM架构
宿主机的配置至少要有1核2G内存15G硬盘，否则开设可能会导致宿主机卡死
安卓版本越新占用越大，以上的配置要求是最低版本安卓的配置要求 (个人测试到 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://ghproxy.com/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 D=JSON.parse('{"title":"使用Docker一键安装某些容器的脚本","description":"","frontmatter":{},"headers":[],"relativePath":"guide/docker_custom.md","filePath":"guide/docker_custom.md","lastUpdated":1692790817000}'),p={name:"guide/docker_custom.md"},n=l(`
使用Docker一键安装某些容器的脚本 ​
每个容器都有对应的配置要求，自行查看，内存不够的用这个开设虚拟内存补足也行
一键开设Android系统的容器 ​
  • 自定义安卓版本
  • 自动创建带校验的web网站
  • 自动进行nginx安装和反向代理的配置，可选择是否绑定域名，默认回车不绑定使用80端口
  • 无需考虑宿主机是否支持嵌套虚拟化
  • 支持x86_64和ARM架构
宿主机的配置至少要有1核2G内存15G硬盘，否则开设可能会导致宿主机卡死
安卓版本越新占用越大，以上的配置要求是最低版本安卓的配置要求 (个人测试到 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://ghproxy.com/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
 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
diff --git a/assets/guide_docker_install.md.899b8e80.js b/assets/guide_docker_install.md.0b7efdda.js
similarity index 99%
rename from assets/guide_docker_install.md.899b8e80.js
rename to assets/guide_docker_install.md.0b7efdda.js
index 382c80e031..b7c04a4a00 100644
--- a/assets/guide_docker_install.md.899b8e80.js
+++ b/assets/guide_docker_install.md.0b7efdda.js
@@ -1 +1 @@
-import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker_install.md","filePath":"guide/docker_install.md","lastUpdated":1692790731000}'),o={name:"guide/docker_install.md"},n=p('
前言 ​
支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统
环境预设 ​
  • 检测环境
  • 安装docker和其他预制组件
  • 下载默认需要的一些配置脚本
国际
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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
开设虚拟内存 ​
WARNING
内存开点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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
',16),e=[n];function t(c,r,C,i,y,d){return a(),l("div",null,e)}const h=s(o,[["render",t]]);export{D as __pageData,h as default};
+import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker_install.md","filePath":"guide/docker_install.md","lastUpdated":1692790817000}'),o={name:"guide/docker_install.md"},n=p('
前言 ​
支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统
环境预设 ​
  • 检测环境
  • 安装docker和其他预制组件
  • 下载默认需要的一些配置脚本
国际
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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
开设虚拟内存 ​
WARNING
内存开点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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
',16),e=[n];function t(c,r,C,i,y,d){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.899b8e80.lean.js b/assets/guide_docker_install.md.0b7efdda.lean.js
similarity index 99%
rename from assets/guide_docker_install.md.899b8e80.lean.js
rename to assets/guide_docker_install.md.0b7efdda.lean.js
index 382c80e031..b7c04a4a00 100644
--- a/assets/guide_docker_install.md.899b8e80.lean.js
+++ b/assets/guide_docker_install.md.0b7efdda.lean.js
@@ -1 +1 @@
-import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker_install.md","filePath":"guide/docker_install.md","lastUpdated":1692790731000}'),o={name:"guide/docker_install.md"},n=p('
前言 ​
支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统
环境预设 ​
  • 检测环境
  • 安装docker和其他预制组件
  • 下载默认需要的一些配置脚本
国际
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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
开设虚拟内存 ​
WARNING
内存开点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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
',16),e=[n];function t(c,r,C,i,y,d){return a(),l("div",null,e)}const h=s(o,[["render",t]]);export{D as __pageData,h as default};
+import{_ as s,v as a,b as l,R as p}from"./chunks/framework.70afa331.js";const D=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker_install.md","filePath":"guide/docker_install.md","lastUpdated":1692790817000}'),o={name:"guide/docker_install.md"},n=p('
前言 ​
支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统
环境预设 ​
  • 检测环境
  • 安装docker和其他预制组件
  • 下载默认需要的一些配置脚本
国际
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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
开设虚拟内存 ​
WARNING
内存开点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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
',16),e=[n];function t(c,r,C,i,y,d){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.8dcdee0e.js b/assets/guide_docker_precheck.md.e7c168f4.js
similarity index 97%
rename from assets/guide_docker_precheck.md.8dcdee0e.js
rename to assets/guide_docker_precheck.md.e7c168f4.js
index 44cbb69179..d72c5db60b 100644
--- a/assets/guide_docker_precheck.md.8dcdee0e.js
+++ b/assets/guide_docker_precheck.md.e7c168f4.js
@@ -1 +1 @@
-import{_ as e,v as r,b as a,R as t}from"./chunks/framework.70afa331.js";const k=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker_precheck.md","filePath":"guide/docker_precheck.md","lastUpdated":1692790731000}'),o={name:"guide/docker_precheck.md"},p=t('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
项目特点 ​
通过docker批量或单独开设NAT服务器(Bulk or individual NAT server provisioning via docker)
默认使用debian系统，每个容器自带1个外网ssh端口，25个内外网一致端口
默认创建的是非特权容器，且不挂载与宿主机的docker的守护进程之间的通信，所以宿主机创建的docker虚拟化的NAT服务器内无法再嵌套虚拟化docker
由于只是在宿主机进行了CPU和内存的限制未在容器内使用cgroup驱动，所以在容器内使用服务器测试脚本检测容器的可用资源是无效的，显示的会是宿主机的资源
由于大部分云服务器xfs文件系统不启用pquota选项，所以默认共享宿主机硬盘，无法限制每个容器的磁盘大小
配置要求 ​
系统可安装docker即可用，网络能连接Github的raw界面就能用，硬件配置只要不拉跨就行，空闲硬盘有3G就行
推荐在开设NAT服务器前先增加部分SWAP虚拟内存，避免突发的内存占用导致母鸡卡死 跳转
PS: 如果硬件资源只是好了一点，需要限制更多东西并需要配置IPV6独立地址和限制硬盘大小，可使用LXD批量开LXC虚拟化的容器 跳转
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
',13),s=[p];function i(d,c,n,h,l,u){return r(),a("div",null,s)}const f=e(o,[["render",i]]);export{k as __pageData,f as default};
+import{_ as e,v as r,b as a,R as t}from"./chunks/framework.70afa331.js";const k=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker_precheck.md","filePath":"guide/docker_precheck.md","lastUpdated":1692790817000}'),o={name:"guide/docker_precheck.md"},p=t('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
项目特点 ​
通过docker批量或单独开设NAT服务器(Bulk or individual NAT server provisioning via docker)
默认使用debian系统，每个容器自带1个外网ssh端口，25个内外网一致端口
默认创建的是非特权容器，且不挂载与宿主机的docker的守护进程之间的通信，所以宿主机创建的docker虚拟化的NAT服务器内无法再嵌套虚拟化docker
由于只是在宿主机进行了CPU和内存的限制未在容器内使用cgroup驱动，所以在容器内使用服务器测试脚本检测容器的可用资源是无效的，显示的会是宿主机的资源
由于大部分云服务器xfs文件系统不启用pquota选项，所以默认共享宿主机硬盘，无法限制每个容器的磁盘大小
配置要求 ​
系统可安装docker即可用，网络能连接Github的raw界面就能用，硬件配置只要不拉跨就行，空闲硬盘有3G就行
推荐在开设NAT服务器前先增加部分SWAP虚拟内存，避免突发的内存占用导致母鸡卡死 跳转
PS: 如果硬件资源只是好了一点，需要限制更多东西并需要配置IPV6独立地址和限制硬盘大小，可使用LXD批量开LXC虚拟化的容器 跳转
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
',13),s=[p];function i(d,c,n,h,l,u){return r(),a("div",null,s)}const f=e(o,[["render",i]]);export{k as __pageData,f as default};
diff --git a/assets/guide_docker_precheck.md.8dcdee0e.lean.js b/assets/guide_docker_precheck.md.e7c168f4.lean.js
similarity index 97%
rename from assets/guide_docker_precheck.md.8dcdee0e.lean.js
rename to assets/guide_docker_precheck.md.e7c168f4.lean.js
index 44cbb69179..d72c5db60b 100644
--- a/assets/guide_docker_precheck.md.8dcdee0e.lean.js
+++ b/assets/guide_docker_precheck.md.e7c168f4.lean.js
@@ -1 +1 @@
-import{_ as e,v as r,b as a,R as t}from"./chunks/framework.70afa331.js";const k=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker_precheck.md","filePath":"guide/docker_precheck.md","lastUpdated":1692790731000}'),o={name:"guide/docker_precheck.md"},p=t('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
项目特点 ​
通过docker批量或单独开设NAT服务器(Bulk or individual NAT server provisioning via docker)
默认使用debian系统，每个容器自带1个外网ssh端口，25个内外网一致端口
默认创建的是非特权容器，且不挂载与宿主机的docker的守护进程之间的通信，所以宿主机创建的docker虚拟化的NAT服务器内无法再嵌套虚拟化docker
由于只是在宿主机进行了CPU和内存的限制未在容器内使用cgroup驱动，所以在容器内使用服务器测试脚本检测容器的可用资源是无效的，显示的会是宿主机的资源
由于大部分云服务器xfs文件系统不启用pquota选项，所以默认共享宿主机硬盘，无法限制每个容器的磁盘大小
配置要求 ​
系统可安装docker即可用，网络能连接Github的raw界面就能用，硬件配置只要不拉跨就行，空闲硬盘有3G就行
推荐在开设NAT服务器前先增加部分SWAP虚拟内存，避免突发的内存占用导致母鸡卡死 跳转
PS: 如果硬件资源只是好了一点，需要限制更多东西并需要配置IPV6独立地址和限制硬盘大小，可使用LXD批量开LXC虚拟化的容器 跳转
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
',13),s=[p];function i(d,c,n,h,l,u){return r(),a("div",null,s)}const f=e(o,[["render",i]]);export{k as __pageData,f as default};
+import{_ as e,v as r,b as a,R as t}from"./chunks/framework.70afa331.js";const k=JSON.parse('{"title":"前言","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/docker_precheck.md","filePath":"guide/docker_precheck.md","lastUpdated":1692790817000}'),o={name:"guide/docker_precheck.md"},p=t('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
项目特点 ​
通过docker批量或单独开设NAT服务器(Bulk or individual NAT server provisioning via docker)
默认使用debian系统，每个容器自带1个外网ssh端口，25个内外网一致端口
默认创建的是非特权容器，且不挂载与宿主机的docker的守护进程之间的通信，所以宿主机创建的docker虚拟化的NAT服务器内无法再嵌套虚拟化docker
由于只是在宿主机进行了CPU和内存的限制未在容器内使用cgroup驱动，所以在容器内使用服务器测试脚本检测容器的可用资源是无效的，显示的会是宿主机的资源
由于大部分云服务器xfs文件系统不启用pquota选项，所以默认共享宿主机硬盘，无法限制每个容器的磁盘大小
配置要求 ​
系统可安装docker即可用，网络能连接Github的raw界面就能用，硬件配置只要不拉跨就行，空闲硬盘有3G就行
推荐在开设NAT服务器前先增加部分SWAP虚拟内存，避免突发的内存占用导致母鸡卡死 跳转
PS: 如果硬件资源只是好了一点，需要限制更多东西并需要配置IPV6独立地址和限制硬盘大小，可使用LXD批量开LXC虚拟化的容器 跳转
PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转
',13),s=[p];function i(d,c,n,h,l,u){return r(),a("div",null,s)}const f=e(o,[["render",i]]);export{k as __pageData,f as default};
diff --git a/assets/guide_docker_qa.md.2e09ddf2.js b/assets/guide_docker_qa.md.66c09a7a.js
similarity index 98%
rename from assets/guide_docker_qa.md.2e09ddf2.js
rename to assets/guide_docker_qa.md.66c09a7a.js
index 884bcdbc2d..f49f810328 100644
--- a/assets/guide_docker_qa.md.2e09ddf2.js
+++ b/assets/guide_docker_qa.md.66c09a7a.js
@@ -1 +1 @@
-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":1692790731000}'),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};
+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":1692790817000}'),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.2e09ddf2.lean.js b/assets/guide_docker_qa.md.66c09a7a.lean.js
similarity index 98%
rename from assets/guide_docker_qa.md.2e09ddf2.lean.js
rename to assets/guide_docker_qa.md.66c09a7a.lean.js
index 884bcdbc2d..f49f810328 100644
--- a/assets/guide_docker_qa.md.2e09ddf2.lean.js
+++ b/assets/guide_docker_qa.md.66c09a7a.lean.js
@@ -1 +1 @@
-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":1692790731000}'),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};
+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":1692790817000}'),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.6c5fe30f.js b/assets/guide_docker_thanks.md.50fb533c.js
similarity index 97%
rename from assets/guide_docker_thanks.md.6c5fe30f.js
rename to assets/guide_docker_thanks.md.50fb533c.js
index 571dc94c0a..6d963e2976 100644
--- a/assets/guide_docker_thanks.md.6c5fe30f.js
+++ b/assets/guide_docker_thanks.md.50fb533c.js
@@ -1 +1 @@
-import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/docker_thanks.md","filePath":"guide/docker_thanks.md","lastUpdated":1692790731000}'),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
',16),h=[n];function c(s,p,i,l,d,g){return e(),t("div",null,h)}const b=r(o,[["render",c]]);export{m as __pageData,b as default};
+import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/docker_thanks.md","filePath":"guide/docker_thanks.md","lastUpdated":1692790817000}'),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
',16),h=[n];function c(s,p,i,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/guide_docker_thanks.md.6c5fe30f.lean.js b/assets/guide_docker_thanks.md.50fb533c.lean.js
similarity index 97%
rename from assets/guide_docker_thanks.md.6c5fe30f.lean.js
rename to assets/guide_docker_thanks.md.50fb533c.lean.js
index 571dc94c0a..6d963e2976 100644
--- a/assets/guide_docker_thanks.md.6c5fe30f.lean.js
+++ b/assets/guide_docker_thanks.md.50fb533c.lean.js
@@ -1 +1 @@
-import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/docker_thanks.md","filePath":"guide/docker_thanks.md","lastUpdated":1692790731000}'),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
',16),h=[n];function c(s,p,i,l,d,g){return e(),t("div",null,h)}const b=r(o,[["render",c]]);export{m as __pageData,b as default};
+import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/docker_thanks.md","filePath":"guide/docker_thanks.md","lastUpdated":1692790817000}'),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
',16),h=[n];function c(s,p,i,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/guide_lxd_custom.md.55f21751.js b/assets/guide_lxd_custom.md.f13b31d2.js
similarity index 83%
rename from assets/guide_lxd_custom.md.55f21751.js
rename to assets/guide_lxd_custom.md.f13b31d2.js
index b76198bfb6..7a93054103 100644
--- a/assets/guide_lxd_custom.md.55f21751.js
+++ b/assets/guide_lxd_custom.md.f13b31d2.js
@@ -1 +1 @@
-import{_ as t,v as e,b as s}from"./chunks/framework.70afa331.js";const p=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/lxd_custom.md","filePath":"guide/lxd_custom.md","lastUpdated":1692790731000}'),a={name:"guide/lxd_custom.md"};function d(o,r,c,_,i,n){return e(),s("div")}const u=t(a,[["render",d]]);export{p as __pageData,u as default};
+import{_ as t,v as e,b as s}from"./chunks/framework.70afa331.js";const p=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/lxd_custom.md","filePath":"guide/lxd_custom.md","lastUpdated":1692790817000}'),a={name:"guide/lxd_custom.md"};function d(o,r,c,_,i,n){return e(),s("div")}const u=t(a,[["render",d]]);export{p as __pageData,u as default};
diff --git a/assets/guide_lxd_custom.md.55f21751.lean.js b/assets/guide_lxd_custom.md.f13b31d2.lean.js
similarity index 83%
rename from assets/guide_lxd_custom.md.55f21751.lean.js
rename to assets/guide_lxd_custom.md.f13b31d2.lean.js
index b76198bfb6..7a93054103 100644
--- a/assets/guide_lxd_custom.md.55f21751.lean.js
+++ b/assets/guide_lxd_custom.md.f13b31d2.lean.js
@@ -1 +1 @@
-import{_ as t,v as e,b as s}from"./chunks/framework.70afa331.js";const p=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/lxd_custom.md","filePath":"guide/lxd_custom.md","lastUpdated":1692790731000}'),a={name:"guide/lxd_custom.md"};function d(o,r,c,_,i,n){return e(),s("div")}const u=t(a,[["render",d]]);export{p as __pageData,u as default};
+import{_ as t,v as e,b as s}from"./chunks/framework.70afa331.js";const p=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/lxd_custom.md","filePath":"guide/lxd_custom.md","lastUpdated":1692790817000}'),a={name:"guide/lxd_custom.md"};function d(o,r,c,_,i,n){return e(),s("div")}const u=t(a,[["render",d]]);export{p as __pageData,u as default};
diff --git a/assets/guide_lxd_extra_config.md.61859656.js b/assets/guide_lxd_extra_config.md.d425073f.js
similarity index 99%
rename from assets/guide_lxd_extra_config.md.61859656.js
rename to assets/guide_lxd_extra_config.md.d425073f.js
index 72e280f2bf..b787da00a9 100644
--- a/assets/guide_lxd_extra_config.md.61859656.js
+++ b/assets/guide_lxd_extra_config.md.d425073f.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":1692790731000}'),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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
自动为容器配置IPV6映射地址
bash
bash build_ipv6_network.sh 容器名称
映射完毕会打印信息
示例(给test容器自动配置IPV6地址，配置完成会写入一个test_v6的文件信息)
bash
bash build_ipv6_network.sh test
删除所有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_extra_config.md","filePath":"guide/lxd_extra_config.md","lastUpdated":1692790817000}'),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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
自动为容器配置IPV6映射地址
bash
bash build_ipv6_network.sh 容器名称
映射完毕会打印信息
示例(给test容器自动配置IPV6地址，配置完成会写入一个test_v6的文件信息)
bash
bash build_ipv6_network.sh test
删除所有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.61859656.lean.js b/assets/guide_lxd_extra_config.md.d425073f.lean.js
similarity index 99%
rename from assets/guide_lxd_extra_config.md.61859656.lean.js
rename to assets/guide_lxd_extra_config.md.d425073f.lean.js
index 72e280f2bf..b787da00a9 100644
--- a/assets/guide_lxd_extra_config.md.61859656.lean.js
+++ b/assets/guide_lxd_extra_config.md.d425073f.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":1692790731000}'),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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
自动为容器配置IPV6映射地址
bash
bash build_ipv6_network.sh 容器名称
映射完毕会打印信息
示例(给test容器自动配置IPV6地址，配置完成会写入一个test_v6的文件信息)
bash
bash build_ipv6_network.sh test
删除所有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_extra_config.md","filePath":"guide/lxd_extra_config.md","lastUpdated":1692790817000}'),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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/build_ipv6_network.sh -o build_ipv6_network.sh && chmod +x build_ipv6_network.sh
自动为容器配置IPV6映射地址
bash
bash build_ipv6_network.sh 容器名称
映射完毕会打印信息
示例(给test容器自动配置IPV6地址，配置完成会写入一个test_v6的文件信息)
bash
bash build_ipv6_network.sh test
删除所有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.9b21121e.js b/assets/guide_lxd_install.md.dc676e10.js
similarity index 99%
rename from assets/guide_lxd_install.md.9b21121e.js
rename to assets/guide_lxd_install.md.dc676e10.js
index 221ace4254..02b9cd46d4 100644
--- a/assets/guide_lxd_install.md.9b21121e.js
+++ b/assets/guide_lxd_install.md.dc676e10.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":1692790731000}'),n={name:"guide/lxd_install.md"},o=p(`
LXD主体安装 ​
手动安装 ​
新手推荐，避免有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_install.md","filePath":"guide/lxd_install.md","lastUpdated":1692790817000}'),n={name:"guide/lxd_install.md"},o=p(`
LXD主体安装 ​
手动安装 ​
新手推荐，避免有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://ghproxy.com/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.9b21121e.lean.js b/assets/guide_lxd_install.md.dc676e10.lean.js
similarity index 99%
rename from assets/guide_lxd_install.md.9b21121e.lean.js
rename to assets/guide_lxd_install.md.dc676e10.lean.js
index 221ace4254..02b9cd46d4 100644
--- a/assets/guide_lxd_install.md.9b21121e.lean.js
+++ b/assets/guide_lxd_install.md.dc676e10.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":1692790731000}'),n={name:"guide/lxd_install.md"},o=p(`
LXD主体安装 ​
手动安装 ​
新手推荐，避免有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_install.md","filePath":"guide/lxd_install.md","lastUpdated":1692790817000}'),n={name:"guide/lxd_install.md"},o=p(`
LXD主体安装 ​
手动安装 ​
新手推荐，避免有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://ghproxy.com/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.7af7a88e.js b/assets/guide_lxd_lxc.md.1e73e1da.js
similarity index 99%
rename from assets/guide_lxd_lxc.md.7af7a88e.js
rename to assets/guide_lxd_lxc.md.1e73e1da.js
index 3aa1bdeba8..6ab20b97b1 100644
--- a/assets/guide_lxd_lxc.md.7af7a88e.js
+++ b/assets/guide_lxd_lxc.md.1e73e1da.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":1692790731000}'),p={name:"guide/lxd_lxc.md"},o=n(`
LXC虚拟化 ​
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载开机脚本是非必须的，如果你使用过一键安装LXD的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
国内
shell
curl -L https://ghproxy.com/https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
使用方法 ​
./buildone.sh 小鸡名称 内存大小 硬盘大小 SSH端口 外网起端口 外网止端口 下载速度 上传速度 是否启用IPV6(Y or N) 系统(留空则为debian11)
内存大小以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
  • 注意都是小写字母+数字的组合，自行尝试，如果搜索无该系统则会自动退出脚本
  • 版本号可以带英文小数点，为了适配alpine的版本号已支持
  • 注意部分系统可能因为未加载cgroup，所以在容器内测试系统资源会显示的宿主机的系统资源，实际是有约束的，类同Docker
TIP
版本号中已结束长期维护的一般不再有官方镜像了，暂时未找到历史镜像的存档地址，如果有找到欢迎留言我会添加支持
示例 ​
以下为开设的示例小鸡的信息：
属性值
小鸡名字test
SSH登录的用户名root
SSH登录的密码随机生成
CPU核数1
内存大小256MB
磁盘大小2G
内外网映射端口一致的区间20002到20025
上传带宽500Mbit
下载带宽500Mbit
自动设置外网IPV6地址N
系统debian11
./buildone.sh test 256 2 20001 20002 20025 500 500 N
需要查看信息则执行
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_lxc.md","filePath":"guide/lxd_lxc.md","lastUpdated":1692790817000}'),p={name:"guide/lxd_lxc.md"},o=n(`
LXC虚拟化 ​
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载开机脚本是非必须的，如果你使用过一键安装LXD的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
国内
shell
curl -L https://ghproxy.com/https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
使用方法 ​
./buildone.sh 小鸡名称 内存大小 硬盘大小 SSH端口 外网起端口 外网止端口 下载速度 上传速度 是否启用IPV6(Y or N) 系统(留空则为debian11)
内存大小以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
  • 注意都是小写字母+数字的组合，自行尝试，如果搜索无该系统则会自动退出脚本
  • 版本号可以带英文小数点，为了适配alpine的版本号已支持
  • 注意部分系统可能因为未加载cgroup，所以在容器内测试系统资源会显示的宿主机的系统资源，实际是有约束的，类同Docker
TIP
版本号中已结束长期维护的一般不再有官方镜像了，暂时未找到历史镜像的存档地址，如果有找到欢迎留言我会添加支持
示例 ​
以下为开设的示例小鸡的信息：
属性值
小鸡名字test
SSH登录的用户名root
SSH登录的密码随机生成
CPU核数1
内存大小256MB
磁盘大小2G
内外网映射端口一致的区间20002到20025
上传带宽500Mbit
下载带宽500Mbit
自动设置外网IPV6地址N
系统debian11
./buildone.sh test 256 2 20001 20002 20025 500 500 N
需要查看信息则执行
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.7af7a88e.lean.js b/assets/guide_lxd_lxc.md.1e73e1da.lean.js
similarity index 99%
rename from assets/guide_lxd_lxc.md.7af7a88e.lean.js
rename to assets/guide_lxd_lxc.md.1e73e1da.lean.js
index 3aa1bdeba8..6ab20b97b1 100644
--- a/assets/guide_lxd_lxc.md.7af7a88e.lean.js
+++ b/assets/guide_lxd_lxc.md.1e73e1da.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":1692790731000}'),p={name:"guide/lxd_lxc.md"},o=n(`
LXC虚拟化 ​
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载开机脚本是非必须的，如果你使用过一键安装LXD的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
国内
shell
curl -L https://ghproxy.com/https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
使用方法 ​
./buildone.sh 小鸡名称 内存大小 硬盘大小 SSH端口 外网起端口 外网止端口 下载速度 上传速度 是否启用IPV6(Y or N) 系统(留空则为debian11)
内存大小以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
  • 注意都是小写字母+数字的组合，自行尝试，如果搜索无该系统则会自动退出脚本
  • 版本号可以带英文小数点，为了适配alpine的版本号已支持
  • 注意部分系统可能因为未加载cgroup，所以在容器内测试系统资源会显示的宿主机的系统资源，实际是有约束的，类同Docker
TIP
版本号中已结束长期维护的一般不再有官方镜像了，暂时未找到历史镜像的存档地址，如果有找到欢迎留言我会添加支持
示例 ​
以下为开设的示例小鸡的信息：
属性值
小鸡名字test
SSH登录的用户名root
SSH登录的密码随机生成
CPU核数1
内存大小256MB
磁盘大小2G
内外网映射端口一致的区间20002到20025
上传带宽500Mbit
下载带宽500Mbit
自动设置外网IPV6地址N
系统debian11
./buildone.sh test 256 2 20001 20002 20025 500 500 N
需要查看信息则执行
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_lxc.md","filePath":"guide/lxd_lxc.md","lastUpdated":1692790817000}'),p={name:"guide/lxd_lxc.md"},o=n(`
LXC虚拟化 ​
单独生成一个NAT服务器 ​
  • 只生成一个NAT服务器，可自定义限制所有内容
下载开机脚本是非必须的，如果你使用过一键安装LXD的命令，自动已下载对应的开机脚本，不需要重复下载该脚本
国际
shell
curl -L https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
国内
shell
curl -L https://ghproxy.com/https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/buildone.sh -o buildone.sh && chmod +x buildone.sh && dos2unix buildone.sh
使用方法 ​
./buildone.sh 小鸡名称 内存大小 硬盘大小 SSH端口 外网起端口 外网止端口 下载速度 上传速度 是否启用IPV6(Y or N) 系统(留空则为debian11)
内存大小以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
  • 注意都是小写字母+数字的组合，自行尝试，如果搜索无该系统则会自动退出脚本
  • 版本号可以带英文小数点，为了适配alpine的版本号已支持
  • 注意部分系统可能因为未加载cgroup，所以在容器内测试系统资源会显示的宿主机的系统资源，实际是有约束的，类同Docker
TIP
版本号中已结束长期维护的一般不再有官方镜像了，暂时未找到历史镜像的存档地址，如果有找到欢迎留言我会添加支持
示例 ​
以下为开设的示例小鸡的信息：
属性值
小鸡名字test
SSH登录的用户名root
SSH登录的密码随机生成
CPU核数1
内存大小256MB
磁盘大小2G
内外网映射端口一致的区间20002到20025
上传带宽500Mbit
下载带宽500Mbit
自动设置外网IPV6地址N
系统debian11
./buildone.sh test 256 2 20001 20002 20025 500 500 N
需要查看信息则执行
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_precheck.md.90630545.js b/assets/guide_lxd_precheck.md.26c290e1.js
similarity index 98%
rename from assets/guide_lxd_precheck.md.90630545.js
rename to assets/guide_lxd_precheck.md.26c290e1.js
index f513b7c49a..739688a7aa 100644
--- a/assets/guide_lxd_precheck.md.90630545.js
+++ b/assets/guide_lxd_precheck.md.26c290e1.js
@@ -1 +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_precheck.md","filePath":"guide/lxd_precheck.md","lastUpdated":1692790731000}'),s={name:"guide/lxd_precheck.md"},l=i('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
要求 ​
硬件要求:
  • 系统：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系统
  • 已屏蔽容器内可能用于滥用的工具包和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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/pre_check.sh)
',15),r=[l];function p(o,n,c,d,h,u){return a(),t("div",null,r)}const m=e(s,[["render",p]]);export{g as __pageData,m as default};
+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":1692790817000}'),s={name:"guide/lxd_precheck.md"},l=i('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
要求 ​
硬件要求:
  • 系统：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系统
  • 已屏蔽容器内可能用于滥用的工具包和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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/pre_check.sh)
',15),r=[l];function p(o,n,c,d,h,u){return a(),t("div",null,r)}const m=e(s,[["render",p]]);export{g as __pageData,m as default};
diff --git a/assets/guide_lxd_precheck.md.90630545.lean.js b/assets/guide_lxd_precheck.md.26c290e1.lean.js
similarity index 98%
rename from assets/guide_lxd_precheck.md.90630545.lean.js
rename to assets/guide_lxd_precheck.md.26c290e1.lean.js
index f513b7c49a..739688a7aa 100644
--- a/assets/guide_lxd_precheck.md.90630545.lean.js
+++ b/assets/guide_lxd_precheck.md.26c290e1.lean.js
@@ -1 +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_precheck.md","filePath":"guide/lxd_precheck.md","lastUpdated":1692790731000}'),s={name:"guide/lxd_precheck.md"},l=i('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
要求 ​
硬件要求:
  • 系统：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系统
  • 已屏蔽容器内可能用于滥用的工具包和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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/pre_check.sh)
',15),r=[l];function p(o,n,c,d,h,u){return a(),t("div",null,r)}const m=e(s,[["render",p]]);export{g as __pageData,m as default};
+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":1692790817000}'),s={name:"guide/lxd_precheck.md"},l=i('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
要求 ​
硬件要求:
  • 系统：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系统
  • 已屏蔽容器内可能用于滥用的工具包和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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/pre_check.sh)
',15),r=[l];function p(o,n,c,d,h,u){return a(),t("div",null,r)}const m=e(s,[["render",p]]);export{g as __pageData,m as default};
diff --git a/assets/guide_lxd_qa.md.5ee50dd6.js b/assets/guide_lxd_qa.md.02566bd0.js
similarity index 98%
rename from assets/guide_lxd_qa.md.5ee50dd6.js
rename to assets/guide_lxd_qa.md.02566bd0.js
index f64cd679b2..99a8175cc8 100644
--- a/assets/guide_lxd_qa.md.5ee50dd6.js
+++ b/assets/guide_lxd_qa.md.02566bd0.js
@@ -1,2 +1,2 @@
-import{_ as a,v as e,b as s,R as t}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd_qa.md","filePath":"guide/lxd_qa.md","lastUpdated":1692790731000}'),l={name:"guide/lxd_qa.md"},p=t(`
解惑 ​
如果LXD安装后lxc命令显示找不到怎么办 ​
! lxc -h >/dev/null 2>&1 && echo 'alias lxc="/snap/bin/lxc"' >> /root/.bashrc && source /root/.bashrc
+import{_ as a,v as e,b as s,R as t}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd_qa.md","filePath":"guide/lxd_qa.md","lastUpdated":1692790817000}'),l={name:"guide/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中的参数末尾加上cgroup_enable=memory。
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash cgroup_enable=memory"
保存文件并运行以下命令更新GRUB引导。
bash
sudo update-grub
重启系统，使更改生效
如果上述更改仍旧不支持开设centos7，那么请使用别的宿主机系统尝试
目前已验证可开带独立IPV6地址容器的VPS商家 ​
kuroit 中的 美国凤凰城 regular
datalix 中的 德国AMD 促销款
luxvps 中的 德国AMD 促销款
`,19),o=[p];function n(r,c,i,d,u,h){return e(),s("div",null,o)}const m=a(l,[["render",n]]);export{b as __pageData,m as default};
diff --git a/assets/guide_lxd_qa.md.5ee50dd6.lean.js b/assets/guide_lxd_qa.md.02566bd0.lean.js
similarity index 98%
rename from assets/guide_lxd_qa.md.5ee50dd6.lean.js
rename to assets/guide_lxd_qa.md.02566bd0.lean.js
index f64cd679b2..99a8175cc8 100644
--- a/assets/guide_lxd_qa.md.5ee50dd6.lean.js
+++ b/assets/guide_lxd_qa.md.02566bd0.lean.js
@@ -1,2 +1,2 @@
-import{_ as a,v as e,b as s,R as t}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd_qa.md","filePath":"guide/lxd_qa.md","lastUpdated":1692790731000}'),l={name:"guide/lxd_qa.md"},p=t(`
解惑 ​
如果LXD安装后lxc命令显示找不到怎么办 ​
! lxc -h >/dev/null 2>&1 && echo 'alias lxc="/snap/bin/lxc"' >> /root/.bashrc && source /root/.bashrc
+import{_ as a,v as e,b as s,R as t}from"./chunks/framework.70afa331.js";const b=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/lxd_qa.md","filePath":"guide/lxd_qa.md","lastUpdated":1692790817000}'),l={name:"guide/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中的参数末尾加上cgroup_enable=memory。
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash cgroup_enable=memory"
保存文件并运行以下命令更新GRUB引导。
bash
sudo update-grub
重启系统，使更改生效
如果上述更改仍旧不支持开设centos7，那么请使用别的宿主机系统尝试
目前已验证可开带独立IPV6地址容器的VPS商家 ​
kuroit 中的 美国凤凰城 regular
datalix 中的 德国AMD 促销款
luxvps 中的 德国AMD 促销款
`,19),o=[p];function n(r,c,i,d,u,h){return e(),s("div",null,o)}const m=a(l,[["render",n]]);export{b as __pageData,m as default};
diff --git a/assets/guide_lxd_thanks.md.b15cc6bd.js b/assets/guide_lxd_thanks.md.28c5f5b7.js
similarity index 97%
rename from assets/guide_lxd_thanks.md.b15cc6bd.js
rename to assets/guide_lxd_thanks.md.28c5f5b7.js
index 8ad58a74fd..ec13c98cfe 100644
--- a/assets/guide_lxd_thanks.md.b15cc6bd.js
+++ b/assets/guide_lxd_thanks.md.28c5f5b7.js
@@ -1 +1 @@
-import{_ as t,v as r,b as e,R as a}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/lxd_thanks.md","filePath":"guide/lxd_thanks.md","lastUpdated":1692790731000}'),s={name:"guide/lxd_thanks.md"},n=a('
致谢 ​
https://github.com/lxc/lxd
https://lxdware.com/
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
感谢 @Ella-Alinda @fscarmen 提供的指导
',10),o=[n];function i(c,l,p,d,h,u){return r(),e("div",null,o)}const x=t(s,[["render",i]]);export{g as __pageData,x as default};
+import{_ as t,v as r,b as e,R as a}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/lxd_thanks.md","filePath":"guide/lxd_thanks.md","lastUpdated":1692790817000}'),s={name:"guide/lxd_thanks.md"},n=a('
致谢 ​
https://github.com/lxc/lxd
https://lxdware.com/
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
感谢 @Ella-Alinda @fscarmen 提供的指导
',10),o=[n];function i(c,l,p,d,h,u){return r(),e("div",null,o)}const x=t(s,[["render",i]]);export{g as __pageData,x as default};
diff --git a/assets/guide_lxd_thanks.md.b15cc6bd.lean.js b/assets/guide_lxd_thanks.md.28c5f5b7.lean.js
similarity index 97%
rename from assets/guide_lxd_thanks.md.b15cc6bd.lean.js
rename to assets/guide_lxd_thanks.md.28c5f5b7.lean.js
index 8ad58a74fd..ec13c98cfe 100644
--- a/assets/guide_lxd_thanks.md.b15cc6bd.lean.js
+++ b/assets/guide_lxd_thanks.md.28c5f5b7.lean.js
@@ -1 +1 @@
-import{_ as t,v as r,b as e,R as a}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/lxd_thanks.md","filePath":"guide/lxd_thanks.md","lastUpdated":1692790731000}'),s={name:"guide/lxd_thanks.md"},n=a('
致谢 ​
https://github.com/lxc/lxd
https://lxdware.com/
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
感谢 @Ella-Alinda @fscarmen 提供的指导
',10),o=[n];function i(c,l,p,d,h,u){return r(),e("div",null,o)}const x=t(s,[["render",i]]);export{g as __pageData,x as default};
+import{_ as t,v as r,b as e,R as a}from"./chunks/framework.70afa331.js";const g=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/lxd_thanks.md","filePath":"guide/lxd_thanks.md","lastUpdated":1692790817000}'),s={name:"guide/lxd_thanks.md"},n=a('
致谢 ​
https://github.com/lxc/lxd
https://lxdware.com/
https://discuss.linuxcontainers.org/
https://discuss.linuxcontainers.org/t/how-to-run-docker-inside-lxc-container/13017/4
https://discuss.linuxcontainers.org/t/error-seccomp-notify-not-supported-on-container-start/15038/3
https://discuss.linuxcontainers.org/t/how-do-i-assign-a-public-ipv6-address-to-a-lxc-container/6028
https://github.com/turtle0x1/LxdMosaic
https://openzfs.github.io/openzfs-docs/Getting Started/Debian/index.html
感谢 @Ella-Alinda @fscarmen 提供的指导
',10),o=[n];function i(c,l,p,d,h,u){return r(),e("div",null,o)}const x=t(s,[["render",i]]);export{g as __pageData,x as default};
diff --git a/assets/guide_pve_custom.md.0aac6ff9.js b/assets/guide_pve_custom.md.d0a01bbc.js
similarity index 98%
rename from assets/guide_pve_custom.md.0aac6ff9.js
rename to assets/guide_pve_custom.md.d0a01bbc.js
index d4bdf732ec..7fa9b270b1 100644
--- a/assets/guide_pve_custom.md.0aac6ff9.js
+++ b/assets/guide_pve_custom.md.d0a01bbc.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":1692790731000}'),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 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":1692790817000}'),p={name:"guide/pve_custom.md"},e=o(`
一些自定义脚本 ​
每个脚本可能有对应的系统要求，自行查看
在非Debian系统上安装 Proxmox VE 7 ​
本机硬件配置的最低要求同先前正常安装的要求一致
需要先安装docker
curl -sSL https://get.docker.com/ | sh
 curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-linux-$(uname -m)" -o /usr/local/bin/docker-compose
 chmod +x /usr/local/bin/docker-compose
 docker-compose --version
然后使用uname -m查询架构，使用对应架构的命令
开设出的PVE面板信息为：
登录用户名和密码都是root，登录后务必使用web的SSH更改密码以免被爆破
用宿主机SSH时务必登录对应https://IPV4地址:8006在web面板上使用SSH，不要使用宿主机的22端口操控PVE
因为web面板上的SSH是在Docker内的，所以不支持后续的一键配置，请自行配置网关等进行使用
X86架构
bash
docker run -idt --network host \\
diff --git a/assets/guide_pve_custom.md.0aac6ff9.lean.js b/assets/guide_pve_custom.md.d0a01bbc.lean.js
similarity index 98%
rename from assets/guide_pve_custom.md.0aac6ff9.lean.js
rename to assets/guide_pve_custom.md.d0a01bbc.lean.js
index d4bdf732ec..7fa9b270b1 100644
--- a/assets/guide_pve_custom.md.0aac6ff9.lean.js
+++ b/assets/guide_pve_custom.md.d0a01bbc.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":1692790731000}'),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 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":1692790817000}'),p={name:"guide/pve_custom.md"},e=o(`
一些自定义脚本 ​
每个脚本可能有对应的系统要求，自行查看
在非Debian系统上安装 Proxmox VE 7 ​
本机硬件配置的最低要求同先前正常安装的要求一致
需要先安装docker
curl -sSL https://get.docker.com/ | sh
 curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-linux-$(uname -m)" -o /usr/local/bin/docker-compose
 chmod +x /usr/local/bin/docker-compose
 docker-compose --version
然后使用uname -m查询架构，使用对应架构的命令
开设出的PVE面板信息为：
登录用户名和密码都是root，登录后务必使用web的SSH更改密码以免被爆破
用宿主机SSH时务必登录对应https://IPV4地址:8006在web面板上使用SSH，不要使用宿主机的22端口操控PVE
因为web面板上的SSH是在Docker内的，所以不支持后续的一键配置，请自行配置网关等进行使用
X86架构
bash
docker run -idt --network host \\
diff --git a/assets/guide_pve_install.md.42dc929c.js b/assets/guide_pve_install.md.960c4fb2.js
similarity index 99%
rename from assets/guide_pve_install.md.42dc929c.js
rename to assets/guide_pve_install.md.960c4fb2.js
index a5e51d70cc..0c1cc00fec 100644
--- a/assets/guide_pve_install.md.42dc929c.js
+++ b/assets/guide_pve_install.md.960c4fb2.js
@@ -1 +1 @@
-import{_ as s,v as a,b as l,R as e}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"PVE主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_install.md","filePath":"guide/pve_install.md","lastUpdated":1692790731000}'),p={name:"guide/pve_install.md"},t=e('
PVE主体安装 ​
安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载
一键安装PVE ​
TIP
建议debian11而不是debian12，因为后者虽然是stable版本但不知道是否有未发现的BUG，debian11安装的目前稳定点
  • 安装的是当下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 文件路径进行只读锁定
国际
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://ghproxy.com/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
  • 移除订阅弹窗
  • 尝试开启硬件直通
  • 对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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)
自动配置宿主机的网关 ​
WARNING
使用前请保证重启过服务器且此时PVE能正常使用WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动成功后至少等1分钟再执行本命令
TIP
这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行
  • 如果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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_nat_network.sh)
TIP
这一步是可能需要你执行成功几分钟后重启系统，详见脚本最后执行完毕的提示
',33),o=[t];function n(c,i,r,d,h,C){return a(),l("div",null,o)}const b=s(p,[["render",n]]);export{m as __pageData,b as default};
+import{_ as s,v as a,b as l,R as e}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"PVE主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_install.md","filePath":"guide/pve_install.md","lastUpdated":1692790817000}'),p={name:"guide/pve_install.md"},t=e('
PVE主体安装 ​
安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载
一键安装PVE ​
TIP
建议debian11而不是debian12，因为后者虽然是stable版本但不知道是否有未发现的BUG，debian11安装的目前稳定点
  • 安装的是当下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 文件路径进行只读锁定
国际
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://ghproxy.com/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
  • 移除订阅弹窗
  • 尝试开启硬件直通
  • 对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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)
自动配置宿主机的网关 ​
WARNING
使用前请保证重启过服务器且此时PVE能正常使用WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动成功后至少等1分钟再执行本命令
TIP
这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行
  • 如果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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_nat_network.sh)
TIP
这一步是可能需要你执行成功几分钟后重启系统，详见脚本最后执行完毕的提示
',33),o=[t];function n(c,i,r,d,h,C){return a(),l("div",null,o)}const b=s(p,[["render",n]]);export{m as __pageData,b as default};
diff --git a/assets/guide_pve_install.md.42dc929c.lean.js b/assets/guide_pve_install.md.960c4fb2.lean.js
similarity index 99%
rename from assets/guide_pve_install.md.42dc929c.lean.js
rename to assets/guide_pve_install.md.960c4fb2.lean.js
index a5e51d70cc..0c1cc00fec 100644
--- a/assets/guide_pve_install.md.42dc929c.lean.js
+++ b/assets/guide_pve_install.md.960c4fb2.lean.js
@@ -1 +1 @@
-import{_ as s,v as a,b as l,R as e}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"PVE主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_install.md","filePath":"guide/pve_install.md","lastUpdated":1692790731000}'),p={name:"guide/pve_install.md"},t=e('
PVE主体安装 ​
安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载
一键安装PVE ​
TIP
建议debian11而不是debian12，因为后者虽然是stable版本但不知道是否有未发现的BUG，debian11安装的目前稳定点
  • 安装的是当下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 文件路径进行只读锁定
国际
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://ghproxy.com/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
  • 移除订阅弹窗
  • 尝试开启硬件直通
  • 对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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)
自动配置宿主机的网关 ​
WARNING
使用前请保证重启过服务器且此时PVE能正常使用WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动成功后至少等1分钟再执行本命令
TIP
这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行
  • 如果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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_nat_network.sh)
TIP
这一步是可能需要你执行成功几分钟后重启系统，详见脚本最后执行完毕的提示
',33),o=[t];function n(c,i,r,d,h,C){return a(),l("div",null,o)}const b=s(p,[["render",n]]);export{m as __pageData,b as default};
+import{_ as s,v as a,b as l,R as e}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"PVE主体安装","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_install.md","filePath":"guide/pve_install.md","lastUpdated":1692790817000}'),p={name:"guide/pve_install.md"},t=e('
PVE主体安装 ​
安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载
一键安装PVE ​
TIP
建议debian11而不是debian12，因为后者虽然是stable版本但不知道是否有未发现的BUG，debian11安装的目前稳定点
  • 安装的是当下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 文件路径进行只读锁定
国际
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://ghproxy.com/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
  • 移除订阅弹窗
  • 尝试开启硬件直通
  • 对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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)
自动配置宿主机的网关 ​
WARNING
使用前请保证重启过服务器且此时PVE能正常使用WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动成功后至少等1分钟再执行本命令
TIP
这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行
  • 如果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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_nat_network.sh)
TIP
这一步是可能需要你执行成功几分钟后重启系统，详见脚本最后执行完毕的提示
',33),o=[t];function n(c,i,r,d,h,C){return a(),l("div",null,o)}const b=s(p,[["render",n]]);export{m as __pageData,b as default};
diff --git a/assets/guide_pve_kvm.md.252331b6.js b/assets/guide_pve_kvm.md.b6d67027.js
similarity index 99%
rename from assets/guide_pve_kvm.md.252331b6.js
rename to assets/guide_pve_kvm.md.b6d67027.js
index ff0faa8f63..282edd6ccd 100644
--- a/assets/guide_pve_kvm.md.252331b6.js
+++ b/assets/guide_pve_kvm.md.b6d67027.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":"KVM虚拟化","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_kvm.md","filePath":"guide/pve_kvm.md","lastUpdated":1692790731000}'),p={name:"guide/pve_kvm.md"},o=n(`
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://ghproxy.com/https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
部分注意事项 ​
执行本项目的检测环境的命令，展示如下
图片
查询如上的只需使用下面的一键脚本自动创建虚拟机即可，无需手动再修改WEB端设置
图片
查询如上的在使用后续脚本创建了虚拟机后，可能需要手动修改WEB端设置，需要关闭对应每个虚拟机的硬件嵌套虚拟化，如下图
图片
先停止虚拟机再修改，修改完后再开机才能使用NOVNC，不关闭可能导致这个虚拟机有BUG无法使用
如果强行安装PVE开KVM，启动不了的也可以关闭这个选项试试能不能启动虚拟机
TIP
开设虚拟机前请使用screen挂起执行，避免开设时间过长，SSH不稳定导致中间执行中断
开设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，需要宿主机至少有一个/64的子网
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
国内
shell
curl -L https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
使用方法 ​
  • 系统支持： 
    • x86_64架构的详见 跳转 中列出的系统，使用时只需写文件名字，不需要.qcow2尾缀
    • arm架构的详见 跳转 中列出的系统，使用时只需要写系统名字+系统版本号，如ubuntu20、ubutnu22这种
TIP
注意这里的用户名不能是纯数字，会造成cloudinit出问题，最好是纯英文或英文开头
shell
./buildvm.sh VMID 用户名 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6地址(留空默认N)
测试示例 ​
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
qm stop 102
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"KVM虚拟化","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_kvm.md","filePath":"guide/pve_kvm.md","lastUpdated":1692790817000}'),p={name:"guide/pve_kvm.md"},o=n(`
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://ghproxy.com/https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
部分注意事项 ​
执行本项目的检测环境的命令，展示如下
图片
查询如上的只需使用下面的一键脚本自动创建虚拟机即可，无需手动再修改WEB端设置
图片
查询如上的在使用后续脚本创建了虚拟机后，可能需要手动修改WEB端设置，需要关闭对应每个虚拟机的硬件嵌套虚拟化，如下图
图片
先停止虚拟机再修改，修改完后再开机才能使用NOVNC，不关闭可能导致这个虚拟机有BUG无法使用
如果强行安装PVE开KVM，启动不了的也可以关闭这个选项试试能不能启动虚拟机
TIP
开设虚拟机前请使用screen挂起执行，避免开设时间过长，SSH不稳定导致中间执行中断
开设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，需要宿主机至少有一个/64的子网
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
国内
shell
curl -L https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
使用方法 ​
  • 系统支持： 
    • x86_64架构的详见 跳转 中列出的系统，使用时只需写文件名字，不需要.qcow2尾缀
    • arm架构的详见 跳转 中列出的系统，使用时只需要写系统名字+系统版本号，如ubuntu20、ubutnu22这种
TIP
注意这里的用户名不能是纯数字，会造成cloudinit出问题，最好是纯英文或英文开头
shell
./buildvm.sh VMID 用户名 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6地址(留空默认N)
测试示例 ​
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
qm stop 102
 qm destroy 102
 iptables -t nat -F
 iptables -t filter -F
diff --git a/assets/guide_pve_kvm.md.252331b6.lean.js b/assets/guide_pve_kvm.md.b6d67027.lean.js
similarity index 99%
rename from assets/guide_pve_kvm.md.252331b6.lean.js
rename to assets/guide_pve_kvm.md.b6d67027.lean.js
index ff0faa8f63..282edd6ccd 100644
--- a/assets/guide_pve_kvm.md.252331b6.lean.js
+++ b/assets/guide_pve_kvm.md.b6d67027.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":"KVM虚拟化","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_kvm.md","filePath":"guide/pve_kvm.md","lastUpdated":1692790731000}'),p={name:"guide/pve_kvm.md"},o=n(`
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://ghproxy.com/https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
部分注意事项 ​
执行本项目的检测环境的命令，展示如下
图片
查询如上的只需使用下面的一键脚本自动创建虚拟机即可，无需手动再修改WEB端设置
图片
查询如上的在使用后续脚本创建了虚拟机后，可能需要手动修改WEB端设置，需要关闭对应每个虚拟机的硬件嵌套虚拟化，如下图
图片
先停止虚拟机再修改，修改完后再开机才能使用NOVNC，不关闭可能导致这个虚拟机有BUG无法使用
如果强行安装PVE开KVM，启动不了的也可以关闭这个选项试试能不能启动虚拟机
TIP
开设虚拟机前请使用screen挂起执行，避免开设时间过长，SSH不稳定导致中间执行中断
开设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，需要宿主机至少有一个/64的子网
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
国内
shell
curl -L https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
使用方法 ​
  • 系统支持： 
    • x86_64架构的详见 跳转 中列出的系统，使用时只需写文件名字，不需要.qcow2尾缀
    • arm架构的详见 跳转 中列出的系统，使用时只需要写系统名字+系统版本号，如ubuntu20、ubutnu22这种
TIP
注意这里的用户名不能是纯数字，会造成cloudinit出问题，最好是纯英文或英文开头
shell
./buildvm.sh VMID 用户名 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6地址(留空默认N)
测试示例 ​
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
qm stop 102
+import{_ as s,v as a,b as l,R as n}from"./chunks/framework.70afa331.js";const d=JSON.parse('{"title":"KVM虚拟化","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_kvm.md","filePath":"guide/pve_kvm.md","lastUpdated":1692790817000}'),p={name:"guide/pve_kvm.md"},o=n(`
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://ghproxy.com/https://raw.githubusercontent.com/fscarmen/tools/main/root.sh) [PASSWORD]
部分注意事项 ​
执行本项目的检测环境的命令，展示如下
图片
查询如上的只需使用下面的一键脚本自动创建虚拟机即可，无需手动再修改WEB端设置
图片
查询如上的在使用后续脚本创建了虚拟机后，可能需要手动修改WEB端设置，需要关闭对应每个虚拟机的硬件嵌套虚拟化，如下图
图片
先停止虚拟机再修改，修改完后再开机才能使用NOVNC，不关闭可能导致这个虚拟机有BUG无法使用
如果强行安装PVE开KVM，启动不了的也可以关闭这个选项试试能不能启动虚拟机
TIP
开设虚拟机前请使用screen挂起执行，避免开设时间过长，SSH不稳定导致中间执行中断
开设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，需要宿主机至少有一个/64的子网
国际
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
国内
shell
curl -L https://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/buildvm.sh -o buildvm.sh && chmod +x buildvm.sh
使用方法 ​
  • 系统支持： 
    • x86_64架构的详见 跳转 中列出的系统，使用时只需写文件名字，不需要.qcow2尾缀
    • arm架构的详见 跳转 中列出的系统，使用时只需要写系统名字+系统版本号，如ubuntu20、ubutnu22这种
TIP
注意这里的用户名不能是纯数字，会造成cloudinit出问题，最好是纯英文或英文开头
shell
./buildvm.sh VMID 用户名 密码 CPU核数 内存 硬盘 SSH端口 80端口 443端口 外网端口起 外网端口止 系统 存储盘 独立IPV6地址(留空默认N)
测试示例 ​
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
qm stop 102
 qm destroy 102
 iptables -t nat -F
 iptables -t filter -F
diff --git a/assets/guide_pve_lxc.md.f1c965da.js b/assets/guide_pve_lxc.md.4b42cede.js
similarity index 99%
rename from assets/guide_pve_lxc.md.f1c965da.js
rename to assets/guide_pve_lxc.md.4b42cede.js
index 808a41ba52..d050031ebc 100644
--- a/assets/guide_pve_lxc.md.f1c965da.js
+++ b/assets/guide_pve_lxc.md.4b42cede.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/pve_lxc.md","filePath":"guide/pve_lxc.md","lastUpdated":1692790731000}'),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，需要宿主机至少有一个/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://ghproxy.com/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
pct stop 102
+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":1692790817000}'),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，需要宿主机至少有一个/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://ghproxy.com/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
pct stop 102
 pct destroy 102
 rm -rf ct102
 iptables -t nat -F
diff --git a/assets/guide_pve_lxc.md.f1c965da.lean.js b/assets/guide_pve_lxc.md.4b42cede.lean.js
similarity index 99%
rename from assets/guide_pve_lxc.md.f1c965da.lean.js
rename to assets/guide_pve_lxc.md.4b42cede.lean.js
index 808a41ba52..d050031ebc 100644
--- a/assets/guide_pve_lxc.md.f1c965da.lean.js
+++ b/assets/guide_pve_lxc.md.4b42cede.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/pve_lxc.md","filePath":"guide/pve_lxc.md","lastUpdated":1692790731000}'),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，需要宿主机至少有一个/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://ghproxy.com/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
pct stop 102
+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":1692790817000}'),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，需要宿主机至少有一个/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://ghproxy.com/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
pct stop 102
 pct destroy 102
 rm -rf ct102
 iptables -t nat -F
diff --git a/assets/guide_pve_precheck.md.e8cf1b1e.js b/assets/guide_pve_precheck.md.ef9a9e48.js
similarity index 99%
rename from assets/guide_pve_precheck.md.e8cf1b1e.js
rename to assets/guide_pve_precheck.md.ef9a9e48.js
index 17822b0d83..8570899b91 100644
--- a/assets/guide_pve_precheck.md.e8cf1b1e.js
+++ b/assets/guide_pve_precheck.md.ef9a9e48.js
@@ -1 +1 @@
-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_precheck.md","filePath":"guide/pve_precheck.md","lastUpdated":1692790731000}'),e={name:"guide/pve_precheck.md"},n=l('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果有未适配的商家或机器欢迎联系@spiritlhl_bot，有空会尝试支持一下
各种要求 ​
建议debian在使用前尽量使用最新的稳定版本的系统
不要在动态IP的服务器上使用本套脚本(重启机器后自动切换本机IP的服务器暂不支持，重启机器后IP不自动切换的支持)
本项目只适配Debian系统(非Debian无法通过APT源安装，官方只给了Debian的镜像，其他系统只能使用ISO安装)
  • 系统要求：Debian 8+
TIP
建议debian11而不是debian12，因为后者是beta版本，debian11安装的才是稳定版
  • 硬件要求：2核2G内存x86_64或arm架构服务器硬盘至少20G
  • 可开KVM的硬件要求：VM-X或AMD-V支持 (部分VPS和全部独服支持)
  • 如果硬件或系统需求不满足，可使用LXD批量开LXC容器跳转
WARNING
内存开点swap免得机器炸了
开设虚拟内存(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://ghproxy.com/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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/check_kernal.sh)
如果你需要更新IPV6信息再查询，那么执行以下命令后再查询
bash
rm -rf /usr/local/bin/pve_ipv6*


',28),o=[n];function t(c,r,i,h,C,d){return a(),p("div",null,o)}const A=s(e,[["render",t]]);export{D as __pageData,A as default};
+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_precheck.md","filePath":"guide/pve_precheck.md","lastUpdated":1692790817000}'),e={name:"guide/pve_precheck.md"},n=l('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果有未适配的商家或机器欢迎联系@spiritlhl_bot，有空会尝试支持一下
各种要求 ​
建议debian在使用前尽量使用最新的稳定版本的系统
不要在动态IP的服务器上使用本套脚本(重启机器后自动切换本机IP的服务器暂不支持，重启机器后IP不自动切换的支持)
本项目只适配Debian系统(非Debian无法通过APT源安装，官方只给了Debian的镜像，其他系统只能使用ISO安装)
  • 系统要求：Debian 8+
TIP
建议debian11而不是debian12，因为后者是beta版本，debian11安装的才是稳定版
  • 硬件要求：2核2G内存x86_64或arm架构服务器硬盘至少20G
  • 可开KVM的硬件要求：VM-X或AMD-V支持 (部分VPS和全部独服支持)
  • 如果硬件或系统需求不满足，可使用LXD批量开LXC容器跳转
WARNING
内存开点swap免得机器炸了
开设虚拟内存(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://ghproxy.com/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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/check_kernal.sh)
如果你需要更新IPV6信息再查询，那么执行以下命令后再查询
bash
rm -rf /usr/local/bin/pve_ipv6*


',28),o=[n];function t(c,r,i,h,C,d){return a(),p("div",null,o)}const A=s(e,[["render",t]]);export{D as __pageData,A as default};
diff --git a/assets/guide_pve_precheck.md.e8cf1b1e.lean.js b/assets/guide_pve_precheck.md.ef9a9e48.lean.js
similarity index 99%
rename from assets/guide_pve_precheck.md.e8cf1b1e.lean.js
rename to assets/guide_pve_precheck.md.ef9a9e48.lean.js
index 17822b0d83..8570899b91 100644
--- a/assets/guide_pve_precheck.md.e8cf1b1e.lean.js
+++ b/assets/guide_pve_precheck.md.ef9a9e48.lean.js
@@ -1 +1 @@
-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_precheck.md","filePath":"guide/pve_precheck.md","lastUpdated":1692790731000}'),e={name:"guide/pve_precheck.md"},n=l('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果有未适配的商家或机器欢迎联系@spiritlhl_bot，有空会尝试支持一下
各种要求 ​
建议debian在使用前尽量使用最新的稳定版本的系统
不要在动态IP的服务器上使用本套脚本(重启机器后自动切换本机IP的服务器暂不支持，重启机器后IP不自动切换的支持)
本项目只适配Debian系统(非Debian无法通过APT源安装，官方只给了Debian的镜像，其他系统只能使用ISO安装)
  • 系统要求：Debian 8+
TIP
建议debian11而不是debian12，因为后者是beta版本，debian11安装的才是稳定版
  • 硬件要求：2核2G内存x86_64或arm架构服务器硬盘至少20G
  • 可开KVM的硬件要求：VM-X或AMD-V支持 (部分VPS和全部独服支持)
  • 如果硬件或系统需求不满足，可使用LXD批量开LXC容器跳转
WARNING
内存开点swap免得机器炸了
开设虚拟内存(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://ghproxy.com/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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/check_kernal.sh)
如果你需要更新IPV6信息再查询，那么执行以下命令后再查询
bash
rm -rf /usr/local/bin/pve_ipv6*


',28),o=[n];function t(c,r,i,h,C,d){return a(),p("div",null,o)}const A=s(e,[["render",t]]);export{D as __pageData,A as default};
+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_precheck.md","filePath":"guide/pve_precheck.md","lastUpdated":1692790817000}'),e={name:"guide/pve_precheck.md"},n=l('
前言 ​
以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了
如果有未适配的商家或机器欢迎联系@spiritlhl_bot，有空会尝试支持一下
各种要求 ​
建议debian在使用前尽量使用最新的稳定版本的系统
不要在动态IP的服务器上使用本套脚本(重启机器后自动切换本机IP的服务器暂不支持，重启机器后IP不自动切换的支持)
本项目只适配Debian系统(非Debian无法通过APT源安装，官方只给了Debian的镜像，其他系统只能使用ISO安装)
  • 系统要求：Debian 8+
TIP
建议debian11而不是debian12，因为后者是beta版本，debian11安装的才是稳定版
  • 硬件要求：2核2G内存x86_64或arm架构服务器硬盘至少20G
  • 可开KVM的硬件要求：VM-X或AMD-V支持 (部分VPS和全部独服支持)
  • 如果硬件或系统需求不满足，可使用LXD批量开LXC容器跳转
WARNING
内存开点swap免得机器炸了
开设虚拟内存(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://ghproxy.com/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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/check_kernal.sh)
如果你需要更新IPV6信息再查询，那么执行以下命令后再查询
bash
rm -rf /usr/local/bin/pve_ipv6*


',28),o=[n];function t(c,r,i,h,C,d){return a(),p("div",null,o)}const A=s(e,[["render",t]]);export{D as __pageData,A as default};
diff --git a/assets/guide_pve_qa.md.7ed699f2.js b/assets/guide_pve_qa.md.a4512ae1.js
similarity index 99%
rename from assets/guide_pve_qa.md.7ed699f2.js
rename to assets/guide_pve_qa.md.a4512ae1.js
index d3015edc35..3458c635d9 100644
--- a/assets/guide_pve_qa.md.7ed699f2.js
+++ b/assets/guide_pve_qa.md.a4512ae1.js
@@ -1,4 +1,4 @@
-import{_ as a,v as s,b as e,R as n}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_qa.md","filePath":"guide/pve_qa.md","lastUpdated":1692790731000}'),t={name:"guide/pve_qa.md"},l=n(`
解惑 ​
安装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 f=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_qa.md","filePath":"guide/pve_qa.md","lastUpdated":1692790817000}'),t={name:"guide/pve_qa.md"},l=n(`
解惑 ​
安装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
diff --git a/assets/guide_pve_qa.md.7ed699f2.lean.js b/assets/guide_pve_qa.md.a4512ae1.lean.js
similarity index 99%
rename from assets/guide_pve_qa.md.7ed699f2.lean.js
rename to assets/guide_pve_qa.md.a4512ae1.lean.js
index d3015edc35..3458c635d9 100644
--- a/assets/guide_pve_qa.md.7ed699f2.lean.js
+++ b/assets/guide_pve_qa.md.a4512ae1.lean.js
@@ -1,4 +1,4 @@
-import{_ as a,v as s,b as e,R as n}from"./chunks/framework.70afa331.js";const f=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_qa.md","filePath":"guide/pve_qa.md","lastUpdated":1692790731000}'),t={name:"guide/pve_qa.md"},l=n(`
解惑 ​
安装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 f=JSON.parse('{"title":"解惑","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"guide/pve_qa.md","filePath":"guide/pve_qa.md","lastUpdated":1692790817000}'),t={name:"guide/pve_qa.md"},l=n(`
解惑 ​
安装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
diff --git a/assets/guide_pve_thanks.md.c463b3ed.js b/assets/guide_pve_thanks.md.b6a7624b.js
similarity index 97%
rename from assets/guide_pve_thanks.md.c463b3ed.js
rename to assets/guide_pve_thanks.md.b6a7624b.js
index 08fffe40a7..4d2f2bd0a6 100644
--- a/assets/guide_pve_thanks.md.c463b3ed.js
+++ b/assets/guide_pve_thanks.md.b6a7624b.js
@@ -1 +1 @@
-import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/pve_thanks.md","filePath":"guide/pve_thanks.md","lastUpdated":1692790731000}'),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
感谢 @Ella-Alinda 提供的PVE指导
',14),n=[p];function s(h,i,l,m,c,b){return e(),t("div",null,n)}const d=r(o,[["render",s]]);export{u as __pageData,d as default};
+import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/pve_thanks.md","filePath":"guide/pve_thanks.md","lastUpdated":1692790817000}'),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
感谢 @Ella-Alinda 提供的PVE指导
',14),n=[p];function s(h,i,l,m,c,b){return e(),t("div",null,n)}const d=r(o,[["render",s]]);export{u as __pageData,d as default};
diff --git a/assets/guide_pve_thanks.md.c463b3ed.lean.js b/assets/guide_pve_thanks.md.b6a7624b.lean.js
similarity index 97%
rename from assets/guide_pve_thanks.md.c463b3ed.lean.js
rename to assets/guide_pve_thanks.md.b6a7624b.lean.js
index 08fffe40a7..4d2f2bd0a6 100644
--- a/assets/guide_pve_thanks.md.c463b3ed.lean.js
+++ b/assets/guide_pve_thanks.md.b6a7624b.lean.js
@@ -1 +1 @@
-import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/pve_thanks.md","filePath":"guide/pve_thanks.md","lastUpdated":1692790731000}'),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
感谢 @Ella-Alinda 提供的PVE指导
',14),n=[p];function s(h,i,l,m,c,b){return e(),t("div",null,n)}const d=r(o,[["render",s]]);export{u as __pageData,d as default};
+import{_ as r,v as e,b as t,R as a}from"./chunks/framework.70afa331.js";const u=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"guide/pve_thanks.md","filePath":"guide/pve_thanks.md","lastUpdated":1692790817000}'),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
感谢 @Ella-Alinda 提供的PVE指导
',14),n=[p];function s(h,i,l,m,c,b){return e(),t("div",null,n)}const d=r(o,[["render",s]]);export{u as __pageData,d as default};
diff --git a/assets/index.md.20391d7d.js b/assets/index.md.09f90416.js
similarity index 96%
rename from assets/index.md.20391d7d.js
rename to assets/index.md.09f90416.js
index bfe595bfab..9e57ef7d81 100644
--- a/assets/index.md.20391d7d.js
+++ b/assets/index.md.09f90416.js
@@ -1 +1 @@
-import{_ as t,v as e,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"一键虚拟化项目","titleTemplate":"开源、易于使用的服务器虚拟化项目","description":"","frontmatter":{"layout":"home","title":"一键虚拟化项目","titleTemplate":"开源、易于使用的服务器虚拟化项目","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":1692790731000}'),i={name:"index.md"};function s(n,d,l,r,o,p){return e(),a("div")}const u=t(i,[["render",s]]);export{m as __pageData,u as default};
+import{_ as t,v as e,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"一键虚拟化项目","titleTemplate":"开源、易于使用的服务器虚拟化项目","description":"","frontmatter":{"layout":"home","title":"一键虚拟化项目","titleTemplate":"开源、易于使用的服务器虚拟化项目","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":1692790817000}'),i={name:"index.md"};function s(n,d,l,r,o,p){return e(),a("div")}const u=t(i,[["render",s]]);export{m as __pageData,u as default};
diff --git a/assets/index.md.20391d7d.lean.js b/assets/index.md.09f90416.lean.js
similarity index 96%
rename from assets/index.md.20391d7d.lean.js
rename to assets/index.md.09f90416.lean.js
index bfe595bfab..9e57ef7d81 100644
--- a/assets/index.md.20391d7d.lean.js
+++ b/assets/index.md.09f90416.lean.js
@@ -1 +1 @@
-import{_ as t,v as e,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"一键虚拟化项目","titleTemplate":"开源、易于使用的服务器虚拟化项目","description":"","frontmatter":{"layout":"home","title":"一键虚拟化项目","titleTemplate":"开源、易于使用的服务器虚拟化项目","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":1692790731000}'),i={name:"index.md"};function s(n,d,l,r,o,p){return e(),a("div")}const u=t(i,[["render",s]]);export{m as __pageData,u as default};
+import{_ as t,v as e,b as a}from"./chunks/framework.70afa331.js";const m=JSON.parse('{"title":"一键虚拟化项目","titleTemplate":"开源、易于使用的服务器虚拟化项目","description":"","frontmatter":{"layout":"home","title":"一键虚拟化项目","titleTemplate":"开源、易于使用的服务器虚拟化项目","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":1692790817000}'),i={name:"index.md"};function s(n,d,l,r,o,p){return e(),a("div")}const u=t(i,[["render",s]]);export{m as __pageData,u as default};
diff --git a/case/case1.html b/case/case1.html
index f521f11443..7d02f0119c 100644
--- a/case/case1.html
+++ b/case/case1.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -46,8 +46,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 903b3682ef..ba356bc88b 100644
--- a/case/case2.html
+++ b/case/case2.html
@@ -11,15 +11,15 @@
     
     
     
-    
+    
     
     
     
     
   
   
-    
一键虚拟化项目
简体中文
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
echo 1 | bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh)
或
bash
echo 1 | bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecs/raw/main/ecs.sh)
或
echo 1 | bash <(wget -qO- bash.spiritlhl.net/ecs)
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的问题
  • [ ] 端口检测(检测是否被墙)--由fscarmen的PR以及本人的技术思路提供 - 待修复
友链 ​
测评频道 ​
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
echo 1 | bash <(wget -qO- --no-check-certificate https://gitlab.com/spiritysdx/za/-/raw/main/ecs.sh)
或
bash
echo 1 | bash <(wget -qO- --no-check-certificate https://github.com/spiritLHLS/ecs/raw/main/ecs.sh)
或
echo 1 | bash <(wget -qO- bash.spiritlhl.net/ecs)
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的问题
  • [ ] 端口检测(检测是否被墙)--由fscarmen的PR以及本人的技术思路提供 - 待修复
友链 ​
测评频道 ​
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 4b62a08847..d7af9ba3e7 100644
--- a/case/case3.html
+++ b/case/case3.html
@@ -11,15 +11,15 @@
     
     
     
-    
+    
     
     
     
     
   
   
-    
一键虚拟化项目
简体中文
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 ec219e057e..118417b325 100644
--- a/case/case4.html
+++ b/case/case4.html
@@ -11,15 +11,15 @@
     
     
     
-    
+    
     
     
     
     
   
   
-    
一键虚拟化项目
简体中文
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 4ab92665c2..6fc7544adc 100644
--- a/case/case5.html
+++ b/case/case5.html
@@ -11,15 +11,15 @@
     
     
     
-    
+    
     
     
     
     
   
   
-    
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
On this page
仓库 ​
https://github.com/spiritLHLS/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/spiritLHLS/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
Thanks ​
Base on https://github.com/spiritLHLS/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/spiritLHLS/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/spiritLHLS/convoypanel-scripts/raw/main/installconvoy.sh -o installconvoy.sh && chmod +x installconvoy.sh && bash installconvoy.sh
Thanks ​
Base on https://github.com/spiritLHLS/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 825d5f6a3e..105d271311 100644
--- a/case/index.html
+++ b/case/index.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,7 +19,7 @@
   
   
     
一键虚拟化项目
简体中文
English
简体中文
English
Appearance
Linux相关项目
与Linux相关的一些一键脚本项目
查看项目 →
注意事项
注意每个项目说明，部分项目有可能对系统造成不可修复的错误，需要重装系统，请仔细查看说明

-    
+    
     
   
 
\ No newline at end of file
diff --git a/developer/index.html b/developer/index.html
index d2cf6bc725..e093e846e5 100644
--- a/developer/index.html
+++ b/developer/index.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,7 +19,7 @@
   
   
     
-    
+    
     
   
 
\ No newline at end of file
diff --git a/developer/l10n.html b/developer/l10n.html
index cb0bec04a4..2d10a27bfe 100644
--- a/developer/l10n.html
+++ b/developer/l10n.html
@@ -11,15 +11,15 @@
     
     
     
-    
+    
     
     
     
     
   
   
-    
一键虚拟化项目
简体中文
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_US/developer/index.html b/en_US/developer/index.html
index 467d301b35..870c5b3f09 100644
--- a/en_US/developer/index.html
+++ b/en_US/developer/index.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -19,7 +19,7 @@
   
   
     
-    
+    
     
   
 
\ No newline at end of file
diff --git a/en_US/developer/l10n.html b/en_US/developer/l10n.html
index 70a328dc35..0903db643c 100644
--- a/en_US/developer/l10n.html
+++ b/en_US/developer/l10n.html
@@ -11,15 +11,15 @@
     
     
     
-    
+    
     
     
     
     
   
   
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
You can follow these steps to support localization when developing new features
Introduction ​
  1. You can directly use the text configuration already available in /resource/l10n/en-US.toml to replace the text in the new feature.
  2. If there is new text in the new feature, please refer to the configuration text in en-US.toml, pull the new text into the configuration files of other languages such as en-US.toml, and add translations.
Adding a new localized text file ​
  1. Add a new language text configuration in /resource/l10n/.
  2. Pull existing text configurations from other languages in the new language text configuration.
  3. Add translations for the new language text configuration.

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

+    
     
   
 
\ No newline at end of file
diff --git a/en_US/guide/dashboard.html b/en_US/guide/dashboard.html
index a155c6d08e..62c3d86e1f 100644
--- a/en_US/guide/dashboard.html
+++ b/en_US/guide/dashboard.html
@@ -11,15 +11,15 @@
     
     
     
-    
+    
     
     
     
     
   
   
-    
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



-    
+    
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
index ea4a4f80b3..48f1971bbe 100644
--- a/en_US/guide/dashboardq.html
+++ b/en_US/guide/dashboardq.html
@@ -11,15 +11,15 @@
     
     
     
-    
+    
     
     
     
     
   
   
-    
-    
+    
+    
     
   
 
\ No newline at end of file
diff --git a/en_US/guide/docker_build.html b/en_US/guide/docker_build.html
index f56d0b0e2a..706c3d14e1 100644
--- a/en_US/guide/docker_build.html
+++ b/en_US/guide/docker_build.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -22,8 +22,8 @@
 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
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.
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.
Uninstall all Docker containers and images ​
shell
docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)
 rm -rf dclog
-ls

-    
+ls

+    
     
   
 
\ No newline at end of file
diff --git a/en_US/guide/docker_custom.html b/en_US/guide/docker_custom.html
index 1cdb07d816..49b4541234 100644
--- a/en_US/guide/docker_custom.html
+++ b/en_US/guide/docker_custom.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -27,8 +27,8 @@
 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
Command:
shell
docker ps -a
Query for containers with a prefix of 'firefox' 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 jlesage/firefox
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

-    
+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
Command:
shell
docker ps -a
Query for containers with a prefix of 'firefox' 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 jlesage/firefox
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
index d5dbdb68e5..95235f4d13 100644
--- a/en_US/guide/docker_install.html
+++ b/en_US/guide/docker_install.html
@@ -11,15 +11,15 @@
     
     
     
-    
+    
     
     
     
     
   
   
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Preface ​
Support for running Docker virtualization on various systems, including Linux, Android, and Windows.
Environment Setup ​
  • Check the environment
  • Install Docker and other prerequisite components
  • Download some default configuration scripts required by default
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
Setting Up Virtual Memory ​
WARNING
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

-    
+    
One Click Virtualization
English
简体中文
English
简体中文
Appearance
On this page
Preface ​
Support for running Docker virtualization on various systems, including Linux, Android, and Windows.
Environment Setup ​
  • Check the environment
  • Install Docker and other prerequisite components
  • Download some default configuration scripts required by default
Command:
shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh
Setting Up Virtual Memory ​
WARNING
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

+    
     
   
 
\ No newline at end of file
diff --git a/en_US/guide/docker_precheck.html b/en_US/guide/docker_precheck.html
index b9cfba8e94..9dad1d6838 100644
--- a/en_US/guide/docker_precheck.html
+++ b/en_US/guide/docker_precheck.html
@@ -11,15 +11,15 @@
     
     
     
-    
+    
     
     
     
     
   
   
-    
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.
Project Highlights ​
This project involves bulk or individual provisioning of NAT servers using Docker containers.
The default operating system used is Debian. Each container comes with one external SSH port and 25 consistent internal and external ports.
The containers created by default are non-privileged and do not establish communication between the Docker daemon on the host and the containers. As a result, containers nested within Docker virtualized NAT servers on the host will not function.
Due to CPU and memory limitations set on the host without utilizing cgroup drivers within containers, any server testing scripts run inside containers to assess available resources will be ineffective. The displayed resources will reflect those of the host.
Since the majority of cloud servers do not enable the 'pquota' option for the XFS file system, the default configuration involves sharing the host's hard drive, thus preventing the restriction of individual container disk sizes.
Configuration Requirements ​
The system should have Docker installed to be operational. As long as the network can connect to GitHub's raw interface, it can be used. Hardware configuration requirements are minimal, as long as they are adequate; a spare 3GB of hard disk space is sufficient.
It is recommended to increase the available SWAP virtual memory prior to provisioning NAT servers to prevent potential host performance issues due to sudden memory spikes. Link
PS: If hardware resources are somewhat limited and more restrictions are necessary, including configuration of individual IPv6 addresses and disk size limitations, consider utilizing LXD to create batch LXC virtualized containers. Link
PS: If hardware resources are abundant and ample, consider using Proxmox Virtual Environment (PVE) to provision batch KVM virtualized machines. Link
Please note that the original formatting has been preserved and enclosed within and for your convenience during copying. No character escaping has been applied.

-    
+    
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.
Project Highlights ​
This project involves bulk or individual provisioning of NAT servers using Docker containers.
The default operating system used is Debian. Each container comes with one external SSH port and 25 consistent internal and external ports.
The containers created by default are non-privileged and do not establish communication between the Docker daemon on the host and the containers. As a result, containers nested within Docker virtualized NAT servers on the host will not function.
Due to CPU and memory limitations set on the host without utilizing cgroup drivers within containers, any server testing scripts run inside containers to assess available resources will be ineffective. The displayed resources will reflect those of the host.
Since the majority of cloud servers do not enable the 'pquota' option for the XFS file system, the default configuration involves sharing the host's hard drive, thus preventing the restriction of individual container disk sizes.
Configuration Requirements ​
The system should have Docker installed to be operational. As long as the network can connect to GitHub's raw interface, it can be used. Hardware configuration requirements are minimal, as long as they are adequate; a spare 3GB of hard disk space is sufficient.
It is recommended to increase the available SWAP virtual memory prior to provisioning NAT servers to prevent potential host performance issues due to sudden memory spikes. Link
PS: If hardware resources are somewhat limited and more restrictions are necessary, including configuration of individual IPv6 addresses and disk size limitations, consider utilizing LXD to create batch LXC virtualized containers. Link
PS: If hardware resources are abundant and ample, consider using Proxmox Virtual Environment (PVE) to provision batch KVM virtualized machines. Link
Please note that the original formatting has been preserved and enclosed within and for your convenience during copying. No character escaping has been applied.

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

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

+    
     
   
 
\ No newline at end of file
diff --git a/en_US/guide/docker_thanks.html b/en_US/guide/docker_thanks.html
index b226ccca6a..a566449e35 100644
--- a/en_US/guide/docker_thanks.html
+++ b/en_US/guide/docker_thanks.html
@@ -11,15 +11,15 @@
     
     
     
-    
+    
     
     
     
     
   
   
-    
One Click Virtualization
English
简体中文
English
简体中文
Appearance

-    
+    
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
index 55c6d101c9..d30bb143bd 100644
--- a/en_US/guide/lxd_custom.html
+++ b/en_US/guide/lxd_custom.html
@@ -11,15 +11,15 @@
     
     
     
-    
+    
     
     
     
     
   
   
-    
-    
+    
+    
     
   
 
\ No newline at end of file
diff --git a/en_US/guide/lxd_extra_config.html b/en_US/guide/lxd_extra_config.html
index 68a10178a7..8cfe7a3fb0 100644
--- a/en_US/guide/lxd_extra_config.html
+++ b/en_US/guide/lxd_extra_config.html
@@ -11,7 +11,7 @@
     
     
     
-    
+    
     
     
     
@@ -29,8 +29,8 @@
 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!

-    
+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 index 23d598caac..cd88876679 100644 --- a/en_US/guide/lxd_install.html +++ b/en_US/guide/lxd_install.html @@ -11,7 +11,7 @@ - + @@ -23,8 +23,8 @@ ufw disable

Enabling Virtual Memory SWAP ​

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

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

Command:

shell
curl -L https://raw.githubusercontent.com/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.

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.

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.

- +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.

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.

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 index f00ea7d6d7..d9c30912f0 100644 --- a/en_US/guide/lxd_lxc.html +++ b/en_US/guide/lxd_lxc.html @@ -11,7 +11,7 @@ - + @@ -39,8 +39,8 @@ rm -rf /root/add_more.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.sh -O /usr/local/bin/ssh.sh && chmod +x /usr/local/bin/ssh.sh
-wget https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/alpinessh.sh -O /usr/local/bin/alpinessh.sh && chmod +x /usr/local/bin/alpinessh.sh

Just download the other one-click scripts yourself.

 - +wget https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/alpinessh.sh -O /usr/local/bin/alpinessh.sh && chmod +x /usr/local/bin/alpinessh.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 index 882a7eb31a..a815fd9f91 100644 --- a/en_US/guide/lxd_precheck.html +++ b/en_US/guide/lxd_precheck.html @@ -11,15 +11,15 @@ - + -
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!

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.

  • 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)
- +
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!

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.

  • 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 index 66a1d74487..01acbd7fb6 100644 --- a/en_US/guide/lxd_qa.html +++ b/en_US/guide/lxd_qa.html @@ -11,7 +11,7 @@ - + @@ -29,8 +29,8 @@ Edit the ```/etc/default/grub`` file and add ``cgroup_enable=memory`` to the end of the parameters in ``GRUB_CMDLINE_LINUX_DEFAULT``.

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash cgroup_enable=memory"

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

- +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 index cc0a574b3c..56897ae001 100644 --- a/en_US/guide/lxd_thanks.html +++ b/en_US/guide/lxd_thanks.html @@ -11,15 +11,15 @@ - + -
One Click Virtualization

English

简体中文

English

简体中文

Appearance

- +
One Click Virtualization

English

简体中文

English

简体中文

Appearance

+ \ No newline at end of file diff --git a/en_US/guide/pve_custom.html b/en_US/guide/pve_custom.html index 8492f3d4f7..cd62288c6d 100644 --- a/en_US/guide/pve_custom.html +++ b/en_US/guide/pve_custom.html @@ -11,7 +11,7 @@ - + @@ -31,8 +31,8 @@ --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!

 - +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 index f3963a8dc3..9531513505 100644 --- a/en_US/guide/pve_install.html +++ b/en_US/guide/pve_install.html @@ -11,15 +11,15 @@ - + -
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

I recommend debian11 instead of debian12, because the latter is a stable version but I don't know if there are any undiscovered bugs, and the debian11 installation is currently more stable.

  • 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.

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.

  • 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

- +
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

I recommend debian11 instead of debian12, because the latter is a stable version but I don't know if there are any undiscovered bugs, and the debian11 installation is currently more stable.

  • 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.

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.

  • 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

+ \ No newline at end of file diff --git a/en_US/guide/pve_kvm.html b/en_US/guide/pve_kvm.html index a40f13366a..671f89cc4f 100644 --- a/en_US/guide/pve_kvm.html +++ b/en_US/guide/pve_kvm.html @@ -11,7 +11,7 @@ - + @@ -37,8 +37,8 @@ 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.

Command:

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

Example of Creation ​

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)
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 ​

Command:

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

Example Usage ​

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)
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 ​

Command:

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

Example Usage ​

shell
./buildvm_onlyv6.sh VMID username password CPU_cores memory_GB disk_GB operating_system storage_disk
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
- +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 index f2959ce1db..51bfb8e787 100644 --- a/en_US/guide/pve_lxc.html +++ b/en_US/guide/pve_lxc.html @@ -11,7 +11,7 @@ - + @@ -36,8 +36,8 @@ iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore

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 ​

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
- +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 index 3c30918a02..f7c50ddf4f 100644 --- a/en_US/guide/pve_precheck.html +++ b/en_US/guide/pve_precheck.html @@ -11,15 +11,15 @@ - + -
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!

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)

This project is only adapted to Debian system (non-Debian can not be installed through the APT source, the official only gave the Debian image, other systems can only use ISO installation)

  • 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

WARNING

I'm not sure if I'm going to be able to do this, but I'm going to be able to do it in a few minutes.

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*


- +
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!

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)

This project is only adapted to Debian system (non-Debian can not be installed through the APT source, the official only gave the Debian image, other systems can only use ISO installation)

  • 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

WARNING

I'm not sure if I'm going to be able to do this, but I'm going to be able to do it in a few minutes.

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*


+ \ No newline at end of file diff --git a/en_US/guide/pve_qa.html b/en_US/guide/pve_qa.html index 1a0def5b7c..1c21da0521 100644 --- a/en_US/guide/pve_qa.html +++ b/en_US/guide/pve_qa.html @@ -11,7 +11,7 @@ - + @@ -27,8 +27,8 @@ iptables -t filter -F service networking restart systemctl restart networking.service -iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore

Verified VPS Providers ​

VPS Providers Offering KVM Virtualization with NAT ​

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

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

Currently Unavailable or Unsupported Providers ​

OVH

- +iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore

Verified VPS Providers ​

VPS Providers Offering KVM Virtualization with NAT ​

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

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

Currently Unavailable or Unsupported Providers ​

OVH

+ \ No newline at end of file diff --git a/en_US/guide/pve_thanks.html b/en_US/guide/pve_thanks.html index 86eda22c3b..faede5e9da 100644 --- a/en_US/guide/pve_thanks.html +++ b/en_US/guide/pve_thanks.html @@ -11,15 +11,15 @@ - + -
One Click Virtualization

English

简体中文

English

简体中文

Appearance

- +
One Click Virtualization

English

简体中文

English

简体中文

Appearance

+ \ No newline at end of file diff --git a/en_US/index.html b/en_US/index.html index f3619bc0d5..779a5c708a 100644 --- a/en_US/index.html +++ b/en_US/index.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@
One Click Virtualization

English

简体中文

English

简体中文

Appearance

One Click Virtualization

Open source, easy to use server virtualization project

Learn More →

One Click Use

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

Based on mainstream systems development

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

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 025a9c9235..38c34800ff 100644 --- a/guide/dashboard.html +++ b/guide/dashboard.html @@ -11,15 +11,15 @@ - + -
一键虚拟化项目

简体中文

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 cc2f1a43ea..c175bf69de 100644 --- a/guide/dashboardq.html +++ b/guide/dashboardq.html @@ -11,15 +11,15 @@ - + -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

Give me a cup of coffee.

https://ko-fi.com/spiritlhl

USDT-TRC20

bash
TZ7nf8XAL9zQUo63xokazaBdCPeCgPfcwd
- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

Give me a cup of coffee.

https://ko-fi.com/spiritlhl

USDT-TRC20

bash
TZ7nf8XAL9zQUo63xokazaBdCPeCgPfcwd
+ \ No newline at end of file diff --git a/guide/docker_build.html b/guide/docker_build.html index 5a699ccae0..2edc5a2259 100644 --- a/guide/docker_build.html +++ b/guide/docker_build.html @@ -11,7 +11,7 @@ - + @@ -20,8 +20,8 @@
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

两种开设方式

单独开设 ​

下载脚本

国际

shell
curl -L https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh

国内

shell
curl -L https://ghproxy.com/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 system

目前system仅支持选择alpine或debian，默认是debian

示例 ​

以下为开设的示例容器的信息：

属性值
容器名字test
SSH登录的用户名root
SSH登录的密码123456
CPU核数1
内存大小512MB
SSH端口25000
内外网映射端口一致的区间34975到35000
系统debian
shell
./onedocker.sh test 1 512 123456 25000 34975 35000 debian

删除示例

shell
docker rm -f test
 rm -rf test
-ls

进入示例

shell
docker exec -it test /bin/bash

要退出容器就执行exit退出。

查询信息 ​

shell
cat 容器名字

输出格式

容器名字 SSH端口 登陆的root密码 核数 内存 外网端口起 外网端口止

批量开设 ​

  • 批量多次运行继承配置生成
  • 生成多个时为避免SSH连接中断建议在screen中执行

国际

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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh

查询批量开设的信息 ​

shell
cat dclog

输出格式

容器名字 SSH端口 登陆的root密码 核数 内存 外网端口起 外网端口止

一行一个容器对应的信息

卸载所有docker容器和镜像 ​

shell
docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)
- +ls

进入示例

shell
docker exec -it test /bin/bash

要退出容器就执行exit退出。

查询信息 ​

shell
cat 容器名字

输出格式

容器名字 SSH端口 登陆的root密码 核数 内存 外网端口起 外网端口止

批量开设 ​

国际

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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/onedocker.sh -o onedocker.sh && chmod +x onedocker.sh

查询批量开设的信息 ​

shell
cat dclog

输出格式

容器名字 SSH端口 登陆的root密码 核数 内存 外网端口起 外网端口止

一行一个容器对应的信息

卸载所有docker容器和镜像 ​

shell
docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)
+ \ No newline at end of file diff --git a/guide/docker_custom.html b/guide/docker_custom.html index a091f1bebb..631de87724 100644 --- a/guide/docker_custom.html +++ b/guide/docker_custom.html @@ -11,7 +11,7 @@ - + @@ -24,8 +24,8 @@ 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浏览器的容器 ​

宿主机需要至少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

删除

执行

shell
docker ps -a

查询name的前缀是firefox的容器，记录容器的ID用

shell
docker rm -f 容器的ID

删除所有关联的容器后可用

shell
docker rmi jlesage/firefox

删除对应镜像

一键开设Desktop的容器 ​

完整的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://ghproxy.com/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
- +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 index 312c26a278..ea2bca09cb 100644 --- a/guide/docker_install.html +++ b/guide/docker_install.html @@ -11,15 +11,15 @@ - + -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统

环境预设 ​

  • 检测环境
  • 安装docker和其他预制组件
  • 下载默认需要的一些配置脚本

国际

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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh

开设虚拟内存 ​

WARNING

内存开点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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

支持开设 Docker 虚拟化的各系统，含 Linux、Android、Windows 系统

环境预设 ​

  • 检测环境
  • 安装docker和其他预制组件
  • 下载默认需要的一些配置脚本

国际

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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/docker/main/scripts/dockerinstall.sh -o dockerinstall.sh && chmod +x dockerinstall.sh && bash dockerinstall.sh

开设虚拟内存 ​

WARNING

内存开点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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/addswap/main/addswap.sh -o addswap.sh && chmod +x addswap.sh && bash addswap.sh
+ \ No newline at end of file diff --git a/guide/docker_precheck.html b/guide/docker_precheck.html index 445aa85838..fa2618c861 100644 --- a/guide/docker_precheck.html +++ b/guide/docker_precheck.html @@ -11,15 +11,15 @@ - + -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了

项目特点 ​

通过docker批量或单独开设NAT服务器(Bulk or individual NAT server provisioning via docker)

默认使用debian系统，每个容器自带1个外网ssh端口，25个内外网一致端口

默认创建的是非特权容器，且不挂载与宿主机的docker的守护进程之间的通信，所以宿主机创建的docker虚拟化的NAT服务器内无法再嵌套虚拟化docker

由于只是在宿主机进行了CPU和内存的限制未在容器内使用cgroup驱动，所以在容器内使用服务器测试脚本检测容器的可用资源是无效的，显示的会是宿主机的资源

由于大部分云服务器xfs文件系统不启用pquota选项，所以默认共享宿主机硬盘，无法限制每个容器的磁盘大小

配置要求 ​

系统可安装docker即可用，网络能连接Github的raw界面就能用，硬件配置只要不拉跨就行，空闲硬盘有3G就行

推荐在开设NAT服务器前先增加部分SWAP虚拟内存，避免突发的内存占用导致母鸡卡死 跳转

PS: 如果硬件资源只是好了一点，需要限制更多东西并需要配置IPV6独立地址和限制硬盘大小，可使用LXD批量开LXC虚拟化的容器 跳转

PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了

项目特点 ​

通过docker批量或单独开设NAT服务器(Bulk or individual NAT server provisioning via docker)

默认使用debian系统，每个容器自带1个外网ssh端口，25个内外网一致端口

默认创建的是非特权容器，且不挂载与宿主机的docker的守护进程之间的通信，所以宿主机创建的docker虚拟化的NAT服务器内无法再嵌套虚拟化docker

由于只是在宿主机进行了CPU和内存的限制未在容器内使用cgroup驱动，所以在容器内使用服务器测试脚本检测容器的可用资源是无效的，显示的会是宿主机的资源

由于大部分云服务器xfs文件系统不启用pquota选项，所以默认共享宿主机硬盘，无法限制每个容器的磁盘大小

配置要求 ​

系统可安装docker即可用，网络能连接Github的raw界面就能用，硬件配置只要不拉跨就行，空闲硬盘有3G就行

推荐在开设NAT服务器前先增加部分SWAP虚拟内存，避免突发的内存占用导致母鸡卡死 跳转

PS: 如果硬件资源只是好了一点，需要限制更多东西并需要配置IPV6独立地址和限制硬盘大小，可使用LXD批量开LXC虚拟化的容器 跳转

PS: 如果硬件非常好资源很多，可使用PVE批量开KVM虚拟化的虚拟机 跳转

+ \ No newline at end of file diff --git a/guide/docker_qa.html b/guide/docker_qa.html index f5d4410aa7..d910316b49 100644 --- a/guide/docker_qa.html +++ b/guide/docker_qa.html @@ -11,15 +11,15 @@ - + -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

解惑 ​

常见的一些docker命令 ​

查询某个容器的实时占用

docker stats 容器名字

进入某个容器

docker exec -it 容器名字 /bin/bash

清理 Docker 缓存，清理未使用的资源，包括镜像、容器、网络等

docker system prune -a

卸载所有docker的镜像和容器

docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)

查看对应容器日志

docker logs 容器名字或ID

查看docker整体的disk占用

docker system df

查看所有容器

docker ps -a

查看所有镜像

docker images

删除某个特定容器

docker rm -f 容器名字或ID

删除某个特定镜像

docker rmi 镜像名字或ID
- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

解惑 ​

常见的一些docker命令 ​

查询某个容器的实时占用

docker stats 容器名字

进入某个容器

docker exec -it 容器名字 /bin/bash

清理 Docker 缓存，清理未使用的资源，包括镜像、容器、网络等

docker system prune -a

卸载所有docker的镜像和容器

docker rm -f $(docker ps -aq); docker rmi $(docker images -aq)

查看对应容器日志

docker logs 容器名字或ID

查看docker整体的disk占用

docker system df

查看所有容器

docker ps -a

查看所有镜像

docker images

删除某个特定容器

docker rm -f 容器名字或ID

删除某个特定镜像

docker rmi 镜像名字或ID
+ \ No newline at end of file diff --git a/guide/docker_thanks.html b/guide/docker_thanks.html index 89c243733c..15f12d7f74 100644 --- a/guide/docker_thanks.html +++ b/guide/docker_thanks.html @@ -11,15 +11,15 @@ - + -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

+ \ No newline at end of file diff --git a/guide/lxd_custom.html b/guide/lxd_custom.html index a4fbaaec84..fd82130271 100644 --- a/guide/lxd_custom.html +++ b/guide/lxd_custom.html @@ -11,15 +11,15 @@ - + -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page
- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page
+ \ No newline at end of file diff --git a/guide/lxd_extra_config.html b/guide/lxd_extra_config.html index 695045e409..c6b497b0ac 100644 --- a/guide/lxd_extra_config.html +++ b/guide/lxd_extra_config.html @@ -11,7 +11,7 @@ - + @@ -29,8 +29,8 @@ 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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/rules.sh -o rules.sh && chmod +x rules.sh && bash rules.sh

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

国际

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://ghproxy.com/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://ghproxy.com/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的密码，其他一路默认就能使用面板了

- +snap install lxdmosaic

安装完毕后打开母鸡IP地址，按照提示设置admin的密码，其他一路默认就能使用面板了

 + \ No newline at end of file diff --git a/guide/lxd_install.html b/guide/lxd_install.html index bd130609ba..a095d29d64 100644 --- a/guide/lxd_install.html +++ b/guide/lxd_install.html @@ -11,7 +11,7 @@ - + @@ -23,8 +23,8 @@ 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://ghproxy.com/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命令是否有报错找不到

一键安装 ​

WARNING

如果是全新的服务器，务必保证apt update和apt install curl都无问题再执行本脚本

TIP

且自开机起最好等待5分钟后再执行以下命令，避免系统默认设置中就执行了本脚本导致apt源卡死

如果是Debian系的宿主机，务必在screen中执行本脚本，避免长期运行时SSH中断导致ZFS编译安装失败

这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的小鸡占的盘的大小的总和

环境安装过程中可能需要重启服务器以加载含zfs的内核，然后再次执行安装命令，一切以运行后命令行的提示为准

如果脚本提示重启系统后需要再次执行脚本，第二次执行安装脚本仍提示重启系统加载内核，那么意味着内核在上一次加载中失败了，最好重装宿主机系统为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://ghproxy.com/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

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

连接后再测试lxc命令是否有报错找不到

一键安装 ​

WARNING

如果是全新的服务器，务必保证apt update和apt install curl都无问题再执行本脚本

TIP

且自开机起最好等待5分钟后再执行以下命令，避免系统默认设置中就执行了本脚本导致apt源卡死

如果是Debian系的宿主机，务必在screen中执行本脚本，避免长期运行时SSH中断导致ZFS编译安装失败

这里的虚拟内存是说要开的SWAP大小，存储池则是你所有要开的小鸡占的盘的大小的总和

环境安装过程中可能需要重启服务器以加载含zfs的内核，然后再次执行安装命令，一切以运行后命令行的提示为准

如果脚本提示重启系统后需要再次执行脚本，第二次执行安装脚本仍提示重启系统加载内核，那么意味着内核在上一次加载中失败了，最好重装宿主机系统为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://ghproxy.com/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

+ \ No newline at end of file diff --git a/guide/lxd_lxc.html b/guide/lxd_lxc.html index a620046146..f911ada268 100644 --- a/guide/lxd_lxc.html +++ b/guide/lxd_lxc.html @@ -11,7 +11,7 @@ - + @@ -39,8 +39,8 @@ rm -rf /root/add_more.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.sh -O /usr/local/bin/ssh.sh && chmod +x /usr/local/bin/ssh.sh
-wget https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/alpinessh.sh -O /usr/local/bin/alpinessh.sh && chmod +x /usr/local/bin/alpinessh.sh

其他一键脚本自己对应下载回来就行了

 - +wget https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/alpinessh.sh -O /usr/local/bin/alpinessh.sh && chmod +x /usr/local/bin/alpinessh.sh

其他一键脚本自己对应下载回来就行了

 + \ No newline at end of file diff --git a/guide/lxd_precheck.html b/guide/lxd_precheck.html index a136e9f95e..d9965a6ecf 100644 --- a/guide/lxd_precheck.html +++ b/guide/lxd_precheck.html @@ -11,15 +11,15 @@ - + -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了

要求 ​

硬件要求:

  • 系统：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系统

  • 已屏蔽容器内可能用于滥用的工具包和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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/lxd/main/scripts/pre_check.sh)
- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了

要求 ​

硬件要求:

  • 系统：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系统

  • 已屏蔽容器内可能用于滥用的工具包和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://ghproxy.com/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 index 02299fa5f3..d4518f09ae 100644 --- a/guide/lxd_qa.html +++ b/guide/lxd_qa.html @@ -11,7 +11,7 @@ - + @@ -19,8 +19,8 @@
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

解惑 ​

如果LXD安装后lxc命令显示找不到怎么办 ​

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

执行这个命令后尝试

lxc -h

看看lxc命令是否已修复

开设centos7发现报错CGroupV1不支持怎么办 ​

启用CGroup V1：要在Ubuntu系统上启用CGroup V1，需要编辑内核启动参数。

请注意，在更改内核启动参数之前，请务必备份重要的数据和设置，以防止意外的问题。

编辑/etc/default/grub文件，将GRUB_CMDLINE_LINUX_DEFAULT中的参数末尾加上cgroup_enable=memory。

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash cgroup_enable=memory"

保存文件并运行以下命令更新GRUB引导。

bash
sudo update-grub

重启系统，使更改生效

如果上述更改仍旧不支持开设centos7，那么请使用别的宿主机系统尝试

目前已验证可开带独立IPV6地址容器的VPS商家 ​

kuroit 中的 美国凤凰城 regular

datalix 中的 德国AMD 促销款

luxvps 中的 德国AMD 促销款

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

执行这个命令后尝试

lxc -h

看看lxc命令是否已修复

开设centos7发现报错CGroupV1不支持怎么办 ​

启用CGroup V1：要在Ubuntu系统上启用CGroup V1，需要编辑内核启动参数。

请注意，在更改内核启动参数之前，请务必备份重要的数据和设置，以防止意外的问题。

编辑/etc/default/grub文件，将GRUB_CMDLINE_LINUX_DEFAULT中的参数末尾加上cgroup_enable=memory。

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash cgroup_enable=memory"

保存文件并运行以下命令更新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 index e8c22409f9..a647e053e6 100644 --- a/guide/lxd_thanks.html +++ b/guide/lxd_thanks.html @@ -11,15 +11,15 @@ - + -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

+ \ No newline at end of file diff --git a/guide/pve_custom.html b/guide/pve_custom.html index a168e93821..61a1d76553 100644 --- a/guide/pve_custom.html +++ b/guide/pve_custom.html @@ -11,7 +11,7 @@ - + @@ -31,8 +31,8 @@ --name pve \ --add-host pve:10.13.14.101 \ --hostname pve \ -spiritlhl/pve:7_aarch64

开设出的面板实际是开设在容器内的，但网络已使用host模式，PVE的端口约等于就使用的宿主机的端口

有许多错误需要修复，欢迎PR解决问题，实测在Ubuntu系统的宿主机上安装Proxmox VE的面板成功，解决了通过网络安装Proxmox VE只能使用Debian系统做宿主机的问题

 - +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 index f7376f7fa5..5874278fb9 100644 --- a/guide/pve_install.html +++ b/guide/pve_install.html @@ -11,15 +11,15 @@ - + -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

PVE主体安装 ​

安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载

一键安装PVE ​

TIP

建议debian11而不是debian12，因为后者虽然是stable版本但不知道是否有未发现的BUG，debian11安装的目前稳定点

  • 安装的是当下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 文件路径进行只读锁定

国际

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://ghproxy.com/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
  • 移除订阅弹窗
  • 尝试开启硬件直通
  • 对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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)

自动配置宿主机的网关 ​

WARNING

使用前请保证重启过服务器且此时PVE能正常使用WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动成功后至少等1分钟再执行本命令

TIP

这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行

  • 如果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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_nat_network.sh)

TIP

这一步是可能需要你执行成功几分钟后重启系统，详见脚本最后执行完毕的提示

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

PVE主体安装 ​

安装过程中遇到选项不会选的可无脑按回车，本项目所有脚本内置国内外IP自动判断，使用的是不同的安装源与配置文件，有使用CDN加速镜像下载

一键安装PVE ​

TIP

建议debian11而不是debian12，因为后者虽然是stable版本但不知道是否有未发现的BUG，debian11安装的目前稳定点

  • 安装的是当下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 文件路径进行只读锁定

国际

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://ghproxy.com/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
  • 移除订阅弹窗
  • 尝试开启硬件直通
  • 对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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/build_backend.sh)

自动配置宿主机的网关 ​

WARNING

使用前请保证重启过服务器且此时PVE能正常使用WEB端再执行，重启机器后不要立即执行此命令，待WEB端启动成功后至少等1分钟再执行本命令

TIP

这一步是最容易造成SSH断开的，原因是未等待PVE内核启动就修改网络会造成设置冲突，所以至少等几分钟待内核启动也就是WEB端启动成功后再执行

  • 如果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://ghproxy.com/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 index 723c19b568..8a3d991c47 100644 --- a/guide/pve_kvm.html +++ b/guide/pve_kvm.html @@ -11,7 +11,7 @@ - + @@ -37,8 +37,8 @@ rm -rf vm*

TIP

PVE修改VM配置前都得停机先，再修改配置，修改完再启动，免得出现配置重载错误

开设独立IPV4地址的虚拟机 ​

两个版本，各取所需

自动选择IPV4地址无需手动指定的版本 ​

WARNING

使用前需要保证当前宿主机的IP段带了至少2个IP，且有空余的IP未配置，该空余的IP未绑定宿主机

国际

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://ghproxy.com/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)
shell
./buildvm_extraip.sh 152 test1 oneclick123 1 1024 10 debian12 local N

上述命令意义为开设一个带独立IPV4地址的虚拟机

属性值
VMID152
用户名test1
密码oneclick123
CPU1核
内存1024MB
硬盘10G
系统debian12
存储盘local盘
IPV6附加默认不附加

需要手动指定IPV4地址的版本 ​

国际

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://ghproxy.com/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)
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地址无需手动指定 ​

国际

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://ghproxy.com/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计算 系统 存储盘
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
- +rm -rf vm152 + \ No newline at end of file diff --git a/guide/pve_lxc.html b/guide/pve_lxc.html index e1d4512ecf..5dcdc15deb 100644 --- a/guide/pve_lxc.html +++ b/guide/pve_lxc.html @@ -11,7 +11,7 @@ - + @@ -36,8 +36,8 @@ iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore

开设纯IPV6地址的虚拟机 ​

前提是宿主机给的是IPV6子网而不是单独一个IPV6地址，且宿主机未开启MAC地址校验

自动选择IPV6地址无需手动指定 ​

国际

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://ghproxy.com/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
- +systemctl restart ndpresponder.service + \ No newline at end of file diff --git a/guide/pve_precheck.html b/guide/pve_precheck.html index e81b8da24f..0454e83146 100644 --- a/guide/pve_precheck.html +++ b/guide/pve_precheck.html @@ -11,15 +11,15 @@ - + -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了

如果有未适配的商家或机器欢迎联系@spiritlhl_bot，有空会尝试支持一下

各种要求 ​

建议debian在使用前尽量使用最新的稳定版本的系统

不要在动态IP的服务器上使用本套脚本(重启机器后自动切换本机IP的服务器暂不支持，重启机器后IP不自动切换的支持)

本项目只适配Debian系统(非Debian无法通过APT源安装，官方只给了Debian的镜像，其他系统只能使用ISO安装)

  • 系统要求：Debian 8+

TIP

建议debian11而不是debian12，因为后者是beta版本，debian11安装的才是稳定版

  • 硬件要求：2核2G内存x86_64或arm架构服务器硬盘至少20G
  • 可开KVM的硬件要求：VM-X或AMD-V支持 (部分VPS和全部独服支持)
  • 如果硬件或系统需求不满足，可使用LXD批量开LXC容器跳转

WARNING

内存开点swap免得机器炸了

开设虚拟内存(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://ghproxy.com/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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/check_kernal.sh)

如果你需要更新IPV6信息再查询，那么执行以下命令后再查询

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


- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

On this page

前言 ​

以下为非自定义部分的介绍，自定义部分有自己对应的介绍，勿弄混了

如果有未适配的商家或机器欢迎联系@spiritlhl_bot，有空会尝试支持一下

各种要求 ​

建议debian在使用前尽量使用最新的稳定版本的系统

不要在动态IP的服务器上使用本套脚本(重启机器后自动切换本机IP的服务器暂不支持，重启机器后IP不自动切换的支持)

本项目只适配Debian系统(非Debian无法通过APT源安装，官方只给了Debian的镜像，其他系统只能使用ISO安装)

  • 系统要求：Debian 8+

TIP

建议debian11而不是debian12，因为后者是beta版本，debian11安装的才是稳定版

  • 硬件要求：2核2G内存x86_64或arm架构服务器硬盘至少20G
  • 可开KVM的硬件要求：VM-X或AMD-V支持 (部分VPS和全部独服支持)
  • 如果硬件或系统需求不满足，可使用LXD批量开LXC容器跳转

WARNING

内存开点swap免得机器炸了

开设虚拟内存(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://ghproxy.com/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://ghproxy.com/https://raw.githubusercontent.com/spiritLHLS/pve/main/scripts/check_kernal.sh)

如果你需要更新IPV6信息再查询，那么执行以下命令后再查询

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


+ \ No newline at end of file diff --git a/guide/pve_qa.html b/guide/pve_qa.html index d81b1d129a..f92627a7d4 100644 --- a/guide/pve_qa.html +++ b/guide/pve_qa.html @@ -11,7 +11,7 @@ - + @@ -27,8 +27,8 @@ iptables -t filter -F service networking restart systemctl restart networking.service -iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore

目前已验证的VPS商家 ​

可开设KVM虚拟化的NAT的商家 ​

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 中的独立服务器

只可开设LXC虚拟化的NAT的商家 ​

腾讯云 中的无忧款和特惠款(学生机)

spectraip 中的KVM服务器

Linode 中美国专用CPU的最低配

hosthatch 中的特价高配服务器

hetzner 的cloud服务器

rackdog 的浮动IP的服务器

vultr 的Cloud普通服务器

azure 的普通机器

已知暂时不可用未适配的商家 ​

OVH

- +iptables-save | awk '{if($1=="COMMIT"){delete x}}$1=="-A"?!x[$0]++:1' | iptables-restore

目前已验证的VPS商家 ​

可开设KVM虚拟化的NAT的商家 ​

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 中的独立服务器

只可开设LXC虚拟化的NAT的商家 ​

腾讯云 中的无忧款和特惠款(学生机)

spectraip 中的KVM服务器

Linode 中美国专用CPU的最低配

hosthatch 中的特价高配服务器

hetzner 的cloud服务器

rackdog 的浮动IP的服务器

vultr 的Cloud普通服务器

azure 的普通机器

已知暂时不可用未适配的商家 ​

OVH

+ \ No newline at end of file diff --git a/guide/pve_thanks.html b/guide/pve_thanks.html index 28afe4f015..a51ae81f1b 100644 --- a/guide/pve_thanks.html +++ b/guide/pve_thanks.html @@ -11,15 +11,15 @@ - + -
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

- +
一键虚拟化项目

简体中文

English

简体中文

English

Appearance

+ \ No newline at end of file diff --git a/hashmap.json b/hashmap.json index 39de291342..fd732e4793 100644 --- a/hashmap.json +++ b/hashmap.json @@ -1 +1 @@ -{"en_us_guide_lxd_install.md":"0880bdc1","case_case3.md":"f70dffcb","case_case4.md":"2ed250b5","case_index.md":"679de9f1","developer_index.md":"1694974e","case_case5.md":"7a22ce54","developer_l10n.md":"74377b58","en_us_developer_index.md":"48d4ebf1","case_case2.md":"2c9a4469","en_us_guide_lxd_custom.md":"90c3be0d","en_us_guide_lxd_extra_config.md":"bc824dfa","en_us_guide_lxd_precheck.md":"d15155ac","en_us_guide_lxd_thanks.md":"cbe6b4e1","en_us_guide_lxd_lxc.md":"907b6ddd","en_us_guide_lxd_qa.md":"9ee5d99d","en_us_guide_pve_custom.md":"f1529c25","en_us_guide_pve_install.md":"11d1a883","en_us_guide_pve_lxc.md":"e98dda75","en_us_index.md":"22c03377","guide_dashboardq.md":"c07acab3","guide_docker_build.md":"bae54da2","guide_dashboard.md":"59b64dc4","guide_docker_custom.md":"6db0b9c6","guide_docker_install.md":"899b8e80","guide_docker_precheck.md":"8dcdee0e","guide_docker_qa.md":"2e09ddf2","guide_docker_thanks.md":"6c5fe30f","guide_lxd_custom.md":"55f21751","guide_lxd_qa.md":"5ee50dd6","guide_lxd_thanks.md":"b15cc6bd","guide_pve_custom.md":"0aac6ff9","guide_pve_install.md":"42dc929c","guide_pve_lxc.md":"f1c965da","guide_pve_kvm.md":"252331b6","guide_pve_precheck.md":"e8cf1b1e","guide_pve_qa.md":"7ed699f2","case_case1.md":"7f86883a","en_us_developer_l10n.md":"6d4e09b4","en_us_guide_dashboard.md":"bc126f99","en_us_guide_dashboardq.md":"1a6c7b9b","en_us_guide_docker_build.md":"12ee0f20","en_us_guide_pve_thanks.md":"6f541899","guide_lxd_extra_config.md":"61859656","en_us_guide_docker_qa.md":"d42fce53","guide_pve_thanks.md":"c463b3ed","guide_lxd_install.md":"9b21121e","en_us_guide_pve_qa.md":"aeb26265","index.md":"20391d7d","guide_lxd_precheck.md":"90630545","en_us_guide_docker_thanks.md":"16ca5b2f","en_us_guide_pve_kvm.md":"2b3a8c29","en_us_guide_docker_install.md":"5ff8b457","en_us_guide_docker_custom.md":"3c1974cd","guide_lxd_lxc.md":"7af7a88e","en_us_guide_docker_precheck.md":"9124e805","en_us_guide_pve_precheck.md":"891461ea"} +{"case_case3.md":"e78a8a38","en_us_guide_pve_custom.md":"a164918b","case_case1.md":"01ad2e8c","en_us_guide_dashboard.md":"a076f0f2","case_case2.md":"b490e17a","case_case5.md":"f1b49f30","case_index.md":"414be4de","en_us_developer_index.md":"998350b8","case_case4.md":"0afe4b74","developer_index.md":"1d79c597","en_us_developer_l10n.md":"0c4609b9","en_us_guide_docker_thanks.md":"658a434c","en_us_guide_dashboardq.md":"9a48881c","en_us_guide_lxd_lxc.md":"f0e22353","en_us_guide_lxd_custom.md":"35af8f37","en_us_guide_docker_precheck.md":"9cd84cef","en_us_guide_lxd_install.md":"c8eeea85","en_us_guide_lxd_qa.md":"86772169","en_us_guide_lxd_precheck.md":"e3837f3a","en_us_guide_lxd_thanks.md":"447a90be","en_us_guide_lxd_extra_config.md":"6e3eba87","guide_pve_thanks.md":"b6a7624b","en_us_guide_pve_install.md":"e8fa40cc","en_us_guide_pve_kvm.md":"3763e6db","en_us_guide_pve_qa.md":"56520221","guide_lxd_custom.md":"f13b31d2","en_us_guide_pve_lxc.md":"d61b2e43","en_us_index.md":"1d0529d7","guide_docker_precheck.md":"e7c168f4","guide_docker_thanks.md":"50fb533c","guide_dashboardq.md":"d32966c2","guide_docker_custom.md":"4dbcc1c0","developer_l10n.md":"dfbce633","guide_pve_custom.md":"d0a01bbc","guide_pve_install.md":"960c4fb2","index.md":"09f90416","en_us_guide_pve_precheck.md":"3cc0f2d8","guide_dashboard.md":"0824d560","guide_docker_build.md":"010451eb","guide_docker_install.md":"0b7efdda","en_us_guide_pve_thanks.md":"47f61a62","guide_pve_precheck.md":"ef9a9e48","guide_docker_qa.md":"66c09a7a","guide_lxd_install.md":"dc676e10","en_us_guide_docker_build.md":"ff848fff","guide_lxd_precheck.md":"26c290e1","guide_lxd_thanks.md":"28c5f5b7","en_us_guide_docker_custom.md":"14448289","en_us_guide_docker_install.md":"254a332a","guide_pve_lxc.md":"4b42cede","guide_pve_qa.md":"a4512ae1","guide_pve_kvm.md":"b6d67027","guide_lxd_extra_config.md":"d425073f","guide_lxd_qa.md":"02566bd0","guide_lxd_lxc.md":"1e73e1da","en_us_guide_docker_qa.md":"a5c8f8d2"} diff --git a/index.html b/index.html index 0d3245b826..9a91275f6e 100644 --- a/index.html +++ b/index.html @@ -11,7 +11,7 @@ - + @@ -19,7 +19,7 @@
一键虚拟化项目

简体中文

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 1e27e88457..cf70454b94 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -1 +1 @@ -https://www.spiritlhl.net/case/case1.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/developer/2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/dashboard.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/case/case2.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/case/case3.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/case/case4.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/case/case5.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/case/2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/developer/l10n.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/dashboardq.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/docker_build.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/docker_custom.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/docker_install.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/docker_precheck.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/docker_qa.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/docker_thanks.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/lxd_custom.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/lxd_extra_config.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/lxd_install.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/lxd_lxc.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/lxd_precheck.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/lxd_qa.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/lxd_thanks.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/pve_custom.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/pve_install.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/pve_kvm.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/pve_lxc.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/pve_precheck.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/pve_qa.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/guide/pve_thanks.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/index.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/developer/2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/dashboard.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/developer/l10n.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/dashboardq.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/docker_build.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/docker_custom.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/docker_install.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/docker_precheck.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/docker_qa.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/docker_thanks.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_custom.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_extra_config.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_install.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_lxc.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_precheck.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_qa.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_thanks.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/pve_custom.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/pve_install.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/pve_kvm.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/pve_lxc.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/pve_precheck.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/pve_qa.html2023-08-23T11:38:51.000Zhttps://www.spiritlhl.net/en_US/guide/pve_thanks.html2023-08-23T11:38:51.000Z \ No newline at end of file +https://www.spiritlhl.net/case/case1.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/developer/2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/dashboard.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/case/case5.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/case/2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/developer/l10n.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/dashboardq.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/docker_build.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/docker_custom.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/docker_install.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/docker_precheck.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/docker_qa.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/docker_thanks.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/lxd_custom.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/lxd_extra_config.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/lxd_install.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/case/case4.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/lxd_precheck.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/lxd_qa.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/lxd_thanks.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/pve_custom.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/pve_install.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/pve_kvm.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/pve_lxc.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/pve_precheck.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/pve_qa.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/pve_thanks.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/index.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/case/case3.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/case/case2.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/guide/lxd_lxc.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/developer/2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/dashboard.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/developer/l10n.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/dashboardq.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/docker_build.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/docker_custom.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/docker_install.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/docker_precheck.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/docker_qa.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/docker_thanks.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_custom.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_extra_config.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_install.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_lxc.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_precheck.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_qa.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/lxd_thanks.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/pve_custom.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/pve_install.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/pve_kvm.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/pve_lxc.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/pve_precheck.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/pve_qa.html2023-08-23T11:40:17.000Zhttps://www.spiritlhl.net/en_US/guide/pve_thanks.html2023-08-23T11:40:17.000Z \ No newline at end of file