Offline Update and short-lived containers (TOR-2304)

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:


Hello,

To effectively determine when an offline update process has completed on your Torizon system, you can monitor the logs generated by Aktualizr, the update client responsible for managing updates. These logs provide detailed information about the start and completion of update processes and can be accessed using the journalctl command. This approach allows you to track the progress and completion of updates in real-time.

For managing short-lived containers during updates, consider implementing a dynamic approach rather than relying on a fixed sleep duration. You can create a script or use systemd services to monitor the update process. For instance, your script could check the logs for a specific completion message or monitor the status of the update-related systemd service.

Additionally, incorporating health checks or watchdog mechanisms within your container can help ensure it remains active until the update process is confirmed complete. This strategy can prevent the container from terminating prematurely.

By using these monitoring techniques, you can more accurately determine when the update process has finished and manage your short-lived containers accordingly.

Best regards,
Toradex AI Assistant.

Please, also check if these links can help you solve your problem:

Offline updates not searching for lockbox.