but I found I spent way too much time trying to manage RAM and tuning it,

I spent none, and it works fine. what was you’re issue?

you don’t have to be imprisoned to have your life ruined. there are many relatively subtle ways to do that

And I wondered who in their right mind would buy just half of that best friends forever charm.

anyone who would like to joke with their depression. I can imagine doing that.

now I actually want something like this

isn’t this prone to a

 || rm -rf /

or something similar at the end of the URL?

if you can docker exec, you have a lot of privileges already, so be sure to make sure this is not a danger

one more thing I remembered when re-reading the title: I think you can send messages to the VM using the qm command. it stands for qemu monitor, basically its a management tool

my solution to this is to only deal with the UPS in proxmox. it shuts down everything if the battery goes below a certain level.

I think you can configure nut to run a few scripts when something changes around the UPS. you could have a script that sends an alert through ntfy, and/or the web services that you want to use for this, but I’m not familiar with the notification system of nextcloud and truenas

would running nut-monitor in the VMs fit your use case?

I have recently discovered what was causing this to me for years. It was IP specific port bindings. Ports of a few containers were only bound for the LAN IP of the system, but if DHCP couldn’t obtain an IP until the Docker service started its startup, then those containers couldn’t be started at all, and Docker in it’s wisdom won’t bother with retrying.

The reasons to move my compose stacks to separate systemd services are counting.