Description of problem: This has been happening during the Cockpit integration tests for about about a week now, but we didn't get around to filing a bug here. May 03 03:47:18 localhost.localdomain dockerd-current[1241]: *** Error in `/usr/bin/dockerd-current': corrupted double-linked list: 0x00007f9d74001160 *** May 03 03:47:18 localhost.localdomain dockerd-current[1241]: ======= Backtrace: ========= May 03 03:47:18 localhost.localdomain dockerd-current[1241]: /lib64/libc.so.6(+0x7c9c4)[0x7f9d9f8199c4] May 03 03:47:18 localhost.localdomain dockerd-current[1241]: /lib64/libc.so.6(+0x881e2)[0x7f9d9f8251e2] May 03 03:47:18 localhost.localdomain dockerd-current[1241]: /lib64/libc.so.6(cfree+0x16e)[0x7f9d9f82a0ee] May 03 03:47:18 localhost.localdomain dockerd-current[1241]: /usr/bin/dockerd-current[0x468a60] May 03 03:47:18 localhost.localdomain dockerd-current[1241]: ======= Memory map: ======== Version-Release number of selected component (if applicable): docker-1.13.1-7.git14cc629.fc26.x86_64 How reproducible: Happens regularly in the Cockpit integration tests.
Created attachment 1275844 [details] Complete journal of system where failure occurs
Created attachment 1275845 [details] Core dump of dockerd-current
Cases of this are tracked upstream at: https://github.com/cockpit-project/cockpit/issues/6432
Cases of this are tracked in the Cockpit integration tests at: https://github.com/cockpit-project/cockpit/issues/6432
I think I remember we backported some patch for this error, I'll check it out.
alright: Upstream issue: https://github.com/moby/moby/issues/30433 Patches for 1.13.1: https://github.com/moby/moby/pull/31263 and https://github.com/moby/moby/pull/31231 Though, we did backport https://github.com/projectatomic/docker/pull/228 but apparently that's not enough, I'll fix the 1.13.1 branches asap
Nalin, could you look into backporting to docker-1.13.1 (and docker-1.13.1-rhel) the following PRs: - https://github.com/moby/moby/pull/31263/commits/d57c330617efb97cad736a3e4ede82bb46ebbbf2 - https://github.com/moby/moby/pull/31231/commits/81630df85439adab1836e83a7e645d67b1c0eb83 Sounds like we also need to revert 636e19c1c888edabd4f78a813d7075b7a194f34e in projectatomic/docker#docker-1.13.1 first.
I think we still need 636e19c1c888edabd4f78a813d7075b7a194f34e to add a fix to 636e19c1c888edabd4f78a813d7075b7a194f34e. Opened https://github.com/projectatomic/docker/pull/244 and https://github.com/projectatomic/docker/pull/245 with the backported patches (the first applies cleanly, the second needed a couple of whitespace changes).
merged both patches
This should be fixed in docker-1.13.1-13.git51eb16e.fc26 and later, which should contain the backported fixes.
The Cockpit integration tests indicate this has not occurred on an up to date version of Fedora 26 for the last 26 days. https://github.com/cockpit-project/cockpit/pull/7301
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.