```Release flyte does not exist Installing it now W0520 06 1

Question

```Release flyte does not exist Installing it now W0520 06 19 59 185843 736 warnings go 70 batch v1beta1 CronJob is deprecated in v1 21+ unavailable in v1 25+ use batch v1 CronJob W0520 06 21 41 614777 736 warnings go 70 batch v1beta1 CronJob is deprecated in v1 21+ unavailable in v1 25+ use batch v1 CronJob NAME flyte LAST DEPLOYED Fri May 20 06 19 57 2022 NAMESPACE flyte STATUS deployed REVISION 1 TEST SUITE None Waiting for Flyte to become ready Terminated Timed out while waiting for the flyteadmin rollout to be created```

Prafulla Mahindrakar · Answer

Can you check the pods in flyte namespace

HaoboGu · Answer

Here s the result

HaoboGu · Answer

```$ kubectl get pods all namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube system coredns 7448499f4d 9t4rk 1 1 Running 0 61m flyte postgres 76c5456bdf 4dlzs 1 1 Running 0 61m flyte flyte kubernetes dashboard 7fd989b99d hz89w 1 1 Running 0 61m flyte minio 699ccf97f9 w7n2w 1 1 Running 0 61m default py39 cacher 0 1 ErrImagePull 0 59m```

Prafulla Mahindrakar · Answer

Can you try to access the console <http localhost 30080 console> Seems the pod are running fine in flyte namespace Can you also do docker ps and check the flyte entry point container logs

HaoboGu · Answer

I found it runs good if I use `flyte demo start` but fails when I use `flytectl sandbox start source `

Prafulla Mahindrakar · Answer

We will have to check the flyteadmin pod logs in case of sandbox start and see whats happening

HaoboGu · Answer

I removed demo project and started again using `flytectl sandbox start source ` After a while I got ```+ + + + | SERVICE | STATUS | NAMESPACE | + + + + | flyte contour contour certgen cj7nz | Running | flyte | + + + + Flyte is ready Flyte UI is available at Add KUBECONFIG and FLYTECTL CONFIG to your environment variable export KUBECONFIG=$KUBECONFIG Users haobogu kube config Users haobogu flyte k3s k3s yaml export FLYTECTL CONFIG= Users haobogu flyte config sandbox yaml ``` But I cannot access to then I checked the pods `kubectl get pods namespace flyte` gives me

HaoboGu · Answer

After waiting 10 minutes I got ```$ kubectl get pods namespace flyte The connection to the server 127 0 0 1 30086 was refused did you specify the right host or port ```

HaoboGu · Answer

The container got killed and I got ```Timed out while waiting for the flyteadmin rollout to be created``` message again in the container s log

Prafulla Mahindrakar · Answer

can you check docker ps a and check the exit code on the failed container Also would suggest try this Can you try ```flytectl sandbox teardown``` ```docker system prune a volumes``` And then ```flytectl sandbox start source ```

HaoboGu · Answer

exit code is 1 ``` tini flyte entrypoi 14 minutes ago Exited 1 57 seconds ago flyte sandbox```

Prafulla Mahindrakar · Answer

And also the logs for this failed container Also any reason you are using sandbox The new ligher way is to use demo You can run the same command as ```flytectl demo start source ```

HaoboGu · Answer

The logs for the failed container ```NAMESPACE flyte STATUS deployed REVISION 1 TEST SUITE None Waiting for Flyte to become ready Terminated Timed out while waiting for the flyteadmin rollout to be created```

Prafulla Mahindrakar · Answer

Not much info here seems like We dont collect support bundles from the failed pods so its harder to know what happened But would suggest to try out the steps i mentioned and use demo instead of sandbox if possible

HaoboGu · Answer

Is there any difference between demo and sandbox I didn t see any from docs

HaoboGu · Answer

`flytectl demo start source ` runs good smile

Prafulla Mahindrakar · Answer

great Demo uses a single binary which bundles all the flyte components and is much lighter and faster to bring up due to this reason I think we still are working on getting docs for explaining the differences between the two

HaoboGu · Answer

many thanks

Ketan (kumare3) · Answer

Ya use demo start

Ketan (kumare3) · Answer

We are trying to make that default

Ketan (kumare3) · Answer

Sandbox mimics a full deploy

Ketan (kumare3) · Answer

But demo is lighter and actually can be run in production