I set display calibration on imx7 torizon . i run debian:buster docker in that i make application without dockerfile and commit that container into other image and push that on docker hub when i want to run my application i need to wait for so long and it takes 5.6gb storage i used this command to run my app.
docker run -it -v /tmp/1000-runtime-dir:/tmp/1000-runtime-dir -v /dev:/dev -v /run/udev:/run/udev -e XDG_RUNTIME_DIR=/tmp/1000-runtime-dir -e QT_QPA_PLATFORM=wayland intersense123/my_app1:1.0
but that runs but not touchable.so give me proper command or approach to run my app on torizon with touchable .which image i should use to run application.because other toradex prebuild packages are run properly with touch so please give better way to build and run app on torizon imx7.
Hi, I’m the Toradex AI Assistant.
I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.
Hello! Thank you for your detailed question.
The main issue is that using debian:buster
as your base container is not recommended for Torizon on i.MX7, especially for touchscreen or graphical apps. Instead, you should use the Toradex-provided Debian base containers for Torizon, which already contain the necessary graphics and touch stack.
Recommended Approach
-
Base Image
Start your own Dockerfile using a Toradex-provided base, for example:FROM torizon/qt5-wayland
or, if you use a different GUI toolkit, choose a suitable Toradex container.
-
Include Application
Add your application binary and required dependencies using a proper Dockerfile instead of committing running containers. This will reduce the image size significantly. -
Permissions and Environment
Launch your container with permissions and environment suited for access to the display/touch input.
Example Dockerfile (for Qt application)
FROM torizon/qt5-wayland:2
COPY my_app /usr/bin/
CMD ["/usr/bin/my_app"]
Build and push your container:
docker build -t <your-dockerhub-username>/my-qt-app:latest .
docker push <your-dockerhub-username>/my-qt-app:latest
Example docker run
Command
docker run -it --rm \
-v /dev:/dev \
-v /tmp:/tmp \
-v /run/udev/:/run/udev/ \
-v /tmp/1000-runtime-dir:/tmp/1000-runtime-dir \
--device-cgroup-rule="c 4:* rmw" \
--device-cgroup-rule="c 13:* rmw" \
-e XDG_RUNTIME_DIR=/tmp/1000-runtime-dir \
-e QT_QPA_PLATFORM=wayland \
<your-dockerhub-username>/my-qt-app:latest
This structure is similar to what the official Toradex Weston container uses for display and touch.
Additional Tips
- Image Size: The Toradex-provided images are much smaller than a committed
debian:buster
image. Avoid committing containers to images; always start from a Dockerfile. - Development Workflow: For fastest and most reliable workflow, use the Torizon IDE Extension in Visual Studio Code. This will help automate container setup for graphics and touch.
- Touch Calibration: If your touchscreen requires calibration, you can use the
weston-touch-calibrator
container as described in the official guide.
Summary:
- Use Toradex’s Debian containers, not plain
debian:buster
- Use a Dockerfile to build your image (don’t commit running containers)
- Mount devices and set up necessary environment variables as shown
- For touch, base your setup on the Weston example for i.MX7
More info:
- Debian Containers for Torizon
- Testing Display and Touch on Torizon
- Touch screen calibration
- Torizon IDE Extension
If you follow these guidelines, your application should start quickly and support touch functionality out-of-the-box.
Best regards,
Toradex AI Assistant.
when i want to run my image i need to run base image weston and on another terminal need to run my app image so on torizon IDE extension can u give me some steps to run my software directly.
Sorry, it’s a bit hard to understand what is your issue here.
So you have 2 problems?
- Your docker container image is 5.6 Gb
- The touch is not working inside your app?
Have you tested this?
The Base Debian images from Toradex is based on the debian-slim,
which is more lightweight and is better for embedded applications rather than the full debian image.
Check this for a full list of base images.
- What is this prebuild packages that you say it’s working?