VNC Wayland not receiving -SYS_NICE functionalities (docker)

Technical Support
, ,
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:

The issue you’re experiencing with setting thread priority using setschedparam in Torizon 6.8 when running your executable from the Wayland terminal, but not when running directly in the Docker container, could be related to how capabilities and permissions are managed in the Wayland environment compared to a direct container shell.

Here are a few points to consider:

  1. Wayland Environment: When running applications in a Wayland session, the environment might impose additional restrictions or lack certain capabilities that are otherwise available when running directly in the container shell. This could be due to how the Wayland compositor or the Weston container is configured.

  2. Capabilities: Although your capsh --print output shows that cap_sys_nice is available, the Wayland session might not be utilizing the same capability set as the direct container shell. Ensure that the Wayland session is started with the necessary capabilities.

  3. Entrypoint Script: The entrypoint script /usr/bin/entry.sh might be setting up the environment in a way that affects capability usage. Check if there are any differences in how the environment is set up when running through Wayland versus directly in the container.

  4. Docker Run Options: Double-check the Docker run options used to start the Weston container. Ensure that the --cap-add=SYS_NICE or equivalent options are correctly applied when the container is started, especially if the Wayland session is initiated as part of the container startup.

  5. Wayland and Weston Configuration: Review the configuration files for Wayland and Weston to see if there are any settings that might affect process capabilities or permissions.

If these suggestions do not resolve the issue, it might be necessary to further investigate the differences in environment setup between the Wayland session and the direct container shell. Additionally, consulting Toradex support or community forums might provide more specific insights related to Torizon 6.8 and Wayland.

Please, also check if these links can help you solve your problem:

Verdin iMX8MP: not HDMI on custom image.