Update Dockerfile

[HAjAdnan]

Summary

• Describe the user-facing or operational change.

Related Issues

• Closes #
• Related to #

Validation

• npm run lint
• npm run test:unit
• npm run test:coverage
• Coverage is still >= 60% for statements, lines, functions, and branches
• SonarQube PR analysis is green or any remaining issues are explicitly documented below

Tests Added Or Updated

• List every changed or added automated test file.
• If no production code changed, state that here.

Coverage Notes

• If this PR changes src/, open-sse/, electron/, or bin/, explain which tests cover the change.
• If coverage moved down in any touched file, explain why and what follow-up task will recover it.

Reviewer Notes

• Call out any risky areas, migrations, feature flags, or manual validation that reviewers should know about.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[diegosouzapw]

Thanks again for the Dockerfile attention — really appreciate you looking at the build. 🙏

Closing this one for the same reason as your #7723 (and noting the two overlap on the same file): it strips id=apt-cache from the BuildKit cache mounts. Those id= arguments were added on purpose in #6291 to fix a parse failure on strict BuildKit frontends like Railway's Metal builder, which reject cache mounts without an explicit id=. Removing them (even partially — this PR leaves id=apt-lists but drops id=apt-cache on the same RUN) re-triggers exactly the shape that strict frontend rejects. Regular docker buildx won't complain locally, so it's an easy one to miss.

Nothing from your diff is being used — closing here just means the current mounts are intentional.

If there's a concrete build issue you ran into, please open an issue with the exact error/builder and we'll sort the real cause. Thank you for contributing — hope to see more from you! 🚀