Open mflorea opened 1 year ago
I might have facing the same issue.
At the moment a pinned a problem down to the this image version. Tag 100 confirmed to work. Running test pipelines at the moment to get actual logs on 102 and 108 tags.
Thanks for details @mflorea !
With the flags from environment variable CHROMIUM_FLAGS
added to the start command I see way less errors on 108 tagged image and my test suite passes with browser crash. So I believe that https://github.com/Zenika/alpine-chrome/commit/a80c4e3e68080bc9f8f090bb1021642b085d70e9 commit should be reverted.
i face the same issue both tag 102 and latest :( 。but happen occasionally。
Describe the bug
I've been using the
zenika/alpine-chrome:latest
image without any issue for almost 1 year but today I had to clear (prune) the Docker images I have locally and the new fetched image stopped working correctly. My code hasn't changed so this is clearly a regression on the Chrome image side. I then run my code with thezenika/alpine-chrome:102
image and everything was fine. So the problem seems to be with the latest 108 tag.To Reproduce
Steps to reproduce the behavior:
Notice that the command line parameters passed to Chrome are different between the two images, most probably related to https://github.com/Zenika/alpine-chrome/commit/a80c4e3e68080bc9f8f090bb1021642b085d70e9 .
http://localhost:9222/json
with the local instance of Chrome to connect remotely to the Chrome instance from the Docker containerhttp://localhost:9222/devtools/inspector.html?ws=localhost:9222/devtools/page/86DA8B8B16A870375D36C324EB4D0FA9
with the local instance of Chrome to connect remotely to the Chrome tabhttps://github.com/Zenika/alpine-chrome
in the remote Chrome tabWhat is the expected behavior?
The web page is loaded fine.
What is the actual behavior?
The web page is loaded fine with the 102 tag but crashes the Chrome browser (with lots of
net::ERR_INSUFFICIENT_RESOURCES
) when thelatest
(108) tag is used.Versions
Docker Engine: 20.10.22