OSTree mirror and updates

Technical Support
, ,
1

Hi all,

In the past, we have been using OSTree to update our modules (torizon-core-docker-colibri-imx6ull-emmc-Tezi_6.x.x). For this purpose, we operate our own OSTree server and mirrored the feed from Service Notice to make it available within our infrastructure. Using a combination of:

ostree pull ...
ostree deploy ...

We have successfully performed OS upgrades on our devices for quite some time. Unfortunately, we discovered last week that the mirror now only displays the message:

“OSTree update distribution has been discontinued”

Is there a new URL that provides the OSTree repositories, or is there an alternative way to create and maintain an OSTree mirror?

Ideally, we would like to keep our current OS update process, as migrating to a different mechanism would require considerable effort and changes on our side.

Thank you very much for any guidance you can provide.

Best regards,
Sören Berger

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

The OSTree feed at Service Notice has been discontinued. The recommended approach for OTA updates with Torizon OS is to use Torizon Remote Updates(1)(2), which is built on OSTree and Aktualizr(1).

Recommended Migration Path

Torizon Remote Updates is the integrated over-the-air update system that works out-of-the-box with Torizon OS(2). It provides both device-side and server-side components(1):

  • Device side: Uses OSTree for filesystem management and Aktualizr (an implementation of Uptane) for secure update handling(1)
  • Server side: Toradex provides a hosted server at app.torizon.io(1)

Alternative: Self-Hosted OSTree Server

If you need to maintain your own infrastructure, you have options:

  1. Use TorizonCore Builder to create and push custom OSTree commits to your own compatible Uptane server(3)
  2. Configure Aktualizr to point to your own OTA backend that is Uptane-compatible(2)

The configuration can be modified by creating .toml files in /etc/sota/conf.d/(4).

Additional Considerations

  • OSTree uses a Git-like model for managing filesystem changes, downloading only deltas between versions(2)
  • The system provides atomic updates with automatic rollback on failure(1)(5)
  • Aktualizr is already deployed by default on Torizon OS devices(2)

To maintain your current workflow while adapting to the new infrastructure, I recommend exploring TorizonCore Builder’s capabilities for creating custom images and managing OSTree commits that can be deployed to your own server infrastructure(3).

Could you let me know which version of Torizon OS you are currently running? This will help provide more specific guidance for your migration path.

Best regards,
Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

Greetings @soeren.berger,

We no longer use the old feeds for our own Torizon Cloud update purposes. For Torizon Cloud, all of our OSTree builds are now uploaded to this AWS S3 bucket: https://tzn-ota-tdxota.s3.amazonaws.com/ostree-repo/

Best Regards,
Jeremias

4

Thanks for the reply!

We just tested it. Simply replacing the URL worked for us. I did not expect that it is that simple. :slight_smile:

Thanks!

5

Glad I was able to help.

Best Regards,
Jeremias