I recently upgraded my hardware and noticed this happening. When I go to update a docker app it goes through pulling all the fs layers. Some larger layers, 200+ MBs, start extracting then stop. The system skips to restarting the docker app without having extracted the rest of the layers. As a result, I have apps that always have updates available. I only noticed this when I migrated to the newer hardware.

 

tower-diagnostics-20240706-1635.zip

This has been happening to some users for some time, unfortunately it's difficult to reproduce, can you detail what changed in the hardware? Also have you tried recreating the docker image?

Hi JorgeB,

 

I went from an 11 year old Xeon, 1x8GBs of DDR3 ECC RAM, and Tyan S5512 MB to an Intel i3 10100, Gigabyte Z490 Gaming X MB, 2x16GB DDR4, and a LSI HBA.

 

I am trying recreating the docker image, but the issue also happened when installing a new app. It started doing the extraction and stopped, skipped to starting the app, but realized it didn't have the full image. Then started downloading the images again and eventually completed successfully.

 

Edit: The recreation is doing the same as the new app install did.

 

Edited July 7, 20242 yr by rocketcoder

Is the docker image on SSD storage?

I'm honestly not sure. I have two SSDs as cache drives. Everything else is HDD.

I cannot see in the diags where the image is, but according to them, the system share also exists on disk1:

 

# Share exists on cache, disk1

 

Disable the VM and Docker services and move everything to the pool, then retest