busy-flag-55906
04/03/2023, 9:13 AMfaint-garage-50552
04/03/2023, 9:58 AMfaint-winter-65091
04/03/2023, 11:11 AMstraight-horse-87868
04/03/2023, 12:10 PMabundant-camera-87627
04/03/2023, 12:57 PMrancher-webhook
helm-chart custom config (I want to override the default value capi.enabled: true
because it breaks Cluster-API)?polite-piano-74233
04/03/2023, 2:31 PMnutritious-camera-49154
04/03/2023, 3:33 PMmagnificent-rainbow-12629
04/03/2023, 3:53 PMsearch domain.tld
in /etc/resolv.conf. This forces the hostname detection by the RKE to use domain.tld
, as result the hostname is not resolvable with the internal ip addresses. In order to solve this problem I set API Server argument in the UI to use this: kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname
with the idea to force the RKE to use the IP addresses instead of the hostname, unfortunately it doesn't work. I have the feeling that it cannot get the IP addresses on the node and as a last solution it tries to use the hostname. Have you experienced similar issue and could you suggest some solutions?swift-hair-47673
04/03/2023, 3:59 PMbig-jordan-45387
04/03/2023, 8:51 PMcurl --connect-timeout 60 --max-time 60 --write-out "%{http_code}\n" -sS -H "Authorization: Bearer xxxxxxxxx" -H "X-Cattle-Id: yyyyyyyyyyy" -H "X-Cattle-Role-Etcd: true" -H "X-Cattle-Role-Control-Plane: true" -H "X-Cattle-Role-Worker: true" -H "X-Cattle-Node-Name: " -H "X-Cattle-Address: " -H "X-Cattle-Internal-Address: " -H "X-Cattle-Labels: <http://cattle.io/os=linux|cattle.io/os=linux>" -H "X-Cattle-Taints: " "<https://zzzzzzzzzzz>"/v3/connect/agent -o /var/lib/rancher/agent/rancher2_connection_info.json
The command above times out and the script ends up in a loop.
Has anyone any idea of how can I do next to understand what is going on?quaint-oyster-88347
04/04/2023, 12:38 AMquaint-needle-99331
04/04/2023, 12:59 AMdocker-desktop
instead of rancher-desktop
.” Should I be bothered by this or is this something safe to ignore? I’m really new to this, so please forgive me if this question seems too naivemillions-journalist-77187
04/04/2023, 1:45 AMdamp-battery-68469
04/04/2023, 3:40 AMcolossal-jordan-27033
04/04/2023, 9:01 AMjolly-cartoon-45915
04/04/2023, 9:58 AMCannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
enough-carpet-20915
04/04/2023, 10:15 AMhigh-ghost-18943
04/04/2023, 10:45 AMrich-alarm-72570
04/04/2023, 12:53 PMflaky-continent-36535
04/04/2023, 1:14 PMCannot create cluster [my_eks_cluster] because an eksclusterconfig exists with the same name
Do you have any solution for this?flaky-continent-36535
04/04/2023, 1:18 PMenough-pencil-16731
04/04/2023, 2:44 PMbrash-belgium-72831
04/04/2023, 8:17 PMcreamy-accountant-88363
04/04/2023, 9:24 PMbrash-belgium-72831
04/04/2023, 10:31 PMlittle-art-55288
04/04/2023, 11:18 PMcuddly-motorcycle-31750
04/05/2023, 5:40 AMThe TensorFlow library was compiled to use AVX instructions, but these aren't available on your machine.
The Dockerfile goes like this:
FROM tensorflow/tensorflow:1.15.2 as warmup
WORKDIR /tmp
RUN pip install tensorflow-serving-api==1.15.0
According to this site, the promising solution seems to be
You can compile a Tensorflow from the source that does not use the AVX instruction set. Or find an already compiled one on the internet.
Would anyone help edit the current Dockerfile so that it compiles a Tensorflow from the source that does not use the AVX instruction set OR use an already compiled one on the Internet?adamant-caravan-14033
04/05/2023, 6:02 AMadamant-caravan-14033
04/05/2023, 6:30 AMbusy-flag-55906
04/05/2023, 9:11 AM