-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Upload container images for arm64 architecture #1851
Comments
We can definitely consider this (: Help wanted to set it up. |
I'd be happy to help, but unfortunately it seems like CircleCI doesn't support it (yet). There are some hacky workarounds, but I'm not sure if this is the correct way. So actually I have no idea how to do this right now. |
I don't think we need any CI special feature for this: Let's instead use the way Prometheus is doing this, so: And Dockerfile taking binaries from (: |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still valid, and in fact we have a PR ready - it's waiting on us to actually test it and update quay a bit. |
This issue/PR has been automatically marked as stale because it has not had recent activity. Please comment on status otherwise the issue will be closed in a week. Thank you for your contributions. |
I am also looking into starting to test with m6g instances. Are there any prediction of when it will be available? |
Hello 👋 Looks like there was no activity on this issue for last 30 days. |
Closing for now as promised, let us know if you need this to be reopened! 🤗 |
Is this still being worked on? I just tested and the thanos-sidecar in Prometheus is one of only a few containers that still make issues. |
We had contributions to add the build/CI process. but I think there is some process of configuration on quay/dockerhub. To test and finish up. cc @daixiang0 |
While I have no permission to test it, please help @bwplotka ! |
Hello people! Is this still a valid thing? We would really like this as well (and are willing to help with anything as well) |
Looks like it's getting quite a popular feature (: We already build such binaries - so you can easily build ( We will try to prioritize this on maintainer team (: Thanks! |
FYI this is how we did it with GitHub actions, works fine for us so far: |
I don't think thanos requires this, it could use standard go crossbuild. I am happy to see how we can share promu with thanos, but generic tools like goreleaser would work too. |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Still needed. |
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Still needed. |
Remove the stale label please |
Just found this issue, but I can confirm: |
We really needed this ARM64 supported official image into the docker hub and quay.io/thanos/thanos. As AWS already started the support graviton2 type images into the EKS. |
We will be very helpful: |
2 years later. Still needed |
Still wanted :) +1, in my case armv7. |
After #4947 is done, we will finally have this ready. @firefixmaarten could you please open a separate ticket for armv7? |
https://quay.io/repository/thanos/thanos/manifest/sha256:ba0b9192a0db3693afcb220c4c1fc8578a1c25df20dc41697e57b3329fe1d7f8 |
Hi @GiedriusS, given the latest release of v0.24.0 and v0.23.2 of thanos, the arm64 images are not built accordingly. Why is this so? |
@WeiTangLau Not a maintainer here, but i guess thats because the release candidates of those versions pre date the merge of this feature. See https://github.com/thanos-io/thanos/commits/v0.24.0. I think the next release (0.25) will have arm64 images. |
Now that AWS announced their way more powerful M6g instances it will start to get interesting to move from x86 to the ARM architecture. You already provide binaries on the releases page, but the docker images are for x86 only. Could you maybe adjust your build pipeline and provide images for ARM like prometheus does?
The text was updated successfully, but these errors were encountered: