CICD for multiple container applications

[i.staehli]

I have set up 2 container applications with the CICD from the VS Code template. The pipeline can successfully push the containers to the registry and also the docker-compose.yml to Torizon Cloud.

On Torizon Cloud I have two docker-compose packages with these file contents:

services:
  server-app:
    image: organization/server-app@sha256:148429dd9c1a37fdbe6dfd036a052f36bc2c2fe7ba351143a2cdcf8cfbf680c2
    volumes:
    - /var/run:/var/run
version: '3.9'

services:
  client-app:
    image: organization/client-app@sha256:23fbc10eef79f6bb4bda713d50730cb36d6219031775ab2d38d69a3784ca3100
version: '3.9'

But now I realized that I can only install one of them at a time.

1. I guess I need a single docker-compose package with a file that contains both?
2. What is the best method to have a pipeline that somehow combines the content of these files?
3. Is there even a point uploading the single applications to Torizon Cloud then?

[ToradexAI]

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

Did you like my answer?

---

Hello!

To deploy both of your container applications simultaneously on Torizon Cloud, you indeed need to combine your two separate docker-compose.yml files into a single file. This will allow you to manage both services as a single deployment unit.

Steps to Combine Docker Compose Files

1. Create a New Docker Compose File:

   • Start by creating a new docker-compose.yml file.

2. Merge the Services:

   • Copy the services section from each of your existing Compose files into the new file. Ensure that each service has a unique name.
   • Your combined file should look something like this:

     version: '3.9'
     services:
       server-app:
         image: organization/server-app@sha256:148429dd9c1a37fdbe6dfd036a052f36bc2c2fe7ba351143a2cdcf8cfbf680c2
         volumes:
           - /var/run:/var/run
       client-app:
         image: organization/client-app@sha256:23fbc10eef79f6bb4bda713d50730cb36d6219031775ab2d38d69a3784ca3100
     

3. Network Configuration:

   • By default, Docker Compose will create a network for your services, allowing them to communicate with each other. If you have specific network requirements, you can define them under a networks section.

Automating the Process in CI/CD

To automate the merging of these files in your CI/CD pipeline, you can use a script or a CI/CD tool feature:

• Script Approach: Write a script (e.g., in Python or Bash) that reads both Compose files and merges them into a single file. This script can be executed as part of your CI/CD pipeline.

• CI/CD Tool Feature: Some CI/CD tools allow you to define steps that can concatenate files or execute scripts. Use these features to automate the merging process.

By combining your Compose files, you can deploy both applications together, simplifying management and ensuring that they are always deployed in a compatible configuration. This approach also aligns well with the microservices architecture supported by Torizon.

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:

Build custom Torizon OS with and without containers

I’ve already setup a tcbuild.yaml to create a TEZI image containing: custom Torizon OS (device trees, kernal arguments, …) containers This works as expected, and I can install it when the SoM runs Toradex Easy Installer. Now I’ve been starting playing with Torizon Cloud, and I tried to upload my custom Torizon OS. But the requirement is that I must provide A .tar file containing the Torizon OS Image with no-container pre-provisioned for offline installation. Should I build a different v…

Using Multiple Containers with Torizon OS | Toradex Developer Center

Docker-compose service `inactive` after combined lockbox update.

[jeremias.tx]

Greetings @i.staehli,

I guess I need a single docker-compose package with a file that contains both?

Yes, if you want a single docker-compose package that contains several other container images, then you need to describe these all in a single docker-compose.yml file.

What is the best method to have a pipeline that somehow combines the content of these files?

If I understand your situation correctly. You basically have two separate VSCode projects for each of your applications right?

If that is the case maybe what you can try is the following. Keep the two separate projects for development purposes. But, in one of the projects, modify that project’s docker-compose.yml file so that it references both your container images. Then, create a CI/CD pipeline from that project. In theory it should use that project’s docker-compose.yml file as the input for the package upload.

If all goes well, the result on Torizon Cloud should be a single docker-compose package that references both container images.

Is there even a point uploading the single applications to Torizon Cloud then?

Depends, is there any point to you only running one of these applications on your system? If no, then it doesn’t really make sense then to have these separate.

Best Regards,
Jeremias