I updated from 7.2.2 to 7.2.3 today. First, the update wasn't smooth, as my server froze when rebooting. I was able to see that it was stuck in the loading screen where you can enter the bios. After shutting off and turning back on, I was able to see Unraid going through the rest of the update. The server booted back up, but now I have Dockers not starting, giving "Execution Error". Wanting to post this in case there's something going on with the update. It of course could be my issue. I also have no clue what to do here. I did a scrub, with no errors (not sure if this even helps).

I had a docker I didn't regularly use do this before, I just waited and it corrected itself. However, I don't want to wait for these Dockers since they're Emby and Plex, which gets used regularly. Any next steps would be appreciated.

Posted diagnostics.

gamingnas-diagnostics-20251222-1233.zip

AFAIK, nothing changed in Docker 7.2.2 vs 7.2.3, so the issue is most likely because of the reboot, not the upgrade.

I'm not seeing any obvious errors, but try recreating the Docker image

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-file

Then:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applications

Also see below if you have any custom docker networks:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks

I do see Btrfs detecting some data corruption on the pool; I recommend Memtest, then scrubbing the pool

I deleted the vDisk and created a new one. Went to add the Dockers and most ran successfully, but some didn't. I noticed that it has something to do with Nvidia. I copied some of log for the Emby docker below. But each docker that uses the video card fails their docker build.

docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running prestart hook #0: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: initialization error: nvml error: driver not loaded: unknown.

The command failed.

So I'm guessing this is an Nvidia driver issue now.

I checked and I have the lastest driver.

gamingnas-diagnostics-20251222-1403.zip

Just to update, I edit my Emby docker and got rid of the extra parameters "--runtime=Nvidia" and the docker runs fine. I got to put the extra parameter back and it fails again. Now I'm trying to figure out what causes this to happen. Hoping it's not having to wait for another driver update.

I had to install the production branch driver, which is 580 vs 590. Doesn't look like my card will be supported in future.

Edited December 22, 2025Dec 22 by kjclark23

On 12/22/2025 at 4:26 PM, kjclark23 said:

I had to install the production branch driver, which is 580 vs 590. Doesn't look like my card will be supported in future.

This was the solution for me as well. It would appear that gtx 10 series will require 580 drivers going forward. 😞

On 12/22/2025 at 4:26 PM, kjclark23 said:

I had to install the production branch driver, which is 580 vs 590. Doesn't look like my card will be supported in future.

This solution worked for me as well. Thanks for posting.

On 12/22/2025 at 1:26 PM, kjclark23 said:

I had to install the production branch driver, which is 580 vs 590. Doesn't look like my card will be supported in future.

Thanks so much for this. Had to do the same thing on both my servers, running 1080 and 1070's. Frustrating that nVidia dropped support on these cards in the new drivers as they're still so useful.

I had the same problem with my server with a 1080ti, and this was the fix.

On 12/22/2025 at 3:26 PM, kjclark23 said:

I had to install the production branch driver, which is 580 vs 590. Doesn't look like my card will be supported in future.

Seems this is the solution for older Quadro cards as well. My M2000 needed the 580 branch

Had the same issue on 7.2.4 with a 3080 FE. Production branch driver + reboot fixed the problem.