laravel - 经过测试，Chrome进程在Docker容器中仍然保留Laravel Dusk

Question

使用 Atlassian Bamboo 运行Dusk测试后，Chrome进程仍然是“僵尸”。
下面是我的驱动程序代码初始化:

$options = (new ChromeOptions())
           ->addArguments(['--disable-gpu', '--headless', '--no-sandbox', ]);

$chrome = DesiredCapabilities::chrome()
          ->setCapability(ChromeOptions::CAPABILITY,$options)
          ->setCapability('acceptInsecureCerts', true);

return RemoteWebDriver::create('http://localhost:9515', $chrome);

我的 composer.json:

"require-dev":{
   "barryvdh/laravel-ide-helper":"^2.5",
   "filp/whoops":"^2.0",
   "fzaninotto/faker":"^1.4",
   "laravel/dusk":"^4.0",
   "mockery/mockery":"^1.0",
   "nunomaduro/collision":"^2.0",
   "phpunit/phpunit":"^7.0",
   "squizlabs/php_codesniffer":"3.*"
}

以下是截图以证明僵尸进程:
最高命令的结果:

感谢您的回复。

Answer 1

挖掘之后，似乎原因是Docker容器上缺少标志:

您必须附加到docker run标志--init
从Atlassian官方文档中:
atlassian/bamboo-server

Note that the --init flag is required to properly reap zombie processes.