Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
To achieve the customizations you need for OTA updates in Torizon OS using Aktualizr, you can follow the suggested approach outlined in the context:
-
Polling: Continue using the existing polling mechanism that checks for updates every 5 minutes, as it is already functioning as intended.
-
Notification to Application: To notify your application running inside a Docker container when an update is available, you can implement a custom notification mechanism. This could involve:
- Using a messaging system or a file-based notification that your application can monitor.
- Implementing a listener within your application that checks for update availability signals from Aktualizr.
-
User Confirmation: Use the
flockcommand to block updates until the user confirms. This command can effectively maintain the lock even after a reboot, ensuring that updates are not applied until you explicitly allow them. You will need to ensure that your application logic handles the user confirmation process correctly.
Regarding the .toml configuration files, there may be a set of these files that can be used to customize the behavior of Aktualizr, including settings for notifications and user confirmation requirements. You should refer to the specific documentation for Torizon OS and Aktualizr for the correct parameters to set.
By implementing this approach, you can ensure that your application is notified of available updates, and updates are only applied with user consent, while safely managing the update process using flock.
Please, also check if these links can help you solve your problem: