Hello everyone! Maybe you can help me. I am migrating from Docker Desktop to Rancher Desktop. Im trying to build a container installing ssh and curl (docker build .) the following packages with the commands you see below ENV HTTP_PROXY=http://proxy... ENV HTTPS_PROXY=http://proxy... RUN apk --no-cache add ca-certificates RUN apk update && apk add curl openssh-client Everything works well in Docker Desktop, every package is dowloaded On the other hand, using Rancher I am unable to download anything. => => # fetch https://ftp.acc.umu.se/mirror/alpinelinux.org/v3.17/main/x86_64/APKINDEX.tar.gz => => # WARNING: Ignoring https://ftp.acc.umu.se/mirror/alpinelinux.org/v3.17/main: operation timed out ...... ** It is important to say the problem is when I am connected to a VPN *, when I am not in the vpn Rancher works correctly and downloads the files. What do I need to configure for Rancher (WLS - rancher-desktop) to connect to the internet within the vpn ? Thanks so much

How can I change the kubernetes version? I am on version 1.26.5, but I want version 1.22.6. Every time I choose version 1.22.6 and then click away and back, it's reset to version 1.26.5.

Hi guys! How are you doing? I'm migrating from docker-desktop to rancher-desktop and I seem to be having a problem with kong not being able to get the certificates. I am using nginx to access localhost thru another website. I have a node server running in localhost. This part is working just fine. My problem starts when I try and access it from https, witch indicates that is likely something with kong. But I didn't change anything about kong configuration, the only thing that is different now is that I am trying to run my docker in rancher-desktop. Is there any known compatibility issues? According to app diagnostics, it should be fine.

Greetings,

NAME                    STATE           VERSION

* rancher-desktop         Stopped         2

wsl-vpnkit              Stopped         2

rancher-desktop-data    Stopped         2

When I try to start wsl.exe -d wsl-vpnkit it stays running for about 45 seconds...

NAME                    STATE           VERSION

* rancher-desktop         Stopped         2

wsl-vpnkit              Running         2

rancher-desktop-data    Stopped         2

but then stops Where are the log files for this?

hello all, we're using rancher desktop with minikube to orchestrate our dev environment. One of our images, a DB image, is fairly large, and each time we start its getting

ImagePullBackOff

error. I see that there are other examples of people suffering from this exists, but I am yet to find a viable (non manual) solution. We're having to pull the image manually each time. Using Rancher Desktop 1.8.1 with latest K8s, any ideas if this can be solved?

Thanks in Advance! any insight would be helpful. Our fairly large team is suffering from this repeatedly

Hello everyone! Now I am facing another problem. The maven plugin "docker-maven-plugin" is not doing the bind of the directories in the container. Is not working <groupId>io.fabric8</groupId> <artifactId>docker-maven-plugin</artifactId> <version>0.25.0</version> <executions> <execution> <id>docker-start</id> <phase>pre-integration-test</phase> <goals> <goal>stop</goal> <goal>start</goal> </goals> <configuration> <images> <image> <name>${fabric8.docker.image}</name> <alias>${project.artifactId}</alias> <run> <namingStrategy>alias</namingStrategy> <ports> <port>${fabric8.docker.container.port}:8080</port> <port>${fabric8.docker.container.debug.port}:8000</port> <port>${fabric8.docker.container.jacoco.port}:6300</port> </ports> <network> <mode>custom</mode> <name>backend</name> </network> <env> <JPDA_ADDRESS>*:8000</JPDA_ADDRESS> <APP_VERSION>${project.version}-${tag.version}</APP_VERSION> </env> <volumes> <bind> <volume>${user.home}/jacocoagent:/opt/app/lib/jacoco</volume> <volume>${config.dir}:/opt/app/etc/webapp</volume> <volume>${config.dir}/log4j2.xml:/opt/app/var/lib/tomee/webapps/ROOT/WEB-INF/classes/log4j2.xml</volume> </bind> </volumes> </run> </image> </images> </configuration> </execution> None of the bindings work <bind> <volume>${user.home}/jacocoagent:/opt/app/lib/jacoco</volume> <volume>${config.dir}:/opt/app/etc/webapp</volume> <volume>${config.dir}/log4j2.xml:/opt/app/var/lib/tomee/webapps/ROOT/WEB-INF/classes/log4j2.xml</volume> </bind> Is there any known problem with this plugin ? Thanks so much

Hello world! Thanks for Rancher Desktop! Unfortunately I can't pull images from the official docker hub, it fails with

Error response from daemon: Head "<https://registry-1.docker.io/v2/library/hello-world/manifests/latest>": EOF

