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#52968 - [containerd] Please add 'i686' to architecture list
Attached to Project:
Community Packages
Opened by Dmitry V. Luciv (dluciv) - Tuesday, 14 February 2017, 21:51 GMT
Last edited by Sébastien Luttringer (seblu) - Monday, 20 February 2017, 23:20 GMT
Opened by Dmitry V. Luciv (dluciv) - Tuesday, 14 February 2017, 21:51 GMT
Last edited by Sébastien Luttringer (seblu) - Monday, 20 February 2017, 23:20 GMT
|
DetailsDescription:
Although Arch i686 support will be dropped soon, there is still some i686 hardware that even runs Docker. Some time ago I posted similar case for docker package: after just adding 'i686' to architectures list in PKGBUILD it works pretty well on my super duper Lenovo S9 with Atom N270. It was not a surprise for me that the same trick could be applied to containerd successfully. So please just change architecture list to: arch=('x86_64' 'i686') Let's allow old hardware to take as deep last breath as possible! =) |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Monday, 20 February 2017, 23:20 GMT
Reason for closing: Implemented
Additional comments about closing: 0.25-2
Monday, 20 February 2017, 23:20 GMT
Reason for closing: Implemented
Additional comments about closing: 0.25-2
Comment by Sébastien Luttringer (seblu) -
Monday, 20 February 2017, 23:10 GMT
that requires runc to be i686 too...