Bug: Rancher on rancher desktop tutorial

[denise-khuu]

Hi,
I think the rancher tutorial is not up-to date on https://docs.rancherdesktop.io/how-to-guides/rancher-on-rancher-desktop
If I run

docker run --privileged -d --restart=no -p 8080:80 -p 8443:443 rancher/rancher

it won't show the rancher UI but an error message instead.

docker run -d --restart=unless-stopped -p 8080:8080 rancher/server
worked for me.

If I just did something wrong, feel free to just close this issue.

Kind regards,
Denise

[joaquinjsb]

can you please share what error message did you get?

I'm having issues I guess with traefik, I get 404 when doing it locally, only works behind a port forward

[gunamata]

docker run --privileged -d --restart=no -p 8080:80 -p 8443:443 rancher/rancher

We use this command as part of our testing, and has been consistently working fine. One observation though is that once the command finishes executing we do need to wait for sometime (up to ~ 1 min sometimes), till we can see the rancher UI on https://localhost:8443/

Not sure if it's something your machine specific, because we test the same command on all 3 OSs(Mac, Linux, Windows) as part of the QA and it works.. I have just tried this morning on my windows and it worked as well.

Can you please try again when you get a chance and share the error message, logs here.

[denise-khuu]

Hi,
I've tried it again and I just got the 'This site can’t be reached. localhost refused to connect.' error message in the browser.

It seems to be working at first as I was able to see that the image 'rancher/rancher' in
docker image ls and a process was created in docker ps , but after around one minute it just closed or deleted itself.
I couldn't find the process there anymore.
I am not sure how to debug this without the logs, but this is all the information I got.

I am currently working on windows 10 if it helps.
It could be something locally, but I don't really need it yet, that's why I didn't investigate it any further.

[denise-khuu]

E0429 07:19:51.294904 34 gvks.go:69] failed to sync schemas: failed to sync cache for cluster.x-k8s.io/v1alpha3, Kind=Machine 2022/04/29 07:19:51 [ERROR] failed to sync cache for cluster.x-k8s.io/v1alpha3, Kind=Machine 2022/04/29 07:19:51 [ERROR] failed to sync cache for cluster.x-k8s.io/v1alpha3, Kind=Cluster 2022/04/29 07:19:51 [ERROR] failed to sync cache for cluster.x-k8s.io/v1alpha3, Kind=MachineDeployment 2022/04/29 07:19:51 [ERROR] failed to sync cache for cluster.x-k8s.io/v1alpha3, Kind=MachineHealthCheck 2022/04/29 07:19:51 [ERROR] failed to sync cache for cluster.x-k8s.io/v1alpha3, Kind=MachineSet

2022/04/29 07:19:51 [ERROR] failed to start controller for cluster.x-k8s.io/v1alpha3, Kind=Machine: failed to wait for caches to sync 2022/04/29 07:19:51 [ERROR] failed to start controller for cluster.x-k8s.io/v1alpha3, Kind=Cluster: failed to wait for caches to sync 2022/04/29 07:19:51 [ERROR] failed to start controller for cluster.x-k8s.io/v1alpha3, Kind=MachineDeployment: failed to wait for caches to sync 2022/04/29 07:19:51 [ERROR] failed to start controller for cluster.x-k8s.io/v1alpha3, Kind=MachineHealthCheck: failed to wait for caches to sync 2022/04/29 07:19:51 [ERROR] failed to start controller for cluster.x-k8s.io/v1alpha3, Kind=MachineSet: failed to wait for caches to sync

The issue seems similar to this one rancher/rancher#34927