Hello, I am new to Rancher, I tried it and I have this problem:
I have installed Rancher v2.2.4 on my local docker machine (v18.09.5, build e8ff056dbc) via this command: docker run -d --restart=unless-stopped -p 2804:80 -p 2805:443 rancher/rancher
My goal for now is to make 1 cluster with 1 node.
After install, I successfully got into settings, logged in and started adding new cluster.
I selected this settings:
Custom - From my own existing nodes
Kubernetes version - v1.13.5-rancher1-3
Network provider - Canal
Cloud provider - none
This settings should be right, but I tried other combinations, but it still didnt work.
In adding nodes I selected all (etcd, Control plane, worker). Again, I tried other combinations, but with no result.
I successfully installed needed containers via provided command and cluster started provisioning.
And then I got this error: Failed to get job complete status for job rke-network-plugin-deploy-job in namespace kube-system.
Then I noticed, that rancher on some point was adding constantly these 2 containers, which couldn’t start:
Every container listed below is from image rancher/rancher-agent:v2.2.4.
Logs messages were repeating, so I copied a little sample.
Docker logs cranky_ramanujan: time="2019-07-11T07:48:53Z" level=info msg="Connecting to wss://my_url.com:2805/v3/connect with token x2sj9pts4x8pmlnh858hmcvm8hnll4ct9fbn4jdkv9prkktkn52ns9"
time="2019-07-11T07:48:53Z" level=info msg="Connecting to proxy" url="wss://my_url.com:2805/v3/connect"
time="2019-07-11T07:48:53Z" level=error msg="Failed to connect to proxy" error="websocket: bad handshake"
time="2019-07-11T07:48:53Z" level=error msg="Failed to connect to proxy" error="websocket: bad handshake"
Docker logs eager_haibt: time="2019-07-11T07:50:41Z" level=info msg="Error while getting agent config: invalid response 500: cluster not found"
Docker logs share-mnt: Error response from daemon: {"message":"No such container: kubelet"} Error: failed to start containers: kubelet
+ sleep 2
Docker logs elegant_austin: time="2019-07-11T07:53:49Z" level=info msg="Error while getting agent config: invalid response 500: cluster not found"
I had the same issue. My nodes got just about 25% free disc storage left. Once I deleted old data and had about 75% of free disc space on all of my 3 nodes the rke-network-plugin was deployed successfully.