-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: Drop down to 50 layers for chunked images #2913
Conversation
xref openshift/os#808 |
/override ci/prow/rhcos |
@cgwalters: Overrode contexts on behalf of cgwalters: ci/prow/rhcos In response to this:
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. |
2c3a15a
to
cb21434
Compare
src/cmdlib.sh
Outdated
# for (older?) versions of podman AKA containers/storage (or maybe) | ||
# a kernel limitation? For example | ||
# `cannot mount layer, mount label "" too large 4168 > page size 4096` | ||
MAX_OSTREECONTAINER_LAYERS=50 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In src/cmdlib.sh line 43:
MAX_OSTREECONTAINER_LAYERS=50
^------------------------^ SC2034: MAX_OSTREECONTAINER_LAYERS appears unused. Verify use (or export if used externally).
It seems that (at least older?) containers/storage barfs on this, so let's drop down a good bit. (We could also change the ostree upstream default, but...mmm, perhaps later)
cb21434
to
c973251
Compare
/override ci/prow/rhcos |
@cgwalters: Overrode contexts on behalf of cgwalters: ci/prow/rhcos In response to this:
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. |
It seems that (at least older?) containers/storage barfs on this, so let's drop
down a good bit.
(We could also change the ostree upstream default, but...mmm, perhaps
later)