Search by Tags

Torizon OS Issue Tracker

 

The following table contains known issues, scheduled bug fixes, and feature improvements for the Torizon OS images. The tickets are split into two major states:

  • Submitted (open): new features and bug fixes for Torizon OS versions that have not yet been released. They may be scheduled for a specific release version; not planned; or in our backlog. All of them have one of the following states:
    • Known Issue: a bug or unexpected behavior that has been reported and pending a fix. Once fixed, the status will transition to Fixed.
    • Feature Request: a new feature that may be added to a future release. Once released, the status will transition to New Feature.
  • Released (closed): new features and bug fixes for BSP versions that have already been released. All of them have one of the following states:
    • Fixed: a bug that has been fixed and released.
    • New Feature: something that didn't exist before and was added to a news release.

Any schedules are not guaranteed but reflect the current planning. The planning could be shifted due to priority changes.
Issues that are scheduled for a specific version will be integrated into the mentioned version of the BSP.

We will update this table continuously in order to always provide the latest state of our development plan.

Please see also the Toradex Embedded Linux Support Strategy to learn more about the different releases.

How to obtain the Torizon OS Images

Using the Toradex Easy Installer application in a Toradex SoM connected to the internet is the easiest and fastest way to install the latest version of Torizon OS into the device. Toradex also offers offline installers.

Clear Filter
Issue #StatusSubjectModuleComponentsSeverity

6.1.0-devel-202212 (Release date: 2022-12-02)
6.1.0-devel-202212 monthly pre-release
TOR-2639New FeatureAs a user, I want to use Docker Compose to V2 on TorizonCore, so I get the latest bugfixes and new featuresNot applicableOpen Embedded

Description: Docker Compose version 1.x was used on TorizonCore 5. On TorizonCore 6, Compose is being upgraded to version 2.x, so we continue to benefit from upgrades.

There should be no customer impact for TorizonCore users, therefore from our perspective, this is not a breaking change. You can continue to use all TorizonCore features and your tooling just like you did so far.

As a positive side-effect, Compose V2 should be much faster than V1, and this may have a positive impact in TorizonCore application startup time.

As another positive side-effect, the dependency on Python is dropped, opening up the possibility to remove Python entirely from the base OS. Users are expected to install Python - just like anything else related to their applications - in a container.

Learn more about Compose V2 on the blog post from Docker Announcing Compose V2 General Availability. For more information about Compose releases in general, see the https://docs.docker.com/compose/release-notes/