Running the chromedp/headless-shell:latest docker image
Running Ubuntu 18.04
Running the container with the command outlined in the readme:
docker run -d -p 9222:9222 --rm --name headless-shell chromedp/headless-shell
The command runs successfully, but when looking into the container I see a lot of error messages. What could be the issue? Thank you!
`[1030/152232.814939:WARNING:resource_bundle.cc(428)] locale_file_path.empty() for locale
[1030/152232.967497:WARNING:resource_bundle.cc(428)] locale_file_path.empty() for locale
DevTools listening on ws://0.0.0.0:9222/devtools/browser/e5dbacd0-ef6a-467a-913e-4b222813d674
[1030/152233.322688:WARNING:resource_bundle.cc(428)] locale_file_path.empty() for locale
[1030/152233.323287:ERROR:egl_util.cc(60)] Failed to load GLES library: /headless-shell/swiftshader/libGLESv2.so: /headless-shell/swiftshader/libGLESv2.so: cannot open shared object file: No such file or directory
[1030/152233.323837:WARNING:resource_bundle.cc(428)] locale_file_path.empty() for locale
[1030/152233.324883:ERROR:viz_main_impl.cc(167)] Exiting GPU process due to errors during initialization
[1030/152233.326917:WARNING:gpu_process_host.cc(1207)] The GPU process has crashed 1 time(s)
[1030/152233.482589:WARNING:resource_bundle.cc(428)] locale_file_path.empty() for locale
[1030/152233.482899:ERROR:egl_util.cc(60)] Failed to load GLES library: /headless-shell/swiftshader/libGLESv2.so: /headless-shell/swiftshader/libGLESv2.so: cannot open shared object file: No such file or directory
[1030/152233.483855:ERROR:viz_main_impl.cc(167)] Exiting GPU process due to errors during initialization
[1030/152233.485564:WARNING:gpu_process_host.cc(1207)] The GPU process has crashed 2 time(s)
[1030/152233.485677:ERROR:browser_gpu_channel_host_factory.cc(138)] Failed to launch GPU process.`
solution ??
Did you solve the problem, I encountered the same problem
@donfrigo why did you close this issue? Is it a non-issue? Pls comment
Hi @briansorahan! I closed it in favor of #502 although I still haven't figured out this whole issue.
Most helpful comment
Did you solve the problem, I encountered the same problem