managing reboot / update on micro OS when some container are running
Hi, I consider to set up a micro-OS mini server for some containers (homeassistant / influx db / graphana ...maybe thingsboard) My concerns is how to manage, a clean stop of the containers, let micro-OS update and then retarts the containers stack . was wondering on how to, - schedule the updates in predictable or defined time windows, to be able to stop my processes and trigger the update - or let them happen whenever a new release is available and find a way to secure my setup each time before it happens (is there an alert or trigger available to catch ? ) I didn't managed to find detailled info on those topics :/ Is there some sort of documentation (wiki /how's to) on those aspect somewhere?
Hi Luc, On 02.01.23 at 10:23 Luc FERRIE wrote:
I consider to set up a micro-OS mini server for some containers (homeassistant / influx db / graphana ...maybe thingsboard)
My concerns is how to manage, a clean stop of the containers, let micro-OS update and then retarts the containers stack . was wondering on how to, - schedule the updates in predictable or defined time windows, to be able to stop my processes and trigger the update - or let them happen whenever a new release is available and find a way to secure my setup each time before it happens (is there an alert or trigger available to catch ? )
Not sure how you want to run the containers, but kured works well with rebootmgr when you are using Kubernetes. In my case k3s on top of microOS (the tumbleweed based on) is running fine with kured. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
participants (2)
-
Johannes Kastl -
Luc FERRIE