On 03/15/2018 08:33 PM, Shengjing Zhu wrote:
On Thu, Mar 15, 2018 at 5:22 PM, Arnaud Rebillout
<[email protected]> wrote:
So I could re-package containerd to an older version. But if I do this
choice, I basically admit that Docker decides of the version of all its
dependencies, possibly holding back all of them. What if someone needs a
pretty recent version of containerd (or any other Docker dependency), and we
can't deliver that because we're waiting for Docker to bump the version it
vendors, and we have no idea when it will happen ?
The docker maintainers have already packaged docker-containerd, and docker-runc.
see #877146 for reasons why this happened.
Thanks for the link, that helps ! I kind of forgot that there is a
separate 'docker-runc' and 'docker-containerd' package. I could make
good use of that, until docker catches up with containerd.
_______________________________________________
Pkg-go-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
