Search by Tags

TorizonCore Issue Tracker

 

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

  • Submitted (open): new features and bug fixes for TorizonCore 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 TorizonCore 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 TorizonCore into the device. Toradex also offers offline installers.

Clear Filter
Issue #StatusSubjectModuleComponentsSeverity

5.7.0 (Release date: 2022-07-28)
5.7.0 LTS release. Learn more on https://www.toradex.com/news/torizon-core-release-5-7-0-quarterly-release
TOR-2366FixedThe docker-integrity-checker and docker-compose systemd services don't use /etc/docker/config.json as the default configuration fileNot applicableOpen EmbeddedLow

Description: Docker uses a configuration file that is kept by default in the user directory (something like "/home/user/.docker/config.json"). This is not ideal for TorizonCore, since the home directory is not touched by updates, and user configuration hardly ever makes sense. Due to that, some of our services explicitly set the DOCKER_CONFIG environment variable to use the config file at /etc/docker/config.json, which is great because, as a user, you can customize it, capture changes with TorizonCore Builder, and replicate the configuration to all boards.

Recently, it was reported that the configuration file /etc/docker/config.json was not being used by the docker-integrity-checker and the docker-compose services, leading to unexpected behavior.

This is being fixed in a way that the DOCKER_CONFIG variable is globally set in TorizonCore, so all systemd services and the shell environment make use of it.

Workaround: Create a systemd override for the affected services that appends the line Environment="DOCKER_CONFIG=/etc/docker", then capture changes with TorizonCore Builder.
Or set "/home/torizon/.docker/config.json" and "/etc/docker/config.json" with the same contents.
Or use a symbolic link from one file to another.