Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
The issue you’re encountering is likely related to file permissions and volume mounting paths. Based on the documentation and similar community issues, here are the solutions to resolve your RDP access problem:
Volume Path Issue
The problem appears to be with mounting volumes directly into the /home/torizon/ directory inside the container (1). When you mount a volume to /home/torizon/Loading.png, it can interfere with the container’s file permissions and directory structure.
Recommended Solutions
1. Use Alternative Mount Path
Instead of mounting the image to /home/torizon/Loading.png, mount it to a different path inside the container (1):
volumes:
- /tmp:/tmp
- /dev:/dev
- /run/udev:/run/udev
- /home/torizon/weston.ini:/etc/xdg/weston/weston.ini
- /home/torizon/Loading.png:/app/Loading.png
Then update your weston.ini configuration:
[core]
idle-time=0
[shell]
background-image=/app/Loading.png
background-type=scale
2. Use Bind Mount Configuration
For better control over file permissions, you can configure the volume as a bind mount with specific ownership (1):
volumes:
background_image:
driver: local
driver_opts:
type: none
device: /home/torizon/Loading.png
o: bind,uid=1000,gid=1000
services:
weston:
# ... other configuration
volumes:
- background_image:/app/Loading.png
3. Alternative Approach: Build Custom Container
For production environments, consider building your own Weston container with the background image included (2):
FROM torizon/weston:$CT_TAG_WESTON
COPY Loading.png /app/Loading.png
COPY weston.ini /etc/xdg/weston/weston.ini
RDP Configuration Verification
Ensure your RDP configuration is correct for Colibri iMX7D. According to the documentation, RDP should work with the following environment variables (3):
environment:
- ENABLE_RDP=1
The RDP_PORT=3389 environment variable you’re using is the default port and should work correctly (3).
File Permissions Consideration
When mounting files as volumes, ensure the torizon user (uid: 1000) has proper access to the mounted files (4). The issue might be that the mounted volume creates permission conflicts that affect the RDP service startup.
Try implementing the first solution with the alternative mount path, as this approach avoids mounting directly into the /home/torizon/ directory and should resolve your RDP access issue while maintaining the custom background image functionality.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
