You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All the Observatorium repos are currently publishing only x86_64 images.
This makes is much more difficult for folks with arm64 computers (like Apple Silicon Macbooks) to be able to contribute to the projects, as most of them use the efficientgo/e2e framework for e2e tests based on container images.
We should publish multi-arch images with at least x86_64 and arm64 architectures. Other architectures could be added in the future.
Proposal
Development container builds should be possible without any cross-build tooling.
Only release builds should be using a cross-build tool like Docker's buildx or podman (its build command supports building multi-arch images).
The compilation process should take advantage of the Go's amazing cross-compilation features and avoid compiling under a different architecture's QEMU. Docker has a cool article on how to do this.
They all have a similar approach to how container images and built and published. After one of them is migrated to multi-arch the steps to migrate the others will be mostly the same.
The text was updated successfully, but these errors were encountered:
I'll try to slowly tackle this starting by the token-refresher, because it has the less probability of being disruptive to development of other features.
All the Observatorium repos are currently publishing only
x86_64
images.This makes is much more difficult for folks with arm64 computers (like Apple Silicon Macbooks) to be able to contribute to the projects, as most of them use the efficientgo/e2e framework for e2e tests based on container images.
We should publish multi-arch images with at least
x86_64
andarm64
architectures. Other architectures could be added in the future.Proposal
Development container builds should be possible without any cross-build tooling.
Only release builds should be using a cross-build tool like Docker's
buildx
orpodman
(its build command supports building multi-arch images).The compilation process should take advantage of the Go's amazing cross-compilation features and avoid compiling under a different architecture's QEMU. Docker has a cool article on how to do this.
Projects to migrate to multi-arch
They all have a similar approach to how container images and built and published. After one of them is migrated to multi-arch the steps to migrate the others will be mostly the same.
The text was updated successfully, but these errors were encountered: