We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Images like gcr.io/prysmaticlabs/prysm/validator:stable should support arm64
gcr.io/prysmaticlabs/prysm/validator:stable
These images should be able to be ran on amd64 or arm64
The build system should implment a fat-manifest
Building, and maintaing my own image. This is required for multi-arch clusters without tolerating to amd64 which increases power usage.
The text was updated successfully, but these errors were encountered:
Probably depends on bazelbuild/rules_docker#1599 or doing something else entirely.
Sorry, something went wrong.
Seems like we can do a workaround like this: buchgr/bazel-remote#453
That looks like a suitable workaround. Are maintainers okay with something like that?
Fixed in #12428. We are planning to switch to these multi-arch images, starting in the next release.
prestonvanloon
No branches or pull requests
🚀 Feature Request
Images like
gcr.io/prysmaticlabs/prysm/validator:stable
should support arm64Description
These images should be able to be ran on amd64 or arm64
Describe the solution you'd like
The build system should implment a fat-manifest
Describe alternatives you've considered
Building, and maintaing my own image. This is required for multi-arch clusters without tolerating to amd64 which increases power usage.
The text was updated successfully, but these errors were encountered: