On linux chrome launch failing

[rajender]

Rod Version: v0.45.1

panic: [launcher] Failed to get the debug url: [0715/074020.195948:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.

[ysmood]

rod/examples_test.go

Lines 202 to 229 in a0664b4

	// Example_customize_browser_launch will show how we can further customise the
	// browser with the launcher library. The launcher lib comes with many default
	// flags (switches), this example adds and removes a few.
	func Example_customize_browser_launch() {
	// Documentation for default switches can be found at the source of the
	// launcher.New function, as well as at
	// https://peter.sh/experiments/chromium-command-line-switches/.
	url := launcher.New().
	// Set a flag- Adding the HTTP proxy server.
	Set("proxy-server", "127.0.0.1:8080").
	// Delete a flag- remove the mock-keychain flag
	Delete("use-mock-keychain").
	Launch()
	browser := rod.New().ControlURL(url).Connect()
	defer browser.Close()
	// Adding authentication to the proxy, for the next auth request.
	// We use CLI tool "mitmproxy --proxyauth user:pass" as an example.
	browser.HandleAuth("user", "pass")
	// mitmproxy needs a cert config to support https. We use http here instead,
	// for example
	fmt.Println(browser.Page("http://example.com/").Element("title").Text())
	// Skip
	// Output: Example Domain
	}

Actually, the error info is quite enough for you to solve it by yourself.

Add flag no-sandbox should solve your issue.

[rajender]

It's working fine with no-sandbox option.