sonar.scanner.skipJreProvisioning=true didn’t help. Setting the path to the local java executable via -Dsonar.scanner.javaExePath=/usr/local/bin/java made it work (“java” is in the path, so you seem to have a bug there). This doesn’t fix it completely, the kubernetes sensor triggers in e.g. the wordpress source and fails as it doesn’t respect the sonar.scanner.os setting.
See the discussion I opened for this here in the forum.
Thanks a lot for you information here, it helped to find a suitable workaround.
FYI:
FreeBSD is compatible enough with sonar.scanner.os=linux to have it working just fine in the past. There are traces back to sonarqube cummunity edition 6 working just fine and currently sonarqube community edition 10.7 also works just fine except for what is presented here (this is a recent regression compared to a lot of years where it simply worked). A part of the regression is now fixed in the FreeBSD port by a simple shell-wrapper script for the sonar scanner to set the path to java (so that it doesn’t need to be set per project).
FreeBSD ships “ports” (= automated installation of 3rd party software) of the community edition (downloads your zip for linux and has a dependency on the openjdk to that this is automatically installed too, and provides integration in the FreeBSD service startup framework – init.d or systemd config if you want to compare it to a similar linux feature) for years. Great for those of us who want to deliver good quality when contributing to open source projects or want to learn about sonarqube and want to play around more freely with it than what people at work allow to do with the enterprise edition.