<#2719 [BUG] Demo cluster not starting on slow int...
# flyte-github
a
#2719 [BUG] Demo cluster not starting on slow internet connection Issue created by nanohanno Describe the bug Starting the demo cluster via
flytectl demo start
returned after ~5 min with this error message
Copy code
+---------------------------------------------+---------------+-----------+
|                   SERVICE                   |    STATUS     | NAMESPACE |
+---------------------------------------------+---------------+-----------+
| flyte-kubernetes-dashboard-7fd989b99d-hgmqb | Pending       | flyte     |
+---------------------------------------------+---------------+-----------+
| minio-55b8c8f4bc-mvjz5                      | Pending       | flyte     |
+---------------------------------------------+---------------+-----------+
| postgres-bdb75f779-cngdp                    | Running       | flyte     |
+---------------------------------------------+---------------+-----------+
Error: Get "<https://127.0.0.1:30086/api/v1/nodes>": dial tcp 127.0.0.1:30086: connect: connection refused
Running
flytectl demo exec -- kubectl describe pod -n flyte
shows that the pending pods are pulling the image before it exits. Also, it turned out that my internet connection was slow but increasing
$FLYTE_TIMEOUT
as recommended in #2197 did not help. Could it be that it fails while waiting for the deployments to be ready ( flyte/docker/sandbox-lite/flyte-entrypoint-dind.sh Line 63 in </flyteorg/flyte/commit/cf24edfbb8c55be5d29c96f7f6ba761ceb44003f|cf24edf> ) when it is still loading the image? The timeout
--timeout=5m
is not affected by changing
$FLYTE_TIMEOUT
I guess. Expected behavior The demo cluster starts succesfully. Additional context to reproduce 1. Slow internet connection :) 2.
flytectl demo start
Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte