| title | Proxmox |
|---|---|
| description | An overview of the Proxmox hypervisor |
| published | true |
| date | 2026-01-15 15:27:46 UTC |
| tags | |
| editor | markdown |
| dateCreated | 2026-01-15 15:02:47 UTC |
Proxmox Virtual Environment is a complete, open-source server management platform for enterprise virtualization. It tightly integrates the KVM hypervisor and Linux Containers (LXC), software-defined storage and networking functionality, on a single platform. With the integrated web-based user interface you can manage VMs and containers, high availability for clusters, or the integrated disaster recovery tools with ease.
I am a big proponent of Ubuntu Server for its simplicity, ease of use, and community support. However, I will admit for beginners, the command line can be intimidating and Webmin is still kind of scary looking. Proxmox gives a lot more functionality to Debian in ways which Webmin does not. It also takes almost no overhead and can do containerization just as well as any other distro out there with the added benefit of virtualization, simple backup, and one-click migration. Many people use this hypervisor in small computers for high-availability clustering.
There is a repository maintained by the community which hosts one-line commands to help automate many of Proxmox's functions. That isn't to say the Proxmox GUI isn't useful, but there are many steps to creating some things which new users may get lost on. These scripts make life a lot simpler and faster for LXC and VM creation, as well as house keeping tasks for the hypervisor itself.
From Tteck:
These scripts empower users to create a Linux container or virtual machine interactively, providing choices for both simple and advanced configurations. The basic setup adheres to default settings, while the advanced setup gives users the ability to customize these defaults.
Options are displayed to users in a dialog box format. Once the user makes their selections, the script collects and validates their input to generate the final configuration for the container or virtual machine.
tteck has released a statement that due to his health the repo will no longer be getting maintenance. Read about it here.
There are probably over 100 scripts in Tteck's repo. Below are the ones I use most frequently, because after I install Proxmox and do some housekeeping, I deploy the Docker-Alpine LXC container and then use Portainer within that for my containers. You can run separate containers for all of your docker apps if you want; I do this because its easier.
For reference, my alpine-docker container is running Portainer + 20 docker containers and it uses less than 2 GB of RAM. My entire Proxmox node uses 3 GB of RAM.
Proxmox VE Post Install (click to expand)
This script provides options for managing Proxmox VE repositories, including:
- Disabling the Enterprise Repo
- Adding/correcting PVE sources
- Enabling the No-Subscription Repo
- Adding the test Repo
- Disabling the subscription nag
- Updating Proxmox VE
- Rebooting the system
Run the command below in the Proxmox VE Shell:
- Source code can be found here
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/post-pve-install.sh)"It is recommended to answer "yes" (y) to all options presented during the process {.is-info}
Proxmox VE Kernel Clean (click to expand)
Cleaning unused kernel images is beneficial for:
- Reducing the length of the GRUB menu
- Freeing up disk space
- Streamlining the boot process
Run the command below in the Proxmox VE Shell:
- Source code can be found here
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/kernel-clean.sh)"Proxmox VE Cron LXC Updater (click to expand)
This script will add/remove a crontab schedule that updates all LXCs every Sunday at midnight.
- Source code can be found here
To exclude specific LXCs from updating:
- Edit crontab (
crontab -e) - Add CTIDs as shown in this example (-s 103 111):
0 0 * * 0 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/update-lxcs-cron.sh)" -s 103 111 >>/var/log/update-lxcs-cron.log 2>/dev/nullRun the command below in the Proxmox VE Shell to set up:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/cron-update-lxcs.sh)"Docker is an open-source project for automating the deployment of applications as portable, self-sufficient containers.
If the LXC is created Privileged, the script will automatically set up USB passthrough {.is-info}
To create a new Proxmox VE Docker LXC, run the command below in the Proxmox VE Shell.
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/docker.sh)"⚡ Default Settings: 2GB RAM - 4GB Storage - 2vCPU ⚡
As an alternative option, you can use Alpine Linux and the Docker package to create a Docker LXC container with faster creation time and minimal system resource usage.
To create a new Proxmox VE Alpine-Docker LXC, run the command below in the Proxmox VE Shell.
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/alpine-docker.sh)"⚡ Default Settings: 1GB RAM - 2GB Storage - 1vCPU ⚡
Run Compose V2 by replacing the hyphen (-) with a space, using docker compose, instead of docker-compose {.is-warning}
Portainer Interface: (https) IP:9443
A note for those using a CF tunnel to connect to your WebUI, make these changes to Additional Application Settings while editing your tunnel to ensure proper connection:
- Turn the No TLS Verify to
ON - Turn the Disable Chucked Encoding to
ON
If you have Botfight Mode enabled you must create a rule to bypass for your IP {.is-info}
-
In the PVE dashboard, select the PVE node you wish to get a certificate for.
-
Under System, select Certificates then, double click or highlight the
pve-root-ca.pem
-
Once the Certificate dialogue box opens, click the Raw Certificate drop-down at the bottom of the dialogue box.
-
Copy the entire section and then paste it into notepad or another text editor. Save the file as pve_root_ca.crt
-
This can now be uploaded to Homarr as the certificate for Proxmox VE app and integration.
-
In the PVE dashboard select Datacenter, open the Permissions section and select Groups.
-
Click Create and create a new group called api-users.
-
Now go to Users, and create a new user, I suggest using the name of the application, in this case we will use homarr. Input a strong password. The realm will be PVE (Proxmox VE authentication server) and the group will be the api-users group we created above. Everything else can stay default.
-
Next click on API Tokens. Click Add and select the user we just created. The Token ID should match its use, i.e. homarr. Check Privilege Seperation. (THE NEXT STEP IS VERY IMPORTANT)
-
Once you click Add you need to record the information provided in the Token Secret. (Token ID and Secret) IF YOU DO NOT RECORD THIS, YOU WILL HAVE TO START THIS STEP OVER. There is no way to retrieve the API token after it is created.
-
Next select the Permissions section again. Click Add and select API Token Permission. Path will be /, the API Token will be the one you just created for the user, Role will be PVEAuditor and leave Propagate checked.
-
We will now repeat the same step above, except we will choose User Permission. The user will be the homarr user we created earlier.
-
In Homarr, under Management and Integrations, select New integration, Proxmox.
-
Under URL, enter the IP address of your Proxmox VE.
-
Under the Secrets section, the Username will be the name of the user you created in step 3, the Token ID will be the name of the Token ID you created in step 4, the API key will be the Secret you recorded in step 4/5 and the Realm will be pve.
-
If everything was done correctly, you will see a successful connection message at the bottom of the screen after clicking "Test connection and create".
-
You may need to restart Homarr to see the information for the Proxmox integration to show up. It may take some time.
To see an example of deploying a docker LXC with a tteck script, go here.
Also, watch this beginners guide.