Could you please assist me in identifying which LXC containers are compatible with Debian 12 as the default operating system?
If you happen to create an application LXC using Debian 12, kindly share your results in this discussion. I appreciate your help!
Here are some reasons why you should avoid installing software directly on the Proxmox host:
- Stability and Security: Installing additional software on the Proxmox host can introduce potential security vulnerabilities and stability issues. Keeping the Proxmox host system clean and minimal reduces the attack surface and enhances the overall stability of the virtualization platform.
- Resource Management: Proxmox needs to efficiently manage the systemβs resources, such as CPU, memory, storage, and networking, to ensure smooth performance of the virtual machines and containers. Installing additional software on the host may lead to resource conflicts and affect the performance of your virtualized environments.
- Isolation: Keeping the Proxmox host dedicated to its primary role allows better isolation between the host and the virtualized environments. If any issues occur with the software installed on the host, it could affect the operation of your virtual machines and containers.
- Updates and Upgrades: When you install software on the Proxmox host, it might interfere with system updates and upgrades.
1 Like
Proxmox VE Processor Microcode
Microcode updates are important for several reasons:
-
Performance Improvements: Microcode updates can include optimizations that improve the performance of your computerβs processor. These updates can help your processor execute instructions more efficiently and quickly, which can lead to better overall system performance.
-
Compatibility and Stability: Microcode updates can address compatibility issues between your processor and other hardware components or software applications. They can also fix bugs and stability issues that might be present in the original microcode. Using updated microcode can help ensure that your system runs smoothly and without unexpected crashes.
-
Security Enhancements: Microcode updates can also address security vulnerabilities in your processor. Modern processors are complex and can sometimes contain vulnerabilities that could be exploited by malicious software. Microcode updates can patch these vulnerabilities and help protect your system from potential attacks.
-
Feature Support: Microcode updates can enable new processor features that might not have been available in the original microcode. These features can enhance your computing experience and allow you to take advantage of new capabilities offered by your processor.
-
Energy Efficiency: Some microcode updates can also improve the power efficiency of your processor, which can lead to longer battery life for laptops and reduced energy consumption for desktop systems.
-
Longevity of Hardware: Microcode updates can extend the useful life of your hardware. By addressing performance, compatibility, stability, and security issues, updated microcode can help keep your system relevant and functional for a longer period.
-
Ease of Updating: Microcode updates are relatively easy to apply and are usually provided by the processor manufacturer. They can be installed through firmware updates provided by your motherboard or computer manufacturer, or in some cases, directly through the operating system.
Itβs worth noting that microcode updates are typically released by the processor manufacturer (e.g., Intel, AMD) to address specific issues or to enhance the functionality of the processor. Keeping your microcode up to date can contribute to a more reliable, secure, and high-performing computing experience.
Current releases:
Intel microcode-20230808
AMD microcode-20230808
Iβm considering the incorporation of an update command across all LXCs. This command would invoke the update script, simplifying the process by eliminating the need to locate, copy, and paste the bash script in the LXC console. Instead, you would only need to execute the update command.
The following applications now include the update command for testing purposes:
- ESPHome
- Home Assistant Core
- Home Assistant
- Node-Red
- Omada
- Zigbee2MQTT
To manually integrate the update command, modify <app> to match the precise application name, and then execute the command within the LXC console:
echo "bash -c \"\$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/<app>.sh)\"" >/usr/bin/update
chmod +x /usr/bin/update
Running Frigate on Proxmox
This is working fine otherwise but how to get rw rights to the config.yml file so configuration from frigate itself is possible?
I suggest checking out other videos on Frigate created by this author.
The website currently hosts 127 useful scripts, with many more additional scripts not visible on the site but available exclusively on GitHub.
Hi tteck, I haved used your z2m script to create a LXC a while ago.
I had to fiddle a little to get it working finally but donβt remember what I did 
Now when I want to update by running the script in the LXC I get an error (tried already a few weeks ago with the same result)
Acquiring necessary componentsβ¦
environment: line 71: 4539 Killed npm ci0 https://registry.npmjs.org/typescript/-/typescript-5.2.2.tgz 8920ms (cache miss)
Failed to install necessary components.
Any idea why this is happening and how to solve this?
TIA!
The βKilledβ message suggests that the process was terminated, likely due to running out of memory or other resource constraints.
1 Like
2023-09-07
Changed
-
Proxmox VE Host Backup
- NEW Script
This script serves as a versatile backup tool for specific files and directories found within the βetcβ directory. It was developed in response to numerous requests for a Proxmox host backup script. The unique feature of this script is its flexibility, it allows users to choose which files and directories to back up, making it suitable for various hosts, not just Proxmox. By default, the compressed backup file is stored in the βrootβ directory.
Thanks man, it was indeed a RAM issue. 
z2m works, latest version has been installed but I got some warnings concerning npm:
89 packages are looking for funding
run `npm fund` for details
1 moderate severity vulnerability
To address all issues, run:
npm audit fix
Run `npm audit` for details.
Ignore, or follow instructions (npm audit fix)
1 Like
Donβt sweat it, I wanted just to inform you as a way of feedback since I installed with your script.
npm audit fix didnβ work
npm cache clean --force
npm audit fix --force
solved it. (found this after a search)
1 Like
Proxmox VE 8.1 (2023/Q4) will be based on the 6.5 kernel.
Hello!
With last update of z2m lxc with your script, I lost some capabilities of some devices. Iβm using the regular branch. How can I switch to the dev branch? I canβt find it in your instructions!