Jan Dubois
Jan Dubois
### Problem Description On Windows the Rancher Desktop Agent code binds Kubernetes LoadBalancer (and NodePort) services to `127.0.0.1`. At least the LoadBalancer port should be bound to the external interface...
Using the Windows CI build from https://github.com/rancher-sandbox/rancher-desktop/actions/runs/3186985517 When performing a Factory Reset, I briefly see a crash dialog before the app terminates. There are no logs because this happens during...
Right now the current docs version is `1.6.1`. This does not match the latest release, which is `1.6.2`. I don't think we want/need separate versions per patch release; patches only...
The URL for any other version is created by including the version string, e.g. > https://docs.rancherdesktop.io/next/references/architecture/ To access the current version of the docs from inside the application, we would...
> Note that any files with a file extension of .start, such as k3s-overrides.start, can be executed when Rancher Desktop starts its Kubernetes backend (if enabled). According to @mook-as this...
Even though the `AcceptEnv` setting has been added, the variable is not accepted, even after a restart of the instance (which shouldn't be necessary anyways): ```console $ lima sudo grep...
The code has been disabled in #2112. See #2064 for details and repro scripts. The underlying issue might very well be inside QEMU, but we probably need a simpler repro-case...
> To avoid inflating the numbers of the limayaml fields, can we consider to support templating cloud-init yaml in limayaml? _Originally posted by @AkihiroSuda in https://github.com/lima-vm/lima/pull/2119#discussion_r1446783563_ I think we should...
In #1220 the default config has become dependent on the local machine configuration, but the tests still use hardcoded default values for expected paths etc, e.g. https://github.com/lima-vm/lima/blob/f3dc6ed97aa8f69821ecbe1c2b29988c97e67eb7/pkg/networks/commands_test.go#L106-L108 This fails unless...
This breaks the expected `copyFile` semantics, which should truncate an existing file instead of throwing an error. We could pro-actively remove the target: ```diff func copyFile(target, source string) error {...