SeleniumHQ / SeleniumHQ/docker-selenium
[🐛 Bug]: Geckodriver logs not sent to standard out
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 2.5k
- Avg merge
- 10h 16m
- Merged PRs (30d)
- 20
Description
What happened?
I am using Selenium Hub with a Firefox node attached. When I create my FirefoxOptions I am setting the log level to 'Trace':
driverOptions = new FirefoxOptions();
((FirefoxOptions)driverOptions).LogLevel = FirefoxDriverLogLevel.Trace;
I run some code that uses this driver to automate some task in Firefox. I look at the standard output for the docker container that is the Firefox node but the logs are not there for the Geckodriver.
Command used to start Selenium Grid with Docker
version: "3"
services:
firefox:
image: selenium/node-firefox:4.13.0-20230926
container_name: firefox-node
shm_size: 2gb
privileged: true
depends_on:
- selenium-hub
environment:
- HUB_HOST=selenium-hub
- SE_EVENT_BUS_HOST=selenium-hub
- SE_EVENT_BUS_PUBLISH_PORT=4442
- SE_EVENT_BUS_SUBSCRIBE_PORT=4443
- SE_NODE_MAX_SESSIONS=1
ports:
- "6902:5900"
networks:
- selenium_grid_internal
selenium-hub:
image: selenium/hub:4.13.0-20230926
privileged: true
container_name: selenium-hub
ports:
- "4442:4442"
- "4443:4443"
- "4444:4444"
environment:
- GRID_TIMEOUT=120000
- GRID_BROWSER_TIMEOUT=120000
networks:
- selenium_grid_internal
networks:
selenium_grid_internal:
Relevant log output
N/A
Operating System
Ubuntu 20.04
Docker Selenium version (tag)
4.13.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the provided Docker Compose configuration and the selenium/node-firefox:4.13.0-20230926 image, then trace how the Firefox node launches geckodriver and handles its output. Reproduce the Trace-level setup and verify whether the expected geckodriver messages appear in docker logs for firefox-node.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100