Closed s1113950 closed 3 years ago
I have had a similar issue when real hostname wasn't matching rke hostname
Thanks for the tip! I'll double check that
I tried 127.0.0.1
just in case for the address
but still no luck. Not sure where to go from here :( I want to create a cluster locally so either 127.0.0.1
or localhost
should work in theory
Is there an example deployment of a bare metal cluster? https://rancher.com/docs/rke/v0.1.x/en/config-options/nodes/ and https://rancher.com/docs/rke/v0.1.x/en/example-yamls/ don't specify bare metal specifically
my bad, I haven't seen that you trying to run cluster on localhost. Better to use virtual IP (just create new interface) or use VM. I believe when rancher is starting control plane, it actually create proxy service on localhost (just in case you have more that one control plane). Actual control plane wouldn't start because of control place IP in that case also 127.0.0.1.
Try different IP, like 127.0.0.2
I created an alias to the loopback adapter as shown here: https://stackoverflow.com/a/624660
And then that resulted in (after the second time running rke up
)
$ rke up --config local_cluster.yml
WARN[0000] This is not an officially supported version (v0.1.9-rc6) of RKE. Please download the latest official release at https://github.com/rancher/rke/releases/latest
INFO[0000] Building Kubernetes cluster
INFO[0000] [dialer] Setup tunnel for host [127.0.0.2]
INFO[0000] [state] Found local kube config file, trying to get state from cluster
INFO[0000] [reconcile] Local config is not vaild, rebuilding admin config
INFO[0000] [reconcile] Rebuilding and updating local kube config
INFO[0000] Successfully Deployed local admin kubeconfig at [./kube_config_local_cluster.yml]
INFO[0000] [state] Fetching cluster state from Kubernetes
INFO[0030] Timed out waiting for kubernetes cluster to get state
INFO[0030] [network] Deploying port listener containers
INFO[0031] [network] Successfully started [rke-etcd-port-listener] container on host [127.0.0.2]
INFO[0032] [network] Successfully started [rke-worker-port-listener] container on host [127.0.0.2]
INFO[0032] [network] Port listener containers deployed successfully
INFO[0032] [network] Running control plane -> etcd port checks
INFO[0032] [network] Successfully started [rke-port-checker] container on host [127.0.0.2]
INFO[0033] [network] Running control plane -> worker port checks
INFO[0033] [network] Successfully started [rke-port-checker] container on host [127.0.0.2]
INFO[0034] [network] Running workers -> control plane port checks
INFO[0034] [network] Successfully started [rke-port-checker] container on host [127.0.0.2]
FATA[0035] [network] Host [127.0.0.2] is not able to connect to the following ports: [127.0.0.1:6443]. Please check network policies and firewall rules
Is this because it's not a true virtual IP or is it because of something on my end (I'm at work)? @stiks
@s1113950 Unfortunately, local mode is currently supported on Linux based machines only. MacOS is not supported.
Thanks for the info! Is there a timeframe for when that would be supported? Maybe I missed a README somewhere that told me this 😕
@s1113950 it's not in the immediate plans, although I agree it would be nice to have. Will keep this issue as an enhancement request
This issue/PR has been automatically marked as stale because it has not had activity (commit/comment/label) for 60 days. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
local mode is currently supported on Linux based machines only. MacOS is not supported.
still not support? - 3 years passed...
RKE version: I tried
v0.1.8
andv0.1.9-rc6
Docker version: (
docker version
,docker info
preferred)Operating system and kernel: (
cat /etc/os-release
,uname -r
preferred) OSX 10.12.6uname -r
:16.7.0
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO) Bare-metal on my Mac
cluster.yml file:
Steps to Reproduce:
rke up --config local_cluster.yml
Results: If I run that command once, I get this output:
I then see 2 docker containers created:
Logs from apiserver that keep looping:
Specifically the part about
Unable to create storage backend
, so I checked theetcd
logs:I tried creating the dir
/var/lib/rancher/etcd/
and making it owned by my user but that didn't work either. I read some github issues that mention that I might just have to rerunrke up
, so I did that again:Then I checked docker containers again:
and notice the port listeners are now up. I see the same error in the
etcd
logs andapiserver
Any help is appreciated! End goal of our project is to see if we can leverage
rke
to create clusters we need onaws
,bare metal
andgke
, but I can't get pastbare metal
.