[🐛 Bug]: Firefox: "Some of Nightly's security features may offer less protection on your current operating system"

[AB-xdev]

What happened?

When executing selenium/standalone-firefox the following warning shows up:

The link seems to lead to https://support.mozilla.org/en-US/kb/install-firefox-linux#w_security-features-warning

Docker Selenium version (image tag)

4.26.0

[github-actions]

@AB-xdev, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[VietND96]

I think that docs for Firefox running on host, since in the container, we don't have a config of apparmor.service
Sometime before, I also tried another installation ways e.g via Mozilla apt, or install without root in $HOME dir, but that flag does not clear.
Do you have any suggestion for this?

[AB-xdev]

NOTE: So far this only seems to happen on the ARM64 variant of the image. Somehow there is Firefox Nightly used while normal Firefox is used for AMD64.

[VietND96]

For case Nightly build in ARM64 image, it is a known issue that noted in README

Mozilla Firefox now is available for Linux/ARM64 via Nightly channel. The Firefox version in ARM64 will be different with the AMD64 until the stable release is available. The Firefox (node and standalone) images are available in multi-arch.

The version in both arch will be in sync once Mozilla release for linux/arm64 on stable channel

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.