https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
h
Are snapshots affected? i.e. can I do a factory reset, then restore a snapshot and still be on the new kernel?
f
Unfortunately not, the snapshot will also restore the old kernel. If this is about preserving the images, you could do 
docker save
to export them to a tarball, and after the reset you can 
docker load
to restore them.
There may be a way to force Rancher Desktop to upgrade the image by editing the template file in the internals, but I haven't tested it. I guess it might be worth trying because even if you break something, you could still fix it with a factory reset.
It worked! Shut down Rancher Desktop. Then edit 
~/Library/Application\ Support/rancher-desktop/lima/0/lima.yaml
. It has a line
Copy code
- location: /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/alpine-lima-v0.2.47.rd1-rd-3.23.0.iso|Desktop.app/Contents/Resources/resources/darwin/alpine-lima-v0.2.47.rd1-rd-3.23.0.iso>
Change the 
rd1
to 
rd0
and save the file. Then restart Rancher Desktop. It should now have switched the ISO to the updated kernel. You can verify with the 
modinfo
command above, or check the 
lima.yaml
file again. It should now show 
rd1.2
.
h
I tried that on my Mac M1 and when I start Rancher that line reverts to rd1. I have 1.22.3
f
Yes, you need to install 1.22.3 first to get the new ISO.
h
As soon as I start RD, that file instantly reverts to rd1
f
But the version in the bottom left of Rancher Desktop shows 
1.22.3
?
h
Yes. But I just did this and it looks like I'm ok
Copy code
> rdctl shell modinfo algif_aead
modinfo: module '/lib/modules/6.6.137-0-virt/algif_aead' not found
f
Does it show 
rd1
or 
rd1.2
in 
lima.yaml
?
h
- location: /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/alpine-lima-v0.2.47.rd1.2-rd-3.23.0.iso|Desktop.app/Contents/Resources/resources/darwin/alpine-lima-v0.2.47.rd1.2-rd-3.23.0.iso>
f
Ok, so it has been updated to 
rd1.2
The old string was 
rd1-rd-...
and now it is 
rd1.2-rd-...
h
I missed the 
.2
I was expecting 
0
to stay.
f
The 
0
was just to trigger the update logic. The regex was only capturing 
0.2.47.rd1
as the new version (it didn't expect the trailing 
.2
), so it looked like the version hadn't changes and the ISO was up-to-date. By putting the 
0
in there we triggered the logic to detect a change, which updated the ISO and put the new version into the config.
You should be all good now. The only other thing is: if you created a snapshot with 1.22.0 and you restore it, then you will have to do this procedure again. So it would be better to create a new snapshot after upgrading, so the snapshot includes the kernel bump
h
Great! I figured I should make a new snapshot. Thanks for clarifying.
8 Views
Open in Slack
PreviousNext
Powered by