Support kicbase image build on arm64 platforms (Apple M1/Linux aarch64)

[ilya-zuyev]

We started to use docker buildx to build multi-arch kicbase images
It's not working on M1 with current preview version of docker:

develop@Devs-Mac-mini --- g/minikube ‹master› » KICBASE_IMAGE_REGISTRIES=gcr.io/kicbase/kicbasr:foo make $_                                                           130 ↵
env DOCKER_CLI_EXPERIMENTAL=enabled docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
Unable to find image 'multiarch/qemu-user-static:latest' locally
latest: Pulling from multiarch/qemu-user-static
d60bca25ef07: Pull complete 
7045fbe28d35: Pull complete 
ed8a5179ae11: Pull complete 
1ec39da9c97d: Pull complete 
0421b3622b1a: Pull complete 
Digest: sha256:14ef836763dd8a1d69927699811f89338b129faa3bd9eb52cd696bc3d84aa81a
Status: Downloaded newer image for multiarch/qemu-user-static:latest
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
make: *** [docker-multi-arch-builder] Error 

develop@Devs-Mac-mini --- g/minikube ‹master› » docker version
Client:
 Cloud integration: 1.0.2
 Version:           20.10.1
 API version:       1.41
 Go version:        devel +37a32a1833 Thu Dec 3 21:34:39 2020 +0000
 Git commit:        831ebeae96
 Built:             Wed Dec 16 02:33:22 2020
 OS/Arch:           darwin/arm64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.1
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       f001486
  Built:            Tue Dec 15 04:35:03 2020
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          v1.4.3
  GitCommit:        269548fa27e0089a8b8278fc4fc781d7f65a939b
 runc:
  Version:          1.0.0-rc92
  GitCommit:        ff819c7e9184c13b7c2607fe6c30ae19403a7aff
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

[ilya-zuyev]

develop@Devs-Mac-mini --- g/minikube ‹master* ?› » docker manifest inspect multiarch/qemu-user-static                                                                 255 ↵
{
	"schemaVersion": 2,
	"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
	"config": {
		"mediaType": "application/vnd.docker.container.image.v1+json",
		"size": 2693,
		"digest": "sha256:a217e72a82933e6080519f3ea06bddaafac51540b5d31161ca1d14da3f5afdba"
	},
	"layers": [
		{
			"mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
			"size": 766574,
			"digest": "sha256:d60bca25ef07e48961711a71bd92e771efdd574b87f3c254f06c0499404c56a1"
		},
		{
			"mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
			"size": 386,
			"digest": "sha256:7045fbe28d35d4057096794c2879e9aea4de0a381bea45a4b7f4431fba293186"
		},
		{
			"mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
			"size": 3091,
			"digest": "sha256:ed8a5179ae114eedb71fdb48ad41727b9eb9d95dee764c81944982347194ee6c"
		},
		{
			"mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
			"size": 3090,
			"digest": "sha256:1ec39da9c97d1e80479f085460e81b4d479cc47c659173f7c63874e0fc504914"
		},
		{
			"mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
			"size": 70235529,
			"digest": "sha256:0421b3622b1a31638576c7183624667ac386b71e08300f6704adb8d746705d14"
		}
	]
}

We use multiarch/qemu-user-static buildx image, which is not multi-arch itself

[ilya-zuyev]

waiting for Docker to support buildx on M1

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[sharifelgamal]

Freezing this since it's still an issue, but it's not really a priority, since we can build the multiarch images on amd64.