This message was deleted.

so not sure i am 100% following, but guessing 20 to 21 changed how https://docs.rancherdesktop.io/ui/snapshots/ works is the problem? they upgraded to 21 and now they can't restore a 20 based snap?

I think that sounds like the issue yeah, I asked the user for a bit more info and images in the ticket because I literally was going off of what they sent in the ticket (which I put above in "")

and did you use a custom win32 for your install to enable priv service to be installed as well?

I have a win32 which we always use but not the priv service, that is new or unknown to me.

the paths you provided were for an RKE install on linux so i don't think its what you are looking for

Ah you are right, sorry you know what I got my wires crossed their because I know on Windows Rancher requires WSL.

well priv is built in. basically did you install as machine scope so it can install priv service or did you leave it as user scope in your config

I think my head went to that for some reason thinking it was linked when I found some "answers"

don't know what you put in your install params for 6 https://docs.rancherdesktop.io/getting-started/installation#installing-rancher-desktop-on-windows

I have not asked them to do that yet I wanted to ask here + research before I say to do anything.

now snaps looks to be experimental so might be a lost cause if there was a breaking change w 21

So best to run the uninstall then install in CP?

well if they need to get back to 20, but they can't stay on 20 forever

Ah so that would be only to go backwards, no no I agree I was thinking the best approach to fix this for them or help them.

whats the error when trying to restore a snap on 21 taken by 20?

Because we have ~20 devices running Rancher which will get the 21 version.

actually maybe i found it

"old Rancher version, clean out manually folders/files left in Rancher’s directories, and install a new version" which I trust AI to some level but always verify 😛

This part?

no the note above

rdctl shell sudo apk add iproute2

Ahh

the note seems to infer old snaps are supported on new rd, but the vm snap will reflect the old release of rd so some commands may not work

Ahh I see ty, I will try to get some feedback from the user - I want to confirm with them first then.

yeah if next time someone can capture the specific error maybe there is a less brute force fix

• There is no known issue with restoring 1.20 snapshots on 1.21; please open a GitHub issue if you have a repro case. • The

iproute2

package is only needed for the new

rdctl info

command; it should not break any existing functionality. It is also only missing on macOS and Linux. Windows should not have this particular problem.

Thanks @fast-garage-66093 very appreciated and helpful info.

Hi there, new here. I suspect my issue may be related. I've just recovered my local rancher-desktop instance. Didn't save the logs, will do it at a later date when I'll try again to update, but in the meantime I hope there's some useful information. Maybe irrelevant: I have moved rancher-desktop ext4.vhdx disk file on a different disk Here's what happened: 1. After windows update, pc restarted, and rancher-desktop downloaded 1.21.0 and asked to be restarted 2. I restarted rancher-desktop, rancher updated, rolled a bit and "started" 3. I go to see my containers, and I find nothing 4. After the initial mild panic, I've tried the usuals: restart rancher, restart windows, swear 5. Tried to restart my compose (from intellij Idea) and got "rancher error getting credentials - err: exec: docker-credential-wincred : executable file not found in %PATH%, out:" 6. Looked at the logs, found "multiple images have the same target, but one of them is still dangling" repeated every few seconds 7. sorry, didn't save the complete logset 8. found this post 9. uninstalled 1.21.0 and downgraded to 1.20.0 , all images, containers, and volumes are now back to normal I have for now disabled auto-update, I'll be able to try again in the near future but right now I need a stable environment. Sorry for not saving more logs, but I was in a rush to get my devbox back to business.

@swift-sundown-78803 Thanks for the update, I can only imagine this may have been caused by relocating the WSL distro disk (

ext4.vhdx

) to another drive unless it was exported/imported properly as a full WSL distribution. If the file was moved manually, WSL may create a new disk or enter a partial-broken state during upgrades.

@swift-sundown-78803 If you can repro and have logs, please file a GitHub issue; things easily get lost here on Slack, especially with the upcoming holidays

@calm-sugar-3169 I've made a proper export+import of the WSL distro in the new location, and I'm pretty sure I've already upgraded Rancher, since I moved it at the end of April and I had auto-update turned on. But sure, can still be something related to the vhdx location if something specific has changed in 1.21.0. @fast-garage-66093 I'll surely try again ASAP and file a proper GitHub issue.