set docker env variable to force it build images for linux/amd64 platform

[showuon]

Since all our images are running in linux/amd64 platform, we need to force docker to build linux/amd64 compatible images. Without this patch, the M1 mac will fail to deploy the fleetshard operator due to the error:

State:         Waiting
      Reason:      CrashLoopBackOff
    Last State:    Terminated
      Reason:      Error
      Message:     exec /bin/opm: exec format error

Note: It won't impact any non-arm64 chip users because they will build with linux/amd64 originally.

ref: https://docs.docker.com/engine/reference/commandline/cli/#environment-variables

[MikeEdgar]

LGTM. Do you know if podman considers this env also?

[showuon]

LGTM. Do you know if podman considers this env also?

Had a quick search, but didn't find any. Podman only provides the --platform for each command. That works for most cases, but for this opm command, we can't set any docker/podman options into it, which will also fail:

kas-installer/operators/generate-kas-fleetshard-olm-bundle.sh

Line 352 in f047433

opm index add --bundles "${BUNDLE_IMAGE}" --tag "${INDEX_IMAGE}" -u docker

ref: https://docs.podman.io/en/latest/markdown/podman-build.1.html#platform-os-arch-variant

[MikeEdgar]

Had a quick search, but didn't find any.

Same, the best I could find was a Reddit comment that seems to imply it would work (given the context of the post): https://www.reddit.com/r/docker/comments/r0r86r/comment/hlwub5r/?utm_source=share&utm_medium=web2x&context=3

I think we can go ahead and merge this. @k-wall are you using podman on an M1?

[showuon]

Had a quick search, but didn't find any.

Same, the best I could find was a Reddit comment that seems to imply it would work (given the context of the post): https://www.reddit.com/r/docker/comments/r0r86r/comment/hlwub5r/?utm_source=share&utm_medium=web2x&context=3

I think we can go ahead and merge this. @k-wall are you using podman on an M1?

I don't think currently podman supports running in M1 mac:
containers/podman#14303

I ran into the same error in the issue, and then decided to use docker instead.