Vivek or lokesh, didn't we fix this by extending the amount of time the docker.service is allowed to run before systemd kills it?
We changed the time to 60 seconds. Then it was pointed out later that default is 90 seconds and instead we ended up reducing the timeout. So now we are planning to keep timeout at 120 seconds and hopefully that will solve some of the issues. Lokesh, have you already made the changes for 120 second timeout?
Any reason to not change this to 5 minutes?
Well, you can if you like to. 5 minutes sounds like a pretty long time. I was hoping we can do this incrementally depending on 2 minute works or not. But if you want to go higher then 2 mins, that's fine.
Well 5 minutes is the max, not the min. In almost all cases this timeout will not hit.
We have another bugzilla where we are suggesting we set this to infinite. Lokesh you can probably close this as a duplicate of that bug.
We should extend the timeout to infinity. Since docker-1.10 is introducing a rewrite of all containers on update.
Fixed in docker-1.9
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.