Torizon Offline Update does not work properly

[Sire]

Hello!

I’ve been working with Torizon’s OTA in development for some time now and it works very well. Now I have activated the offline update and wanted to perform an update with a USB stick. Unfortunately I can’t get it to work satisfactorily.

• If I only select the base image in the lockbox, the update works
• If I only select the “docker-compose.yaml” in the lockbox (without image), the update no longer works (it is relatively large, the update folder is 650MB)

When updating, the aktualizr always gives me the following message:

Mar 07 06:31:54 verdin-imx8mm-15035165 aktualizr-torizon[879]: Successfully loaded metadata from tarball: “/media/USB/update/images/473df850a8523c99d90d4b68994015050cbe7c7a5414d0b804d7347287579b68.images/4f0379704a1372b7a66b682c18950f7e25d4cf1a6a8488f006c45305310d605a.tar”
Mar 07 06:31:54 verdin-imx8mm-15035165 aktualizr-torizon[879]: validateMetadata: bad config file extension [RE]
Mar 07 06:31:54 verdin-imx8mm-15035165 aktualizr-torizon[879]: Loading of tarballs aborted!
Mar 07 06:31:54 verdin-imx8mm-15035165 aktualizr-torizon[879]: Offline loading failed: Failed to load docker tarball 4f0379704a1372b7a66b682c18950f7e25d4cf1a6a8488f006c45305310d605a.tar
Mar 07 06:31:54 verdin-imx8mm-15035165 aktualizr-torizon[879]: Event: AllInstallsComplete, Result - INSTALL_FAILED

I have looked at various posts, including the following:

• https://community.toradex.com/t/aktualizr-offline-updates-found

Greeting Simon

Software summary
------------------------------------------------------------
Bootloader:               U-Boot
Kernel version:           5.15.148-6.8.0+git.8c5c2dcbf6ba #1-TorizonCore SMP PREEMPT Tue Aug 6 10:01:59 UTC 2024
Kernel command line:      root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/0f2c059f6cb2d4d59ddaae4833a593e9c56460bff272ad93c67b18164eb5b7d6/0
Distro name:              NAME="TorizonCore"
Distro version:           VERSION_ID=6.8.0-build.22
Distro variant:           VARIANT="Docker"
Hostname:                 verdin-imx8mm-15035165
------------------------------------------------------------

Hardware info
------------------------------------------------------------
HW model:                 Toradex Verdin iMX8M Mini on Nouvag Baseboard
Toradex version:          0057 V1.1B
Serial number:            15035165
Processor arch:           aarch64
------------------------------------------------------------

[ToradexAI]

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

Did you like my answer?

---

Hello Simon,

Thank you for reaching out with your question about Torizon’s offline update. It seems like you’re encountering an issue with the docker-compose.yaml file during the update process. The error message “validateMetadata: bad config file extension” suggests there might be a problem with how the configuration file is being processed.

Here are some steps you can take to troubleshoot and potentially resolve this issue:

1. Check File Naming and Extensions: Ensure that your docker-compose.yaml file is correctly named and has the proper extension. Sometimes, hidden characters or incorrect extensions can cause issues.

2. Validate the YAML File: Use a YAML validator to ensure that your docker-compose.yaml file is correctly formatted. Any syntax errors in the YAML file could lead to issues during the update process.

3. Consider File Size and USB Formatting: Since the update folder is 650MB, make sure your USB stick has sufficient space and is formatted correctly (e.g., FAT32 or ext4) to handle large files.

4. Review Lockbox Configuration: Double-check the lockbox configuration in the Torizon Platform Services web UI. Ensure that all necessary files are included and correctly defined.

5. Monitor Logs for Additional Errors: Keep an eye on the logs for any additional error messages that might provide more context. You can increase the verbosity of the logs if needed to get more detailed information.

6. Update TorizonCore: Ensure that your TorizonCore version is up to date, as updates may include fixes for known issues with offline updates.

If these steps do not resolve the issue, you might try simplifying the docker-compose.yaml file to see if a smaller, simpler configuration works, then gradually add complexity to identify the specific cause of the problem.

I hope this helps you resolve the issue. If you have any more questions, feel free to ask.

Best regards,
Toradex AI Assistant.

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

Torizon OTA update using docker-compose.override.yml

I am in the process of configuring my application to be deployed with OTA and have read several articles including Using Multiple Containers with TorizonCore | Toradex Developer Center and Visual Studio Code Extension for Torizon | Toradex Developer Center. Basically my application is to be configured as follows: Image: goji-io - [based on torizon/debian] - should not be accessible outside, but communicates to goji-server over UDP. e.g networks: - backend image: goji-server - based on [bas…

Offline updates not searching for lockbox

Hello, we want to use a custom TorizonOS with offline updates managed by the Torizon Cloud. To test the offline update functionality I built a vanilla torizon-minimal (BSP6.6.0) with Yocto and flash it with TEZI. The device isn’t connected to the internet. After bootup I deactivated the aktualizr-daemon with sudo systemctl stop aktualizr sudo systemctl disable aktualizr to trigger and observe the update process manually. After that I provisioned and configured my device for offline updates…

Offline updates usb fail.

[Sire]

1. Check File Naming and Extensions : File extension is .yml
2. Validate the YAML File : YAML Formatter say OK
3. Consider File Size and USB Formatting: USB Stick is FAT32 and 32GByte free
4. Review Lockbox Configuration:
   61-custom-polling-interval.toml:
   [uptane]
   polling_sec = 30

99-offline-updates.toml
[uptane]
enable_offline_updates = true
enable_online_updates = true
offline_updates_source = /media/USB/update
force_install_completion = true // That was an attempt, even without the flag it didn’t work…

[rudhi.tx]

Hello @Sire,

Thanks for reporting this issue. We have a known issue that causes this error and we are currently working on fixing this. This is related to the TorizonCore Builder version that you are using to create the lockbox. It happens if the lockbox was created by TorizonCore Builder version 3.12.0.
The current workaround that we propose is to use either version 3.11.0 or a newer release than 3.12.0.

This Readme file explains how to switch to an early access tag for example: tcb-env-setup/README.md at master · toradex/tcb-env-setup · GitHub

Could you please give it a try and let me know how that goes?

[Sire]

It works with version 3.11.0! Thank you.