element not interactable about noip-renewer HOT 8 CLOSED

I think the image, I used, was too old

I change for this image : simaofsilva/noip-renewer:debian

and I have another error

Opening browser
Traceback (most recent call last):
File "//renew.py", line 41, in
browser = webdriver.Chrome(options=browserOptions)
File "/root/.local/lib/python3.10/site-packages/selenium/webdriver/chrome/webdriver.py", line 76, in init
RemoteWebDriver.init(
File "/root/.local/lib/python3.10/site-packages/selenium/webdriver/remote/webdriver.py", line 157, in init
self.start_session(capabilities, browser_profile)
File "/root/.local/lib/python3.10/site-packages/selenium/webdriver/remote/webdriver.py", line 252, in start_session
response = self.execute(Command.NEW_SESSION, parameters)
File "/root/.local/lib/python3.10/site-packages/selenium/webdriver/remote/webdriver.py", line 321, in execute
self.error_handler.check_response(response)
File "/root/.local/lib/python3.10/site-packages/selenium/webdriver/remote/errorhandler.py", line 242, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: unknown error: Chrome failed to start: crashed.
(chrome not reachable)
(The process started from chrome location /usr/bin/chromium is no longer running, so ChromeDriver is assuming that Chrome has crashed.)

from noip-renewer.

The image with tag 3.9.1 is a year old so I do not recommend use it, so please use tag debian and update that from time to time.
I have the image with tag debian running on a arm/v7 device without any issues. Are you running the right image for your processor's architecture? What is the output of uname --m?

from noip-renewer.

The output of uname --m is
armv7l

is debian tag the right image for my raspberry ?

from noip-renewer.

Yes, debian is the right tag for that architecture. Can you check if the creation date of the image is from 6 days ago?

docker image ls simaofsilva/noip-renewer:debian

from noip-renewer.

Yes, it seems to be the right version, what can be wrong ?

REPOSITORY                 TAG       IMAGE ID       CREATED      SIZE
simaofsilva/noip-renewer   debian    bc1c130454d9   6 days ago   462MB

from noip-renewer.

That seems alright.
It can be a memory problem with the container exhausting the RAM and crashing. Have you check the Raspberry status while the container is running?

from noip-renewer.

I didn't find some trouble with my raspberry. So I build my own image but I change bullseye by buster because my raspberry run with buster

And it works with this new image

My change :

FROM python:3.10.4-slim-buster@sha256:c2824bf9bdb9dbeed967df6805388e90e67439aae4934c02526d8ce5c29ae6d1

Could you upgrade your debian image to buster ?

I also use renew.py and not renew_legacy.py : I don't know why you keep a specific version for debian : maybe you can merge.

Thanks a lot

from noip-renewer.

Your running in a container so it does not matter which version of Debian you are using on your Raspberry Pi. Still, going from bullseye to buster is a downgrade, not an upgrade.
I am still wondering how the current image does not work in your environment but I am glad you found a solution for your issue.

from noip-renewer.