Pulling a new docker container hoses my system | Version 6.12.8 2024-02-15

[tiny-e]

What I was able to observe:  

• Tried to install a new container (beets, 100ish MB) 
• Container downloaded quickly (gigabit connection) 
• 10 minutes passed to get to this: 
• A few minutes later, it finally finished.   During all of this, my server webui was super unresponsive.   It's been happening a lot lately, I'm wondering if it's anything to do with recent Unraid OS updates (as I don't remember this issue before them, but that is pretty subjective)
• The container shows up in the gui as not knowing if it's up to date or not.  If I force update it, it then figures it out.  Force update happens pretty quickly as (I'm guessing) all downloaded/extracted items are cached. 

 

Diagnostic logs attached.   I'm kinda at a loss here. 

 

nimbus-diagnostics-20240316-1046.zip

Edited March 16 by tiny-e

[strike]

I'm seeing this as well since updating to 6.12.8. Looks like at least some of my containers are considerably more slow/unresponsive as well. And like you the unraid webui is unresponsive whenever updating a container and takes longer time then usual.

[tiny-e]

Yeah, I'm not sure what's going on.

[tiny-e]

Nearly a month goes by....   The behavior still exists.  As my system is unresponsive as I try to pull a docker container now... 

 

[Kilrah]

Check your Docker image is really on an SSD.

[tiny-e]

Thanks for the reply -- It is:

...

 

You know, the cache was originally part of a ZFS pool, and one drive died and I've yet to replace it.   Could that be the issue?   If so, can I un-pool the cache temporarily until I have a replacement in place? 

Edited April 5 by tiny-e

[Kilrah]

Wouldn't know. Is the cache working as expected otherwise?

Also it seems you're using an XFS Docker image, can't make use of the features of the default btrfs, might be contributing. Was there a specific reason to change the default?