chromium-browser not starting about alpine-chrome HOT 37 CLOSED

@ardeois
you need to upgrade libstdc++ to let chromium starts
apk add libstdc++@edge

from alpine-chrome.

Hi there!
I just tried @wtayyeb suggestion and it's working 🎉
#41

@paretl I've pushed a 76-with-puppeteer version. See here

from alpine-chrome.

For your information, I just manually published a 76-with-node version for your needs.

docker container run -it --rm --entrypoint "" zenika/alpine-chrome:76-with-node chromium-browser --version

Chromium 76.0.3809.132 

from alpine-chrome.

@FibreFoX full installation command is like below on a pure alpine1.10 image

    apk add --no-cache chromium@edge harfbuzz@edge nss@edge freetype@edge ttf-freefont@edge libstdc++@edge

from alpine-chrome.

We also ran into this with the :with-node images. Since we extend this image anyway; we could around it with a similar approach to @robwilde

FROM zenika/alpine-chrome:with-node
USER root
# Workaround for https://github.com/Zenika/alpine-chrome/issues/39
RUN apk add --no-cache chromium@edge=73.0.3683.103-r0
USER chrome

# ...

Would be great if we could get versioned variants of the with-node tags here as these images are very convenient. :-)

from alpine-chrome.

Hi there 👋

Sorry for the delay.
Thanks @chadlwilson for your precious replies. 💚
Indeed, with-node has no version but I created the issue #38 to fix that. 👌

Has someone investigated why Chromium 77 create this error? 🤔

from alpine-chrome.

What about the one with the with-puppeteer tag ? This image has the exact same error with the latest version. For the moment I rebuild the image with the version 76 of Chrome.
@jlandure If you can publish a 76-with-puppeteer version it would be very great 😄
Thank you in advance!

from alpine-chrome.

FROM zenika/alpine-chrome:with-node@sha256:a449df361d60dddef4f5b7de8d31e6c57d7a0feef74b6ac42b777fe30b7aef85

Is also an option for those who want to use the old image in its entirety - the one that had Chromium 76 prior to its removal from Alpine's repository.

$ chromium-browser --version
Chromium 76.0.3809.132

Thank you for that!

from alpine-chrome.

Thank you @jlandure
I think it could be a great idea to have a tag with the chrome version for each one (in the future of course). It will permit to us to have a fix version of this image into our pipeline
We can talk about it if you want

from alpine-chrome.

Thank @jlandure
I confirm using latest docker version fixed the issue.
Should I close this issue or I let you close it?

from alpine-chrome.

@ardeois The Chromium version you used (in the table ?) is 77.0.3865.75-r0.

Cloning the Dockerfile and downgrading the Chromium version eliminated this error. Didn't test many due to crunch here but found no such issue with chromium@edge=72.0.3626.121-r0.
So, issue seems to be upstream

from alpine-chrome.

Hi @ardeois

Thank for your warm feedback 👋
I got the same error in the build done by the Docker Hub. 👌

Error relocating /usr/lib/chromium/chrome: _ZNSt7__cxx1118basic_stringstreamIcSt11char_traitsIcESaIcEEC1Ev: symbol not found

@teddy-error Thank for your suggestion. 👍

You could do that but the best way managing docker image is to set the version of the image used using a tag like zenika/alpine-chrome:76 (available versions listed here)

For of all, we can set the version of the docker image using:

docker container run -it --rm --entrypoint "" zenika/alpine-chrome:76 chromium-browser --version

@robwilde @teddy-error 📝 I think the change is around the apk add chromium@edge (L20)
You could set a version: apk add chromium@[VERSION]
Available versions of Chromium are listed here

from alpine-chrome.

For your information, the latest version installed is Chromium 77.0.3865.75-r0.
We have to investigate to check what's the problem. 🙌

from alpine-chrome.

Thank you for the analysis.
I indeed got around the issue by fixing the version of the docker image. However, as we're using with-node tag, and this tag is not versioned, we had to duplicate what this Dockerfile is doing

I guess fixing this issue would have avoided that override, but it's not a big deal for now
#38

from alpine-chrome.

FROM zenika/alpine-chrome:with-node@sha256:a449df361d60dddef4f5b7de8d31e6c57d7a0feef74b6ac42b777fe30b7aef85

Is also an option for those who want to use the old image in its entirety - the one that had Chromium 76 prior to its removal from Alpine's repository.

$ chromium-browser --version
Chromium 76.0.3809.132

from alpine-chrome.

Thanks @jlandure - that's nicer than a direct SHA FROM instruction :-)

from alpine-chrome.

@wtayyeb I tried this, but did not work:

apk add --no-cache chromium@edge chromium-chromedriver@edge libstdc++@edge

Result:

Error relocating /usr/lib/chromium/chrome: _ZNSt7__cxx1118basic_stringstreamIcSt11char_traitsIcESaIcEEC1Ev: symbol not found
Error relocating /usr/lib/chromium/chrome: _ZNSt7__cxx1119basic_ostringstreamIcSt11char_traitsIcESaIcEEC1Ev: symbol not found
Error relocating /usr/lib/chromium/chrome: _ZNSt19_Sp_make_shared_tag5_S_eqERKSt9type_info: symbol not found

