Skip to content
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

OSError: [Errno 8] Exec format error #62

Closed
aravindkarnam opened this issue Jul 26, 2024 · 6 comments
Closed

OSError: [Errno 8] Exec format error #62

aravindkarnam opened this issue Jul 26, 2024 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@aravindkarnam
Copy link
Contributor

aravindkarnam commented Jul 26, 2024

Issue description

With the latest release in google-chrome-stable(version 127.0.6533.72), when we run the crawler it's throwing the following error OSError: [Errno 8] Exec format error: '/root/.wdm/drivers/chromedriver/linux64/127.0.6533.72/chromedriver-linux64/THIRD_PARTY_NOTICES.chromedriver'. You'll get this error only if you rebuild your docker image to install latest chrome.

Suggestion

Looks like its due to webdriver_manager confusing a new file called THIRD_PARTY_NOTICES.chromedriver file in the latest release for actual driver. webdriver_manager fixed this in latest version 4.0.2 as per this issue. Crawl4ai is currently using 4.0.1, if we can bump this up we can use chrome latest version without any hassle. I've already checked out this version of webdriver_manager with crawl4ai on a ubuntu ec2 instance and it works as expected.

Workaround in the meantime

In the meantime for anyone who come across this issue, the following patch actually works. You can install this patch between the pip install and uvicorn startup commands in the dockerfile and current version of crawl4ai will work - or you can also force install the latest version of webdriver_manager.
__
@unclecode please consider updating the dockerfile to remove the installation of chrome driver. Since you introduced ChromeDriverManger in V 0.2.71, this line has become redundant. It's also confusing, I was trying to fix the issue at first by updating the dockerfile, only to later realise crawl4ai is installing and running different chrome driver.

@unclecode unclecode self-assigned this Jul 27, 2024
@unclecode unclecode added the bug Something isn't working label Jul 27, 2024
@unclecode
Copy link
Owner

@aravindkarnam That's very true, I removed it already and will release soon in the version 0.2.76

@Emekaborisama
Copy link

i am having this same issue

@ghost
Copy link

ghost commented Jul 31, 2024

@unclecode Thanks for fixing it. Will the requirements be updates to install webdriver_manager==4.0.2 in v0.2.76 ?
when will v0.2.76 be released?

@nicosalto
Copy link

I am having this issue too, but not in docker, when i install the default install on ubuntu.
what is the process to fix this issue ?
you mentioned to update webdriver_manager to v4.0.2, but when i update this package i only get v4.0.1 ...

@ghost
Copy link

ghost commented Aug 1, 2024

@nicosalto
4.0.2 is available https://pypi.org/project/webdriver-manager/
Delete the ~/.wdm directory, if it exists.

@unclecode
Copy link
Owner

@shamikct @nicosalto @Emekaborisama @aravindkarnam Tomorrow, I will release the new versions, tested on all three platforms, and a Docker image will be available on Docker Hub. Additionally, there's no longer a need for webdriver_manager, simplifying the process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants