Build multi-arch images for ARM64 and AMD64 at the same time

[sarandia]

We can use buildx, which is already set up in the Makefile, to
simultaneously build a multi-arch Docker image for this component for
ARM64 and AMD64, such that the image will work for both architectures.

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
We can publish an image that is multi-arch across X86 and ARM64.
Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

[k8s-ci-robot]

Welcome @sarandia!

It looks like this is your first PR to kubernetes-sigs/gcp-compute-persistent-disk-csi-driver 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/gcp-compute-persistent-disk-csi-driver has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @sarandia. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mattcary]

/assign

[mattcary]

/ok-to-test
/release-note-none

[mattcary]

/lgtm

[sarandia]

/retest

[sarandia]

/retest

[mattcary]

I think you're running into #743. I'll have a fix out for that today.

[mattcary]

#743 just fixed.

/retest

[saad-ali]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: saad-ali, sarandia

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [saad-ali]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jingxu97]

This PR breaks the multi-arch build. Linux build with current Dockerfile does not work for amd 64, I think. Need to consider revert this PR until the issue is fixed.

https://storage.googleapis.com/kubernetes-jenkins/logs/ci-gce-pd-csi-driver-latest-k8s-master-windows-2004/1383518650501173248/build-log.txt

See errors

#25 41.10 Fetched 5318 kB in 0s (14.1 MB/s)
#25 41.20 Error while loading /usr/sbin/dpkg-split: No such file or directory
#25 41.21 Error while loading /usr/sbin/dpkg-deb: No such file or directory
#25 41.22 dpkg: error processing archive /var/cache/apt/archives/libuuid1_2.33.1-0.1_arm64.deb (--unpack):
#25 41.22  dpkg-deb --control subprocess returned error exit status 1
#25 41.25 Errors were encountered while processing:
#25 41.25  /var/cache/apt/archives/libuuid1_2.33.1-0.1_arm64.deb
#25 41.38 E: Sub-process /usr/bin/dpkg returned an error code (1)
#25 ERROR: executor failed running [/dev/.buildkit_qemu_emulator /bin/sh -c clean-install udev]: exit code: 100
------
 > [linux/arm64 base 2/2] RUN clean-install udev:
------
Dockerfile:22
--------------------
  20 |     # MAD HACKS: Build a version first so we can take the scsi_id bin and put it somewhere else in our real build
  21 |     FROM k8s.gcr.io/build-image/debian-base:v2.1.3 as base
  22 | >>> RUN clean-install udev
  23 |     
  24 |     # Start from Kubernetes Debian base
--------------------
error: failed to solve: rpc error: code = Unknown desc = executor failed running [/dev/.buildkit_qemu_emulator /bin/sh -c clean-install udev]: exit code: 100
make: *** [Makefile:83: build-and-push-container-linux] Error 1
make: Leaving directory '/home/prow/go/src/sigs.k8s.io/gcp-compute-persistent-disk-csi-driver'

[sarandia]

@jingxu97 Thanks for pointing it out. We need to add one more line. I created #751 to fix this.