I reinstalled rancher-desktop, and install (per user) which is my user, also it's using containerd + nerdctl

Hi, I'm running Rancher Desktop 1.8.1 on Windows 11 and have suddenly started having all ASP.NET containers fail with the following error and just wondering if anyone else has had the same issue or knows a fix, thanks

Unhandled exception. System.IO.IOException: The configured user limit (128) on the number of inotify instances has been reached, or the per-process limit on the number of open file descriptors has been reached.

at <http://System.IO|System.IO>.FileSystemWatcher.StartRaisingEvents()

at Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.TryEnableFileSystemWatcher()

at Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.CreateFileChangeToken(String filter)

`at Microsoft.Extensions.Primitives.ChangeToken.OnChange(Func`1 changeTokenProducer, Action changeTokenConsumer)`

at Microsoft.Extensions.Configuration.FileConfigurationProvider..ctor(FileConfigurationSource source)

at Microsoft.Extensions.Configuration.Json.JsonConfigurationSource.Build(IConfigurationBuilder builder)

at Microsoft.Extensions.Configuration.ConfigurationBuilder.Build()

at Microsoft.AspNetCore.Hosting.WebHostBuilder.BuildCommonServices(AggregateException& hostingStartupErrors)

at Microsoft.AspNetCore.Hosting.WebHostBuilder.Build()

Getting the following error when Rancher Desktop is about to ask for sudo password:

at maybeClose (node:internal/child_process:1092:16)
    at Socket.<anonymous> (node:internal/child_process:451:11)
    at Socket.emit (node:events:527:28)
    at Pipe.<anonymous> (node:net:709:12) {
  code: 127,
  killed: false,
  signal: null,
  cmd: `cd "/home/ubuntu"; "/usr/bin/pkexec" --disable-internal-agent /bin/bash -c "echo SUDOPROMPT; /bin/sh -xec 'ln -sf \\"/home/ubuntu/.rd/docker.sock\\" \\"/var/run/docker.sock\\"'"`
}

Running Rancher Desktop on headless (i.e. no UI) Ubuntu 20.04 server, displaying Rancher Desktop UI on MacOS using XQuartz. @fast-garage-66093

@future-night-17486 has left the channel

Hi! I'm using Rancher Desktop 1.8.1 on M1 Mac and encountering the following error.

The TensorFlow library was compiled to use AVX instructions, but these aren't available on your machine.

The current Dockerfile goes like this:

FROM tensorflow/tensorflow:1.15.2 as warmup
RUN pip install tensorflow-serving-api==1.15.0

According to this site, the promising solution seems to be

You can compile a Tensorflow from the source that does not use the AVX instruction set. Or find an already compiled one on the internet.

Would anyone help edit the current Dockerfile so that it compiles a Tensorflow from the source that does not use the AVX instruction set OR use an already compiled one on the Internet?

Hi Team, I am hitting error while installing Rancher(1.4.1) on Windows machine

image.png

Can someone please help here ASAP?

@glamorous-barista-99511 I suspect you will need to upgrade to the current version....

Hi all, I’m new here so I apologize if this question or a similar question has been asked before. Doing a quick search through slack and online, I don’t see any helpful, so here goes: I’m trying to use Rancher Desktop with dockerd to handle a development environment for a project at the company I work for. The development environment consists of a Drupal container and a MariaDB container, and is spun up using docker compose. On my machine, everything works in acceptable timeframes. However, on the machine of the other dev on the project, everything takes nearly 10x as long. For example, clearing the Drupal cache using Drush via

docker exec

takes ~6s on my machine and ~50s on the other dev’s. We have very similar machines: we’re both on i7 Macs, although I’m on Catalina and he’s on Monterey. We both have 16GB RAM, and have Intel UHD Graphics 630, 1536 MB. The only hardware difference I notice is I have an additional Radeon Pro 555X, 4 GB. Is there an obvious reason this development environment (and docker as a whole) would be slower on the other dev’s machine? What steps can I take to narrow down the difference causing the performance issues?

☝️ that’s the other dev lol

does anyone know what's going on if the credential helper on WSL2 is erroring out with "error saving credentials: error storing credentials - err: exit status 22, out: `A specified logon session does not exist. It may already have been terminated.`" when using containerd (nerdctl login)? I have searched through forums and blogs now for hours. Most of them are saying just remove "credsStore":"wincred" from your docker.config or set it to empty or just remove the whole config.json. None of this works, nerdctl login will always try to use a credential helper in the form docker-credential-xxxxx. If you delete the file it tries 'docker-credential-' if you set it to empty it tries 'docker-credential-undefined', if you set it to 'pass' it tries 'docker-credential-pass' but none of them exists with Rancher Desktop. What I can find is the docker-credential-wincred.exe but for whatever reason is doesn't work with above error,

Hi Everyone! I’m having issues with the startup of Kubernetes using Rancher. The concrete error is the following:

Error Starting Kubernetes
Error: Command failed: /bin/sh -xec 'cp "/var/folders/2k/cdjg6vvj0glb1zzz7n0x15d80000gn/T/rd-sudoers19106489.txt" /private/etc/sudoers.d/zzzzz-rancher-desktop-lima && rm -f "/var/folders/2k/cdjg6vvj0glb1zzz7n0x15d80000gn/T/rd-sudoers19106489.txt"'
+ cp /var/folders/2k/cdjg6vvj0glb1zzz7n0x15d80000gn/T/rd-sudoers19106489.txt /private/etc/sudoers.d/zzzzz-rancher-desktop-lima
cp: /private/etc/sudoers.d/zzzzz-rancher-desktop-lima: No such file or directory

Can anyone help me there? I tried a Kubernetes reset and a factory reset, in both cases it still requires the administrative network config. Once I approve that, it leads to this error.

Possible installer issue for Rancher Desktop on macOS 13.3: MacOS no longer has /private/etc/sudoers.d dir by default. Workaround is to sudo mkdir before running rancher desktop install (or restart rd). I've confirmed this on 2 macOS 13.3 systems on m1/m2 cpus. One 13.3 system DID still have the sudoers.d, but it may be due to it being recovered from an earlier intel install or something. I'd suggest the fix would be for rd installer on macos to check for /private/etc/sudoers.d and create it if it doesn't exist.

Problems getting elasticsearch to work on rancher desktop on macos (docker/moby) while following doc to increase ulimit and sysctl vm.max_map_count. Doc says sysctl line near bottom, for me it worked near top (details in reply coming)

I'm experiencing a little bit of strangeness with networking on the WSL side, not sure how to explain. Sometimes, *.localhost times out and fails to respond, but I can hit forwarded ports directly. Other times, I can hit *.localhost (traefik), but port forwards do nothing. I can sometimes remedy the issue by disabling traefik in the preferences, then re-enabling it. Another thing I've noticed, is that sometimes I can't curl the traefik workloads on *.localhost from within WSL when I can hit them in browser on the same machine. I edit etc/hosts and I see that there are different IPs for the host machine.

127.0.0.1 localhost
127.0.1.1 computername

If I update the localhost entry to 127.0.1.1, then I can curl the *.localhost traefik endpoints from within WSL, but then I can no longer access them from the browser.

I ended up grabbing the Node IP from the rancher-desktop dashboard, and manually added entries in wsl's etc/hosts file, and those ended up working as a workaround. such as:

172.26.122.158       mysite.localhost

Hi All,I am using rancher desktop on windows pc to up haproxy (loadbalancer) with the following docker-compose configuration attached as image .Problem is even haproxy image is getting up still I am not able to access my site via "*mydocker-firstSite.ui*",although i can acess it at "*127.0.0.1:9002*".I have also mentioned the mapping in hosts file C:\Windows\System32\drivers\etc as 127.0.0.1 mydocker-firstSite.ui. I tried pinging "*host.docker.internal*" from haproxy (loadbalancer) using terminal but it failed.Also I am behind company proxy.

Hello, Do we have Separate Rancher Desktop Installer (1.81) latest for Windows Server 2016? I tried to Install Rancher desktop 1.81 on Windows Server 2016 from https://github.com/rancher-sandbox/rancher-desktop/releases , clicking on windows link but Installation was unsuccessful and errored out saying "it required Windows 10-9091 or newer"

@fast-garage-66093 looks like a recent PR removed the macos build steps

npm run build
npm run package --publish=never

unless included back in the

npm install

. Haven't tried it, just thought you should know.

Is it possible to use local gpu from Rancher Desktop?

When using rancher-desktop, it uses the rancher-desktop WSL distro. Is there a way to change that...?

Hi everyone! I'm trying to follow this tutorial on Win10, but have some problems: Remote Explorer panel looks different, than on the screenshot, and most importantly - there is no option

Open Folder in Container...

in Remote Development extension command palette. Am I missing something or is this tutorial outdated?

-

Hi, on Rancher startup I have this error message : `msg="errors inspecting instance: [field

