In most situations, you would be entering your containers as root, and that’s perfectly reasonable. After all, an unprivileged container ensures that the root inside it will only have root privileges within that container and nowhere else. Sometimes, however, it might be useful to enter a container with a specific user.

This article goes through all the reasons why you might want to replace Proxmox with Incus / LXD and how it could save you from a lot of headaches down the line. While free Proxmox, much like VMWare ESXi was, is a potential disaster waiting to happen.

ESPHome provides built-in support for the BME680 sensor with a fully open-source implementation; however, it is not compatible with all the sensor’s features. The project also includes Bosch’s proprietary BSEC v1 software library, which provides all features, but it only runs on the original ESP32, making it incompatible with the ESP32-S2 or ESP32-C3.

There are cases where we need LXD / Incus containers to have direct access to the network. In such cases, we want the containers to be assigned an IP address by a router on the network, treating them as individual devices on the network rather than containers inside a host machine that get to the network through NAT.

hdparm.conf can be used to store hdparm settings permanently, ensuring they are automatically applied at every boot. However, for testing purposes, rebooting a machine multiple times can be inconvenient. Fortunately, with a simple command, changes made to the file can be applied live without the need for a system reboot.