Any ideas how to fix/troubleshoot this? I tried searching on docker, but some issues point to disable hardware acceleration on a FristBox (which I don't have), ot running docker logout.

Hi! When bind mounting volumes (

-v

) from my Mac to a container, am I able to specify the owner of the volume? Default behavior seems to map the owner/group by numeric id from the host to the container. For me, this mounts a directory that’s owned by tim:staff on my host to be owned by 502:games (tim user id is 502, but the container doesn’t have a user with id 502; staff group id is 20, which maps to games group of 20 in the container). Coworker using docker desktop seems to see the same volume mount get owner/group of root without specifying anything to that effect. Specifically mounting this:

-v /User/tim/.ssh:/root/.ssh

, so I want the files to be owned by root:root within the container.

Hello everyone, I have a problem by installing Rancher Desktop. I've already update wsl and switch to WSL2. What can be the problem?

MS Build conference had several sessions on trivy and I'm trying to run it in RD, but get errors and found this issue. https://github.com/aquasecurity/trivy/issues/1342 Any update or workarounds? I see trivy can be invoked in the Rancher GUI, but I'd like to be able to get the output to use in copacetic. I get the same error in the issue running on Mac M1, Ventura, using RD 1.8.1 dockerd engine.

Untitled

Hi team, we encountered the above error when doing port-forwarding with RD. Looks like the cert in ~/.kube/config does not match the node IP, so port-forwarding failed. In our case, the node IP is 192.168.1.11.

Do you have any idea what could contribute to this so that we can avoid it in the future. And more importantly, what’s the fix for it? Thanks.

Good morning, still lost in Rancher Land.. Have 3 WSL Linux instances running; However, when I try to start the Windows Rancher Desktop client I never see any GUI and the C:\Users\KH027556\AppData\Local\rancher-desktop\logs\background.log contains the follow message. I've tried changing the port to 6444 with zero help after updating the config and recycling all instances.

2023-06-07T14:18:33.571Z: Stopping background process Win32 socket proxy.
2023-06-07T14:18:33.574Z: mainEvents settings-update: {"version":4,"kubernetes":{"version":"1.25.3","memoryInGB":6,"numberCPUs":2,"port":6443,"containerEngine":"containerd","checkForExistingKimBuilder":false,"enabled":true,"WSLIntegrations":{},"options":{"traefik":true,"flannel":true},"suppressSudo":false,"hostResolver":true,"experimental":{"socketVMNet":false}},"portForwarding":{"includeKubernetesServices":false},"images":{"showAll":true,"namespace":"<http://k8s.io|k8s.io>"},"telemetry":false,"updater":false,"debug":false,"pathManagementStrategy":"notset","diagnostics":{"showMuted":false,"mutedChecks":{}}}
2023-06-07T14:18:33.656Z: Stopping background process Win32 socket proxy.
2023-06-07T14:18:35.966Z: UnhandledRejectionWarning: Error: C:\Windows\system32\wsl.exe exited with code 1
    at ChildProcess.<anonymous> (C:\Users\KH027556\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js:1:7750)
    at ChildProcess.emit (node:events:390:28)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) {
  stdout: '',
  code: 1,
  command: [
    'C:\\Windows\\system32\\wsl.exe',
    '--distribution',
    'wsl-vpnkit',
    '--exec',
    '/bin/wslpath',
    '-a',
    '-u',
    'C:\\Users\\KH027556\\AppData\\Local\\Programs\\Rancher Desktop\\resources\\resources\\linux\\bin\\docker-compose'
  ]
}
2023-06-07T14:18:36.446Z: Error starting up: Error: C:\Windows\system32\wsl.exe exited with code 1
    at ChildProcess.<anonymous> (C:\Users\KH027556\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js:1:7750)
    at ChildProcess.emit (node:events:390:28)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) {
  stdout: '',
  code: 1,
  command: [
    'C:\\Windows\\system32\\wsl.exe',
    '--distribution',
    'wsl-vpnkit',
    '--exec',
    '/bin/wslpath',
    '-a',
    '-u',
    'C:\\Users\\KH027556\\AppData\\Local\\Programs\\Rancher Desktop\\resources\\resources\\linux\\bin\\docker-compose'
  ]
}

I even tried to execute: C:\Windows\system32\wsl.exe --distribution wsl-vpnkit --exec /bin/wslpath -a -u C:\Users\KH027556\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\bin\docker-compose Directly from PS and get;

