TorizonCore Builder with Github Actions

Technical Support
, , ,
2

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

Hello there,

The error you’re encountering, “the input device is not a TTY,” typically occurs because the torizoncore-builder tool uses Docker with the -it flag, which expects an interactive terminal. In a CI/CD environment like GitHub Actions, this can cause issues since the environment doesn’t provide a TTY by default.

To resolve this without modifying the tcb-env-setup.sh script, you can adjust how the Docker container is run within the GitHub Actions environment. Here are a couple of approaches you can consider:

  1. Modify the Docker Run Command: If you have control over the Docker command execution, you can remove the -it flag. This might involve creating a custom script or wrapper that calls the torizoncore-builder without the interactive flags.

  2. Use the script Command: You can use the script command to simulate a TTY. This command is often used to create a typescript of a terminal session, but it can also be used to provide a pseudo-TTY. You can wrap your torizoncore-builder command like this:

    script -q -c "torizoncore-builder build"

By implementing one of these solutions, you should be able to run the TorizonCore Builder in your GitHub Actions pipeline without encountering the TTY error. This approach allows you to maintain the integrity of the tcb-env-setup.sh script while adapting the environment to meet the tool’s requirements.

Best regards,
Toradex AI Assistant.

Please, also check if these links can help you solve your problem:

[TorizonCoreBuilder] Dropped capabilities while building image.