Skip to content

[TT-16950, TT-17009] fix: make Docker images backward compatible with runAsUser: 1000 #8102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
buger merged 1 commit into from
Apr 20, 2026
+9 −2

fix: make Docker images backward compatible with runAsUser: 1000

270c3e2
Select commit
Loading
Failed to load commit list.
Merged

[TT-16950, TT-17009] fix: make Docker images backward compatible with runAsUser: 1000 #8102

fix: make Docker images backward compatible with runAsUser: 1000
270c3e2
Select commit
Loading
Failed to load commit list.
probelabs / Visor: quality succeeded Apr 20, 2026 in 1m 47s

✅ Check Passed (Warnings Found)

quality check passed. Found 1 warning, but fail_if condition was not met.

Details

📊 Summary

  • Total Issues: 1
  • Warning Issues: 1

🔍 Failure Condition Results

Passed Conditions

  • global_fail_if: Condition passed

Issues by Category

Architecture (1)

  • ⚠️ .github/workflows/release.yml:179 - The build argument NONROOT_CHOWN=true is added in four separate but very similar jobs (build-and-push-ee, build-and-push-ee-main, build-and-push-fips, build-and-push-fips-main). This repetition, along with the overall similarity of the jobs, increases maintenance overhead. A change to the build arguments for these images needs to be applied in multiple places.

Powered by Visor from Probelabs

💡 TIP: You can chat with Visor using /visor ask <your question>

Annotations

Check warning on line 296 in .github/workflows/release.yml

See this annotation in the file changed.

@probelabs probelabs / Visor: quality

architecture Issue 

The build argument `NONROOT_CHOWN=true` is added in four separate but very similar jobs (`build-and-push-ee`, `build-and-push-ee-main`, `build-and-push-fips`, `build-and-push-fips-main`). This repetition, along with the overall similarity of the jobs, increases maintenance overhead. A change to the build arguments for these images needs to be applied in multiple places.
Raw output 
To improve maintainability and reduce redundancy, consider refactoring these jobs. Options include using a matrix strategy to run the same job with different parameters, or creating a reusable workflow (`workflow_call`) for the common build-and-push logic. As a smaller-scale improvement, YAML anchors could be used to deduplicate the common `build-args` block across the jobs.
View more details on probelabs