New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker: ARM images doesn't work since v6.4.x #19585
Comments
Thanks for reporting this @theWaldschrat we'll investigate it further |
@theWaldschrat what device are you using? Is that 32- or 64-bit architecture (armv6m armv7, armv8 etc)? |
Maybe we need to include https://pkgs.alpinelinux.org/package/edge/main/armhf/libc6-compat in Grafana docker image? apk add --no-cache --repository=http://dl-cdn.alpinelinux.org/alpine/edge/main libc6-compat @theWaldschrat can you confirm that above solves the prioblem? Harder for us to verify without access to an actual ARM device.Docker based arm image maybe a possibility, but appreciate if you can help us out here. Thanks |
The device is a Raspberry Pi 4B. Technically it's an ARM64v8, but Raspbian by default runs a 32 bit kernel and userland, so ARM32v7.
I didn't build a lot of Docker images yet, so I'm not able to try above command in a new image, at least not quickly. But what I did do: Run a grafana:latest container with entry point bash and user root:
I'm not an expert, but I guess the lib-c are still not compatible. |
@theWaldschrat thank you very helpful. Just to verify some additional things can you specifically try these to verify that you get the same problem:
Just to be sure, can you also try to run and start grafana-server: |
First two all do the same as previously described. The third one doesn't even start with an arch mismatch: |
I have the same issue and had to downgrade to version |
Thanks. After you entered bash can you try and install the musl-dev packade using apk add? |
|
Installing the glibc apks from https://github.com/armhf-docker-library/alpine-pkg-glibc/releases allows |
It's the idea of Alpine to statically link to musl instead of dynamic glibc linking. It's faster, smaller, more stable and potentially more secure. At least that's what they say. |
Considering this change effectively broke the docker image for ARM devices, I was expecting something better than a tag of "needs investigation". Sigh! The curse of "agile development", I guess. |
I can reproduce the error in OS X, even though it looks a bit different from yours:
I will see if I can fix it. |
I might have a lead on the root cause for this issue, hoping I can fix it by tomorrow. |
Working to solve this by building musl binaries in addition to glibc ones. |
Just ran into this as well. My system is aarch64 (RockPro64) and I'm getting the same error:
|
LGTM running on a Raspberry 3B |
SBC: Cubietruck (aka CubieBoard 3)
LGTM
|
Thanks a lot for the quick responses and help. Very appreciated. |
Agreed, thanks for helping test!
…On Tue, Oct 22, 2019, 19:05 Marcus Efraimsson ***@***.***> wrote:
Thanks a lot for the quick responses and help. Very appreciated.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#19585?email_source=notifications&email_token=AACEVV4YMCESH5G7XWTY3QLQP4XHPA5CNFSM4I42J4CKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB6PL5A#issuecomment-545060340>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACEVV3OBIAWAV3ZNAP4XEDQP4XHPANCNFSM4I42J4CA>
.
|
raspberry pi 4b
|
LGTM: raspberry pi 4
|
LGTM rockchip rock64
|
Docker skill level LOG file: |
Thanks all. We've merged this to master, but decided to include this fix in Grafana v6.5.0, to be released in a couple of weeks. Until then you may use nightly builds if you want to run Grafana v6.5-pre ARM-compatible Grafana docker images by using the |
Please add a note to docker hub so it is easier to find this issue. If you are currently pulling grafana/grafana you still get a non-functional image on armhf. |
Just commenting to note that grafana/grafana-arm32v7-linux:latest now works fine for me (this image), so I've unpinned versions 👍 |
@mhansen you can use directly the base image (grafana/grafana:latest), it's multiarch :) I'm currently using grafana/grafana:6.5.1@sha256:befcd84da2c1f3310b23d93ba9eec4a80df4c86c04bd39455623ac632fbcefdd in an ARM cluster. |
@theWaldschrat @pedroetb @mhansen @herm @SySfRaMe @krystian-wojtas @pgolm @gcgarner @JochenLutz @iwittkau @JasonSwindle @protik77 @ata4 we could use some help testing new builds (Docker images and tar archives) on various ARM architectures, might you lend a hand? We would appreciate it! The Docker images in question
The tar archives in questionMUSL archives are for Alpine Linux, GLIBC ones are for regular Linux distros: RPMs |
Docker image |
Thanks @volschin! |
Had a problem with the container today after running about 24h (no templating init). This is nothing that happend in the last months. So perhaps there is a stability problem. |
What kind of problem did you see exactly @volschin? |
@aknuds1 sorry, I did not get around to fully testing the new docker arm images yet. Is there a way to automate testing? |
I don't have any automated method, sorry @iwittkau. |
I'm no longer seeing grafana/grafana:latest as being multiarch, only amd64/linux.
I've switched to grafana/grafana:master |
@mhansen Interesting, thanks for the heads up. I will have to check on this. |
For what it's worth, I am using |
What happened:
Grafana 6.4.X ARM in Docker does not work on Raspbian Buster.
Error message when trying to run the container:
/run.sh: line 80: /usr/share/grafana/bin/grafana-server: No such file or directory
What you expected to happen:
Obvious: Grafana runs without error.
How to reproduce it (as minimally and precisely as possible):
docker run grafana/grafana
Anything else we need to know?:
Error is caused by a lib-c mismatch: Grafana is build with ld-linux-armhf.so, but Alpine base image contains only ld-musl-armv7.so.
Environment:
The text was updated successfully, but these errors were encountered: