Error executing SonarScanner on aarch64

Hello,

I have installed SonarScanner for Linux AArch64 on a docker image (also aarch64).

When launching the command sonar-scanner -Dsonar.login="${SONAR_TOKEN}" -Dsonar.projectBaseDir=$(pwd) -Dsonar.verbose=true -X it’s trying to run a version of the sonar-go-to tool-slang-linux-amd64 file which is not valid on the aarch64 platform.

Information of interest:

[Container] 2024/09/19 16:01:51.543893 Running command sonar-scanner -Dsonar.login="${SONAR_TOKEN}" -Dsonar.projectBaseDir=$(pwd) -Dsonar.verbose=true -X
16:01:51.774 INFO  Scanner configuration file: /codebuild/output/src1371797169/src/sonar-scanner-6.1.0.4477-linux-aarch64/conf/sonar-scanner.properties
16:01:51.777 INFO  Project root configuration file: /codebuild/output/src1371797169/src/myproject/sonar-project.properties
16:01:51.790 INFO  SonarScanner CLI 6.1.0.4477
16:01:51.792 INFO  Java 17.0.11 Eclipse Adoptium (64-bit)
16:01:51.793 INFO  Linux 4.14.336-257.562.amzn2.aarch64 aarch64
16:01:51.799 DEBUG Scanner max available memory: 3 GB
16:01:51.817 DEBUG uname -m returned 'aarch64'
16:01:51.819 DEBUG Create: /root/.sonar/cache
16:01:51.819 INFO  User cache: /root/.sonar/cache
16:01:51.819 DEBUG Create: /root/.sonar/cache/_tmp
....
....
....
16:02:02.602 INFO  176 source files to be analyzed
16:02:02.634 ERROR Unable to parse file: file:///codebuild/output/src1371797169/src/myproject/internal/application/myfile.go 
16:02:02.634 ERROR Cannot parse 'internal/pointapplication/myfile.go': Stream closed
16:02:02.634 DEBUG /codebuild/output/src1371797169/src/myproject/.scannerwork/sonar-go-to-slang-linux-amd64: /codebuild/output/src1371797169/src/myproject/.scannerwork/sonar-go-to-slang-linux-amd64: cannot execute binary file
16:02:02.666 DEBUG /codebuild/output/src1371797169/src/myproject/.scannerwork/sonar-go-to-slang-linux-amd64: /codebuild/output/src1371797169/src/myproject/.scannerwork/sonar-go-to-slang-linux-amd64: cannot execute binary file

Can you help me, please? Thank you so much.

Hey there.

Thanks for the report. This is a known issue unfortunately, tracked at [SONARGO-25] - Jira. I’ve linked your thread to help the ticket build traction.