fix remote build isolation on client side

[Luap99]

Follow up to 493179b which only fixed the issue on the server despite me trying to fix it on the client as well, with this change here we always correctly unset the default on the remote client as the root/rootless status will be wrong.

This means it is enough for users to either have a new server or client with the bug fix which should make the update process easier.

Does this PR introduce a user-facing change?

None

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99

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

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

[mheon]

LGTM

[cdrage]

Follow up to 493179b which only fixed the issue on the server despite me trying to fix it on the client as well, with this change here we always correctly unset the default on the remote client as the root/rootless status will be wrong.

This means it is enough for users to either have a new server or client with the bug fix which should make the update process easier.

Does this PR introduce a user-facing change?

None

Thank you so much for the follow up!

This works now and has solved my issue (podman client building against podman machine rootful on v5.0.0) 🚀 🚀 🚀

[cdrage]

I'm assuming backported as well?

[Luap99]

I'm assuming backported as well?

yes we should do that

/cherry-pick v5.0

[openshift-cherrypick-robot]

@Luap99: once the present PR merges, I will cherry-pick it on top of v5.0 in a new PR and assign it to you.

In response to this:

I'm assuming backported as well?

yes we should do that

/cherry-pick v5.0

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.

[baude]

/lgtm

[openshift-cherrypick-robot]

@Luap99: new pull request created: #22143

In response to this:

I'm assuming backported as well?

yes we should do that

/cherry-pick v5.0

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.