We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I have chrome running as docker image with docker-compose.
If I try to connect to exposed to local machine port - it works fine, however if I try to connect using "compose" URL as host, getting just false.
false
Any hints?
I'm connecting like this:
server = ChromeRemoteInterface.Session.new(host: "chrome") {:ok, pages} = ChromeRemoteInterface.Session.list_pages(server)
Getting this:
im_1 | ** (exit) an exception was raised: im_1 | ** (MatchError) no match of right hand side value: false
Docker image with chrome correctly expose needed default port. As I mentioned above, using host machine works fine.
The text was updated successfully, but these errors were encountered:
@solshark try looking @ https://github.com/holsee/chroxy which runs chrome as a service (now including a Dockerfile see the README) and has a convenient mechanism through https://github.com/holsee/chroxy_client to obtain chrome endpoints which can be connected to using ChromeRemoteInterface (this project). This might be of use to you. This video might be useful too: https://www.youtube.com/watch?v=FGUEDu8A7GY (although was made before Chroxy got a Dockerfile).
Sorry, something went wrong.
No branches or pull requests
Hi,
I have chrome running as docker image with docker-compose.
If I try to connect to exposed to local machine port - it works fine, however if I try to connect using "compose" URL as host, getting just
false
.Any hints?
I'm connecting like this:
Getting this:
Docker image with chrome correctly expose needed default port. As I mentioned above, using host machine works fine.
The text was updated successfully, but these errors were encountered: