vendor of containers/(common, storage, image)

[rhatdan]

Does this PR introduce a user-facing change?

None

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhatdan

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

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

[rhatdan]

Preparing for release.

[ashley-cui]

LGTM, but before the RC is cut we probably need released versions of common, storage, image.

[rhatdan]

Not before RC, but before final.

[ashley-cui]

I think in our release process doc we said that RC's were intended to be fully stable and ready for release, which means we probably want a versioned common, storage, image. In any case, we can do another dance on the branch when it's cut.

[rhatdan]

Sure, the problem with that is it does not allow for bug fixes in any level without requiring a complete vendor dance. I have no problem doing it, but I don't believe we have dones this in the past.

[mheon]

We really need to go over the release doc again and finalize it to have a solid answer here, but the goal was to make RCs more stable - IIRC, so we would be comfortable if one somehow ended up in Fedora Stable.

[mheon]

That being said, I have no objections about merging this now and figuring out details later, we have a few days.

[mheon]

Adding bloat label

* bin/podman grew by 65544 bytes; max allowed is 51200.
*
* Please investigate, and fix if possible.
*
* A repo admin can override by setting the bloat_approved label

[rhatdan]

I think the bloat is all in the Windows code paths. But does that affect the size of the linux app or the Mac Client?