Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
For your docker-compose packages to appear in the Lockbox creation interface, they must be canonicalized(1). This is a critical requirement for offline updates compatibility.
Required Steps
When pushing your docker-compose file to Torizon Cloud, you must use the --canonicalize flag(2):
torizoncore-builder platform push --canonicalize --credentials <credentials file> <path to docker-compose file>
Additionally, there’s a known issue with the Torizon Cloud interface: the package name must end with .lock.yml or .lock.yaml for it to appear in the Lockbox dropdown(3).
If you specified a custom package name using --package-name, ensure it follows this naming convention(1):
torizoncore-builder platform push --canonicalize --credentials <credentials file> --package-name myapp.lock.yaml <path to docker-compose file>
Important Naming Restrictions
The package name must only use basic ASCII characters, excluding control characters and the set \/:*?"<>|(1). Violating this can cause Lockbox generation to fail later(1).
What Canonicalization Does
Canonicalizing a docker-compose file puts it into a specific YAML format, removes comments, and associates HASH values to Docker images(2). This makes your deployment more secure since images are pulled based on HASHES instead of tags(2).
Try re-pushing your packages with the --canonicalize flag and ensure the package names end with .lock.yml or .lock.yaml. They should then appear in the Lockbox creation interface.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.