-
Notifications
You must be signed in to change notification settings - Fork 18.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
vendor: bump libcontainer and its deps #18106
Conversation
#17211 updated
|
created moby/libnetwork#765 to address the above comment and fix the compilation issue here |
/cc @tianon (I'll use v0.0.5 here if tag gets pushed to runc) |
Wooot, "v0.0.5" now available! 😄 ❤️
|
8bb2472
to
b35a70a
Compare
updated! though this still needs libnetwork changes before being merged :( |
b35a70a
to
92a8bb5
Compare
6a7a66d
to
9989c7f
Compare
🤘 👍 LGTM |
I'll wait for CI :D |
oh noes, cross-compile failed lol |
opened moby/libnetwork#770 which addresses failures in cross compilation |
9989c7f
to
70ba302
Compare
\o/ green! |
bump runc/libcontainer to v0.0.5 bump runc deps to latest bump docker/libnetwork to 04cc1fa0a89f8c407b7be8cab883d4b17531ea7d Signed-off-by: Antonio Murdaca <runcom@redhat.com>
70ba302
to
65900d7
Compare
LGTM |
vendor: bump libcontainer and its deps
@tiborvass I added this to the 1.9.2 milestone for consideration, because it fixes #18145 and #18169. however I see this PR not only updates libnetwork, but also libcontainer, and I'm not sure (if a 1.9.2 release is released) we want both in a patch release... |
@thaJeztah @tiborvass Please, add this to a 1.9.2 :( |
@sitamet we most likely won't be releasing 1.9.2; but this will be in docker 1.10; code freeze is this Thursday - scheduled for release February 4th |
@thaJeztah ok ... lets go forward then :S |
Pulls latest libcontainer code and updates its deps (and libnetwork)
Signed-off-by: Antonio Murdaca runcom@redhat.com
Fixes #18535