-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Vendor in lots of kubernetes stuff to shrink image size #554
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
Conversation
|
+300,000 -700,000... One of the biggest single-patch diffs I've ever seen. LGTM pending tests. |
|
Looks like build errors - might need a higher version of golang.org/x/crypto? |
ca44ecf to
7c869cc
Compare
|
bot, retest this please |
Signed-off-by: Daniel J Walsh <[email protected]>
|
Travis failure looks like a flake. LGTM |
|
i kicked travis, it passed |
|
Alright, tests are green, going to merge |
|
📌 Commit 93013d8 has been approved by |
|
⌛ Testing commit 93013d8 with merge c0ca436... |
|
💔 Test failed - status-papr |
|
sig-proxy failed, probably a flake |
|
⌛ Testing commit 93013d8 with merge d4b3903... |
|
💔 Test failed - status-papr |
|
@rh-atomic-bot retry |
|
☀️ Test successful - status-papr |
This directory just had Markdown and vendor.conf. I'm not sure why we have it in our version control, maybe old versions of vndr kept it? Or maybe folk dropped it into vendor/ by hand without using vndr? The history of that vendored directory is: * 619637a (Handle Linux Capabilities from command line, 2017-11-03, containers#17) added the three files to our version control. * c344fe6 (Update vendoring, 2017-11-22, containers#60) bumped hack/README.md. * af64e10 (Vendor in lots of kubernetes stuff to shrink image size, 2018-03-26, containers#554) bumped hack/README.md. * 27107fd (Vendor in latest containers/image and contaners/storage, 2018-04-18, containers#509) removed the files. * a824186 (Use buildah commit and bud in podman, 2018-04-25, containers#681) added the files back. * I'm removing them again in this commit. With this commit, $ vndr github.com/docker/docker becomes a no-op. Signed-off-by: W. Trevor King <[email protected]>
This directory just had Markdown and vendor.conf. I'm not sure why we have it in our version control, maybe old versions of vndr kept it? Or maybe folk dropped it into vendor/ by hand without using vndr? The history of that vendored directory is: * 619637a (Handle Linux Capabilities from command line, 2017-11-03, #17) added the three files to our version control. * c344fe6 (Update vendoring, 2017-11-22, #60) bumped hack/README.md. * af64e10 (Vendor in lots of kubernetes stuff to shrink image size, 2018-03-26, #554) bumped hack/README.md. * 27107fd (Vendor in latest containers/image and contaners/storage, 2018-04-18, #509) removed the files. * a824186 (Use buildah commit and bud in podman, 2018-04-25, #681) added the files back. * I'm removing them again in this commit. With this commit, $ vndr github.com/docker/docker becomes a no-op. Signed-off-by: W. Trevor King <[email protected]> Closes: #752 Approved by: baude
Signed-off-by: Daniel J Walsh [email protected]