I am currently working on the Offline update feature.
I have successfully updated my Toradex system by providing an OS image and a Docker compose file and its working perfectly. But I’ve updated my system by providing one package at the time, first I’ve updated my systems by installing an OS Image and then I’ve updated the Docker compose file on my Toradex system.
To do this I had to create two seperate Lockboxes.
When I create one single Lockbox that contains an OS Image and a Docker compose file my system is only installing the OS Image and not the Docker compose file.
Unfortunately I cannot show you my image and my Docker compose file …
On the log I am not getting any error I think that the system is not recognising the Docker compose file or it doesn’t see it.
Do you have any suggestion ?
Thank you for your help
This sounds strange, synchronous OS & Docker updates should work with offline updates. Before I investigate further can you please provide the following information:
- What version of TorizonCore are you on?
- The full log from Aktualizr when the update is occurring. Please do not share just the end of the logs I want to see the full logs of Aktualizr from when the update starts to when it finishes.
Hello @jeremias.tx ,
I am currently using the 5.7.0 version of TorizonCore. on my imx8m-plus.
The logs are the following :
Then the system is restarting and I have the following logs :
It seems like I’m missing some logs but don’t know how can I get the history.
The way that I can fix this is to remove and insert the USB Stick into my system.
Than the logs are the following :
I’ve discover a topic that had the same issue. And I was able to solve it thanks to this.
I’ve disable the automatic boot and I’ve written this line force_install_completion = true in my uptane conf file and it is working perfectly.
Sorry for disturbing and thank you for answering,
I think I see what happened here. You must have run into the issue where the system was rebooting before the docker-compose portion of the update was complete: TorizonCore Issue Tracker
But it looks like you found this out on your own. As a side-note this issue was improved/fixed in the latest TorizonCore 6.X if you ever transition versions.
Hi @jeremias.tx ,
Thank you for this information.