I am using the new Torizon Cloud front end today and when attempting to create a new lockbox I’ve found that I cannot specify some of the docker-compose packages in my repository.
What I see when I click the dropdown menu under Available Packages > Select Package is a list of the packages in the base directory starting with the word ‘docker…’. We have some of these stray packages from ad-hock builds, but I am unable to view/select a version within a ‘TESTING’ package.
Perhaps the way we are building and organizing these packages needs to change to work with the new interface - if so that’s OK, just want to understand what qualifies a package and its versions to appear in that drop-down menu, and what we should do differently going forward with the new interface.
Right now when pushing a docker-compose package to, say, release candidate 5 of version 2.2.0 of the TESTING package, I’ll run something like the following:
Please let me know if I’m missing something simple in the filtering on the website or maybe we need to change our naming convention or include some other data in the platform push?
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello there!
I understand you’re having some trouble with the Torizon Cloud interface, specifically with certain docker-compose packages not appearing in the dropdown menu when creating a new lockbox. Let’s see how we can address this.
To ensure your packages appear in the dropdown, consider the following:
Consistent Naming Conventions: Make sure your package names follow a consistent and recognizable pattern. Avoid unexpected characters or formats that might cause them to be excluded.
Correct Directory Structure: Verify that your packages are located in the correct directory within your repository. The Torizon Cloud interface may only display packages from specific directories, so ensure your packages are in the expected location.
Clear Versioning: When pushing a package, ensure the versioning is clear and follows a logical sequence. The command you are using (torizoncore-builder platform push) should have the package name and version correctly set.
Interface Filters: Check if there are any filters applied in the Torizon Cloud interface that might be hiding certain packages. Ensure no filters are unintentionally applied.
Testing with a Simple Package: As a troubleshooting step, try creating a simple test package with a straightforward name and version to see if it appears in the dropdown. This can help determine if the issue is with specific packages or a broader configuration problem.
By reviewing these aspects, you should be able to identify why certain packages are not appearing and adjust your process accordingly. If you continue to experience issues, simplifying your package structure and naming to align with typical conventions used in Torizon Cloud might help.
I hope this helps! If you have any more questions, feel free to ask.
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem:
I just tried this myself and was able to reproduce the same behavior. What I noticed is that in the new frontend it only recognizes docker-compose packages where the package name ends in *.lock.yml/yaml for lockboxes.
For example, your package name here of “TESTING” was not recognized. But, if I changed the package name to “TESTING.lock.yaml” then it does show up in the package listing when creating a Lockbox.
This is definitely unintended as in the old frontend, both “TESTING” and “TESTING.lock.yaml” are recognized as valid options for a lockbox. Of course assuming the docker-compose file that was uploaded is canonicalized, which I assume yours is since it has the *.lock.yml extension.
I will report this behavior to our team to fix. For now, to workaround this use package names ending in *.lock.yml/yaml if possible.