dns

must be empty when field

HostResolver.Enabled

is true]"` do anyone has any clue ? I am on macOS Ventura13.3 and I applied this change previously https://github.com/rancher-sandbox/rancher-desktop/issues/797 (installation path was too long).

The full stack :

2023-04-07T11:15:51.435Z: Error starting lima: Error: /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura> exited with code 1

at ChildProcess.<anonymous> (/Applications/Rancher Desktop.app/Contents/Resources/app.asar/dist/app/background.js:1:8136) at ChildProcess.emit (nodeevents527:28) at ChildProcess._handle.onexit (nodeinternal/child process291:12) { stdout: '', stderr: 'time="2023-04-07T131551+02:00" level=warning msg="Non-strict YAML is deprecated and will be unsupported in a future version of Lima" comment="override file \\"/Users/mafullname/.rdlima/_config/override.yaml\\"" error="[2:1] unknown field \\"useHostResolver\\"\\n 1 | # Updated by FixDNS Daemon\\n > 2 | useHostResolver: false\\n ^\\n 3 | dns:\\n 4 | - 192.168.5.3\\n 5 | - 10.39.196.24\\n 6 | "\n' + 'time="2023-04-07T131551+02:00" level=info msg="Using the existing instance \\"0\\""\n' + 'time="2023-04-07T131551+02:00" level=fatal msg="errors inspecting instance: [field

dns

must be empty when field

HostResolver.Enabled

is true]"\n', code: 1, command: [ '/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura', 'start', '--tty=false', '0' ] }

Hi Folks, Rancher desktop is using set my Kubectl version to latest 1.26. But currently most of my K8s clusters are running in 1.19 and its giving few warning while running Kubectl command with old cluster.

-> kubectx
I0413 15:29:59.844450   64080 versioner.go:56] Remote kubernetes server unreachable
I0413 15:30:05.131215   64088 versioner.go:56] Remote kubernetes server unreachable

how can I set my kubectl version to 1.21 or similar

ls -la /usr/local/bin/kubectl
lrwxr-xr-x  1 root  admin  55 Nov 11 11:08 /usr/local/bin/kubectl -> /Applications/Docker.app/Contents/Resources/bin/kubectl

Also facing issue with kubectx also

Anyone see this error in their background.log upon starting Rancher Desktop 1.6 on Windows 11 Enterprise 64 bit? 2023-04-13T150916.418Z: Error starting up: Error: Platform "win32" is not supported by RcFilePathManager at new b (C:\Users\KH027556\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js119466) at k (C:\Users\KH027556\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js120819) at C:\Users\KH027556\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js2996630

upgraded to rancher-desktop 1.8.1 on Windows 10. Now I no longer have helm or kubectl. Ouch.