Headless permissions

1,053 views
Skip to first unread message

br...@dockyard.com

unread,
Oct 9, 2017, 9:01:26 AM10/9/17
to headless-dev
When launching Chrome from the CLI if I don't use `--headless` Chrome launches without issue. But if I add `--headless` I get "Permission denied" errors.

Is there a way to ensure that headless mode has the necessary permissions? What exactly is different about headless mode that it would require permissions?

Alex Clarke

unread,
Oct 9, 2017, 10:01:21 AM10/9/17
to Brian Cardarella, headless-dev
What operations are failing with Permission denied?  Loading a web page?

On 9 October 2017 at 14:01, <br...@dockyard.com> wrote:
When launching Chrome from the CLI if I don't use `--headless` Chrome launches without issue. But if I add `--headless` I get "Permission denied" errors.

Is there a way to ensure that headless mode has the necessary permissions? What exactly is different about headless mode that it would require permissions?

--
You received this message because you are subscribed to the Google Groups "headless-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev+unsubscribe@chromium.org.
To post to this group, send email to headle...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/dd3d55a1-33bd-40c1-bdae-63c07d6d3f67%40chromium.org.

br...@dockyard.com

unread,
Oct 9, 2017, 10:05:43 AM10/9/17
to headless-dev, br...@dockyard.com
This is the output:

➜  MacOS ./Google\ Chrome --headless
[1009/100340.443190:ERROR:crash_report_database_mac.mm(94)] mkdir /Applications/Google Chrome.app/Contents/Versions/61.0.3163.100/Google Chrome Framework.framework/Versions/A/new: Permission denied
[1009/100340.443558:ERROR:crash_report_database_mac.mm(94)] mkdir /Applications/Google Chrome.app/Contents/Versions/61.0.3163.100/Google Chrome Framework.framework/Versions/A/new: Permission denied
[1009/100340.443617:INFO:crashpad_client_mac.cc(295)] restarting handler in 0.987s
[1009/100340.590801:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.

it appears a `mkdir` command is failing. My installation of Chrome is just the normal dmg installation. I could run chown on the directory but I would have to ask all consumers of our lib to do this every time.

On Monday, October 9, 2017 at 10:01:21 AM UTC-4, Alex Clarke wrote:
What operations are failing with Permission denied?  Loading a web page?
On 9 October 2017 at 14:01, <br...@dockyard.com> wrote:
When launching Chrome from the CLI if I don't use `--headless` Chrome launches without issue. But if I add `--headless` I get "Permission denied" errors.

Is there a way to ensure that headless mode has the necessary permissions? What exactly is different about headless mode that it would require permissions?

--
You received this message because you are subscribed to the Google Groups "headless-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev...@chromium.org.

Sami Kyostila

unread,
Oct 9, 2017, 1:10:33 PM10/9/17
to br...@dockyard.com, headless-dev
Could you check if the --disable-crash-reporter command line flag makes the problem go away?

- Sami

br...@dockyard.com

unread,
Oct 9, 2017, 1:17:21 PM10/9/17
to headless-dev, br...@dockyard.com
I was just about to follow this up with:

I added `--crash-dumps-dir` to a path the launching process has permissions to and this resolved it. Thanks for following up!

Sami Kyostila

unread,
Oct 9, 2017, 1:26:14 PM10/9/17
to br...@dockyard.com, headless-dev
Reply all
Reply to author
Forward
0 new messages