ASQATASUN 6.0.0-rc.1 : NoSuchDriverException: geckodriver

Bonjour,

sur ASQA 6 dockerisé, l’analyse d’une page echoue. Dans le log, je trouve cette erreur
app-1 | org.openqa.selenium.remote.NoSuchDriverException: geckodriver at location /opt/geckodriver, does not exist

J’imagine que ce composant est un prerequis. Mais il ne semble pas embarqué dans les images.

selenium/standalone-firefox est lancé. Ce n’est peut être suffisant ?

Quelqu’un peut il me dire quelques mots sur l’installation de ce driver ?
faut il l’intégrer à une image ?

Voici l’etat de compose :

[asqatasun@cnp31devotlab1bd1 v6]$ docker compose ps
NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS
v6-app-1 asqatasun/asqatasun-webapp:6.0.0-rc.1 “/__cacert_entrypoin…” app 38 minutes ago Up 38 minutes 0.0.0.0:8080->8080/tcp
v6-db-1 mariadb:10.6 “docker-entrypoint.s…” db 38 minutes ago Up 38 minutes 0.0.0.0:3306->3306/tcp
v6-mailhog-1 mailhog/mailhog “MailHog” mailhog 38 minutes ago Up 38 minutes 0.0.0.0:1025->1025/tcp, 0.0.0.0:8025->8025/tcp
v6-selenium-firefox-standalone-1 selenium/standalone-firefox:latest “/opt/bin/entry_poin…” selenium-firefox-standalone 38 minutes ago Up 38 minutes 4444/tcp, 5900/tcp, 0.0.0.0:7900->7900/tcp, :::7900->7900/tcp
v6-server-1 asqatasun/asqatasun-server:6.0.0-rc.1 “/__cacert_entrypoin…” server 38 minutes ago Up 38 minutes 0.0.0.0:8081->8081/tcp

Merci

ci dessous : un passage du log montrant une tentative de scan de https://google.com

app-1 | 2024-11-07 10:47:39.820 [Thread-7] INFO org.asqatasun.service.command.AuditCommandImpl - Audit 6 initialized, queried URL https://www.google.com
app-1 | 2024-11-07 10:47:40.418 [Thread-7] INFO org.asqatasun.webapp.orchestrator.AsqatasunOrchestrator - Audit org.asqatasun.entity.audit.AuditImpl@36309ce8 crashed, https://www.google.com,1730976459
app-1 | org.openqa.selenium.remote.NoSuchDriverException: geckodriver at location /opt/geckodriver, does not exist
app-1 | For documentation on this error, please visit: Unable to Locate Driver Error | Selenium
app-1 | Build info: version: ‘4.19.1’, revision: ‘abe0ee07dc’
app-1 | System info: os.name: ‘Linux’, os.arch: ‘amd64’, os.version: ‘5.14.0-284.25.1.el9_2.x86_64’, java.version: ‘17.0.11’
app-1 | Driver info: driver.version: FirefoxDriver
app-1 | at org.openqa.selenium.remote.service.DriverFinder.getPath(DriverFinder.java:76)
app-1 | at org.openqa.selenium.remote.service.DriverFinder.getPath(DriverFinder.java:33)
app-1 | at org.openqa.selenium.firefox.FirefoxDriver.generateExecutor(FirefoxDriver.java:141)
app-1 | at org.openqa.selenium.firefox.FirefoxDriver.(FirefoxDriver.java:133)
app-1 | at org.openqa.selenium.firefox.FirefoxDriver.(FirefoxDriver.java:128)
app-1 | at org.openqa.selenium.firefox.FirefoxDriver.(FirefoxDriver.java:113)
app-1 | at org.asqatasun.scenarioloader.RemoteWebDriverFactory.createFirefoxDriver(RemoteWebDriverFactory.kt:78)
app-1 | at org.asqatasun.scenarioloader.RemoteWebDriverFactory.chooseDriver(RemoteWebDriverFactory.kt:63)
app-1 | at org.asqatasun.scenarioloader.RemoteWebDriverFactory.createDriver(RemoteWebDriverFactory.kt:56)
app-1 | at org.asqatasun.scenarioloader.ScenarioLoaderImpl.(ScenarioLoaderImpl.kt:70)

Problème résolu lié après modification du docker-compose (dependance, selenium hub, node firefox,…)