fix checking of relative idmapped mount

[karuboniru]

Like stated in PR for crun

that HostID is what being mapped here, so we should be checking HostID instead of ContainerID. v.ContainerID here is the id of owner of files on filesystem, that can be totally unrelated to the uid maps.

Does this PR introduce a user-facing change?

Yes, but this should make more sense?

Relative id mapped mount will check which segment of uidmap to use based on host id instead of filesystem id.

[rhatdan]

@giuseppe PTAL

@karuboniru You either need to add a test or add the [ no new tests needed ] flag to your description.

[karuboniru]

@rhatdan I added a test and it seems the pipeline did not raise a red flag so it should be fine I guess? (the failures are related to cockpit-podman which I think it is unrelated here)

[giuseppe]

LGTM

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: giuseppe, karuboniru

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

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

[github-actions]

A friendly reminder that this PR had no activity for 30 days.

[karuboniru]

Is there anything missing or we are just waiting for something else?

[giuseppe]

@rhatdan fine to merge?

[rhatdan]

/lgtm