- https://systemd.io/
- https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/using_systemd_unit_files_to_customize_and_optimize_your_system/assembly_working-with-systemd-unit-files_working-with-systemd#con_introduction-to-unit-files_assembly_working-with-systemd-unit-files
- https://www.freedesktop.org/software/systemd/man/latest/
- https://tadeubento.com/2023/systemd-hidden-gems-for-a-better-linux/
Systemd does a lot of stuff I guess it is easier to just lean based on what comes up / you need. There isn’t a single path.
The normal and recommended Proxmox file structure is what you’ve after running
rm -rf /
. Just move to Incus (LXD) and be done with it.Incus provides a unified experience to deal with both LXC containers and VMs. If you’re running a modern version of Proxmox then you’re already running LXC containers so why not move to Incus that is made by the same people? Why keep dragging all of the Proxmox overhead and potencial issues?
Incus is free can be installed on any clean Debian system with little to no overhead and on the release of Debian 13 it will be included on the repositories. Another interesting advantage of Incus is that you can move containers and VMs between hosts with different base kernels and Linux distros.
Read more here: https://tadeubento.com/2024/replace-proxmox-with-incus-lxd/