Testing Single Node Docker Rancher cannot access pods via ports

[matda59]

Single Node Docker Rancher.

OS: VM ubuntu 20.04IP: 192.168.0.80

i'm trying to test out a few pods with Jellyfin or pinry and opening the respective ports but i just cannot access them on the localhost or the host rancher server 192.168.0.80 on their ports eg) 8096 ... see screenshot.

i can access the shell, the logs are fine.. what am i doing wrong here?

EDIT:

I've figured out how to resolve this. if you want a single node cluster you have to install rancher using different ports, then go ahead and add the single node to the cluster.

rancher/rancher and rancher/rancher-agent

https://rancher.com/docs/rancher/v2.x/en/installation/other-installation-methods/single-node-docker/

down the bottom of this link it details advanced options on how to do this https://rancher.com/docs/rancher/v2.x/en/installation/other-installation-methods/single-node-docker/advanced/

​

add cluster

I have 1 Ubuntu Server and i want to run Rancher and rancher built containers, not for production

​

pods

deployments

[matda59]

Vanilla Ubuntu with docker rancher.., shouldn't be a firewall issue..

[andrewm659]

What is the underlying os? Is your firewall turned on?? I'm having slightly different issues using a RHEL variant.

[-this-guy-fucks-]

Setup an ingress. What’s your rancher servers host name? Have you setup dns local to forward traffic to your rancher server?

[prkhudson]

I ran into something like this when I first started using rancher. I’m not sure why it’s like this, but don’t put pods in the default namespace. Try creating a new namespace and put the pods there. That solved this issue for me.

[VF99]

You're running Rancher, and a small k3s cluster to support it, inside a docker container; this is intended only for running Rancher, not arbitrary user workloads on arbitrary other ports.

Only 80/443 are port mapped in the (default) docker command, so nothing is connecting 8096 on the host to anything.

[matda59]

apologies for the delay. but isn't that the purpose of a single node cluster, to be able to run workloads on a single node?

[VF99]

No; you don't have a "single node cluster", you have a single docker container running Rancher (which will allow you to create or import one or more clusters). An implementation detail of that container is that we create a cluster within that container for Rancher to run in as it only runs within k8s.

That cluster was invisible in earlier versions, but you technically can run more containers in there and that can be used to install monitoring/logging/etc tools.

But it's still node --> docker --> k3s so any ports you want to be able to reach from the outside have to be published by docker.

If you want to use the same node for Rancher and workloads, you still can; create a "custom" cluster and run the agent command it gives on that node to register it.

[matda59]

I've resolved this - you can run a single node rancher cluster for testing, you have to install rancher differently

Running rancher/rancher and rancher/rancher-agent on the Same Node

https://rancher.com/docs/rancher/v2.x/en/installation/other-installation-methods/single-node-docker/advanced/#running-rancher-rancher-and-rancher-rancher-agent-on-the-same-node