I think you meant to say βYouβre rightβ?
Just picking
As a link has been shared here, itβs worth noting that the Proxmox Team does not recommend it.
The link in question is: Proxmox Helper Scripts & Other News - #35 by BassT23
2023-05-16
Changed
-
Proxmox VE LXC Updater
- Add information about the boot disk, which provides an easy way to determine if you need to expand the disk.
Proxmox Virtual Environment 8
It seems that Proxmox Virtual Environment 8 is on the horizon. With the recent update to pve-manager: 7.4-13
, you can now utilize the command pve7to8 --full
to check readiness for the transition.
To remain current with the most recent advancements
No longer in beta!
https://proxmox.com/en/news/press-releases/proxmox-virtual-environment-8-0
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.
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
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.