September 18, 20241 yr Have a resolution...in part. After posting and reading some comments I started wondering if something got messed up a few months ago when I replaced a single drive in my two-drive zfs cache pool. Going with that I replaced both drives, removed the cache, re-created it and got everything back in place. Now, it seems as though the updates are completing as they should, however, the problem I am still having is that the first container (or array, if I shut it down) takes an extremely long time to complete...this is where the delays in updating are occurring. Subsequent containers don't seem to take as long, always the first. Is there anything or anywhere to check and see why it would take such a long time to shut a container down?
September 18, 20241 yr Community Expert 34 minutes ago, CountryBoy_71 said: why it would take such a long time to shut a container down? I assume there's nothing out of the ordinary logged?
September 18, 20241 yr 6 minutes ago, JorgeB said: I assume there's nothing out of the ordinary logged? nothing at all logged during the update process.
January 3, 20251 yr Did this ever get solved? I have the same problem. Is the timeout update the recommended solution?
February 2, 20251 yr Reformatting the appdata drive should do it. Since then i never had an issue again😅 Before that, make sure you backup your appdata!.
February 20, 20251 yr I didn't follow the whole thread but I found a solution for my problem. Essentially like others, I would click to update my container and the pull/extract process of the docker image would timeout. Hopefully this helps out someone having similar issues. How I fixed this... 1. Open Unraid terminal as the 'root' user. 2. Run the following commands... a. I like to verify the image is in my local repository. It's also easier to copy/paste the repository name docker image ls b. Manually update the container, replace with the actual repository name from above docker pull repository_name Note: Because my image was pretty big (2 GB at this point), it took 5+ minutes for it to update in the terminal 3. Go back to Unraid GUI > Docker > Click to update container 4. Update should be quick, because we already pulled/updated the image to the latest version 5. Now says "up to date". Profit Edited February 20, 20251 yr by tacojutsu missing part of the example command
February 20, 20251 yr I moved my docker folder back to my cache disk and that appears to have fixed the issue as everything is much faster. Not surprising but frustrating.
February 21, 20251 yr 21 hours ago, tacojutsu said: I didn't follow the whole thread but I found a solution for my problem. Essentially like others, I would click to update my container and the pull/extract process of the docker image would timeout. Hopefully this helps out someone having similar issues. How I fixed this... 1. Open Unraid terminal as the 'root' user. 2. Run the following commands... a. I like to verify the image is in my local repository. It's also easier to copy/paste the repository name docker image ls b. Manually update the container, replace with the actual repository name from above docker pull repository_name Note: Because my image was pretty big (2 GB at this point), it took 5+ minutes for it to update in the terminal 3. Go back to Unraid GUI > Docker > Click to update container 4. Update should be quick, because we already pulled/updated the image to the latest version 5. Now says "up to date". Profit This is what I have been doing and it works without fail. Thank you for the good write up Taco! A feature I would love to see is if we could have a UI piece to pull the new image without a timeout. Anything that has a CUDA component to it in my set up takes 5+ minutes to download and extract.
April 24, 20251 yr On 2/20/2025 at 1:46 PM, tacojutsu said: I didn't follow the whole thread but I found a solution for my problem. Essentially like others, I would click to update my container and the pull/extract process of the docker image would timeout. Hopefully this helps out someone having similar issues. How I fixed this... 1. Open Unraid terminal as the 'root' user. 2. Run the following commands... a. I like to verify the image is in my local repository. It's also easier to copy/paste the repository name docker image ls b. Manually update the container, replace with the actual repository name from above docker pull repository_name Note: Because my image was pretty big (2 GB at this point), it took 5+ minutes for it to update in the terminal 3. Go back to Unraid GUI > Docker > Click to update container 4. Update should be quick, because we already pulled/updated the image to the latest version 5. Now says "up to date". Profit I'll second that this is the answer to this issue. Works every time.
November 9, 2025Nov 9 So in theory setting the Docker Stop Timeout should also work perhaps (but also not ideal as that can cause issues during shutdowns). I had mine set to 360 seconds, but it still wasn't enough for home assistant to update.I guess I'll put the terminal commands into a user script and kick that off before the next update for now. It's too bad the system isn't smart enough to be a bit more generous with the time allowances during an update...
December 3, 2025Dec 3 I just started running into this in the past few weeks. Certain docker updates that include pulls of >200MB for a section fail. I also could not complete the download of the 7.2.2 update as it also repeatedly failed during the download. The percent completed on the download varies somewhat - never at the same point. I had to do a manual update for the 7.2.2 and manual pulls for the dockers that have larger file segments. Even then the docker pull command struggles.I can't help thinking that this is not an issue with my network and/or server? Everything else runs fine and have no issue with file transmission and my server is connected through 10GPS SFP+ to my router.Of course I am open to suggestions as there may be something configured incorrectly here. But why did it just start doing this? Edited December 3, 2025Dec 3 by The Transplant
December 3, 2025Dec 3 2 hours ago, The Transplant said:I just started running into this in the past few weeks. Certain docker updates that include pulls of >200MB for a section fail. I also could not complete the download of the 7.2.2 update as it also repeatedly failed during the download. The percent completed on the download varies somewhat - never at the same point. I had to do a manual update for the 7.2.2 and manual pulls for the dockers that have larger file segments. Even then the docker pull command struggles.I can't help thinking that this is not an issue with my network and/or server? Everything else runs fine and have no issue with file transmission and my server is connected through 10GPS SFP+ to my router.Of course I am open to suggestions as there may be something configured incorrectly here. But why did it just start doing this?Just out of curiosity I went to another machine on my network running docker. I ran the docker pull on this (Windows PC) and it worked each time. It is in the rack next to my unraid server. This seems to point to having an issue running these commands on unraid only but not sure if that proves anything?
December 19, 2025Dec 19 This is now a repeating issue for me. Ollama and Immich both have large files in them and my server fails downloading them with every update.
February 7Feb 7 I too have started to use "docker pull repository_name" for Immich and frigate (Thanks tacojutsu). Looking at the forums and reddit, this seems this has been an ongoing problem in verson 6 and 7, that has never been truly solved. People try changing DNS, change the docker timeout, move the docker image from cache to array, or array to cache, and then it works sometimes, I don't think any of those solutions, are solutions, and they just appear to work, randomly, but not repeatable because of the several times the user re-runs update. I too think it has something to do with dockers that have large files that have to be downloaded.Looking at all the different threads, there is no true fix...Please fix..
February 14Feb 14 On 2/20/2025 at 7:46 PM, tacojutsu said:I didn't follow the whole thread but I found a solution for my problem. Essentially like others, I would click to update my container and the pull/extract process of the docker image would timeout. Hopefully this helps out someone having similar issues. How I fixed this... 1. Open Unraid terminal as the 'root' user.2. Run the following commands... a. I like to verify the image is in my local repository. It's also easier to copy/paste the repository namedocker image ls b. Manually update the container, replace with the actual repository name from abovedocker pull repository_name Note: Because my image was pretty big (2 GB at this point), it took 5+ minutes for it to update in the terminal3. Go back to Unraid GUI > Docker > Click to update container4. Update should be quick, because we already pulled/updated the image to the latest version5. Now says "up to date". ProfitI confirm this is the way while waiting for a fix.
May 13May 13 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 - SUCCESSMySQL: 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 Edited May 13May 13 by aziemer Update
.thumb.jpg.dcd55e454d1da02c38e7706786a27d11.jpg)
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.