Torizon cloud and docker compose

Playing around with the OTA updates with the torizon cloud. When I upload a docker-compose file and trigger an update, were does the compose file go on the target device? Were can I find the documentation for this.

Also, I plan to have this auto boot, but I want to make my own service. Can the torizon cloud be set up to update the docker-compose file I point to in my .service file. If so were is the documentation for this as well

Last question - can I set up the cloud to update a particular folder. Lets say I just need to update an image and it’s located in /home/torizon/images.

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

Did you like my answer?

:+1: :-1:


Based on the provided context:

  1. Where does the docker-compose file go on the target device?

    • The specific path where the docker-compose file is stored on the target device is managed by the Torizon system, but the exact location is not detailed in the provided data. For precise information, you should consult the official Torizon documentation.
  2. Can Torizon Cloud be set up to update the docker-compose file specified in a custom .service file?

    • Yes, Torizon Cloud can be configured to update the docker-compose file specified in your custom .service file. For detailed instructions on how to set this up, you should refer to the Torizon documentation, which provides guidelines on creating and managing services with Torizon Cloud.
  3. Can the cloud update a particular folder, such as /home/torizon/images?

    • Currently, Torizon Cloud does not support direct updates to a specific folder on the target device for individual files like images. Updates are generally managed through docker-compose files and the associated services. For more detailed information, it is advisable to consult the official documentation.

For all these queries, the official Torizon documentation will be the best resource for detailed guidance.

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

Signing and Pushing Torizon OS Packages to Torizon Cloud | Toradex Developer Center.

Hi @jeffbelz

The file goes to this location and is replaced when updated.

/var/sota/storage/docker-compose/docker-compose.yml

Sorry, I think we don’t have a clear documentation about this, but the docker-compose update is implemented similar to a subsystem update.

The firmware_path (“update payload path”) is defined when creating the subsystem update.

The “correct” way is to create a subsystem update similar to what we do with the firmware update example.

Did you have any further questions on this topic?

Best Regards,
Jeremias

I think I’m good

Glad to hear, thanks for getting back to us.

Best Regards,
Jeremias