You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/en/guide/docker/docker_build.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,12 @@ outline: deep
4
4
5
5
# Introduction
6
6
7
-
There are two methods of building
7
+
There are two deployment methods.
8
8
9
9
## Setting Up Standalone
10
10
11
-
- Generate only one docker
12
-
- Can be configured to bind a separate IPv6 address, but requires a docker previously installed using the environment installation command of this set of scripts, and requires the host to be bound to at least the /112 IPv6 subnet
11
+
- Generate a single Docker container
12
+
- Can bind an independent IPv6 address, but requires Docker to be installed with this project's installer and a host IPv6 subnet of at least /112
./onedocker.sh name cpu memory password sshport startport endport <independent_ipv6> <system> <disk>
@@ -39,7 +39,7 @@ Currently, the system only supports selecting:
39
39
40
40
with Debian being the default choice.
41
41
42
-
The hard disk size can only be set by filling in the value if you have selected the option to support limiting the hard disk size during the previous Docker installation, it is not limited when not filled in by default.
42
+
Disk size can be set only if you previously enabled disk-limit support during Docker installation. If omitted, disk size is unlimited by default.
43
43
44
44
```shell
45
45
./onedocker.sh test 1 512 123456 25000 34975 35000 N debian 5
One line corresponds to information about a container, the docker's ipv6 address can only be looked up within the container itself, it doesn't exist in the docker's configuration.
119
+
Each line corresponds to one container. The IPv6 address can only be checked from inside that container.
120
120
121
121
## Uninstall all Docker containers and images
122
122
123
-
The following command offload ignores ndpresponder to prevent IPv6 configuration failure
123
+
The following cleanup command keeps `ndpresponder` to avoid breaking IPv6 configuration.
The default containers are not set to restart themselves after stopping, you need to execute the following command to start all stopped containers.
159
+
By default, containers are not configured for auto-restart after host reboot. Run the following command to start all stopped containers.
160
160
161
161
```
162
162
docker start $(docker ps -aq)
163
163
```
164
164
165
165
## Start SSH service for all containers after host reboot
166
166
167
-
Since the container itself does not have a daemon, the SSH service cannot start itself, and you need to execute the following command to start the SSH process for all containers.
167
+
Because these containers do not run a full init system by default, SSH may not auto-start. Use the following command to start SSH in all running containers.
Copy file name to clipboardExpand all lines: docs/en/guide/docker/docker_install.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ outline: deep
6
6
7
7
Support for running Docker virtualization on various systems, including Linux, Android, and Windows.
8
8
9
-
If your host does not have an IPv6 subnet and you want to assign IPv6 addresses to containers, then please check the ``Customize``partition in the ``LXD`` module for the ``Attach a free IPv6 address segment`` to the host, and attach an IPv6 subnet to the host before installing the environment.
9
+
If your host has no IPv6 subnet but you want to assign IPv6 addresses to containers, check the ``Customize``section in the ``Docker`` module for ``Attach a free IPv6 address segment to the host``, then attach an IPv6 subnet before installation.
10
10
11
11
## Setting Up Virtual Memory
12
12
@@ -48,7 +48,7 @@ bash dockerinstall.sh
48
48
```
49
49
50
50
:::tip
51
-
The environment installation process may require you to reboot the server and then execute the script again, see the instructions after the script is run for more details
51
+
The installation process may require a reboot. If prompted, reboot the server and run the script again.
52
52
:::
53
53
54
54
## Detect whether Docker supports limiting container hard disk size
Copy file name to clipboardExpand all lines: docs/en/guide/docker/docker_precheck.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
1
# Introduction
2
2
3
-
The following is an introduction to the non-customized sections. Please ensure that you don't confuse them with the customized parts.
3
+
This page introduces the standard (non-customized) workflow.
4
4
5
-
If your host does not have an IPv6 subnet and you want to assign IPv6 addresses to containers, then please check the ``Customize``partition in the ``incus`` module for the ``Attach a free IPv6 address segment`` to the host, and attach an IPv6 subnet to the host before installing the environment.
5
+
If your host has no IPv6 subnet but you want to assign IPv6 addresses to containers, check the ``Customize``section in the ``Docker`` module for ``Attach a free IPv6 address segment to the host``, then attach an IPv6 subnet before installation.
6
6
7
7
:::warning
8
-
If the host has an IPv6 network, the installation will change the network structure of the host, please make sure that the host can reset the system at any time and that there is no important data on the host before running.
8
+
If the host has IPv6 networking, installation may change host network structure. Ensure the hostcan be recovered/reinstalled at any time, and do not run on machines with critical data.
9
9
:::
10
10
11
11
Feel free to give the project a ```Star``` for free support!-->[https://github.com/oneclickvirt/docker](https://github.com/oneclickvirt/docker)
@@ -21,7 +21,7 @@ Containers are created as unprivileged by default, and Docker daemon sockets are
21
21
22
22
By default, lxcfs is installed and enabled, so that when querying resources within a container, CPU and memory use the configured view instead of the host's view.
23
23
24
-
By default, you can choose whether or not to share the hard disk of the host machine, and you can choose whether or not to install it as an environment that can limit the size of the hard disk during Docker installation.
24
+
By default, the installer lets you choose whether to share host disk space and whether to enable container disk-size limits.
Copy file name to clipboardExpand all lines: docs/en/guide/incus/incus_custom.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -246,7 +246,7 @@ Copy the last red box of the page without the blank lines.
246
246
Then open [https://ipv6tunnel.spiritlhl.top/](https://ipv6tunnel.spiritlhl.top/) and select```Option```for```TunnelBrokerCh```, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
247
247
248
248
249
-
Then click```Covert```to convert the format, and wait for the page to refresh to show the converted configuration file.
249
+
Then click```Convert```to convert the format, and wait for the page to refresh to show the converted configuration file.
250
250
251
251
252
252
Then use vim or vi to modify the```/etc/network/interfaces```file to add content, or modify the following command to add new content
@@ -304,7 +304,7 @@ For these four lines, press ctrl+c to copy or right-click to copy
304
304
305
305
Then open [https://ipv6tunnel.spiritlhl.top/](https://ipv6tunnel.spiritlhl.top/) and select```Option```for```ip4market```, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
306
306
307
-
Then click```Covert```to convert the formatting
307
+
Then click```Convert```to convert the formatting
308
308
309
309

310
310
@@ -345,7 +345,7 @@ The above content will appear, copy all the boxed parts without blank lines.
345
345
346
346
Then open [https://ipv6tunnel.spiritlhl.top/](https://ipv6tunnel.spiritlhl.top/) and select```Option```for```NetAssist```, another drop-down selection box to choose the name of the package you successfully installed previously, then paste what you copied in the input box.
347
347
348
-
Then click on```Covert```to convert the formatting
Copy file name to clipboardExpand all lines: docs/en/guide/incus/incus_install.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,7 +64,7 @@ If you need to specify the path of a non-system disk as the default pool, then y
64
64
If the corresponding disk has 18 Gigabytes of free hard disk space in addition to the occupied space and you want to open a 15 Gigabyte storage pool, follow the command line prompts to enter ```15```.
65
65
66
66
:::tip
67
-
The execution process **may** require a **manual reboot** to load the storage type into the kernel, the installation is completed at the end of the execution will**automatically reboot** the server, the first time after the complete installation of the reboot will take about 400 ~ 500 seconds, please be patient
67
+
The process **may** require a **manual reboot** to load storage drivers into the kernel. At the end of installation, the server may**automatically reboot**. The first full reboot can take about 400-500 seconds.
68
68
:::
69
69
70
70
:::warning
@@ -123,16 +123,16 @@ apt-get install incus -y
123
123
incus -h
124
124
```
125
125
126
-
If there are no exceptions, continue execution
126
+
If no errors occur, continue with:
127
127
128
128
```
129
129
incus admin init
130
130
```
131
131
132
-
Just enter the default for the normal options
132
+
For standard options, keep the defaults.
133
133
134
134
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.
135
135
136
-
Remember to select 'no' for options containing 'auto' when prompted to update the image, in order to avoid occupying the system.
136
+
When prompted about automatic image updates, choose `no` to avoid unnecessary resource usage.
-oracle7, centos7 (CGroupV1 needs to be enabled in GRUB or it won't start.)
18
+
- kali, archlinux
19
19
20
20
* Note that **the combination of lowercase letters + numbers** or **only lowercase letters**, try it yourself, if the search is not the system will automatically exit the script
21
21
* The version number can be with English decimal point, in order to adapt to the alpine version number has been supported.
. /buildct.sh name Cpu_num Memory_size Hard_disk_size SSH_port Extranet_start_port Extranet_stop_port Download_speed Upload_speed Whether_IPV6_is_enabled(Y or N) System(leave blank for debian11)
48
48
```
49
49
50
-
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
50
+
Memory is in MB, disk size in GB, and download/upload speeds in Mbit. For IPv6, you can provide `Y` or `N`, or leave it empty (default: disabled).
51
51
52
-
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.
52
+
If both ```external start port``` and ```external stop port``` are set to `0`, no port-range mapping is created and only SSH is mapped. These fields cannot be empty.
53
53
54
-
Support custom container system, do not fill in the leave blank default use debian11, pay attention to the incoming parameters for the system name + version number
54
+
Custom container systems are supported. If left empty, `debian11` is used by default. Use the format `system + version`.
55
55
56
56
### Example
57
57
58
-
Here is the information about the example chick that is being raised:
58
+
Example container configuration:
59
59
60
60
| Attribute | Value |
61
61
|-----------------------------|-----------------|
62
-
|container's Name | test |
62
+
|Container Name| test |
63
63
| Username for SSH Login | root |
64
64
| Password for SSH Login | Randomly generated |
65
65
| Number of CPU Cores | 1 |
@@ -87,9 +87,9 @@ For example, the information for the query example is
87
87
cat test
88
88
```
89
89
90
-
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
90
+
If you already created a test container and want to do batch generation, delete the test container first.
91
91
92
-
### Delete Test Chick
92
+
### Delete Test Container
93
93
94
94
```shell
95
95
incus stop test
@@ -101,14 +101,14 @@ ls
101
101
102
102
## Normal version batch generation
103
103
104
-
Opened Chick Configuration:
104
+
Batch Profile:
105
105
106
106
- 1 core 256MB RAM 1GB hard disk limited to 300Mbit bandwidth
107
107
- With 1 SSH port, 24 extranet ports
108
108
- Default memory and hard disk size
109
109
110
110
:::tip
111
-
incus if the command is no problem, the execution of the initialization of the opening of the containers, this step is best to put ```screen`` in the background to suspend the execution of the opening of the containers, the length of time with you to open a few and the mother hen configuration-related
111
+
If `incus` commands run normally, proceed with initialization. It is recommended to run this in a `screen` session because runtime depends on host resources and the number of containers.
112
112
:::
113
113
114
114
Execute the following command to load the boot script
The following command opens **10**chicks with the name prefix **tj**.
122
+
The following command opens **10**containers with prefix **tj**.
123
123
124
124
```shell
125
125
./init.sh tj 10
126
126
```
127
127
128
-
Sometimes there is a problem with the path where init.sh is run, in this case it is recommended to add sudo in front of it to force it to run in the root directory
128
+
If path issues occur when running `init.sh`, prepend `sudo` and run it from the root directory.
129
129
130
130
## Bulk generation of pure SSH port versions
131
131
132
-
Opened Chick Configuration:
132
+
Batch Profile:
133
133
134
134
- 1 core 128MB RAM 1GB hard disk limited to 300Mbit bandwidth
135
135
- Only one SSH port
136
136
- Unable to mount warp
137
137
138
138
:::tip
139
-
incus if the command is no problem, the execution of the initialization of the opening of the chick, this step is best to put the ```screen`` in the background to hang the execution of the opening of the chick, the length of time you open the chick with the opening of a few and the mother hen configuration-related
139
+
If `incus` commands run normally, proceed with initialization. Use a `screen` session to avoid interruption; runtime depends on host resources and container count.
The last line of the following command opens **10**chicks with the chick name prefix **tj**
150
+
The last command below opens **10**containers with prefix **tj**.
151
151
152
152
```shell
153
153
./least.sh tj 10
154
154
```
155
155
156
-
Sometimes there is a problem with the path where last.sh is run, in this case it is recommended to force the root directory to run by adding sudo in front of it.
156
+
If path issues occur when running `least.sh`, prepend `sudo` and run it from the root directory.
Can be run multiple times to batch generate chicks, and inherit the previous part has been generated in the back to add, customizable memory and hard disk size
171
+
This script can be run multiple times. It appends new containers while inheriting previous configuration, with customizable memory and disk size.
172
172
173
-
## View the information of the batch opened chicks
173
+
## View Batch Container Information
174
174
175
-
After opening the chicks, the specific information will be generated in the log file in the current directory, with the following format
175
+
After creation, container information is written to a log file in the current directory in this format:
To view it, simply print the log file by executing the following command in the current directory
182
+
To view it, print the log file from the current directory:
183
183
184
184
```shell
185
185
cat log
186
186
```
187
187
188
188
:::warning
189
-
Don't use the chicks opened by this script as a production environment, incus virtualization doesn't support changing kernel, dd, turning on bbr, etc.
189
+
Do not use containers created by this script as production environments. Incus containers do not support kernel replacement, DD reinstall flows, BBR toggling, and similar host-level changes.
0 commit comments