Personally, I just have a couple of cheap CyberPower UPSs for my servers. I know I know, but I'm waiting for them to get old and die before I replace them with something better. My modem, router, and primary WiFi AP are on a custom LiFePO4-based UPS that I designed and built, because I felt like it. It'll keep them running for around 10 hours, long past everything else in the house has shut down.
suicidaleggroll
Anything on a separate disk can be simply remounted after reinstalling the OS. It doesn't have to be a NAS, DAS, RAID enclosure, or anything else that's external to the machine unless you want it to be. Actually it looks like that Beelink only supports a single NVMe disk and doesn't have SATA, so I guess it does have to be external to the machine, but for different reasons than you're alluding to.
I'd like to know the same. I really like the RP2040 and use it often, looking to move to the RP2350 but the GPIO issue is holding me back.
This is their attempt to get around that pesky 1st amendment. Make criticism of the king a "mental disorder", and then you can lock them up involuntarily "for their own protection".
This is a great tool, thanks for the continued support.
Personally, I don't actually use dockcheck to perform updates, I only use it for its update check functionality, along with a custom plugin which, in cooperation with a python script of mine, serves a REST API that lists all containers on all of my systems with available updates. That then gets pulled into homepage using their custom API function to make something like this: https://imgur.com/a/tAaJ6xf
So at a glance I can see any containers that have updates available, then I can hop into Dockge to actually apply them on my own schedule.
Sure, it's a bit hack-and-slash, but not too bad. Honestly the dockcheck portion is already pretty complete, I'm not sure what all you could add to improve it. The custom plugin I'm using does nothing more than dump the array of container names with available updates to a comma-separated list in a file. In addition to that I also have a wrapper for dockcheck which does two things:
Basically there are 5 steps to the setup:
Once running, you should be able to run
curl http://localhost:9323/metrics
and see a dump of Prometheus metricsAt this point you should be able to run your script, and at the end you'll have the file "updatelist.txt" which will either contain a comma-separated list of all containers with available updates, or "None" if there are none. Add this script into cron to run on whatever cadence you want, I use 4 hours.
The neat thing about this program is it's nestable, meaning if you run steps 1-4 independently on all of your Docker servers (assuming you have more than one), then you can pick one of the machines to be the "master" and update the "staturls" variable to point to the other ones, allowing it to collect all of the data from other copies of itself into its own output. If the output of this program will only need to be accessed from localhost, you can change the host variable in app.run to 127.0.0.1 to lock it down. Once this is running, you should be able to run
curl http://localhost:5000/metrics
and see the running and stopped container counts and available updates for the current machine and any other machines you've added into "staturls". You can then turn this program into a service or launch it @reboot in cron or in /etc/rc.local, whatever fits with your management style to start it up on boot. Note that it does verify the age of the updatelist.txt file before using it, if it's more than a day old it likely means something is wrong with the dockcheck wrapper script or similar, and rather than using the output the REST API will print "Error" to let you know something is wrong.