[v4.5] libpod: use new libcontainer BlockIO constructors

[haircommander]

[NO NEW TESTS NEEDED]

Does this PR introduce a user-facing change?

none

[haircommander]

PTAL @vrothberg @mheon @Luap99 @lsm5

[mheon]

LGTM

[lsm5]

@haircommander remind me why the cherrypick to this branch. Is it for rhel ?

[lsm5]

we can ignore packit failures for now, and maybe only do centos builds for rhel branches

[lsm5]

hit the wrong button, my bad.

[haircommander]

CRI-O will eventually vendor this commit, no need for a packaged version or even a tag.

[lsm5]

/lgtm
/hold

[Luap99]

/approve
/hold cancel

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: haircommander, Luap99

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

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

[openshift-cherrypick-robot]

@saschagrunert: new pull request could not be created: failed to create pull request against containers/podman#v4.6 from head openshift-cherrypick-robot:cherry-pick-19136-to-v4.6: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between containers:v4.6 and openshift-cherrypick-robot:cherry-pick-19136-to-v4.6"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"}

Details

In response to this:

/cherry-pick v4.6

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.

[vrothberg]

We would need this for 4.6 / main as well, right?

They're already in both branches. We should only backport after things are in main.

[saschagrunert]

Found the issue: v4.6.0-rc1 does not have the change in yet, so we wait for another RC or the final version. :)

[lsm5]

rc2 should be going out today