Torizon Core Builder 3.11 platform push command throws an error

Technical Support
, , , ,
1

Hello, I have a command that stopped working at some point {these values haven't changed}:

torizoncore-builder platform push --credentials {credentials_file_name} --hardwareid {hardware_id} --package-name {package_name} --package-version {package_version} build/lockbox.tar.gz

WARNING: This script is outdated. To update it, run 'wget -o tcb-env-setup.sh https://raw.githubusercontent.com/toradex/tcb-env-setup/master/tcb-env-setup.sh'

Setting up TorizonCore Builder with version 3.11.

Pulling TorizonCore Builder...

3.11: Pulling from torizon/torizoncore-builder

Digest: sha256:789105f3394c5d422a26395e356b2f30a33f6de68305bc5831d8394b85b0cbec

Status: Image is up to date for torizon/torizoncore-builder:3.11

docker.io/torizon/torizoncore-builder:3.11

Done!

Setup complete! TorizonCore Builder is now ready to use.

TorizonCore Builder internal status and image customizations will be stored in Docker volume named ‘storage’.

********************

Important: When you run TorizonCore Builder, the tool can only access the files inside the current working directory. Files and directories outside of the current working directory, or links to files and directories outside of the current working directory, won’t be visible to TorizonCore Builder. So please make sure that, when running TorizonCore Builder, all files and directories passed as parameters are within the current working directory.

Your current working directory is: /builds/…/build

********************

For more information, run ‘torizoncore-builder -h’ or go to TorizonCore Builder Overview | Toradex Developer Center

An unexpected Exception occurred. Please provide the following stack trace to

the Toradex TorizonCore support team:

Traceback (most recent call last):

File “/builder/torizoncore-builder”, line 222, in 

mainargs.func(mainargs)

File “/builder/tcbuilder/cli/platform.py”, line 584, in do_platform_push

platform.push_ref(

File “/builder/tcbuilder/backend/platform.py”, line 1034, in push_ref

commit = repo.read_commit(ref).out_commit

gi.repository.GLib.GError: g-io-error-quark: Refspec 'build/lockbox.tar.gz' not found (1)

The goal is to generate lockbox for one boards and push it into the Torizon Cloud so that it can be referred to from another lockbox for another board. The whole workflow worked just fine. The file that I am trying to push is present on the file system. Last known successful build with this lockbox happened on 28 Aug 2025 with the same Core Builder image. I am not sure if the credentials file can be broken as there are other commands that use the same file and they work totally fine.

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

The error you’re encountering indicates that TorizonCore Builder is trying to interpret build/lockbox.tar.gz as an OSTree reference rather than a file path(1). This is causing the GError: Refspec 'build/lockbox.tar.gz' not found error.

Issue Analysis

The platform push command expects different input types depending on what you’re trying to push(1):

  • OSTree references (commit or branch names)
  • Docker-compose files (ending in .yml or .yaml)
  • Generic package files (any other file type)

Solution

For pushing a lockbox (which is a generic package), you should use the correct command structure. Based on the documentation, the platform push command for generic packages requires(1):

torizoncore-builder platform push --credentials <credentials file> --hardwareid <my generic package hardwareid> <path to generic package file>

Recommended Approach

Since you’re working with lockboxes for offline updates, you should instead use the dedicated platform lockbox command(1). This command is specifically designed for generating lockboxes:

torizoncore-builder platform lockbox <LOCKBOX_NAME> --credentials <credentials file>

The platform lockbox command generates a lockbox by fetching metadata from Torizon Cloud, creating a unique secure image for offline updates in a format ready to copy to an SD Card or USB Stick(1).

Alternative Workflow

If you need to push the lockbox as a generic package to Torizon Cloud, ensure you’re using the correct syntax for generic packages(2):

torizoncore-builder platform push --credentials <credentials file> --hardwareid <hardware_id> --package-name <package_name> --package-version <package_version> build/lockbox.tar.gz

However, make sure the hardwareid parameter matches your target hardware and that the file path is accessible within your current working directory.

Troubleshooting Steps

  1. Verify file accessibility: Ensure build/lockbox.tar.gz exists in your current working directory
  2. Check file format: Confirm the file is not corrupted and is a valid tar.gz archive
  3. Update TorizonCore Builder: The warning suggests updating your setup script
  4. Use absolute paths: Try using the full path to the lockbox file

The most likely solution is to use the platform lockbox command instead of trying to push the lockbox file as a generic package, as this aligns with the intended workflow for lockbox management(1)(3).

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

Greetings @ollamh,

I’m a bit confused, you’re trying to push a Lockbox as a package?

The issue is that TorizonCore Builder assumes the type of package is an OS and it’s looking for an OS with the reference “build/lockbox.tar.gz”.

Is build/lockbox.tar.gz a valid file-path that TorizonCore Builder can access? Looking at the logic in the tool it goes like so:

  • If input is a file then it pushes the file as a package
  • If the input is not a file then it assumes you’re trying to push an OS with the same reference name as the input.

Looking here it seems the tool decided that build/lockbox.tar.gz was not a file. Meaning the file-path isn’t valid. Could be due to a typo, wrong file-path, or the file-path is somewhere TorizonCore Builder can’t access.

Best Regards,
Jeremias

4

Thank you @jeremias.tx , I reviewed the path situation and it seems that it was the error.

5

Glad we were able to help clarify.

Best Regards,
Jeremias