-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Avoid disk usage explosion when copying busybox #1629
Avoid disk usage explosion when copying busybox #1629
Conversation
1 similar comment
@crosbymichael hmm travis hadnt run here yet. Wait for it before merging |
Not sure why travis is not running, I tried reopening to bump it but nothing. Humm... |
According to https://travis-ci.org/opencontainers/runc/requests, "Abuse detected" 😕 |
@tianon This happened recently to a PR made to containers/image. An email to travis support and they were able to remove this "abuse" marker. I can email them in a few hours when I'm home. |
👍 |
@crosbymichael could you try opening and closing again please? I've contacted Travis and they've marked our org as not abusive :) |
When running runc tests with temp directory with size 500M copying busybox without preserving hardlinks causes the folder to inflate to roughly 330M. Copying busybox twice in certain tests causes the /tmp directory to overfill. Using `-a` preserves links which busybox uses to implement its choice of binary to run. Signed-off-by: Tom Godkin <tgodkin@pivotal.io>
a403e9e
to
fdbb9e3
Compare
@dqminh @crosbymichael We've force pushed an empty commit to re-trigger Travis and it's gone green :) Looks like the "LGTM"s have reset as a side effect. |
When running runc tests with temp directory with size 500M, copying
busybox without preserving hardlinks causes the folder to inflate to
roughly 330M. Copying busybox twice in certain tests causes the /tmp
directory to overfill. Using
-a
preserves links which busybox uses toimplement its choice of binary to run.
Signed-off-by: Tom Godkin tgodkin@pivotal.io