PS C:\data\deployment_tools> C:\Windows\system32\wsl.exe --distribution wsl-vpnkit --exec /bin/wslpath -a -u C:\Users\KH027556\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\bin\docker-compose
Usage:
    -a    force result to absolute path format
    -u    translate from a Windows path to a WSL path (default)
    -w    translate from a WSL path to a Windows path
    -m    translate from a WSL path to a Windows path, with '/' instead of '\'

EX: wslpath 'c:\users'
C:\Windows\system32\wsl.exe : /bin/wslpath: Invalid argument
At line:1 char:1
+ C:\Windows\system32\wsl.exe --distribution wsl-vpnkit --exec /bin/wsl ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (/bin/wslpath: Invalid argument:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

Any and all help greatly appreciated.

also tried with quoted paths; PS C:\data\deployment_tools> C:\Windows\system32\wsl.exe --distribution wsl-vpnkit --exec '/bin/wslpath' -a -u 'C:\Users\KH027556\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\bin\docker-compose' C:\Windows\system32\wsl.exe : /bin/wslpath: C:\Users\KH027556\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\bin\docker-compose At line:1 char:1 + C:\Windows\system32\wsl.exe --distribution wsl-vpnkit --exec '/bin/ws ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (/bin/wslpath: C...\docker-compose:String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError

Hello! By default 10.42.0.0/16 are used for pods and 10.43.0.0/16 for service IPs. I want to add range 192.0.0.0/24 to the service IPs pool that can be used for static IP addressing. How do I do that?

I installed a fresh rancher-desktop 1.8.1 on my Window box. Dockerd runs fine, but k3s fails to start. Rancher Desktop keeps showing "Updating kubeconfig". I have two noticeable error messages in my log files: " kubernetes: failed to read kubeconfig [config-path=/etc/rancher/k3s/k3s.yaml][error=could not load Kubernetes client config from /etc/rancher/k3s/k3s.yaml: stat /etc/rancher/k3s/k3s.yaml: no such file or directory]" and k3s.log:time="2023-06-08T192954Z" level=fatal msg="starting kubernetes: preparing server: failed to normalize server token; must be in format K10<CA-HASH>:&lt;USERNAME&gt;<PASSWORD> or <PASSWORD>" Could anyone please give me some hints on how to proceed? Thank you.

Hi @fast-garage-66093, I'm tripping on https://github.com/rancher-sandbox/rancher-desktop/issues/1439 again...

Hello! Can anyone help me resolve this issue, I am doing

docker build

for

nodejs app

- it get stuck at

npm run build

and after awhile I see this error message:

ERROR: failed to receive status: rpc error: code = Unavailable desc = error reading from server: EOF

after which if i try to use docker again I see that docker has crashed I use Rancher Desktop1.8.1 on Mac M1

@little-microphone-41463 nodejs builds can be really fickle with ARM machines, because your machine may be defaulting to emulation instead of building for your architecture. (i'm literally working on an issue with one right now to support multi-arch builds, where npm run build eventually times out) That can be due to the base image you might be using as well in the dockerfile. What is your base image?

you can try using buildkit's platform detection features like

FROM --platform=$BUILDPLATFORM node:18

good article here https://www.docker.com/blog/faster-multi-platform-builds-dockerfile-cross-compilation-guide/

I use docker as CRI in Rancher Desktop. docker pull push images subcommands are fine, but build not. Ex: docker build -t zheng11581/test:latest . ERROR: failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to read dockerfile: open /var/lib/docker/tmp/buildkit-mount3485957920/Dockerfile: no such file or directory

Im using rancher-desktop-1.8.1-x86_64.AppImage. Very offen zsh uses 100% cpu like it have hung.

Hi can anyone help me on this. wsl error

Hi all. Does anyone know how to fix the error displayed in the screenshot? I already tried running the chmod command. I also gave Rancher full disk access in Privacy & Security settings

Hi everyone, I am trying to connect with nerdctl login to Nexus Repository Manager from Windows 10, and I am having problems connecting, I attach the evidence, please helpme

Hi everyone! I have installed rancher desktop in my mac. Purpose is to run below command

sudo docker run \
    --detach --rm \
    --name lensesio \
    -p 2181:2181 \
    -p 3030:3030 \
    -p 8081-8083:8081-8083 \
    -p 9581-9585:9581-9585 \
    -p 9092:9092 \
    -e ADV_HOST=127.0.0.1 \
    -e RUN_TESTS=0 \
    lensesio/fast-data-dev:latest

but i found out in order to run above command i need to have disable "enable kubernates" from the rancher desktop screen and enable the dockered(moby) option. When i do this i get the below error, can you please help here