This is in WSL that I no longer have kubectl or helm

Anybody got neuvector running in rancher desktop’s moby docker’s k3d?

@busy-teacher-96897 if your running MacOS it should work... well with k3s as per the demo a couple of weeks ago.

It did not work properly. Some pods keeps rebooting

Hello: I'm switching from centos-based k8s development to rancherdesktop and I'm stuck immediately after installation. From git-bash I type

kubectl get pods -A

but I see

W0415 09:45:07.823631   25376 loader.go:223] Config not found: C:/Program Files/Git/etc/rancher/k3s/k3s.yaml

And there is no such file there. Where does rancherdesktop put k3s.yaml? Thanks

@proud-jewelry-46860: have the lawyers decided that 2023 doesn't matter? 🙂

Hi, is there an ETA for the 1.9 release? Thanks

The tech-preview contains one important bug fix:

Fixes an issue that was introduced in 1.8 in Rancher Desktop Agent, where If Kubernetes sends updates for services and the port mappings had not changed, the existing maps are deleted.

But otherwise it is just a way to look at the ongoing extension support work. We wanted to show this during KubeCon this week, and we don't like to talk about things unless users can download and try them themselves as well.

Oh, almost forgot: as a tech preview, it will not be included in auto-updates; you will have to install it manually if you want to check it out.

Can anyone help me with the issue I'm getting?

Hello, I was wondering if there was a way to configure flags for the kube-apiserver with kubernetes in Rancher Desktop. I'm attempting to enable PodSecurity for k8s v1.24 (running on mac OS if that makes a difference)

Hello! I am working on upgrading Rancher within my company. I was wondering why as of 1.8.1, Rancher requires +w permissions on the settings.json file on launch and close. We usually chmod this so that users cannot make any changes to enable, disable settings that they shouldn’t be. I know the locked .plist file was introduced to lock down the Docker repositories that you can visit, but it appears that is all it can. Is there any suggestion for locking down the rest of the settings since it writes to that file anytime a user updates settings in the GUI?

hello all: apologies if this seems odd, but I am just a lowly network guy. I am looking for pointers to resources and advice: I have a group of tools for my team of network engineers built and distributed as a docker container they run with rancher-desktop (1.8.1) with some CLI tools in the container that get cloned into the container by a shell script. the point has come that i need to solve some performance problems with the database the tools use by moving to a network DB that we can read and write in parallel threads (current is a sqlite db). so i am working to build and launch a DB container that the App container would connect to for its DB. Up to this point, we have been using Docker not containerd and have kubernetes disabled in rancher-desktop config. As i understand it, i can accomplish the goal, but i need to use k3s in rancher-desktop to run multiple containers? and either a docker-compose or nerdctl-compose file to configure and launch both containers together? Is there a way to at boot launch both containers together and get it to just start up on laptop boot? how might this bee accomplished?

Just a question. When we deploy a pod with a service that exposes a port it first works as expected as it opens the port on the WSL2 machine only. If we shutdown rancher and re-start with this already deployed pod the pod doesn't start anymore if there's a service on the host machine listening on the same port. So in our case we have the "Cisco AnyConnect Umbreall Security Module" which opens a listening port on host machine on port 53. And we use dockerd that starts the coredns service for the cluster. When I do a "reset kubernetes" and coredns gets freshly deployed it works perfectly (even though the cisco security module is running) os both obviously only block the port only for their ip. But when I stop rancher and restart it with our current deployments (including coredns) it says "port already in use". As soon as I had uninstalled the cisco module it started working. The same happened to one of our other developers that had postgres installed locally. When the postgres pod in our deployment was for deployed both postgres instances the one the host and the one in rancher co-exist without any problems. When he restarted rancher the same happened as with coredns. The postgres pod was claiming that port is already in use? Can anyone explain what's going on here and can this be prevented by some setting or do I have to file a bug?

I am running Rancher-Desktop on MacOS ( Apple M1 Pro ) . I am frequently getting following errors

Has anybody installed localstack on Rancher Desktop and gotten Lambda's working?

Hi all, we need to monitor rancher it self on Datadog, like status of rancher components, health status of rancher deployment,etc. In general any kind of Metric that Rancher might expose and Datadog agent can process and send to Datadog console, regarding Rancher health status. Thanks!

how do i configure insecure registry in rancher desktop

Hi team, I tried to reinstall rancher desktop on Mac arm64 but notice that it retained the images from the previous installation. Where can I delete the old data? Thanks.

Looks like factory reset will do the trick

I';m doin the same Raphael, factory + reboot still retains old stuff... M2 here..

At least it removed the old images, shell path and ~/.rd still need to do it manually

@wooden-spoon-95626 @tall-pharmacist-56859 on linux I remove the lima instance on MacOS it's

rm -rf ~/Library/Application\ Support/rancher-desktop/lima/0

the configuration then stays the same (eg ram and cpu)

Hello folks I have some questions about rancher desktop. Is it possible or recommended to install it on a VPS frol à hosting provider? Is it possible as VPS is mostly accessible through SSH and don't have GUI Is it recommended to use rancher desktop like this? Or should just use docker compose? Thanks

Hi folks, I've been using rancher-desktop for awhile now and it's great! I've recently started using it with

skaffold

and it works most of the time, however after 2-3 reloads from my code changes, the node becomes unusable due to disk pressure. I'm using linux with rancher desktop 1.8.1. Has anyone ran into this before or have any suggestions to try to help avoid this disk pressure issue?

@refined-analyst-8898 has left the channel