Specifying Lockbox Contents in the New Torizon Cloud Interface

[ToradexAI]

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:

1. 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.

2. 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.

3. 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.

4. 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.

5. 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:

Several question for torizon-minimal and offline updates

Hello, I have several general questions regarding Yocto build of Torizon and the offline updates: In OSTree | Toradex Developer Center it says “Whenever Torizon OS is built using Yocto/OpenEmbedded’s bitbake, a OSTree repository is automatically initialized and a new OSTree commit is created. For every following build, a new commit is created where only changed files are added to the repository.” What happens to the OSTree repo when the build environment is reset? How is an installation …

Update using Torizon OTA for newbie

I’ve programmered two .Net Core applications in different containers and came to the next step: Deployment of two application containers and a local UI in Kios mode. I’ve read the articles Link 1 and link 2 I’ve saved an example from the first article, uploaded in our account and assigned to the device. At first I’ve got an error update failed, then I’ve stopped the containers and tried again. This time there were no errors, but all containers exept three disappiered. Do I have to include …

Use torizoncore-builder to add tags for torizon.io packages.