-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failing to start ZAP due to errors in the pipeline #8850
Comments
|
From logs, it clearly has "openjdk 11.0.26 2025-01-21", but not sure why it again reports "ZAP requires a minimum of Java 11 to run, found". |
How have you installed ZAP? Using exactly which release and where did you get it from? |
Everything was working fine until 2.15.0 version. This issue started only from latest 2.16.0 version. The agent is installing Ubuntu 22.04.5 [Not sure if this is installing Java 11]. We have following steps in our pipeline yaml :
|
If it's complaining about Java 11 you're still on 2.15 because 2.16 requires Java 17. |
From logs, I see the following as part of the step 'sudo snap install zaproxy --classic': /usr/bin/pwsh -NoLogo -NoProfile -NonInteractive -Command . '/home/vsts/work/_temp/4be285ad-3f04-4b64-a10f-eb3743724a59.ps1' |
I think, I understood the reason. Ubuntu 22.04.5 LTS includes OpenJDK 11 as the default Java Development Kit (JDK). I will add script to install 17 version of OpenJDK and see if it makes any difference in the result. |
The error is currently misleading, the newer ZAP version does require Java 17. |
Anyone has an idea on how to install specific version of ZAProxy using snap install command? Tried this, but does not work as expected -> sudo snap install zaproxy --channel=2.15/stable --classic |
Older versions are not available right now, we need to manually tweak that. |
I am facing the same issue but the problem is not the Java version but the zaproxy binary itself. For some reason, it is unable to get the Java version.
If I run
My ZAP version is 2.16.0 and my OS is Ubuntu 22.04.5 LTS. |
We have been using ZAProxy from long back and everything was working fine until 2.0.15 version. We started seeing below issue from latest 2.0.16 version.
Can you please help if we ae missing anything? Tried including java 17 version as well, but the result is same.
We use the following bash script to run this:
The text was updated successfully, but these errors were encountered: