remote: enable support for additional --build-context on macOS and remote

[flouthoc]

Feature of additional build context added here containers/buildah#3978
already exists on podman following PR just enables this feature of
podman-remote and podman on macOS setups.

Follow up to : #14320

Does this PR introduce a user-facing change?

Enables additional build context for podman-remote and macOS using --build-context

[openshift-ci]

@flouthoc: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: flouthoc

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 [flouthoc]

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

[openshift-ci]

@flouthoc: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

[Luap99]

How can this work? There no logic to actually copy the additional build context to the remote system.

[flouthoc]

@Luap99 Additional build context can also be other container images and url sources or git repos, so if you see uncommented tests there are still some tests commented where additional context exists on hosts while other additional build context can stilll be used by remote users where additional context is image,url or git repo.

Additional build context from host to remote is still a spike since this feature is new for both docker and buildah and they don't expose API for it as of now so tarring up and posting context from host to remote might be too early implementation hence it is still skipped for remote users.

PS: Same reason is that we should avoid listing this in swagger as of now.

[Luap99]

Additional build context can also be other container images and url sources or git repos, so if you see uncommented tests there are still some tests commented where additional context exists on hosts while other additional build context can stilll be used by remote users where additional context is image,url or git repo.

This should be documented then. The current podman-build page doesn't event mention that this was not supported via remote.

[flouthoc]

Additional build context can also be other container images and url sources or git repos, so if you see uncommented tests there are still some tests commented where additional context exists on hosts while other additional build context can stilll be used by remote users where additional context is image,url or git repo.

This should be documented then. The current podman-build page doesn't event mention that this was not supported via remote.

Yes docs needs to state this, update docs.

[TomSweeneyRedHat]

Changes as they are LGTM, but we need to update the docs before this goes.

[flouthoc]

Changes as they are LGTM, but we need to update the docs before this goes.

@TomSweeneyRedHat Already updated docs in the PR.

[TomSweeneyRedHat]

LGTM
and happy green test buttons

[rhatdan]

/lgtm