Error Starting Kubernetes

[gopibabus]

Actual Behavior

After opening Rancher Desktop App, It is throwing me following error

Error Starting Kubernetes

Error: /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura exited with code 1

Some recent logfile lines:

'--tty=false',
    '/Users/gopibabusrungavarapu/Library/Application Support/rancher-desktop/lima/_config/0.yaml'
  ],
  stdout: '',
  stderr: 'time="2024-03-23T14:02:19-04:00" level=info msg="Terminal is not available, proceeding without opening an editor"\n' +
    'time="2024-03-23T14:02:19-04:00" level=fatal msg="instance name \\"0\\" too long: \\"/Users/gopibabusrungavarapu/Library/Application Support/rancher-desktop/lima/0/ssh.sock.1234567890123456\\" must be less than UNIX_PATH_MAX=104 characters, but is 104"\n',
  code: 1,
  [Symbol(child-process.command)]: '/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura start --tty=false /Users/gopibabusrungavarapu/Library/Application Support/rancher-desktop/lima/_config/0.yaml'
}

Steps to Reproduce

1. Visit Rancher Desktop Website
2. Download Latest Version of ARM Mac Installer. At the time of my installation the version is 1.13.1
3. Install it
4. When I try to run rancher Desktop, I am getting above mentioned error

Result

Error Starting Kubernetes

Error: /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura exited with code 1

Some recent logfile lines:

'--tty=false',
    '/Users/gopibabusrungavarapu/Library/Application Support/rancher-desktop/lima/_config/0.yaml'
  ],
  stdout: '',
  stderr: 'time="2024-03-23T14:02:19-04:00" level=info msg="Terminal is not available, proceeding without opening an editor"\n' +
    'time="2024-03-23T14:02:19-04:00" level=fatal msg="instance name \\"0\\" too long: \\"/Users/gopibabusrungavarapu/Library/Application Support/rancher-desktop/lima/0/ssh.sock.1234567890123456\\" must be less than UNIX_PATH_MAX=104 characters, but is 104"\n',
  code: 1,
  [Symbol(child-process.command)]: '/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura start --tty=false /Users/gopibabusrungavarapu/Library/Application Support/rancher-desktop/lima/_config/0.yaml'
}

Expected Behavior

After installing Rancher Desktop on my machine (M1 Mac), it should open and show me the main window.

Additional Information

Rancher Desktop Version

1.13.1

Rancher Desktop K8s Version

1.28.4

Which container engine are you using?

containerd (nerdctl)

What operating system are you using?

macOS

Operating System / Build Version

Sonoma (14.2)

What CPU architecture are you using?

arm64 (Apple Silicon)

Linux only: what package format did you use to install Rancher Desktop?

deb

Windows User Only

No response

[smnandre]

Is it accessible in PHP easily ?

[squrious]

Is it accessible in PHP easily ?

It's in the LiveProp metadata, so yes

[weaverryan]

Thanks for this!

What's the use-case for needing to do:

data-live-url-mapping-search-alias="q"

This doesn't look like something that Livewire has (I check there as a quick way to validate the value of features).

Also: QueryMapping(alias: 'q') or QueryMapping(as: 'q')? as stolen from Livewire :p

[smnandre]

Is it accessible in PHP easily ?

It's in the LiveProp metadata, so yes

But... it's on a call per call basis... so a call to metadataFactory would not bring this data right ? So it's not usable in events, cache, etc ?

(just want to clarify when/where this data will be exposed, accessible, etc)

[smnandre]

I'm not sure to understand how the live prop mapping is "kept" during live action / event.. but it's probably just me needing coffee..

[squrious]

@weaverryan

What's the use-case for needing to do:

data-live-url-mapping-search-alias="q"

If the users just want to override this mapping property they can do it with this shortened syntax instead of passing an object. It may also be useful in the future when the mapping object contain other options: it will be easier to conditionally render specific attributes in this way, than setting up an object, IMO.

This doesn't look like something that Livewire has (I check there as a quick way to validate the value of features).

That's true, but I tried the Livewire feature, and honestly I missed it. As far I know, you can't avoid parameter name collision in Livewire, but I find it pretty useful.

Also: QueryMapping(alias: 'q') or QueryMapping(as: 'q')? as stolen from Livewire :p

I'm totally open for any renaming :) as looks good to me!

@smandre

But... it's on a call per call basis... so a call to metadataFactory would not bring this data right ? So it's not usable in events, cache, etc ?

The metadata defined in your PHP component is available through the metadata factory. If you override the mapping in a template, the overridden values will not be available from metadata. Though there is a utility class that helps in getting those values from mounted attributes.

I'm not sure to understand how the live prop mapping is "kept" during live action / event.. but it's probably just me needing coffee..

The mapping is render as a Stimulus value here.

[smnandre]

I'm still not sure if i'm paranoiac ... but if you're telling me that the "mapping configuration" is read and used from request data ...

I'm 90% sure i still miss something so i stop here :)

[squrious]

I renamed QueryMapping to UrlMapping, alias to as, and rebased to add some doc on this feature :)

[squrious]

Hi there!

Just rebased to get the LiveProp modifier feature.

I also rewrote the test component for url bindings. We often add use cases and I found it becomes hard to understand things like "prop1", "prop2", etc in assertions. This is in a separate commit, so if it's not the best place do do this it can be removed easily ;)

Doc section is also updated!

[smnandre]

@squrious where are we here ? Do you need something / is it "ready" for you ?

[squrious]

@squrious where are we here ? Do you need something / is it "ready" for you ?

Hi @smnandre! It's ready for me

[kbond]

Thanks Nicolas for your time and patience on this!