Use symlink to shorten Lima config path

[jsoref]

Fixes #797

[mook-as]

This wouldn't actually solve the issue, as we're running limactl start with the long path (and that's the one emitting the failure).

We will need to fix the nerdctl stub too, of course (because that also spawns limactl), but this isn't the full thing.

[ericpromislow]

This kind of setup should be done as soon as the directory is either created or known to exist. The problem with this solution is that we're going to run the same code every time someone runs nerdctl.

So setting up the symlink after LAS/rd/lima is first created should happen at

rancher-desktop/src/k8s-engine/lima.ts

Line 582 in e17f930

await fs.promises.mkdir(path.dirname(this.CONFIG_PATH), { recursive: true });

.

Creating a symlink when the LAS/rd/lima already exists could actually be done on upgrades only by leveraging the settings update table at

rancher-desktop/src/config/settings.ts

Line 21 in e17f930

const CURRENT_SETTINGS_VERSION = 4;

and adding a setting for 4: at

rancher-desktop/src/config/settings.ts

Line 255 in e17f930

};

. If we don't want to overload the settings module with non-settings stuff we could just check for an existing symlink in the else part of the above code.

Or did I miss something?

[jandubois]

There are a number of issues to think through:

• what is the name we want to create? Is ~/.lima-rd the right one (it doesn't tab-complete when you already have ~/.lima)?
• what do we do when both ~/Library/Application\ Support/rancher-desktop/lima and ~/.lima-rd exist?
• how do we migrate an existing install from the current name to the symlink setup
• how does this affect the code excluding the directory from time machine backups?
• should the symlink always be created, or only when necessary?

I'm tempted to move this discussion into a new issue, as this should be hashed out before coding starts... 😄

[jandubois]

Please move discussion to #1465

[mook-as]

Closing this PR — this needs to be done in the TypeScript code (and will probably more discussion before we can agree on the details of the implementation).

Thanks for getting this rolling!