SeleniumBase specify path to chromedriver

[FindingBen]

I have my lambda code deployed on ECR and I have a script that downloads the crome driver for linux. I know that seleniumbase initiation downloads the chrome automatically but the problem is it uses downloaded_files folder and my lambda can't write it since it has limitations. I tried making /tmp folder where lambda seems to have writing permission but it doesn't work.

Can I manually specify the path where my chromedriver gets downloaded and use it like its being used in selenium?

Something like this:

driver = Driver(undetectable=True,headless2=True,binary_location="/opt/chrome/chrome-linux64/chrome", executable_path=...here for example?...)

[mdmintz]

There are 2 places SeleniumBase checks for drivers:

1. The seleniumbase/drivers folder.
2. Each folder of os.environ["PATH"], in order.

If you don't want to use the seleniumbase/drivers folder for driver storage, then you can download chromedriver manually to a folder on your System PATH. The version of chromedriver must match your version of Chrome, or else SeleniumBase will automatically download a matching driver to the seleniumbase/drivers folder, which can't be changed. You can, however, change os.environ["PATH"] at runtime so that you can add a folder to the front that isn't already there.

[FindingBen]

Ok So I managed to get the files up and running but there is an issue. Since Lambda runtime environment allows the writing only on /tmp folder I am getting issue of : OSError: [Errno 30] Read-only file system: '/var/lang/lib/python3.12/site-packages/seleniumbase/drivers/uc_driver'

My question is I guess, can I use seleniumbase on lambda AWS given its runtime environment restricitons?

[mdmintz]

You could try this thread: #2459

[FindingBen]

This doesn't really help my case because I cannot even initate the Driver. I have problem with the Lambda environment and I was hoping there is some kind of workaround in this.

Also I am using Driver() and in that thread the guy was using SB context

[mdmintz]

The Driver() doesn't have the special virtual display code that SB() has.