This message was deleted.
# academy
a
This message was deleted.
c
Hi Dave, WSL IP is what you need but if you elaborate a bit more on what you are planning todo I can help you better, thanks.
b
I ran into problems ages ago trying to run rancher manager as a container in WSL due to hyper-v networking, I also ran into the same issue running other containers I wanted to expose outside of my host latptop. For Rancher Manager it is needed to allow a harvester cluster to register.
Simply put... I need containers ran in rancher desktop, including deploying Rancher Manager on rancher desktop to be accessible from my Windows 11 laptop's static external IP address. WSL2's internal/private IP is not an externally resolvable FQDN when following along with the academy course material.
nevermind. It seems that things have improved either on Microsoft and SUSE's side and this just works now, unlike my original attempts a couple years ago.
c
OK, so this isn't an issue for you anymore?
b
I /don't/ believe so, hoping it's not. I suspect it has been fixed on the Microsoft side or the linux distro used in WSL2/Hyper-V. Thanks for engaging. Much appreciated.
c
I don't own a windows machine so, but when i see these issues I try to jump in where i can
b
If anyone is following along at home and taking the courses. I used the external, public facing IP of my windows host. Luckily it is a static IP.
in other words. When deploying rancher manager on rancher desktop, make sure --set hostname=rancher.domain.com resolves to your external IP and not your WSL2 private IP.
c
I don't miss these Windows nuances. I used to be a .NET developer and i remember the windows pain.
Let me add that to my notes I am updating the course now.
b
I used to a HUGE Microsoft guy. Even creating an Exchange hosting product for AT&T Canada before they just went out and made Office365 on the backs of all our hard work. Am I jaded? Maybe just a bit. BUT... it was C# when the light bulb went off and I understood OOP.
@clever-analyst-23771 I'm not sure the state this laptop is in. It's evolved over time so not sure if I've done any other netsh port forwarding or windows defender things to it. I'm not an ideal test case 😉
c
You are one step away from an openSUSE Tumbleweed as your daily driver 🙂
b
I'll play course Guinea pig.... Rancher Basics/Rancher GUI. Renaming local cluster. Caution: This is the cluster that Rancher is using as a data store. Only administrators should be given write access to this cluster. Users with write access to this cluster can use it to grant themselves access to any other cluster managed by this installation. There must be at least one member with the Owner role. Following the course to a T (at least I think I am). And yes... I've wanted to get rid of Windows for awhile but I bought into the Microsoft Surface laptop, OneNote and multiple input mechanisms (touch, pen, keyboard) and is part of my personal knowledge management along with Outlook. Trying to slowly break free from those chains ;)
rancher latest does not show version number in menu but does link to the support page for the relevant info.
actually... it doesn't
clicking about does though
c
Where is that screen shot from?
b
rancher manager web user interface after accessing it and during the GUI lab portion.
that whole section has been invaluable in the past with harvester so I could get to rancher and longhorn user interfaces. Very handy.
c
Ok let me look
b
while you are doing that I am going to download the CLI and see where else I can break, errr fix, your labs.
the CLI lab broke me, not the other way around. Had to retake the quiz. LOL. Other than that, looks good.
c
Ok I got meeting all this week will pick this back up on Monday
👍 1
b
the quiz for templates is a bit confusing when it asks whether rancher supports version control or revisioning (not sure what it asked). I just cloned a template, using rancher manager. A bit confusing.
What is the CLI command for listing projects? Choose only ONE best answer. A ./rancher project list B ./rancher context switch C ./rancher kubectl get projects It is rancher projectS list and not project C is incorrect: rogue@TUMBLER:~$ rancher projects list ID NAME STATE DESCRIPTION local:p-rnchs System active System project created for the cluster local:p-tfbq2 Default active Default project created for the cluster rogue@TUMBLER:~$ rancher kubectl get projects No resources found in default namespace. But choosing A as an answer was wrong.