qm start $v_id
qm shutdown $v_id
qm reboot $v_id
qm resume $v_id
qm reset $v_id
qm stop $v_id
qm config $v_id
qm set -onboot 1 $v_id
pct start $v_id
pct shutdown $v_id
pct reboot $v_id
pct config $v_id
pct set -memory $v_ram $v_id
pct set -memory 1024 420
pct enter $v_id
bash <(curl -s https://raw.githubusercontent.com/Weilbyte/PVEDiscordDark/master/PVEDiscordDark.sh ) install
Name Servers: 184.108.40.206, 220.127.116.11
Search Servers: fqdn.com
XXX.XXX.XXX.XXX is the IP of the container.
DDD.DDD.DDD.DDD is the IP of the dedicated server.
NOTE: As it turns out, this doesn’t work, and we’re not sure if it will ever work.
addresses: [XXX.XXX.XXX.XXX/32] # The IP of the container
- to: 0.0.0.0/0
via: XXX.XXX.XXX.254 # The first three octets of the host
addresses: [18.104.22.168, 22.214.171.124] # Default Nameservers (Shouldn't matter)
#addresses: [126.96.36.199, 188.8.131.52] # OVH Nameservers
NOTE: If you’ve set up the ubuntu box using the minimized version (which lacks vim, nano, etc), move or delete the existing 00-installer-config.yaml and run cat <<EOF >>00-installer-config.yaml followed by the configuration above.
cat <<EOF >>00-installer-config.yaml
# Setting up Docker Swarm on multiple Proxmox VE containers
> Ziggy9263 (@jzanecook), h0lybyte (@KBVE)
## 1. Introduction
### 1.a. Crack your head against a wall
> The important thing to remember is that any all things that go horribly wrong can and will do so.
> Ziggy9263, from the docker container he has found himself trapped in
In order to begin working on a Docker Swarm, first you need to brush up on the general concepts behind the entire premise of this system. There are no winners, and there are no losers, there are only those who have discovered the wonders of setting up Docker Swarm, and those who have wandered a little too close to the wonders and have developed a pus filled growth on their abdomen.
If you have begun emitting a yellowish bioluminescence from your fingertips or have developed a large green and cyan vein stretching from your lower cheek to your posterior, then this article is not for you, and it's too late.
Otherwise, if you've simply peered over the edge of this foreign landscape, not yet realizing that the brush you're walking through is toxic in nature due to the radiation left from previous swarms, then this article may come in handy in your short lived traversal from bomb stricken wasteland to the maw of the amorphous creature you accidentally brought to your doorstep while typing `docker stack deploy`.
In the following sections, we'll go over the process of:
- Setting up Proxmox VE (7.2.1)
- Installing Proxmox Darkmode for Comfort
- Setting up `vmbr1` for Internalized Networking
- Setting up Traefik
- Minimizing DUIs
- Initializing a Docker Swarm
- Creating Nodes and Keeping Order via Quorum
- Creating Replicants and how to keep Rick Deckard off your ass
- Creating Reverse Proxies for your Nodes
### 1.b. Invest in your retirement fund
If you haven't already, it's important that you do before it's too late. This article, however, will not help you with that.
## 2. Proxmox
### 2.a. Setting up Proxmox VE (7.2.1)
### 2.b. Installing Proxmox Darkmode for Comfort
### 2.c. Setting up `vmbr1` for Internalized Networking
## 3. Traefik
### 3.a. Setting up Traefik (Version Number Here h0ly don't forget version number here version number don't forget)
### 3.b. Minimizing DUIs
## 4. Docker Swarm
### 4.a. Initializing a Docker Swarm
### 4.b. Creating Nodes and Keeping Order via Quorum
### 4.c. Creating Replicants and how to keep Rick Deckard off your ass
In case you aren't in the know like coolguy Jones, Rick Deckard is from Bladerunner and he hunts stray replicants, the premise here don't let replicants go stray.
### 4.d. Creating Reverse Proxies for your Nodes