Skip to content

docs(development): describe the multi-arch default of make image #711

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.

Sign up for GitHub

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

Open
Aleksei Sviridkin (lexfrei) wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(development): describe the multi-arch default of make image #711

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions content/en/docs/next/development.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -301,6 +301,10 @@ docker buildx create \

Alternatively, omit the --driver* options to set up the build environment in an local Docker environment.

`make image` builds for `linux/amd64` and `linux/arm64` by default, so the builder must support both platforms, as the one above does. Pass `BUILDER=<name>` to pick it. Go builders compile natively on the build platform, so only package installs in the image run under emulation; a local Docker builder needs QEMU (or Rosetta on Apple Silicon) registered for the other architecture. Set `PLATFORM` to build something else, for example `PLATFORM=linux/amd64` for a single architecture.

`LOAD=1 PUSH=0` loads the image into the local Docker image store instead of pushing it, and builds for the host architecture only, because the classic image store cannot load a multi-platform image. The `talos` and `testing` packages always build `linux/amd64`, since what they produce only runs there.

### Packages management

Each application includes a Makefile to simplify the development process. We follow this logic for every package:
Expand Down
Loading