-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[Nodriver] upgrade to 0.40 - browser does not start in docker (hangs forever) #2152
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
Comments
Try run not as root |
Oh wait. You run on Docker. Ever thought about displaying a browser on Docker? This can be done but is everything but convenient. Headless mode should do |
I am having the same problem, how do I run not as root on docker? |
In undetected_chrome driver I used add_experimental_option("debuggerAddress", "localhost:9222"), but now in nodriver I haven't found any way to run the nodriver in a already existing browser. Someone help? |
await uc.start(config=opt, port=9222, user_data_dir=r"C:\Users\User\Desktop\Chromium", browser_executable_path=r'C:\Program Files\Google\Chrome\Application\chrome.exe') I've tried this configuration set, but it doesn't work as I expected |
Can you share the dockerfile please? |
Hi. Is this fixed ? |
Hello,
I am running Nodrier on Docker, ubuntu 18 image with Chrome latest and the latest upgrade to version 0.40 caused that the browser does not start anymore. These are the logs from Nodriver when I start the app:
03 March 2025 at 16:13 (UTC)
enabling autodiscover targets
app
03 March 2025 at 16:13 (UTC)
--window-size=1920,1080
app
03 March 2025 at 16:13 (UTC)
--start-maximized
app
03 March 2025 at 16:13 (UTC)
--no-sandbox=true
app
03 March 2025 at 16:13 (UTC)
--no-sandbox
app
03 March 2025 at 16:13 (UTC)
--remote-debugging-host=127.0.0.1
app
03 March 2025 at 16:13 (UTC)
--remote-debugging-port=36423
app
03 March 2025 at 16:13 (UTC)
detected root usage, autoo disabling sandbox mode
app
03 March 2025 at 16:13 (UTC)
starting
app
03 March 2025 at 16:13 (UTC)
executable :/bin/google-chrome
app
03 March 2025 at 16:13 (UTC)
arguments:
app
03 March 2025 at 16:13 (UTC)
--remote-allow-origins=*
app
03 March 2025 at 16:13 (UTC)
--no-first-run
app
03 March 2025 at 16:13 (UTC)
--no-service-autorun
app
03 March 2025 at 16:13 (UTC)
--no-default-browser-check
app
03 March 2025 at 16:13 (UTC)
--homepage=about:blank
app
03 March 2025 at 16:13 (UTC)
--no-pings
app
03 March 2025 at 16:13 (UTC)
--password-store=basic
app
03 March 2025 at 16:13 (UTC)
--disable-infobars
app
03 March 2025 at 16:13 (UTC)
--disable-breakpad
app
03 March 2025 at 16:13 (UTC)
--disable-component-update
app
03 March 2025 at 16:13 (UTC)
--disable-backgrounding-occluded-windows
app
03 March 2025 at 16:13 (UTC)
--disable-renderer-backgrounding
app
03 March 2025 at 16:13 (UTC)
--disable-background-networking
app
03 March 2025 at 16:13 (UTC)
--disable-dev-shm-usage
app
03 March 2025 at 16:13 (UTC)
--disable-features=IsolateOrigins,site-per-process
app
03 March 2025 at 16:13 (UTC)
--disable-session-crashed-bubble
app
03 March 2025 at 16:13 (UTC)
--disable-search-engine-choice-screen
app
03 March 2025 at 16:13 (UTC)
--user-data-dir=/tmp/uc_9ki2mo8z
app
03 March 2025 at 16:13 (UTC)
--disable-features=IsolateOrigins,site-per-process
app
03 March 2025 at 16:13 (UTC)
--disable-session-crashed-bubble
After that, it hangs forever.
Does anyone know the potential culprit?
The text was updated successfully, but these errors were encountered: