selenoid: Unable to launch browser when Selenoid is started in custom network
2017/05/18 12:12:23 [12] [SERVICE_STARTUP_FAILED] [unknown] [wait: http://172.17.0.2:4444/ does not respond in 30s]
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 21 (14 by maintainers)
Commits related to this issue
- Added ability to specify custom network for containers (fixes #87) — committed to vania-pooh/selenoid by vania-pooh 7 years ago
- Merge pull request #172 from vania-pooh/master Added ability to specify custom network for containers (fixes #87) — committed to aerokube/selenoid by aandryashin 7 years ago
- Correctly determining container IP in custom network (related to #87) — committed to vania-pooh/selenoid by vania-pooh 7 years ago
- Merge pull request #186 from vania-pooh/master Correctly determining container IP in custom network (related to #87) — committed to aerokube/selenoid by aandryashin 7 years ago
@seanmaxwell like this:
@mattiasmgn so far as I can see you had 6 months old
aerokube/selenoid:latest.