Related issues: https://github.com/containers/buildah/issues/1213
Seen in https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-4.4/1005 https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_installer/2932/pull-ci-openshift-installer-master-e2e-libvirt/3563
Per [1], I don't think restoring MEMORYSWAP settings will happen any time soon. My understanding is that this feature made sense when we used Docker, but is obsolete since we've moved to use buildah: > The OpenShift builder uses buildah's chroot isolation, which doesn't implement setting control group settings. > > Because the builder is run in a container, and the we can count on that container having its memory.limit_in_bytes limit set on its behalf by the runtime (CRI-O), so we don't have to do anything for that limit, and a couple of others. @Cesar the issues you reported seem unrelated to this BZ - tests are failing because the binary source is timing out uploading to the build pod. [1] https://github.com/containers/buildah/issues/1213#issuecomment-571277448