Hello,

 

I've been chasing a "why won't some docker containers update" problems for a while, and while investigating, I noticed that some updates run through Downloading, Extracting and then say Pull Complete at the end of the line.

 

Other installs, when the downloaded file is over 50 MB, never get to the Pull Complete message before the installation starts. Additionally, several files below the one currently being extracted may have also been downloaded successfully but don't appear to have been extracted (Pull Complete) before the installation starts.

 

I've had this problem on V7 and V7.01. Appdata is on the cache drive only. I've expanded the Docker image to 50GB. Rebuild Docker.img. I swapped to Google DNS (I was using Cisco Umbrella before that). Download speeds are good (I'm on fibre). Single NIC.

 

It is almost as if there is a timer that is triggering, "That is all the time you need to extract the file ... on with the update."

 

Any thoughts on how to stop this behaviour - Is this even a problem?

 

I've tried searching but haven't found the correct search phrase for this puzzle. If it is already been answered, could you point me to the correct thread?

 

Thanks for your help.

 

 

 

 

Can you post a screenshot after the docker run command completes with all the layers being pulled.   Usually I find that small layers never show Extracting or pull complete.  I suspect that what you're seeing is that the GUI "lost" the message on the large layers for some reason.  

 

But these don't sound like 0B pulls so its not a container always showing an update being available, and I don't believe that it sounds like you're having any issues after it installs the container.

 

Hi Squid,

 

Will do, as soon as the next update comes out. All my chasing about managed to get the containers into the "Unknown" status, where I could force an update. This had the same characteristic of starting before fully extracted, but as parts were missing, the install went into a longer, more rigorous download and extract routine.

 

The problem I have now is that SABNZB works but the WebUI isn't responding - but that is a different story.

 

I'll be back with the screen shots as soon as I can

Edited March 5, 20251 yr by Himself

I tried installing Firefox, which has a 703mb file as part of the installation. 

 

The screenshot shows the issue and the subsequent when the installation began, which I assume is prematurely. 

Once the install is finished I get the version Not Available issue

 

Force an update and ...

 

Can you uninstall then reinstall but don't switch the network to container:GluetunVPN. Leave it at the default bridge.  If that fixes, then the issue is somewhere in Gluetun

I added Glutun to see if I could get the error to show again after I had "fixed" everything.

 

Glutun is new and wasn't installed when I reported the issue. Everything was Bridge until this evening's (for me) installs

Edited March 5, 20251 yr by Himself

So I changed everything back to how it was, and after success updating HomeAssistant a few days ago, the recent update to BinHex Sonarr is now starting before the update has finished extracting and consequently never updates.

 

Any thoughts ... ?

 

 

So I did some more digging as more docket updates arrived.

 

Plex - Updated without any error. The largest image in the update was 103mb - Extracting took 17 seconds. 

 

Home Assistant - Largest Imahe was 366mb - Extraction rn for 84 seconds before the update started prematurely. 

 

Binhex Sonarr - Largest image was 667mb, but image being extracted was 222Mb. It ran for 83 seconds before the update started prematurely.

 

Everything is downloading; it is the extraction that is not complete before the update starts.

 

Any help is appreciated. I'm out of ideas, other than wipe everything and go back to the start, which I've all but done as I've recreated the docker environment. Next would be a new Unraid installation.

 

I have exactly the same problem for openwebui container, ollama and other containers on Unraid 7.0.0

 

IMAGE ID [main]: Pulling from open-webui/open-webui.
IMAGE ID [6e909acdb790]: Already exists.
IMAGE ID [245f048c9f8a]: Pulling fs layer. Downloading 100% of 3 MB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [b4a6013a75d1]: Pulling fs layer. Downloading 100% of 15 MB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [9eab895eb84c]: Pulling fs layer. Downloading 100% of 249 B. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [3e6bafb34603]: Pulling fs layer. Downloading 100% of 117 B. Download complete. Extracting. Pull complete.
IMAGE ID [4f4fb700ef54]: Pulling fs layer. Downloading 100% of 32 B. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [8f9277341095]: Pulling fs layer. Downloading 100% of 138 B. Download complete. Extracting. Pull complete.
IMAGE ID [67cdb545514b]: Pulling fs layer. Downloading 100% of 190 B. Verifying Checksum. Extracting. Pull complete.
IMAGE ID [5cca3004ff90]: Pulling fs layer. Downloading 100% of 325 MB. Verifying Checksum. Download complete. Extracting.
IMAGE ID [8896974b5da1]: Pulling fs layer. Download complete.
IMAGE ID [c53ed2ad177b]: Pulling fs layer. Downloading 100% of 982 MB. Verifying Checksum. Download complete.
IMAGE ID [3b7cb8865223]: Pulling fs layer. Downloading 100% of 86 MB. Verifying Checksum. Download complete.
IMAGE ID [ed37b502135e]: Pulling fs layer. Downloading 100% of 46 KB. Verifying Checksum. Download complete.
IMAGE ID [0ab4c4826c70]: Pulling fs layer. Downloading 100% of 2 KB. Verifying Checksum. Download complete.
IMAGE ID [7a39a3532647]: Pulling fs layer. Downloading 100% of 38 MB. Verifying Checksum. Download complete.

TOTAL DATA PULLED: 1 GB

 

after this is running docker run.....

  -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/open-webui/open-webui/main/static/favicon.png'
  -v '/mnt/user/appdata/ollama-webui':'/app/backend/data':'rw' 'ghcr.io/open-webui/open-webui:main'
Please wait ....

Unable to find image 'ghcr.io/open-webui/open-webui:main' locally
main: Pulling from open-webui/open-webui
6e909acdb790: Already exists
245f048c9f8a: Pulling fs layer
b4a6013a75d1: Pulling fs layer
9eab895eb84c: Pulling fs layer
3e6bafb34603: Pulling fs layer
4f4fb700ef54: Pulling fs layer
8f9277341095: Pulling fs layer
67cdb545514b: Pulling fs layer
5cca3004ff90: Pulling fs layer
3e6bafb34603: Waiting
8896974b5da1: Pulling fs layer
c53ed2ad177b: Pulling fs layer
4f4fb700ef54: Waiting
3b7cb8865223: Pulling fs layer
ed37b502135e: Pulling fs layer
67cdb545514b: Waiting
0ab4c4826c70: Pulling fs layer
8f9277341095: Waiting
7a39a3532647: Pulling fs layer
5cca3004ff90: Waiting
ed37b502135e: Waiting
3b7cb8865223: Waiting
8896974b5da1: Waiting
0ab4c4826c70: Waiting
c53ed2ad177b: Waiting
7a39a3532647: Waiting
9eab895eb84c: Verifying Checksum
9eab895eb84c: Download complete
245f048c9f8a: Verifying Checksum
245f048c9f8a: Download complete
3e6bafb34603: Download complete
b4a6013a75d1: Verifying Checksum
 

A partial work around I've found is to run Watertower to update the containers. It isn't bullet proof and it doesn't update the docker display to reflect the current version is installed, but it is updating containers in the background.

 

 

Not ideal - but something

5 hours ago, Neomatrix433 said:

I have exactly the same problem for openwebui container, ollama and other containers on Unraid 7.0.0

3 hours ago, Himself said:

Not ideal - but something

To what repository is the container set in the Docker template?

Do you have added any extra parameters to the container, please post a screenshot from your template with Advanced View enabled.

Hello Ich777,

 

This isn't limited to one container it is all of them. Lidarr is below. The pull works fine; the extraction starts, but the command to run the update begins - for some reason - before the extract is complete.

 

 

This is still happening with v7.2.3. Is there a solution?