Hi, I'm attempting to run "flytectl demo start" in...
# flyte-support
f
Hi, I'm attempting to run "flytectl demo start" in both WSL Ubuntu 22.04 and 20.04, but when the cluster is running, I encounter dns issues. ping google.com doesn't work. Not surprisingly, workflows that depends on pulling images fails. I have upgraded to latest version 0.9.2. After tearing the cluster down, I'm able to ping google.com after a while. I have tried the /etc/resolv.conf
namespace 8.8.8.8
fix. It doesn't solve the problem, and it's not the root cause. Can you help me? Below are some details: Error message from running hello world example:
Grace period [3m0s] exceeded|containers with unready status: [a6plbgwnbzb7fqxb7nsb-n0-0]|Back-off pulling image "<http://cr.flyte.org/flyteorg/flytekit:py3.10-1.13.5|cr.flyte.org/flyteorg/flytekit:py3.10-1.13.5>"
Pods info:
Copy code
flytectl demo exec -- kubectl get pods -A
INFO[0000] [0] Couldn't find a config file []. Relying on env vars and pflags.
NAMESPACE     NAME                                                  READY   STATUS    RESTARTS   AGE
flyte         flyte-sandbox-kubernetes-dashboard-5b4465fcfb-dtqnd   1/1     Running   0          111s
flyte         flyte-sandbox-docker-registry-7fc74d9f75-d625h        1/1     Running   0          111s
flyte         flyte-sandbox-buildkit-55b956cfbb-gbdp4               1/1     Running   0          111s
kube-system   coredns-6799fbcd5-ztvch                               1/1     Running   0          111s
kube-system   local-path-provisioner-84db5d44d9-57qqb               1/1     Running   0          111s
kube-system   metrics-server-67c658944b-xzj96                       1/1     Running   0          111s
flyte         flyte-sandbox-minio-797448f46d-v26pd                  1/1     Running   0          111s
flyte         flyte-sandbox-postgresql-0                            1/1     Running   0          111s
flyte         flyte-sandbox-proxy-74bcd9c78f-vzxcq                  1/1     Running   0          111s
flyte         flyteagent-54fc99879c-9x8j2                           1/1     Running   0          111s
flyte         flyte-sandbox-5d89dbd6fc-l99c9                        1/1     Running   0          111s
Logs from coredns pod:
Copy code
flytectl demo exec -- kubectl logs coredns-6799fbcd5-ztvch -n kube-system
INFO[0000] [0] Couldn't find a config file []. Relying on env vars and pflags.
[WARNING] No files matching import glob pattern: /etc/coredns/custom/*.override
[WARNING] No files matching import glob pattern: /etc/coredns/custom/*.server
.:53
[WARNING] No files matching import glob pattern: /etc/coredns/custom/*.override
[WARNING] No files matching import glob pattern: /etc/coredns/custom/*.server
[INFO] plugin/reload: Running configuration SHA512 = b941b080e5322f6519009bb49349462c7ddb6317425b0f6a83e5451175b720703949e3f3b454a24e77f3ffe57fd5e9c6130e528a5a1dd00d9000e4afd6c1108d
CoreDNS-1.10.1
linux/amd64, go1.20, 055b2c3
[WARNING] No files matching import glob pattern: /etc/coredns/custom/*.override
[WARNING] No files matching import glob pattern: /etc/coredns/custom/*.server
[ERROR] plugin/errors: 2 flyte-sandbox-grpc. AAAA: read udp 10.42.0.4:39625->172.24.176.1:53: i/o timeout
[ERROR] plugin/errors: 2 flyte-sandbox-http. AAAA: read udp 10.42.0.4:48988->172.24.176.1:53: i/o timeout
[ERROR] plugin/errors: 2 flyte-sandbox-kubernetes-dashboard. AAAA: read udp 10.42.0.4:49184->172.24.176.1:53: i/o timeout
[ERROR] plugin/errors: 2 flyte-sandbox-minio. AAAA: read udp 10.42.0.4:47493->172.24.176.1:53: i/o timeout
[ERROR] plugin/errors: 2 flyte-sandbox-http. AAAA: read udp 10.42.0.4:51184->172.24.176.1:53: i/o timeout
[ERROR] plugin/errors: 2 flyte-sandbox-grpc. AAAA: read udp 10.42.0.4:48524->172.24.176.1:53: i/o timeout
[ERROR] plugin/errors: 2 flyte-sandbox-http. AAAA: read udp 10.42.0.4:57235->172.24.176.1:53: i/o timeout
[ERROR] plugin/errors: 2 flyte-sandbox-grpc. AAAA: read udp 10.42.0.4:57592->172.24.176.1:53: i/o timeout
[ERROR] plugin/errors: 2 flyte-sandbox-kubernetes-dashboard. AAAA: read udp 10.42.0.4:40954->172.24.176.1:53: i/o timeout
[ERROR] plugin/errors: 2 flyte-sandbox-minio. AAAA: read udp 10.42.0.4:48398->172.24.176.1:53: i/o timeout
[ERROR] plugin/errors: 2 flyte-sandbox-http. AAAA: read udp 10.42.0.4:34119->172.24.176.1:53: i/o timeout
...
ping google.com changes logs messages when cluster goes from starting to running:
Copy code
64 bytes from arn09s22-in-f14.1e100.net (142.250.74.46): icmp_seq=68 ttl=52 time=23.3 ms
64 bytes from arn09s22-in-f14.1e100.net (142.250.74.46): icmp_seq=69 ttl=52 time=23.1 ms
64 bytes from arn09s22-in-f14.1e100.net (142.250.74.46): icmp_seq=70 ttl=52 time=29.2 ms
64 bytes from arn09s22-in-f14.1e100.net (142.250.74.46): icmp_seq=71 ttl=52 time=18.3 ms
64 bytes from arn09s22-in-f14.1e100.net (142.250.74.46): icmp_seq=72 ttl=52 time=19.4 ms
64 bytes from 142.250.74.46: icmp_seq=73 ttl=52 time=17.6 ms
64 bytes from 142.250.74.46: icmp_seq=74 ttl=52 time=24.7 ms
64 bytes from 142.250.74.46: icmp_seq=75 ttl=52 time=31.0 ms
64 bytes from 142.250.74.46: icmp_seq=76 ttl=52 time=18.5 ms
Later, ping google.com fails. On ubuntu 20.04:
Copy code
ping: google.com: Temporary failure in name resolution
d
I think this is a wsl problem
can you help me install the docker desktop and try again?
maybe this will help, but if not, there's no maintainer using wsl to develop flyte.
f
Thanks for quick reply. I actually don't use docker desktop, just wsl, distros and docker installed directly in the distros. It appears that there are installeres for Mac and Linux only, and if wsl is not used to develop flyte, how is intended that users on Windows should work with Flyte? Perhaps there are some docs I have missed?
Regarding how I set up wsl, I have to look into it, because it was a while ago. I will try to recreate the environment from scratch and describe the setup in detail
d
how is intended that users on Windows
I think this is for window's OS, not wsl, wsl is ubuntu, but with lots of bugs in my opinion.
f
I made it work by using a fixed DNS configuration in Docker with the file /etc/docker/deamon.json:
Copy code
{
   ["8.8.8.8", "8.8.4.4."] 
}
followed by restarting wsl using
wsl --shutdown