image: Switch to oci-chunked format

[cgwalters]

Now that we have rpm-ostree v2022.2 in the bootimage, we should
be able to switch to the chunked image format.

This matches coreos/fedora-coreos-config#1698

[travier]

Should we hold on this one until master is 4.12?

[travier]

Hum, looks like this is already the case: https://github.com/openshift/os/tree/release-4.11

[cgwalters]

Should we hold on this one until master is 4.12?

Yeah, I guess we might as well.

[cgwalters]

error: build error: error committing container for step {Env:[BUILD_LOGLEVEL=0 OPENSHIFT_BUILD_NAME=machine-os-oci-content OPENSHIFT_BUILD_NAMESPACE=ci-op-ithpf5wd PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin] Command:label Args:[io.openshift.build.name machine-os-oci-content io.openshift.build.namespace ci-op-ithpf5wd io.openshift.build.commit.author  io.openshift.build.commit.date  io.openshift.build.commit.id  io.openshift.build.commit.message  io.openshift.build.commit.ref  io.openshift.build.name  io.openshift.build.namespace  io.openshift.build.source-context-dir  io.openshift.build.source-location  vcs-ref  vcs-type  vcs-url ] Flags:[] Attrs:map[] Message:LABEL "io.openshift.build.name" "machine-os-oci-content" "io.openshift.build.namespace" "ci-op-ithpf5wd" "io.openshift.build.commit.author" "" "io.openshift.build.commit.date" "" "io.openshift.build.commit.id" "" "io.openshift.build.commit.message" "" "io.openshift.build.commit.ref" "" "io.openshift.build.name" "" "io.openshift.build.namespace" "" "io.openshift.build.source-context-dir" "" "io.openshift.build.source-location" "" "vcs-ref" "" "vcs-type" "" "vcs-url" "" Original:LABEL "io.openshift.build.name"="machine-os-oci-content" "io.openshift.build.namespace"="ci-op-ithpf5wd" "io.openshift.build.commit.author"="" "io.openshift.build.commit.date"="" "io.openshift.build.commit.id"="" "io.openshift.build.commit.message"="" "io.openshift.build.commit.ref"="" "io.openshift.build.name"="" "io.openshift.build.namespace"="" "io.openshift.build.source-context-dir"="" "io.openshift.build.source-location"="" "vcs-ref"="" "vcs-type"="" "vcs-url"=""}: error copying layers and metadata for container "2195c35d8189e1727e77673dd23bdf130685d7039b29eeab6d4db3d6845bc8c9": initializing source containers-storage:latest-working-container: error creating new image source "containers-storage:latest-working-container": error extracting layer "de4146265712a44c5438a282204ab7fe821bcb03f5206abbf357540b170949bd": cannot mount layer, mount label "" too large 4168 > page size 4096

😢

This is ostreedev/ostree-rs-ext#69 (comment)

• rpm-ostree container-encapsulate clearly needs to make the number of layers configurable
• We're really close to the limit...would it work if we just cut down one layer? Will test
• Probably worth seeing if there's a way we can optimize the mount layer option handling; must it really be a single page? What if overlayfs supported parsing data from...a sealed memfd or something? Or just parsed a file on disk, since it already is reading from the filesystem

[cgwalters]

coreos/coreos-assembler#2913

[cgwalters]

OK this also blocks on https://bugzilla.redhat.com/show_bug.cgi?id=2095528 at least.

[openshift-ci]

@cgwalters: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/test-in-cluster	8b359ed	link	true	/test test-in-cluster
ci/prow/validate-built-image	8b359ed	link	true	/test validate-built-image
ci/prow/build-test-qemu-kola-all	8b359ed	link	true	/test build-test-qemu-kola-all

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[cgwalters]

OK rebased 🏄 - I'd like to try landing this again!

[jlebon]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cgwalters, jlebon

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 [cgwalters,jlebon]

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