[java] Linux ARM "os.arch" system property is "aarch64"

[mkurz]

User description

💥 What does this PR do?

I am running Linux on a MacBook Pro M1 via https://asahi-alarm.org/.
The architecture of this machine is identified as aarch64 in Java (and in general).
When selenium tries to start selenium manager it fails because it tries to execute the x86-64 binary, which of course does not work on an aarch64 system.

🔧 Implementation Notes

Just also checking for aarch64.. Easy.

$ uname -a
Linux mkurz-macbook-pro 6.16.4-asahi-2-1-ARCH #1 SMP PREEMPT_DYNAMIC Tue, 02 Sep 2025 08:56:47 +0000 aarch64 GNU/Linux
$ uname -m
aarch64

$ jshell
|  Welcome to JShell -- Version 17.0.16
|  For an introduction type: /help intro

jshell> System.getProperty("os.arch")
$1 ==> "aarch64"

🔄 Types of changes

• Bug fix (backwards compatible)

---

PR Type

Bug fix

---

Description

• Add support for detecting aarch64 architecture on Linux systems

• Fix Selenium Manager binary selection for ARM-based Linux platforms

• Improve error handling for unsupported ARM architectures

---

Diagram Walkthrough

flowchart LR
  A["System Architecture Check"] --> B["os.arch Property"]
  B --> C["ARM Detection Logic"]
  C --> D["aarch64 Support Added"]
  D --> E["WebDriverException Thrown"]

Loading

File Walkthrough

	Relevant files
Bug fix	SeleniumManager.java Add aarch64 architecture detection support                              java/src/org/openqa/selenium/manager/SeleniumManager.java Extended ARM architecture detection to include aarch64 Modified conditional check in getBinary() method Maintains existing error handling for unsupported ARM platforms +2/-1

---

[CLAassistant]

All committers have signed the CLA.

[qodo-merge-pro]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
⚪	No custom compliance provided Follow the guide to enable custom compliance check.
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Improve architecture detection for robustness Improve the robustness of the OS architecture check by storing os.arch in a variable, converting it to lowercase, and using startsWith() instead of contains() for matching. java/src/org/openqa/selenium/manager/SeleniumManager.java [203-206] -if (System.getProperty("os.arch").contains("arm") - || System.getProperty("os.arch").contains("aarch64")) { +String osArch = System.getProperty("os.arch").toLowerCase(); +if (osArch.startsWith("arm") || osArch.startsWith("aarch")) { throw new WebDriverException("Linux ARM is not supported by Selenium Manager"); } [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 6 __ Why: The suggestion improves code robustness and readability by using a local variable, converting to lowercase, and using startsWith() for a more precise architecture check.	Low
Update

[mkurz]

Seems like the failing test times out.
This has nothing to do with my change.

[shbenzer]

This is a good addition - thank you @mkurz !

[cgoldberg]

Hopefully we will be supporting Linux and Windows on ARM soon, and we can update the platform detection code.

[mkurz]

I am using and maintaining Asahi Arch Linux ARM, which is just a thin layer on top of Arch Linux ARM, and I can build and run selenium manager from you repo without any problems.
There is even an selenium-manager AUR ("Arch User Repository") which provides the selenium-manger package , which people can easily install with yay -S selenium-manager: https://github.com/archlinux/aur/blob/selenium-manager/PKGBUILD As you see it's just compiling what you provide in the repo (though a bit outdated version 4.30 as of today).

So regarding selenium manager I think all you have to do is build it for the aarch64 architecture and bundle it just like the x86-64 binary. You can do that easily nowadays with an arm GitHub actions runner, all you have to do is use runs-on: ubuntu-24.04-arm (see the -arm suffix): https://github.blog/changelog/2025-01-16-linux-arm64-hosted-runners-now-available-for-free-in-public-repositories-public-preview/

geckodriver can also be build for aarch64 easily, there is also an AUR for it: https://gitlab.archlinux.org/archlinux/packaging/packages/geckodriver/-/blob/main/PKGBUILD?ref_type=heads
You could build that too in a GitHub actions arm runner, or you could even use the precompiled package from Arch Linux ARM: https://eu.mirror.archlinuxarm.org/aarch64/extra/ (search for geckodriver on that page, you would need to unpack it and copy over the binary.

For the chromiumdriver it's similiar, either you compile chromium yourself (which takes quite a while...) or you use the precompiled binaries from the chromium package again (https://eu.mirror.archlinuxarm.org/aarch64/extra/). (currently chromium is totally outdated in Arch Linux ARM because they have a problem in the build setup).

[cgoldberg]

We already have PRs open for building Selenium Manager on ARM64 for Linux and Windows. However, we have no intention of publishing our own geckodriver/chromedriver builds. (Mozilla already publishes geckodriver for ARM anyway).