 TCB-426 | Known Issue | Building kernel modules for Verdin AM62 fails with error "make[1]: *** No rule to make target 'arch/arm64/tools/gen-sysreg.awk', needed by 'arch/arm64/include/generated/asm/sysreg-defs.h'. Stop." | Low |
Description: As reported on Hello-mod kernel module doesn’t build Building kernel modules for Verdin AM62 fails with error "make[1]: *** No rule to make target 'arch/arm64/tools/gen-sysreg.awk', needed by 'arch/arm64/include/generated/asm/sysreg-defs.h'. Stop." Workaround: This has been fixed and you must use the Torizon OS monthly 202403 or newer. |
| TorizonCore Builder 3.8.1 release |
| TCB-401 | Known Issue | "platform lockbox" command fails with error "TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'" when using a custom OS image | Low |
Description: On TCB 3.8.0, when you use the "platform lockbox" to create a lockbox that has been defined in the Platform Services, it may fail with the error "TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'" in case your lockbox contains an OS update with a custom OS image that you pushed to the Platform Services. |
| TCB-399 | Feature Request | As a user, I want the "platform lockbox" to work on non-host networks, so I can use it on GH Actions | |
Description: As reported on the TorizonCore Builder issue tracker on GitHub, the command "platform lockbox" fails on non-host networks. |
| TorizonCore Builder 3.5.1 patch release |
| TCB-293 | Known Issue | Build error "KeyError: 'dir'" in TCB 3.5.0 when bundling images | Critical |
Description: When bundling a Docker Compose file with TorizonCore Builder 3.5.0, a stack trace is printed and the error "KeyError: 'dir'" is displayed |
| TorizonCore Builder 3.10.0 release |
| TCB-438 | Feature Request | Add basic support for WIC images on TCB by supporting some OSTree features with the build command | |
Description: Until this feature is introduced, only Toradex SoMs with images in the Toradex Easy Installer format are supported.
Moving forward, raw filesystem images including the WIC images generated by Yocto/OpenEmbedded are also supported. The initial support is limited to using standalone commands and making OSTree operations. The build command, bundling of images, kernel and device tree operations are not supported yet. |
| TCB-328 | Known Issue | Bundle command fails with the error "ConnectionRefusedError: [Errno 111] Connection refused" when using a Linux distro with the ZFS filesystem | Low |
Description: TorizonCore Builder does not support the ZFS filesystem. If you setup a computer with a Linux distro that uses ZFS - for example, Ubuntu 22.04 LTS with the experimental ZFS support enabled - you will see errors such as "ConnectionRefusedError: [Errno 111] Connection refused" when running the bundle command.
On TorizonCore Builder we run Docker in Docker (DinD) and use the OverlayFS driver. As stated on Docker storage drivers - Supported storage drivers per Linux distribution, it is the recommended storage driver and requires XFS or ext4 as the filesystem where "/var/lib/docker" (from the DinD) is located. In practice, this means that you have to use a filesystem compatible with OverlayFS on your computer for TorizonCore Builder to work, even if you don't run the Docker daemon itself with OverlayFS.
At the moment, our plans are to make the error message more intuitive, stating that ZFS is not supported. We will keep monitoring the adoption of ZFS and possibly other filesystems and, as they gain traction and become the default on major Linux distros, we might consider adding support for them in upcoming TorizonCore versions. Workaround: Use a Linux distro with either ext4 or XFS (with `d_type=true` enabled) as the filesystem |
| TCB-208 | Known Issue | TorizonCore Builder: bundled container executed with net=host permission fails with error "SIOCSIFFLAGS: Operation not permitted" | Low |
Description: As reported in our community, with TorizonCore Builder, If you bundle a container that sets extended attributes on files inside the container (for example, using the "setcap" command), the container will fail upon execution with the error "SIOCSIFFLAGS: Operation not permitted" or another related error.
If you remove the bundled container and manually pull it from Docker Hub, then try to run it again, the same error will not happen.
While this bug was investigated, we came to docker build does not preserve xattrs in the generated image, and after several tests such as setting capabilities and building the container with the classic Docker vs Buildkit, we concluded that:
- Docker does not keep all extended attributes that are set in a Dockerfile, regardless of using Buildkit or the Classic Docker builder, and using Docker directly (without Compose).
- Even some capabilities that are kept by Docker get lost when bundling a container with TorizonCore Builder
Given the constraints of Docker, we won't work on a fix in TorizonCore Builder, and we advise you to not rely on xattrs or any feature based on them inside a container.Workaround: For this specific bug: set the suid for executable files rather than using setcap. For example use "chmod u+s" instead of "setcap" seems to work as well and may carry through the bundle process.
In general, do not rely on xattrs or any feature based on them inside a container. Capabilities and ACLs are features that may be set via xattrs and can also be set via docker-compose properties, which is the recommended way to set them in a portable and reliable way. |
| TCB-232 | Known Issue | TorizonCore Builder: "bundle" command causes issues on a local registry on Windows machines | Low |
Description: After using the "bundle" command the container running the local registry stops working properly. On further investigation, it appears that while the container for the local registry is still up and running the port for this container is no longer accessible.
This issue only happens on Windows machines.
Update: this bug is not reproducible anymore, therefore it has possibly been fixed by an update on Docker for Windows. If you face such issue, please let us know and we'll reevaluate it. Workaround: Until the bug is fixed, use a Linux machine. |
| TCB-409 | Known Issue | Applying overlay on Apalis iMX8X fails | Low |
Description: Activating device tree overlay fails on Apalis i.MX8 |
| TCB-327 | Feature Request | As a user of torizoncore-builder I want a line number when a parse error occurs in the "build" command | |
Description: When running the build command with a tcbuild.yaml file with incorrect syntax, the error does not display the line number. |
| TCB-316 | Known Issue | Build command fails when not using Docker volumes | Low |
Description: It is possible to run TorizonCore Builder without using a Docker volume, by passing some extra flags to the setup script: "source tcb-env-setup.sh -d -s /srv/builder-tool/storage".
When using the "tcb build" command, though, it does not create the output directory as expected.
It has been reported on the TCB GitHub issues. Workaround: Use docker volumes (the default option) when using the build command. |
| TCB-305 | Known Issue | "dto deploy" error "AttributeError: 'Namespace' object has no attribute 'update'" because it does not have the "update" switch | Low |
Description: The command "dto deploy" is a combination of several commands at once. It essentially runs the following commands in sequence:
- images download
- dt checkout
- dto remove
- dto apply
- union
- deploy
However not every switch for the individual commands is supported by dto deploy. In particular for this bug the --update switch from the dt checkout command isn’t supported which causes the error AttributeError: 'Namespace' object has no attribute 'update'Workaround: Run the commands stated in the public description above one-by-one.
You might not need to run all of them, though. Consult each command functionality in the TorizonCore Builder - Commands Manual to evaluate which ones you need to run. |
| TCB-205 | Known Issue | "images serve" command not working on Windows | Low |
Description: The TorizonCore Builder "images serve" command was added to TorizonCore Builder on version 3.2.0. It does not work on Windows due to two limitations: (1) the Docker host network driver is not supported on Windows and (2) the multicast DNS (mDNS) used by Avahi does not work. Workaround: Take the output image from TorizonCore Builder and use an SD Card/USB stick to install it to a Toradex SoM.
Alternatively, use a Linux machine. |
| TCB-230 | Known Issue | Torizoncore builder "bundle" command fails when TCP docker access is enabled | Low |
Description: When Docker is run with TCP access, the bundle command fails with error "ConnectionRefusedError: [Errno 111] Connection refused" Workaround: Run Docker with the default configuration instead of TCP. |
