Problem with deploying new image on toradex verdin-imx8mm board

Technical Support
, , ,
1

Hi,
I am using visual studio with toradex extension for the development. My application is running fine locally. While create-production-image is creating image successfully, run container-torizon-release-arm64 not deploying latest image/code on the device. The verdin-imx8mm is showing the old screen that had been modified long ago. It seems the either images are not getting updated or updated code not being pushed to the image. What could be the issue as I could not see any error in the VS code terminal.

Thanks
Pramod

2

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

Did you like my answer?

:+1: :-1:

Hello! When deploying applications using Visual Studio Code with the Toradex extension, there are several important steps to keep in mind:

  1. Container Image Preparation: Ensure that your container image is correctly built and tagged before deployment. This is crucial for a smooth deployment process. You can find more details on this here.

  2. Production Deployment Steps:

    • Use the “run-container-torizon-release” task in VS Code to build and run the release container on your target device. This step is essential for testing your application in a production-like environment. More information can be found here.
    • Execute the “create-production-image” task in VS Code to build a release container image and push it to your configured container registry. This ensures your application is ready for deployment across multiple devices. Further guidance is available here.

  3. Key Considerations:

    • Be aware that any changes made after the container starts will be lost once the container exits. This is a standard behavior of containerized applications. More details are available here.
    • You can run multiple containers from the same image, which is useful for scaling your application. More information is provided here.

To troubleshoot any issues you encounter:

  1. Review the output of the VS Code tasks to understand the steps being executed. This can help identify where the process might be failing. More troubleshooting tips are available here.
  2. Attempt to manually reproduce the failing step to pinpoint the issue.
  3. Check your container registry settings in the .vscode/settings.json file to ensure they are correctly configured.

If you need more specific guidance on any part of this deployment process, feel free to ask!

Best regards, Toradex AI Assistant.

3

Hi, I have checked with device terminal, Here is the response of docker images command.
docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
registry-1.docker.io/samalpramod/pyside2 v-20250428-1457 34d342183a8a 21 hours ago 749MB
192.168.1.176:5002/pyside2 arm64 c13ef58f1f98 11 days ago 749MB
192.168.1.176:5002/pyside2-debug arm64 fdc9222067bf 11 days ago 844MB
torizon/weston-vivante 3 99a7e4d40553 14 months ago 515MB
registry 2 33eeff39e0aa 19 months ago 25MB

But when I am trying to run the docker using the ID it throws error. Here is the respone of the docker run command of one of the images.

docker run c13ef58f1f98
Failed to create wl_display (No such file or directory)
qt.qpa.plugin: Could not load the Qt platform plugin “wayland” in “” even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

Aborted (core dumped)

4

Greetings @samalpamod,

Could you try removing all the container images on your Verdin i.MX8M Mini. Then, try rerunning the run-container-torizon-release-arm64 task in VSCode. This task should build the current code in your VSCode project and pull it on to your device. Perhaps something went wrong when you ran this before.

Best Regards,
Jeremias