feat: determine platform details from local docker installation for jibDockerBuild

[mpeddada1]

This code has been tested manually with jib/examples/helloworld/.

Notes:

• If manifest list found then the log picks the image that contains the same os and architecture as the local docker environment (derived through docker info). Otherwise, it throws an error when no matching os and architecture are found. For example, if the platform configurations are as follows then the image with os of linux and architecture of arm64 will be pushed to the docker engine:

<platforms>
                <platform>
                  <architecture>arm64</architecture>
                  <os>linux</os>
                </platform>
                <platform>
                  <architecture>amd64</architecture>
                  <os>linux</os>
                </platform>
 </platforms>

[profhenry]

I think this feature does not work with podman, did you test or consider this?

When using podman the docker info command output differs :-/. It returns

{
  "host": {
    "arch": "amd64",
    "buildahVersion": "1.23.0",
    "cgroupManager": "systemd",
    "cgroupVersion": "v2",
    "cgroupControllers": [],

Please also see: https://docs.podman.io/en/latest/markdown/podman-info.1.html

So determining os and architecture fails and you get "The configured platforms don't match the Docker Engine's OS and architecture (/). It would be nice if we could support podman as well.

[profhenry]

In addition this feature is also enabled when having just one single platform specified.

Even when specifying

<platforms>
  <platform>
    <architecture>amd64</architecture>
    <os>linux</os>
  </platform>
</platforms>

there is no need for this new feature. But it kicks in and fails the build when using podman. How can i disable this feature? This leaves Jib is no longer usable with podman :-/

[chanseokoh]

@profhenry #4265