feat: docker multi arch images

[cheyer]

This closes #12.

We need to build our docker images for multiple architectures (amd64 and arm64) since we need to be able to develop on MacBooks based on Apple silicon (M1 etc.).

This PR uses docker buildx to simply build multi arch images. The docker buildx build also includes pushing the images to the registry (with --push), so we can get rid of the separate docker push commands.
In order to use docker buildx we need to setup it using the setup-buildx-action action.

The github action mentioned in the docker guide is deprecated. However it mentions the correct docker gh actions that we can use:

      # https://github.com/docker/setup-qemu-action
      - name: Set up QEMU
        uses: docker/setup-qemu-action@v1
      # https://github.com/docker/setup-buildx-action
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v1

How to test (locally)

I tested the docker buildx command locally on MacBook Pro with M2 chip creating a test image for the data graph repository:

docker buildx build . -t ghcr.io/dot-base/data-graph:2023-06-28-test --push --platform linux/amd64,linux/arm64

Running the command above for the 1st time will result in an error, since we are missing the correct driver:

[+] Building 0.0s (0/0)
error: multiple platforms feature is currently not supported for docker driver. Please switch to a different driver (eg. "docker buildx create --use")

Therfore, we need to create a docker driver first:

docker buildx create --use

If we run the buildx command again, it will work successfully.

docker buildx build . -t ghcr.io/dot-base/data-graph:2023-06-28-test --push --platform linux/amd64,linux/arm64

It successfully creates an image for both architectures. See registry

Reference

• Docker guide on building multi arch images
• GH action to setup buildx mentioned in the docker guide
• Docker Setup Qemu GH action
• Docker Buildx GH action

[Zbozi]

Testing the commands locally with the medical-dashboard resulted in three images:

See: https://github.com/dot-base/medical-dashboard/pkgs/container/medical-dashboard/108518743?tag=test-review

The command i used was:

• docker buildx build . -t ghcr.io/dot-base/medical-dashboard:test-review --push --platform linux/amd64,linux/arm64 --build-arg FONTAWESOME_NPM_AUTH_TOKEN=xxxx

[cheyer]

Testing the commands locally with the medical-dashboard resulted in three images:

See: https://github.com/dot-base/medical-dashboard/pkgs/container/medical-dashboard/108518743?tag=test-review

The command i used was:

• docker buildx build . -t ghcr.io/dot-base/medical-dashboard:test-review --push --platform linux/amd64,linux/arm64 --build-arg FONTAWESOME_NPM_AUTH_TOKEN=xxxx

I could reproduce this, now that I have the latest version of Docker and docker buildx.
This is related to Provenance attestations which are now automatically created with newer versions of docker. Provenance attestations include facts about the build process. This is getting important, as people parallelise building multiarch images on different machines, so build times are faster (we do not do this).
How this information is stored, causes the Github Registry to show more architectures, so it seems to be a bug on Github's side.

I think we have 2 alternatives:

• do nothing, as Github will fix this eventually and the information should be displayed correctly
• call docker buildx build with --provenance=false to not generate this information (data graph image build with this command)

What do you think? @Zbozi

Related Issues:

• Github Container Registry Packages lists the architecture unknown/unknown when manifest attestations are present
• Action started to push manifest indexes instead of images for a single platform docker/build-push-action#755
• improve docs on "emulated" vs "native" multi-arch builds docker/buildx#1510
• docker manifest does not work with output from buildx v0.10 docker/buildx#1509

[cheyer]

We decided to not change it for now, as Github should fix it eventually.