-
Notifications
You must be signed in to change notification settings - Fork 183
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
Unable to run as service or with docker #364
Comments
Hi @Dunkhan , The second issue (the chrome page crash) sometimes shows up when the docker container doesn't have enough memory available. How much memory are you assigning to your docker containers? The first issue is less clear - there's not enough information in the error message you pasted to point to any |
Thanks for the response. I am not sure how to increase the memory to the docker container (I am not terribly familiar with docker). My understanding was that the memory isn't limited by default and I have not taken any steps to limit it. I checked to make sure chrome was installed on the server for the service and it seems it was not installed correctly, now I think it is though, and the error output has changed:
I read in another report a suggestion to check --version on google-chrome, chrome and chromium. In case this is relevant it only returns a version (112.0.5615.121) for google-chrome and nothing for the other two. |
Hi @Dunkhan , Looking here, there does seem to be a system memory limit for Docker Mac: It might be worth checking if increasing the memory allocation there helps with your issue. The error message could also be because of a mismatch between the version of There are some discussions on the You might find that hard-coding the version ( |
I am using ssh to set this up on a linux virtual server. The guides on docs.docker cover how to change the memory limit on a GUI that I don't have access to. |
I was able to resolve the page crash issue using following args: driver_arguments:
- "--headless"
- "--disable-dev-shm-usage" |
@kevincali Thanks, the - "--disable-dev-shm-usage" parameter solved this issue for me. |
Had the same problem. These To clarify this for other readers. I set the following in the captcha:
driver_arguments:
- "--headless"
- "--disable-dev-shm-usage" I found this confusing, but the arguments are not only used when solving captchas, but for all chrome instances in general. |
When I try to run this as a service I get the following output:
I am also having a different error when trying to run it in docker (not docker-compose).
I am running on a virtual server on strato.de running linux (ubuntu)
Any advice is appreciated
The text was updated successfully, but these errors were encountered: