Changing/modifying default Weston container when debugging Qt application in VSCode


When I debug a Qt application through VSCode, I see two containers running - the torizon/weston-vivante:2 (Weston container) and my application container. Is there a way to modify or change the default Weston container that gets deployed to the board by VSCode? For example, I want to be able to change the default resolution settings for the Weston container. I can do that by following the instructions here: Working with Weston on TorizonCore | Toradex Developer Center .
If I map a volume containing a custom weston.ini file while manually running the Weston container, then I can see the modified display resolution. Is there a way to do something similar through VSCode with the default Weston container? I would like VSCode to either launch a custom Weston container or allow me to specify a custom weston.ini file so that I can modify the default behavior of the Weston container.


Greetings @govalles,

In our VSCode extension there should be configuration option dockercomposefile this let’s you supply a docker-compose file that describes a number of containers separate from your application container.

What this does is that using this compose file, the extension will launch the other container(s) described in the file in parallel with your application container. This would let you specify a custom weston container and such.

We have an example of how this configuration option is used as part of this example here: How to Build a GUI with ASP.NET Core and Blazor for TorizonCore | Toradex Developer Center

Give this a try and see if it suits your needs.

Best Regards,

Thanks for the reply Jeremias. I’ll take a look and let you know what I find. Appreciate the assistance as always.

Thanks Jeremias. That worked great.

Glad I was able to help!