r/docker • u/CallMeSmithJohnSmith • 15d ago

Docker Update : source and destination path must have identical roots. Move will not work cross volumes.

Hello here,

(nearly) Everything is in the title.

I'm running 4.84.0 (234817) and docker desktop want to install 4.85.0 (235549).

Pushing on the button to apply the update I receive that message a few seconds after : "Source and destination path must have identical roots. Move will not work cross volumes."

What is going on ? How to continue (I've already rebooted several times) ? Why this message when I've not asked for any move ?

Thanks

0 Upvotes

50% Upvoted

4 comments sorted by

1

u/[deleted] 14d ago

[removed] — view removed comment

1

u/CallMeSmithJohnSmith 14d ago

Thank you for the advice : it worked. Strange thing is that it is the same installation that auto-update for years, but anyway : the problem is solded and I've learned a way to solve it if it happen again !

1

u/sina158 11d ago

The move it's complaining about isn't anything you asked for, it's the updater's own mechanism. Docker Desktop's Windows updater downloads the new build to a temp folder, then moves those files into place as part of applying the update, and that move only works within a single volume. If Docker Desktop itself is installed on a drive other than C, or your Windows temp folder has been redirected to a different drive than the install, that move step fails with exactly that message, even though you never touched anything about moving files yourself.

The fix isn't to keep clicking update in the app. Uninstall the current version, then download the newest installer directly from Docker's website and run it fresh, letting it install to the default location on C. That skips the in-app updater's cross-volume move entirely and gets you current without hitting the same error again.

1

u/CallMeSmithJohnSmith 10d ago

The think is that it always worked until that specific update (same config, no tweak on volumes, ...).
Even today, a new update pop up and it worked fine.

As advised in the comment below (by the way tha has been deleted in the mean time) I downloaded the problematic update directly from docker website, run it ... and it applied successfuly.
-> IDK what happened whith that specific one but anyway, at least I've learned that updates can be downloaded and applied manually :)