Hello [email protected], or anyone else affected, Accepted runc into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/0.1.1-0ubuntu5~16.04 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: runc (Ubuntu) Importance: Undecided Status: New ** Changed in: runc (Ubuntu) Status: New => Fix Released ** Changed in: runc (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1574904 Title: Old clients cannot talk to Docker in 16.04 Status in docker.io package in Ubuntu: Fix Released Status in runc package in Ubuntu: Fix Released Status in docker.io source package in Xenial: Fix Committed Status in runc source package in Xenial: Fix Committed Bug description: [impact] The docker.io 1.10.3 packaged in Ubuntu 16.04 was compiled with Go[lang] 1.6.1. Go 1.6.x contains a change to how the HTTP "Host" header is parsed, and using this to compile Docker has the effect of breaking the ability for any older version of the Docker client to talk to the daemon. It is proposed to fix this by uploading a new version of docker, which has been agreed to as an exception to the usual process by ~tech-board (although possibly this has not been documented anywhere yet). This also means updating the runc and containerd packages. [test case] Simply run: $ docker run -it -v /var/run/docker.sock:/var/run/docker.sock --rm docker:1.9 version it will fail with a problematic version installed and succeed with a fixed version installed. [regression potential] Obviously there is a risk of regressions here. But it is Ubuntu policy to offer an "upstream experience" with docker and not try to shield our users from that. The docker.io package in yakkety contains an autopkgtest that tests (very!) basic functionality, so we know the packages are not completely broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1574904/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : [email protected] Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
