Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
I’d be glad to help with your questions about Torizon Cloud updates! To provide you with the most accurate guidance, could you let me know which OS and version you are using? You can run the tdx-info command to get detailed information about your hardware and OS setup. For more details about this command, see tdx-info.
Update Information and Metadata
Based on the available documentation, here’s what I can tell you about update information:
Online Updates Information
For online updates, Aktualizr handles the update process and logs detailed information that you can monitor (1). You can track update progress and completion by monitoring the logs generated by Aktualizr using the journalctl command (1).
Package Metadata for Updates
When pushing packages to Torizon Cloud, you can specify custom metadata and versioning information (2):
For Docker Compose packages:
- Use
--package-name to set a custom name for the update package (2)
- Use
--package-version to specify the version (can be any legitimate string, not just numerical) (2)
- The package name and version will appear in the Torizon Cloud web UI (2)
For generic packages:
- Use
--custom-meta to add custom metadata in JSON format (2)
- This custom metadata is available on the device during the installation phase (2)
Example command for adding custom metadata to a generic package:
torizoncore-builder platform push --credentials credentials.zip --hardwareid genpack --package-name tcb-test-genpack --custom-meta '{"fw_ver": "000007"}' --package-version 1.1 generic-package.bin
(2)
Canonicalized Docker Compose Files
Regarding canonicalized docker-compose files, the documentation explains that canonicalizing puts the file into a specific YAML format, removes comments, and associates HASH values to Docker images (2). When using the --canonicalize option, TorizonCore Builder will save a copy with .lock.yml or .lock.yaml extension (2).
Recommendations
For better tracking of update contents, consider:
- Using descriptive package names and versions when pushing updates (2)
- Adding custom metadata to generic packages using the
--custom-meta option (2)
- Implementing your own meta-file approach for additional information as you suggested
The metadata approach you mentioned could indeed be a good solution for providing more detailed update information beyond what’s available in the standard update metadata.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
