Chrome fails in Pipelines because docker images aren't run with "--privileged" flag

Issue #13622 resolved
Badal created an issue

Please add a setting in bitbucket-pipelines.yml to allow docker images to be started with the "--privileged" flag.

Privileged flag allow to run selenium with chrome without crashing. It crashes without privileged mode due to sandboxing and using same container as docker container in linux.

Comments (5)

  1. Matt Ryall

    Hi Badal, we had a few customers notice this problem and there's a simple workaround by using the --no-sandbox flag when running Chrome to disable its sandboxing.

    Can you please try this and let us know if it fixes the problem for you?

  2. Balinder Singh

    Is anybody still seeing this issue? I am able to run my selenium solution fine in Docker locally but when I run it in pipeline it crashes.

    here’s my code. I am adding the sandbox flag as well

  3. Log in to comment