A bit more help about azure-pipelines-multiarch-docker HOT 3 OPEN

It shouldn’t be a problem, and should even simplify the bits where I explicitly tag the images with the target architecture - I do that out of habit from the pre-manifest days and also because I sometimes want to have extra architectures on the side, and it’s entirely optional.

What bits do you need help with? We can use this issue to discuss that.

from azure-pipelines-multiarch-docker.

I have no clue where to start. Probably need the following information:

• Base image: node:lts-alpine = multi architecture
• Working docker file: Dockerfile

And what I need to do is create the correct makefile (and optionally schedule it on some azure pipeline).

But I don't really understand what's happening in the makefile. What's that qemu I'm seeing everywhere.

To my understanding this is what get executed for each arch

• make qemu
• make wrap-$(ARCH)
• make build-$(ARCH)
• make push-$(ARCH)

And then make manifest to publish

from azure-pipelines-multiarch-docker.

Hello there,

What the qemu step does is register QEMU on the current system to allow ARM binaries to be run inside an Intel host. This is because most public CI services only have x64 workers.

The wrap step builds a temporary container with the base image and a static qemu binary inside it, which acts as a base container for the build step. The added file is only a few megabytes (and can be removed later, although I don't bother), but is required for the ARM binaries to work inside the build step.

The rest should be straightforward, although I do use make recursively to set a few environment variables (it's easier to maintain than adding a bunch of external 5-line shell scripts).

Hope this helps (and Happy 2020!)

from azure-pipelines-multiarch-docker.