Chromium headless not work at 2019 image #3438
Comments
|
Hi, I can confirm the same faulty behavior, I use CefSharp 71 in Offscreen mode, which also uses Chromium internally. This is the bug I logged originally: While attempting to fix the original problem, I now encounter these errors:
Reproduced on Docker 18.09.2 |
|
I ran across this error as well. Using Windows Server Core 1803 Images in HyperV-isolation allows headless Chrome to work as expected, but is really not ideal. |
|
Hello, I was troubled by this line in particular:
Usually an error code isn't 0, which usually indicates success, so I got the chromium sources, compiled it, and noticed a bug in the logging code. After fixing that bug, the real error code is:
This seems to indicate an 'The RPC server is unavailable' Is there a service that should be running and that isn't? For information, I checked on my running container (following @vasokot exact steps) that both RpcSs and RpcEptMapper services were running, but that doesn't seem enough. |
|
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
|
/remove-lifecycle stale |
|
I'm not sure if this is the same issue, but there is a lot of overlap of symptoms ( In the chromium bug, it looks like the problem appears to be the font cache not being able to fallback to the last resort font. I thought I would share this here in case the chrome bug ends up being the root cause. I am running docker 19.03.1 and a base docker image of |
|
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
|
To the best of my knowledge the issue still stands. /remove-lifecycle stale |
|
2019 image does not contain fonts, so chrome can't default to last resort font. The solution is to install fonts manually (which is not trivial though). Example and working Dockerfile can be found in my repo here: https://github.com/gantrior/docker-chrome-windows |
|
Hi Gantrior, I tried your solution and ran powershell command given in the start.ps1 inside of container but failed with below error: c:\Program Files (x86)\Google\Chrome\Application>chrome.exe --headless --disable-gpu --no-sandbox --enable-logging --print-to-pdf="C:/export/pdftest.pdf" htt c:\Program Files (x86)\Google\Chrome\Application>[1213/205519.925:ERROR:network_change_notifier_win.cc(141)] WSALookupServiceBegin failed with: 0 could you please suggest here. |
|
@KGitanjali I think you have to create the C:/export folder first or change the --print-to-pdf value to a valid path. After that it should works! |
|
Thank you abmarko for the correction..after creating the required path it worked..!! |
|
@gantrior your files worked like a charm!!!! thanks a ton :)) |
BEST ever solution!!! |
|
Thank you for this. It seems to have solved my issue as well. |
|
Issues go stale after 90 days of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
|
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Expected behavior
pdf-file created
Actual behavior
error:
Information
Steps to reproduce the behavior
Download Chromium 74.0.3714.0 or any other (64.0.3282.0 for example)
Extract chrome-win.zip to C:\chrome
run docker container: docker run --rm -v C:\chrome-win:c:\chrome -i microsoft/dotnet-framework:3.5-runtime-windowsservercore-ltsc2019
run command: C:\chrome\chrome.exe --headless --no-sandbox --print-to-pdf="C:/chrome/pdftest.pdf" https://www.google.com/
Work at:
The text was updated successfully, but these errors were encountered: