-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Comments
@aravindkarnam That's very true, I removed it already and will release soon in the version 0.2.76 |
i am having this same issue |
@unclecode Thanks for fixing it. Will the requirements be updates to install |
I am having this issue too, but not in docker, when i install the default install on ubuntu. |
@nicosalto |
@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. |
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 calledTHIRD_PARTY_NOTICES.chromedriver
file in the latest release for actual driver.webdriver_manager
fixed this in latest version4.0.2
as per this issue. Crawl4ai is currently using4.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.The text was updated successfully, but these errors were encountered: