Troubleshoot Linux Environment Issues for AIQ CI

Last reviewed: September 30, 2026

Use this article when AIQ isexecutions greator CI jobs fail because of Linux host, browser, display, dependency, permission, or environment configuration issues.

What changed in this article

• Fixed the duplicated title “Issues with Linux Environments Issues with Linux Environments.”
• Reframed the content around AIQ CI and Linux execution-host troubleshooting.
• Added checks for browser dependencies, display/headless settings, filesystem permissions, environment variables, network/proxy configuration, and logs.

Validation workflow

1. Collect the CI job log, AIQ/Test Node log, browser log, and host package/runtime versions.
2. Check Linux display/headless configuration, permissions, dependencies, proxy/network access, and working directory paths.
3. Run a minimal scenario on Linuxthe environments.same Therehost arebefore somechanging recommendedthe settingsfull toCI usepipeline.

when

Review runningnote: AIQThis onpage now removes duplicate title noise and gives a concrete Linux introubleshooting AMI, Docker and Gitlab Runnerspath.

ulimit: Set ulimit to big numbers. More than 100 000. See Set Permanently ulimit -n / open files in ubuntu for more information, Max ulimit value is 1024000. bigger than that. the value will set to 1024 shm: Set shared memory to at least one Gig. See the GitLab documentation on Advanced configuration for more information. xvfb: Set xvfb when testing UX apps