Looks like Alpine is broken, probably due to a missing patch or so :(

EDIT:
Running chromedriver directly explodes the same way, so I assume a generic problem in the Alpine version

/ # /usr/lib/chromium/chromedriver
Error relocating /usr/lib/chromium/chromedriver: _ZNSt7__cxx1119basic_ostringstreamIcSt11char_traitsIcESaIcEEC1Ev: symbol not found
Error relocating /usr/lib/chromium/chromedriver: _ZNSt7__cxx1118basic_stringstreamIcSt11char_traitsIcESaIcEEC1Ev: symbol not found
Error relocating /usr/lib/chromium/chromedriver: _ZNSt19_Sp_make_shared_tag5_S_eqERKSt9type_info: symbol not found

EDIT 2:

I dug a bit deeper, there are similar issues on other projects (like this one https://gitlab.alpinelinux.org/alpine/aports/issues/4758) and to me it seems that there is a compability-problem, which might not be that easy to get resolved. Mixing repositories seems to be not good with Alpine-Chromium/Chromedriver anymore 😿

from alpine-chrome.

@paretl 💡 Yes Indeed. I'm trying to do it in #38 🙌

from alpine-chrome.

Issue closed! Thanks everyone for your support 🎉

Do not hesitate to give information on your usage with this image using the issue template "support".
I am thinking of refactoring the readme and add a contributor page like this one

from alpine-chrome.

@teddy-error could possibly share the line you changed in the docker file to adjust the version as I am not sure of the syntax.

Thanks

from alpine-chrome.

In our case we changed our docker build to

chromium@edge=72.0.3626.121-r0

That solved our problem for now in our Pipelines

from alpine-chrome.

Hi @mllopart 👋
Thanks for your reply!

This is an option but you need to fork the project. 👌
I'm thinking: why are not you using the image tag zenika/alpine-chrome:72 instead of modifying the Dockerfile and building it by our own?
I am very interested! 👍

from alpine-chrome.

@jlandure This was of course the first attempted solution (much easier than cloning after all…) but interestingly using a static version tag did not resolve the issues.

Noting for others who seem confused that the syntax to downgrade is slightly different than you wrote:
apk add chromium@edge=VERSION

from alpine-chrome.

Thanks for the info. I investigated the apk installs and did just that. I found that if I replace @edge with @v3.9 it will complete the build and install chrome 72, then everything works.
A colleague had a similar issue and suggested it actually has something to do with the Linux Kernal version 5.0.0.27 and everything works OK with 5.0.0.25.

I can confirm that as I have one build running on Elementary OS (18.04 LTS) and it works just fine with @edge version and chrome 77 but on my laptop, running POP OS (19.04 confirmed to have Kernal 5.0.0.27) it does not work until v3.9 and chrome 72
I did the test with Chrome 73 and it also fails.

Hope this helps

from alpine-chrome.

@chadlwilson Why did you use USER chrome there, is there an issue using root?

from alpine-chrome.

@chadlwilson Why did you use USER chrome there, is there an issue using root?

The base Dockerfiles run as USER chrome rather than root; so was just switching back to the same user as the base image for consistency (although running as non-root is good practice in general).

from alpine-chrome.

As this issue is hitting other people too, did this issue already got reported to Alpine? Do you have any issue-tracker-link or such thing?

from alpine-chrome.

For your information, it's hacktoberfest. Do not hesitate to create PR to support and improve this image 🙌
More about Hacktoberfest here

from alpine-chrome.

Hey @paretl 👋
You can now find new tags: 🎉

• with-node, 77-with-node, 77-with-node-10
• with-puppeteer, 77-with-puppeteer

See README or DockerHub for more info

from alpine-chrome.

@wtayyeb ;) my problems are fixed now, switched our docker-image to be based on alpine:edge, due to the problem with mixing repositores having different glibc-stuff (which ends up not being able to get mixed that easy). I got to this issue "by accident" using DuckDuckGo because I found that _ZNSt19_Sp_make_shared_tag5_S_eqERKSt9type_info: symbol not found-stuff. So your solution did not work for me, so I created a new docker-image based on the same repository instead of mixed ones.

from alpine-chrome.

Hi @FibreFoX
Glad you succeed 🎉
I was wondering: why don't you update this repository to improve it and help others instead of forking or creating your own image? 🤔
It's hacktoberfest 🎉✌️

from alpine-chrome.

@all-contributors please add @ardeois for bug

from alpine-chrome.

@jlandure

I've put up a pull request to add @ardeois! 🎉

from alpine-chrome.

@all-contributors please add @FibreFoX for question

from alpine-chrome.

@jlandure

I've put up a pull request to add @FibreFoX! 🎉

from alpine-chrome.

@all-contributors please add @chadlwilson for question and ideas

from alpine-chrome.

@jlandure

I've put up a pull request to add @chadlwilson! 🎉

from alpine-chrome.