forked from snxraven/ravenscott-blog
Update
This commit is contained in:
Raven Scott
parent
2d0d653e83
commit
b1b6cfd650
@ -224,51 +224,51 @@ cmd(`docker run --dns 1.2.3.4 --ulimit nofile=10000:50000 --mount type=bind,sour
|
||||
|
||||
### Key Elements of the Command
|
||||
|
||||
#### `docker run`
|
||||
`docker run`
|
||||
This is the core Docker command that starts a new container. It is followed by various options and configurations that tailor how the container will be run.
|
||||
|
||||
#### `--dns 1.2.3.4`
|
||||
`--dns 1.2.3.4`
|
||||
This option sets the DNS server for the container to `1.2.3.4`. This can be used to force the container to use a specific DNS server instead of the system default.
|
||||
|
||||
#### `--ulimit nofile=10000:50000`
|
||||
`--ulimit nofile=10000:50000`
|
||||
The `ulimit` option is used to control the number of open file descriptors allowed in the container. In this case, the limit is set to a soft limit of 10,000 and a hard limit of 50,000. This is particularly useful when dealing with containers that require a large number of file handles, such as servers with heavy network or file I/O activity.
|
||||
|
||||
#### `--mount type=bind,source=/etc/hosts,target=/etc/hosts,readonly`
|
||||
`--mount type=bind,source=/etc/hosts,target=/etc/hosts,readonly`
|
||||
This bind mount command maps the host machine’s `/etc/hosts` file into the container’s `/etc/hosts` path as a read-only file. It allows the container to access the same host-to-IP mappings as the host system, ensuring consistency in DNS lookups within the container.
|
||||
|
||||
#### `-e PATH=/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/nodejs/bin:/usr/local/go/bin:/root/.cargo/bin:/root/.go/bin`
|
||||
`-e PATH=/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/nodejs/bin:/usr/local/go/bin:/root/.cargo/bin:/root/.go/bin`
|
||||
The `-e` flag sets environment variables inside the container. In this case, it modifies the `PATH` environment variable to include several common directories where executable files are located, including Node.js, Go, and system binaries.
|
||||
|
||||
#### `--ip ${IPAddress}`
|
||||
`--ip ${IPAddress}`
|
||||
This option sets a specific IP address for the container. The variable `${IPAddress}` is dynamically set in the script, likely determined earlier based on network or configuration.
|
||||
|
||||
#### `-td`
|
||||
`-td`
|
||||
These two flags are combined:
|
||||
- `-t` allocates a pseudo-TTY (terminal), which is useful for interactive applications.
|
||||
- `-d` runs the container in detached mode, meaning it runs in the background.
|
||||
|
||||
#### `${freeStorage} ${specialStartup}`
|
||||
`${freeStorage} ${specialStartup}`
|
||||
These variables are used to dynamically inject additional options for storage and startup configurations. They are passed as part of the Docker run command:
|
||||
- `freeStorage` might define storage-related options such as volume mounting or storage limits.
|
||||
- `specialStartup` likely contains commands or environment variables that are executed or passed when the container starts.
|
||||
|
||||
#### `--network=${randNetwork}`
|
||||
`--network=${randNetwork}`
|
||||
This specifies the Docker network to which the container will be connected. The variable `randNetwork` contains the name of the network, which is chosen randomly in the script from a predefined list of network names.
|
||||
|
||||
#### `-e CONTAINER_NAME=${myArgs[4]}`
|
||||
`-e CONTAINER_NAME=${myArgs[4]}`
|
||||
This sets an environment variable `CONTAINER_NAME` inside the container, with the value coming from the command-line argument `myArgs[4]`. This is useful for tracking or logging the container’s name during execution.
|
||||
|
||||
#### `${trialVar} ${memoryVar} ${cpusVar} ${restartVar}`
|
||||
`${trialVar} ${memoryVar} ${cpusVar} ${restartVar}`
|
||||
These variables are used to define additional container settings:
|
||||
- `trialVar`: Determines if the container is part of a trial, potentially adding `--rm` to automatically remove the container when it stops.
|
||||
- `memoryVar`: Sets memory limits for the container, such as `--memory=1024m` to limit the container to 1024 MB of RAM.
|
||||
- `cpusVar`: Specifies CPU limits, for example, `--cpus=2` to restrict the container to 2 CPU cores.
|
||||
- `restartVar`: Adds a restart policy to the container, such as `--restart always` to ensure the container restarts automatically if it crashes or is stopped.
|
||||
|
||||
#### `--hostname ${myArgs[4]} --name ${myArgs[4]}`
|
||||
`--hostname ${myArgs[4]} --name ${myArgs[4]}`
|
||||
These options set the hostname and name of the container, both based on the value of `myArgs[4]`. The hostname is the internal network name of the container, while the name is how the container will be referenced in Docker.
|
||||
|
||||
#### `${osChosen}`
|
||||
`${osChosen}`
|
||||
Finally, the `${osChosen}` variable specifies which Docker image to use when creating the container. This variable is dynamically set based on the chosen operating system earlier in the script.
|
||||
|
||||
#### Handling Edge Cases and Custom Roles
|
||||
@ -306,9 +306,6 @@ async function updateNetworkID(netID, sshSurfID) {
|
||||
);
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
This script is a highly customizable and automated solution for managing Docker containers, tailored to dynamically handle various Linux distributions and custom resource allocations based on user input. The use of random network and port assignment ensures that each container is unique, while the integration with MySQL and external APIs adds a layer of user management and user-specific configurations. By combining these powerful tools, the script efficiently handles container orchestration, making it a robust solution for system administrators.
|
||||
|
||||
### Container Configuration
|
||||
|
||||
Loading…
Reference in New Issue
Block a user