Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#50436 - docker package should bundle specified versions of runc and containerd to ensure compatibility
Attached to Project:
Community Packages
Opened by Mike Javorski (javmorin) - Thursday, 18 August 2016, 19:01 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 19 August 2016, 13:57 GMT
Opened by Mike Javorski (javmorin) - Thursday, 18 August 2016, 19:01 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 19 August 2016, 13:57 GMT
|
DetailsThe official docker releases bundle specific (and vendored with "docker-" prefix) versions of the runc and containerd software. In order to ensure a working system and to prevent issues like FS #50430, it would be advisable to update the docker package to fetch, build and prefix the specific runc and containerd versions specific to the given docker release.
This would also allow timely releases of new docker versions as 1.12.0 is currently (I suspect) blocked by the fact that the required versions of runc and containerd haven't been officially released yet and are only available via git. The release versions of both are not compatible with docker 1.12. It could be argued that this is a flaw in the docker release process, but at this time, this is how they are operating. |
This task depends upon

Done in the latest docker version (1.12.1-1): https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/docker&id=d5b1be8cb8ac4f11e95e26e29a38679ef6cd8f98