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

5.6.0-devel-202203 (Release date: 2022-03-09)
5.6.0-devel-202203 monthly pre-release
TOR-1566New FeatureAs a developer, I want to use a lint tool in Dockerfiles, so code quality is improvedAll supported modulesDebian Base Containers

Description: Even though we pay attention to best practices since practically the birth of Torizon, so far we didn't use a linter in our CI pipelines. After some investigation, we have decided to adopt hadolint and we recommend that, if you write your own Dockerfiles, you also use a linter.

As an example, you can see the implementation in our torizon-samples repository. we ignore some warnings on a per-repository basis, adapted to their context.