aziemer

For the last months (years?) I tried all possibilities known to me, to solve this problem. Nothing helped. So I took another round on this today and tried to keep my brain turned on while doing so. As the most promising way mentioned in this thread was the "docker stop timeout" way, I was wondering why this was initially set to 20 (at least on my system - others had 10 - perhaps I set it to this value myself in the past). I thought what might happen when I set it even higher. Lo and behold, after setting it to 600 (10 minutes) my home bridge and music-assistant dockers - which before permanently refused to complete the extraction phase - updated till the end!! So, perhaps this timeout not only controls the timeout when STOPPING a container, but also when UPDATING it. I now have set it to 900, just to be sure... UPDATE: The success above seems to have been by chance... Just ran an update session containing NextCloud AIO, MySQL and HomeBridge. Results: NextCloud: 18 files, 94MB pulled, largest file 25MB - SUCCESS MySQL: 10 files, 261MB pulled, largest file 155MB - FAILURE on the 2nd last file, the largest one... HomeBridge: 8 files, 371MB pulled, largest file 254MB - SUCCESS (the 254MB file was the first in the list, so had been extracted first) So I am as wise as before... At least, it worked for 66% of the update 😎 I have no idea why it seems to be so hard to find the correct timer resp. timeout setting to end this mess. Andreas