Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hello there!
I believe that you’re correct to suspect that the --no-sandbox argument might be contributing to the issue. While necessary for running Chrome in a Docker container or in certain restricted environments, no-sandbox can affect how the browser interacts with alerts and other pop-ups.
Here are a few things that you could check out:
WebDriverWait(driver, 10).until(EC.alert_is_present())
driver.switch_to.alert.accept()
Make sure to import the necessary modules:
from selenium.webdriver.support import expected_conditions as EC
driver.execute_script("window.confirm = function(){return true;}")
This script auto-confirms alerts, which might suffice depending on your needs.
--no-sandbox is necessary in some environments, it can lead to unpredictable browser behavior. If your Droplet configuration allows, try running without this argument to see if there’s any change. Note, this might not be applicable in all environments, especially in containerized setups.Besides that, here’s an example of how you might add these logging options:
options.add_argument('--enable-logging')
options.add_argument('--v=1')
Best of luck, and happy coding!
Bobby