rancher-users #windows

Channels

windows

incalculable-nail-18520

05/26/2022, 7:39 PM

Hi All, I'm playing with the windows cluster, all up and running, except pods can't reach out to the host network/internet. I tried both options vxlan/l2 with same result. Not sure how to solve it. Any suggestions/reference are greatly appreciated

clean-laptop-5791

06/08/2022, 8:46 PM

Hey everyone -- so grateful to find this channel! when following this blog entry, how do I know what needs to be done on the Win host and what needs to be done on WSL?

colossal-minister-18571

07/06/2022, 1:18 AM

Does anyone know where I can find information managing and hardening WSL2 for a corporate environment. That one of the road blocks for using Rancher-Desktop in a corporate environment.

clever-pillow-86258

07/13/2022, 11:37 AM

Hello. I'm setting up a cluster to do a POC to check if we can use Rancher to run our windows docker images. I have set up a Rancher on an separate K3s cluster. In Rancher i created a new rke2 cluster. With version v1.23.7+rke2r2. There are 3 linux Control Planes. They work perfectly. 1 Windows agent was added based on Server 2019. I added the container and hyper-v features in windows. The node is running in Rancher and is green. When i try to run a windows container on that node, It fails with the message failed to create containerd task: failed to create shim: hcs::CreateComputeSystem 4c94c11d23498ae7b56845b9a074ba99387e4ea12e947e052f8a2d32b752931c: The directory name is invalid.: unknown I have no clue what this is and how to fix this. Does this ring a bell to someone?

straight-vr-13697

08/18/2022, 7:15 AM

Getting error "404 page not found" for http://localhost/ after installing rancher desktop could any one help on this? facing this issue in windows

worried-football-17739

08/18/2022, 1:25 PM

Created new Windows cluster k8s v1.21.14 using Rancher 2.6.6 and facing an issue with provisioning windows nodes. It’s unable to pull an image rancher/rke-tools:v0.1.87 Looking at dockerhub the latest windows compatible image is v0.1.83. Any suggestions?

bright-whale-83501

09/02/2022, 10:15 AM

rancher-agent:v2.6.8 fails with log error="Error response from daemon: failed to start service utility VM (createreadwrite): kernel 'C:\\Program Files\\Linux Containers\\kernel' not found". I'm running docker in a windows 2019 vm on ESXI, and I have turned on "Expose hardware virtualization to the guest OS" in the CPU setting of the VM.

bright-whale-83501

09/29/2022, 8:43 PM

Is there anyone using windows with RKE2, k8s 1.24+ ?

bright-whale-83501

10/04/2022, 6:53 PM

I'm looking at C:\etc\rancher\rke2\registries.yaml which contains "{"configs":{},"mirrors":null}" and that doesn't look like yaml to me. If I do a manual edit of the content, And the same goes for C:\etc\rancher\rke2\config.yaml.d\50-rancher.yaml. Also very much looking like json. Changes made to registries.yaml are nuked

microscopic-carpenter-74639

10/21/2022, 12:49 PM

https://user-images.githubusercontent.com/53906153/197119202-6478fa95-a103-4f6d-9633-3b20c76900e4.png▾

Is this just me? Docker not producing standard output unless run interactively is a major bug.

eager-coat-67039

01/24/2023, 12:22 PM

Hi everyone, I'm trying to create a new cluster using RKE2 (1.24.9+rke2r2) + W2022 LTSC, but I'm stuck on some odd networking/calico issue: windows pods can reach each other and external addresses, but they cannot reach any linux pod, even the cluster DNS IP 10.43.0.10 cannot be reached from windows pods. I have previous experience with a k8s cluster using RKE + Windows 2019, so not a first-time k8s user, but I've exhausted my options debugging it I'd appreciate if someone could give me an insight into whatever it could be.

Title

eager-coat-67039

01/24/2023, 12:22 PM

Well, sometimes asking a question is enough to spark the insight. The problem was that my linux nodes has two dedicated SAN network interfaces, and somehow it's a routing problem, even everything else working fine ... once I disabled the interfaces, the windows pods could reach the linux nodes. Now that I know what is the problem, I have just to figure out how to properly configure rke/calico to use the correct network interface.

It was easy, just needed to inform which network interface will be used by calico during the cluster installation:

cat >/var/lib/rancher/rke2/server/manifests/rke2-calico-config.yaml <<'EOF'
apiVersion: <http://helm.cattle.io/v1|helm.cattle.io/v1>
kind: HelmChartConfig
metadata:
  name: rke2-calico
  namespace: kube-system
spec:
  valuesContent: |-
    installation:
      calicoNetwork:
        mtu: 1500
        nodeAddressAutodetectionV4:
          interface: eth0
EOF

Or, if the cluster is already installed, just change the

installation

manifest

View count: 5