Is your feature request related to a problem? Please describe.
Loki and promtail is not available for ARM architecture
Describe the solution you'd like
Loki and promtail available on ARM architecture
Describe alternatives you've considered
Would be really nice that loki and promtail will have support for ARM devices
Razikus
All 10 comments
Okay, in theory promtail as well as loki are already ARM compatible. As they are written in Golang, which is cross platform, they can run everywhere ARM is supported. However, building production binaries is not currently supported using the Makefile, as the assets task fails because of the wrong GOARCH.
Nevertheless you can build development binaries for your platform yourself:
- Obtain a recent Golang build: https://nats.io/documentation/tutorials/go-install/
- Checkout loki:
git clone https://github.com/grafana/loki && cd loki - Build promtail:
GOOS=linux GOARCH=arm64 go build ./cmd/promtail - Build loki:
GOOS=linux GOARCH=arm64 go build ./cmd/loki
Now you have ./loki and ./promtail binaries for arm64. You may tune GOOS for the Operating System (linux, windows, darwin), and GOARCH for the architecture (amd64, arm64, arm, etc.)
sh0rez
on 6 Jun 2019
Have made a start at Docker images for amd64/arm64 images for both loki and promtail as I have a multi-arch k8s cluster.
Still need to work out ports/configuration/etc in Dockerfiles but hopefully this gets you going (you'll probably overwrite all that with k8s or compose though)
kskewes
on 12 Jun 2019
If you have multi arch cluster how do you deploy for example daemon set of promtail ? You are deploying two and in case of arch is amd you use amd image and in case of arm you deploy arm image ?
RRadziejewski
on 14 Jun 2019
Currently, this is probably impossible with a single DS. However, once we implemented Image Manifest v2, the docker daemon automatically picks the right version for the OS.
Until that you need two.
sh0rez
on 14 Jun 2019
@Kuqd Duplicate of https://github.com/grafana/loki/issues/67
steven-sheehy
on 18 Jun 2019
@sh0rez what is the obstacle to using Image Manifest v2? Is that an internal dependency, or an external one?
vielmetti
on 20 Jun 2019
@vielmetti there is no real obstacle, the required code is just not finished yet. Our current Dockerfile is not cross-platform and the new one is not merged yet (See #668)
Once this is done, I can add manifest v2 support to the CI and cross-platform functionality is provided. Stay tuned!
sh0rez
on 20 Jun 2019
Thanks @sh0rez - that clarifies things. (I know that in the past some registries did not support manifest v2, e.g. Quay.io, wanted to distinguish between things within the project and external to it.)
vielmetti
on 20 Jun 2019
Hello everyone!
I can proudly announce that this has been finally implemented in b887602e3654d9525467ed0cde79884887d94749 :tada:
From now on, it is sufficient to just pull the docker image on the desired architecture and it should be the right one.
Currently supported are amd64, arm64 (sometimes called arm8 or aarch64) and arm7.
Thanks for your patience!
sh0rez
on 1 Aug 2019
Gr8 work, keep it up !!
czw., 1.08.2019, 18:19: sh0rez notifications@github.com napisał(a):
Closed #653 https://github.com/grafana/loki/issues/653.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/grafana/loki/issues/653?email_source=notifications&email_token=AHXPQ2SAIVMPQJ5JWDNDNDTQCMEITA5CNFSM4HTUGZG2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOS2QQUPI#event-2527136317,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHXPQ2XPSW6BMCPD3HDWIQDQCMEITANCNFSM4HTUGZGQ
.
RRadziejewski
on 1 Aug 2019
Related issues
setevoy2
·
4Comments
Menda
·
5Comments
naughtyGitCat
·
3Comments
Mario-Hofstaetter
·
4Comments
cyriltovena
·
4Comments
Most helpful comment
Currently, this is probably impossible with a single DS. However, once we implemented Image Manifest v2, the docker daemon automatically picks the right version for the OS.
Until that you need two.