This message was deleted.

when you run Rancher as a container, it spins up an embedded K3s instance as its “local” cluster. It seems your issue is coming from that embedded K3s being unable to start. If you are persisting your containerized /var/lib/rancher, you can look at the k3s.log file in there.

“I want to conduct a simple test of Rancher’s functionalities, but the installation is not going as described in the manual. My environment consists of ① a Kubernetes cluster, and I would like to run Rancher on ② a separate physical host. For setting up environment ②: • Host OS: AlmaLinux 9 • Docker is already installed • K3s is already installed Is there anything else needed? I can’t even get to the initial login screen.” Please let me know if you need any further assistance!

From your logs:

BindHost: HTTPListenPort:80

Try changing the exposed port from

-p 8080:8800

to

-p 80:80

https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/installation-requirements/port-requirements#ports-for-[…]-in-docker

I get the same error when I set the port to 80.