Unable to launch Rancher Web Console

Installed single node Rancher using docker on Ubuntu 20.04 for PoC. But unable to launch the webconsole. Any help to resolve the issue would be greatly appreciated. Here are the details for reference

ubuntu@ip-10-0-1-243:~$ docker run -d --restart=unless-stopped -p 8080:80 -p 8443:443 -v /opt/rancher:/var/lib/rancher --privileged rancher/rancher:latest
Unable to find image ‘rancher/rancher:latest’ locally
latest: Pulling from rancher/rancher
a8ac3a907045: Pull complete
ddc011b5e45a: Pull complete
183428406682: Pull complete
4383b61779a0: Pull complete
69e5bbd60a3f: Pull complete
263c8e71aebe: Pull complete
44edf2f8127e: Pull complete
df6122681172: Pull complete
805a19149124: Pull complete
51cba9d98e19: Pull complete
7bf4da5aef95: Pull complete
f3455eff5db9: Pull complete
17042d61ef59: Pull complete
0eca1f00aa64: Pull complete
d14813cf6598: Pull complete
cfa7ba581d24: Pull complete
7efc8b2f77be: Pull complete
5f99bef3c776: Pull complete
1b950e7852e4: Pull complete
aadf9192f288: Pull complete
Digest: sha256:ae5135c25b2141bb2aac8a03a9afd77e845f36b9a6c000377c858233aae355d4
Status: Downloaded newer image for rancher/rancher:latest
ubuntu@ip-10-0-1-243:~$ systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2022-06-10 19:27:17 UTC; 36s ago
TriggeredBy: ● docker.socket
Docs: https://docs.docker.com
Main PID: 634 (dockerd)
Tasks: 36
Memory: 109.5M
CGroup: /system.slice/docker.service
├─634 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
├─779 /usr/bin/docker-proxy -proto tcp -host-ip -host-port 8443 -container-ip -container-port 443
├─785 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 8443 -container-ip -container-port 443
├─797 /usr/bin/docker-proxy -proto tcp -host-ip -host-port 8080 -container-ip -container-port 80
└─803 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 8080 -container-ip -container-port 80

Jun 10 19:27:15 ip-10-0-1-243 dockerd[634]: time=“2022-06-10T19:27:15.689262919Z” level=warning msg=“Your kernel does not support CPU realtime scheduler”
Jun 10 19:27:15 ip-10-0-1-243 dockerd[634]: time=“2022-06-10T19:27:15.689308322Z” level=warning msg=“Your kernel does not support cgroup blkio weight”
Jun 10 19:27:15 ip-10-0-1-243 dockerd[634]: time=“2022-06-10T19:27:15.689318973Z” level=warning msg=“Your kernel does not support cgroup blkio weight_device”
Jun 10 19:27:15 ip-10-0-1-243 dockerd[634]: time=“2022-06-10T19:27:15.690003826Z” level=info msg=“Loading containers: start.”
Jun 10 19:27:16 ip-10-0-1-243 dockerd[634]: time=“2022-06-10T19:27:16.055768322Z” level=info msg="Default bridge (docker0) is assigned with an IP address>
Jun 10 19:27:16 ip-10-0-1-243 dockerd[634]: time=“2022-06-10T19:27:16.874316080Z” level=info msg=“Loading containers: done.”
Jun 10 19:27:16 ip-10-0-1-243 dockerd[634]: time=“2022-06-10T19:27:16.945045812Z” level=info msg=“Docker daemon” commit=459d0df graphdriver(s)=overlay2 version=20.10.12
Jun 10 19:27:16 ip-10-0-1-243 dockerd[634]: time=“2022-06-10T19:27:16.948228836Z” level=info msg=“Daemon has completed initialization”
Jun 10 19:27:17 ip-10-0-1-243 systemd[1]: Started Docker Application Container Engine.
Jun 10 19:27:17 ip-10-0-1-243 dockerd[634]: time=“2022-06-10T19:27:17.014864617Z” level=info msg=“API listen on /run/docker.sock”

Did you confirm there is no UFW or IPTABLES blocking any of the ports?

Don’t think it is causing your issue, but can’t hurt to check the warning messages also. There is a pre-flight check script from Docker to validate what kernel features are needed. You can find the script here.

I suggest to also have good look at /opt/rancher/k3s.log.

Ports are open. I have deactivated the firewall. I have run the script. Here are the missing links

  • zfs command: missing
  • zpool command: missing

That should not be the issue.
Any hints in the log file?
What does netstat -anp4 show for port 80 and 443?

Also, it could be worth a try to start fresh by stopping the container and deleting the /opt/rancher content.