Hello all! New Rancher Desktop (1.4.1) user here! I'm on Windows 10, WSL2, Ubuntu 20.04. I'm trying to enable the WSL Integration in the UI and I see my WSL distro but when I hover over the checkbox I get a 🚫 icon. Any help would be much appreciated.

Hello Everyone, My Mac and Fedora computers both have Rancher desktop installed and kuberenets enabled. My MacBook could ping the internal IP address of the kubectl node, but Fedora was unable to. Am I overlooking any Fedora configurations? Can someone assist me in getting ping to function on my Fedora computer? Thank you so much for your help in advance.

Hello, I come here because I have a problem since my company moved from Docker desktop to Rancher desktop and I didn't found a response on Internet. We have a container which need to request the host but I can't seem to ping

host.docker.internal

I tried on a new container, it does not work too. Step i've done : Firewall rule

New-NetFirewallRule -DisplayName "WSL" -Direction Inbound -InterfaceAlias "vEthernet (WSL)" -Action Allow

New container

docker run -d -p 80:80 docker/getting-started

Ping :

docker exec -it containerName sh

/ # ping -c 2 host.docker.internal

PING host.docker.internal (172.17.32.1): 56 data bytes

--- host.docker.internal ping statistics ---

2 packets transmitted, 0 packets received, 100% packet loss

Do you have an idea ? Thank's

If I wanted to pull an image (using nerdctl, docker cli, whatever) that is in the k8s.io namespace and listed in the Rancher Desktop UI, what would be the command?

"nerdctl image ls" lists my base image (smp/mqlua:dev), but I can not use it in a Dockerfile FROM command. What am I missing?

Hi, I am having an issue when I try to launch Rancher Desktop. I am running Ubuntu version 18.04.6 LTS. I have a suspicion the error is because I need a newer Ubuntu version but I am not sure. Also, my CPU has virtualization enabled (checked BIOS) so I am not sure why it is doing this.

Error: virtualization does not appear to be supported on your machine

bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds bogomips: 6820.02 clflush size: 64 cache_alignment: 64 address sizes: 43 bits physical, 48 bits virtual power management: 2022-07-19T233447.202Z: Error starting lima: Error: Virtualization does not appear to be supported on your machine. at Qe.ensureVirtualizationSupported (/opt/rancher-desktop/resources/app.asar/dist/app/background.js17179719) at processTicksAndRejections (nodeinternal/process/task queues96:5

I posted this queston already in the wrong channel, so here is my second try: I have switched from Docker Desktop to Rancher. Now I have the problem that when I start a container via docker-compose, I get the following error: "Error response from daemon: create \\wsl$\Ubuntu\home\david\projects\test\.configuration\docker\test.linux.dev \docker-data\mysql: "\\\\wsl$\\Ubuntu\\home\\david\\projects\\test\\.configuration\\docker\\test.linux.dev\\do cker-data\\mysql" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path" Can I start the container from windows even though the volumes are in wsl?

Is there any doc or recommendation to run local registry with rd and use it push/pull images ?

Hi team i am getting following error while run docker login any idea ?/usr/local/bin/docker-credential-rancher-desktop: source: line 5: can't open '/etc/rancher/desktop/credfwd': No such file or directory FATA[0003] error saving credentials: error storing credentials - err: exit status 2, out: `

hello all, how can I reduce the diffdisk ? it still growing

Is there any documentation on how the lima VM is configured on macOS? There seems to be a 100GB volume called data-volume on the VM:

lima-rancher-desktop:~# ls -l /dev/disk/by-label/data-volume
lrwxrwxrwx    1 root     root            10 Jul 22 17:18 /dev/disk/by-label/data-volume -> ../../vdb1

But it seems it’s mounted on multiple mountpoints, however there is different data in each of them:

lima-rancher-desktop:/dev/disk/by-label# mount |grep data-volume
/dev/disk/by-label/data-volume on /mnt/data type ext4 (rw,relatime)
/dev/disk/by-label/data-volume on /etc type ext4 (rw,relatime)
/dev/disk/by-label/data-volume on /home type ext4 (rw,relatime)
/dev/disk/by-label/data-volume on /tmp type ext4 (rw,relatime)
/dev/disk/by-label/data-volume on /usr/local type ext4 (rw,relatime)
/dev/disk/by-label/data-volume on /var/lib type ext4 (rw,relatime)
/dev/disk/by-label/data-volume on /root type ext4 (rw,relatime)

Not sure how that is supposed to work. Also I’d like to know where the 100GB /dev/vdb1 is stored on macOS:

lima-rancher-desktop:~# fdisk /dev/vdb
...
Command (m for help): p
Disk /dev/vdb: 100 GB, 107374182400 bytes, 209715200 sectors
366634 cylinders, 13 heads, 44 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/vdb1    2,0,33      178,12,44         2048  209715199  209713152 99.9G 83 Linux

As I understand from the documentation data volumes are stored in /var/lib/docker/volumes on the lima vm, which is also the data-volume, so vdb1:

lima-rancher-desktop:/var/lib/docker/volumes# df -h .
Filesystem                Size      Used Available Use% Mounted on
/dev/disk/by-label/data-volume
                         97.9G      1.9G     90.9G   2% /mnt/data

I’m looking at where those are on my macOS host machine.

Hi Team, I have Mac version: MacOs Monterey 12.4 (21F79) I am trying to install Rancher Desktop version 1.2.1 but, getting the error 255 with Kubernetes. Can anyone help m here?

Rancher Desktop Ubuntu .deb package depends on

pass

. Having

pass

installed completely changes the way

docker login

works. It stops all of the (admittedly fairly insecure) auths from

.docker/config.json

from working. To use

docker login

, and any interaction with registries which relies on

docker login

,

pass

insists that the user uses

gpg

to create a key and reenters their

docker login

credentials. This change was sprung upon me just by installing Rancher Desktop. For me, this stopped me from working for a while, which delayed a deployment, whilst I looked up all the manuals I needed to learn this new approach. Maybe

pass

could be suggested by Rancher Desktop instead of be depended upon by Rancher Desktop?

Hi, there, I'm using Rancher Desktop on Windows with WSL2, it seems that private registry is not working. I'v already put the registry config in /etc/rancher/k3s/registries.yaml, but nothing happens, k3s should update the containerd config at startup, but actually nothing happens. Is this a bug?

The same configuration works if I manually install k3s in ubuntu. I noticed that the start command of containerd is different. In k3s it's

containerd -c /var/lib/rancher/k3s/agent/etc/containerd/config.toml -a /run/k3s/containerd/containerd.sock --state /run/k3s/containerd --root /var/lib/rancher/k3s/agent/containerd

Hi all. I’m pretty new to Rancher Desktop, containering, clustering, Kubernetes etc but I’ve installed Rancher desktop on a Mac, done a few simple tutorials and it seems like a really impressive and efficient, minimal code way to do things. Anyway, I want to figure out how to get multiple LAMP stacks each with a Wordpress install running all with SSL certs using Certbot and LetsEncrypt for sub-domains. It’s so I can send links to my clients so they can see the websites I am currently building for them. I have access to DNS for all my domains so the sub-domains part is already done and working. How hard is this and where should I start please?

Just a sanity check, buildx and scan are missing from my local RD (1.4.1):

Invalid Plugins:
  buildx      failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-buildx: no such file or directory
  scan        failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-scan: no such file or directory

:~/.docker/cli-plugins$ ls
docker-compose

From tracking through the github issues, this looks like it should be downloaded and installed automatically. On the two machines I checked with 1.4.1, it isn't. Should it be?

Has anyone used Ambassador with k3d ? i.e. this tutorial on k3d https://www.getambassador.io/docs/edge-stack/latest/tutorials/getting-started/

Good morning. How can I edit buildkitd.toml on macOS? I see the file nowhere, so I assume on macOS it is inside a container?

getting an issue with docker pull. Seems to be a dns related error. mac version - 11.4 Big Sur RD version - 1.3.0 docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io on 192.168.5.353 read udp 192.168.5.1557539 >192.168.5.353: i/o timeout. Any help appreciated.

I've got a Dockerfile with a remote ADD in it that is failing with nerdctl on my local Windows, but working fine with docker in our GitHub Actions CI environment.

Does anyone have a good workaround for

docker buildx build --platform linux/amd64

(on m1) being fairly annoying? Namely, I don't have a local registry (I suppose I could add one), and I need a local image w/ an extra piece of software. But:

WARNING: No output specified for docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load

And I don't have the bandwidth to upload my patched image to a registry just so i can download it so i can use it.

I (re)installed Rancher Desktop v1.4.1 on an x86_64 MacBook running macOS Monterey 12.4. Installing Rancher Desktop successfully installed docker but it's as if it hasn't installed docker*d* and is not starting dockerd when I open Rancher Desktop [1]. Rancher Desktop appears to claim that dockerd is running (see attached image) and doesn't have any obvious error/warning messages in the UI but it doesn't look like it actually is [1]. Any help debugging or pointing me towards documentation, etc. is greatly appreciated. [1]

$ docker run ubuntu echo hi  # Simple test
docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
$ dockerd
-bash: dockerd: command not found
$ which dockerd
$ which docker
/Users/mikel.mcdaniel/.rd/bin/docker
$ ls /Users/mikel.mcdaniel/.rd/bin
docker				docker-compose			docker-credential-osxkeychain	kubectl				nerdctl
docker-buildx			docker-credential-ecr-login	helm				kuberlr				rdctl
$ ps -e | grep -i docker
 4243 ttys004    0:00.00 grep -i docker
$ ls /var/run/*docker*
ls: /var/run/*docker*: No such file or directory
$

I am still trying to build containers using local base images on macOS using nerdctl (RD 1.4.1, using containerd).

I entered the RD VM using rdctl shell and created the file /etc/buildkitd/buildkitd.toml, but that seems not to work (trying to set the namespace to "default" in the worker.containerd section). Any help is much appreciated.

err, /etc/buildkit/buildkitd.toml, ofc....

Ok, so it picks up the file now. But I am not sure what to put in there, can I just specify the options I need or does the file have to be complete?

Hi all. I have an issue with my Mac using Rancher Desktop. I have killed off the built in httpd Apache service and now when I see what is listening on port 80 I get the following: paulrandall@Pauls-Mac-mini % sudo lsof -i ‘:80’ COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME ssh 1522 paulrandall 36u IPv4 0xea441d2a14d8ed23 0t0 TCP *:http (LISTEN) I am trying to get NGINX proxy Manager to work on port 80 and it won;t work even though the docker-container.yml file I use has - 80:80 in the settings. It launches ok. I can get to it on port 81 as there is also - 81:81 in the YAML file but port 80 won’t respond which is a problem for me as I want to be able to get to port 80 with the proxy manager to then redirect to port 8080 where the Wordpress container resides. I’m so close. Any ideas please?

whats the result of ps u 1522

Hi All. Quick question. We had a dev who started RD ran docker-compose up and was working fine. Accidentally started another instance of RD which failed and so then he quit that. BUT at this point the only way to connect again to the services that were exposed was to reboot his PC, start RD and run docker-compose. Things that were tried before the reboot were like docker compose down and then back up. Has anyone else seen this behavior? Should I open issue on GitHub? Thanks!