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#56249 - [lxc] Please include a 2.1.1-pre patch to keep lxc-copy from coredumping
Attached to Project:
Community Packages
Opened by John (graysky) - Sunday, 05 November 2017, 19:23 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 09 November 2017, 13:10 GMT
Opened by John (graysky) - Sunday, 05 November 2017, 19:23 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 09 November 2017, 13:10 GMT
|
DetailsA known (and fixed) upstream bug affects lxc-1:2.1.0-2 currently in [community]. The bug is triggered when a user attempts to use lxc-copy which ends in a coredump.
Link to upstream bug report: https://github.com/lxc/lxc/issues/1802 Link to upstream patch teed up for 2.1.1 (no timeline to release per my knowledge): https://github.com/lxc/lxc/commit/3874902c63de007c5f9a8dcb0fcbddc5560266bf Patched PKGBUILD incorporating the patch which I have verified works is attached. Steps to reproduce: Using lxc-1:2.1.0-2 run `lxc-copy -n base -N clone1 -B overlayfs -s` This results in the core dump: *** Error in `lxc-copy': corrupted size vs. prev_size: 0x01ca0aa8 *** [1] 4993 abort sudo lxc-copy -n base -N pitime3 -B overlayfs -s 
update_lxc.patch
(1.3 KiB)
|
This task depends upon
Closed by Sergej Pupykin (sergej)
Thursday, 09 November 2017, 13:10 GMT
Reason for closing: Fixed
Additional comments about closing: 2.1.1 already in repo
Thursday, 09 November 2017, 13:10 GMT
Reason for closing: Fixed
Additional comments about closing: 2.1.1 already in repo
Comment by John (graysky) -
Sunday, 05 November 2017, 19:33 GMT
Headsmack... our package is out-of-date since 2.1.1 proper was released which incorporates this patch. I built it and am no longer experiencing this issue. Safe to close; sorry for the noise.