Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Hi, everyone! Any tips to help debugging Helm errors when trying to start the new sandbox lite? I can only see
```Starting Docker daemon...
Done.
Starting k3s cluster...
Done.
Deploying Flyte...
"flyteorg" has been added to your repositories
Release "flyte" does not exist. Installing it now.
Error: timed out waiting for the condition```

which sandbox are you using ? `sandbox or demo`

I'm using demo, and starting it using Docker, not flytectl

Here's my Docker command:
```docker run -d --name flyte-sandbox --privileged --mount type=bind,src=.,dst=/root -p 30080-30082:30080-30082 -p 30084:30084 -p 30086:30086 -p 30088:30088 -p 30089:30089 <http://cr.flyte.org/flyteorg/flyte-sandbox-lite:sha-5570eff6bd636e07e40b22c79319e46f927519a3|cr.flyte.org/flyteorg/flyte-sandbox-lite:sha-5570eff6bd636e07e40b22c79319e46f927519a3>```

Can you give me your k8s state while running demo sandbox ?
```docker exec -it flyte-sandbox /bin/sh
k3s kubectl get pods -n flyte```

I don't know if this is relevant, but I'm trying to run the sandbox on Windows. The old image, `flyte-sandbox`, started normally, but I'm having trouble with sandbox-lite

Not sure but we can check. Can you post the log here ?

Can you check why are you getting ImagePullBackOff in k8s-dashboard ?

logs.txt

i think its just taking a bizarre amount of time

4min to pull the postgres image, while on a linux machine it takes 1min30

hey, just an update: it really was a timeout. we "fixed" it by injecting the --timeout flag at the entrypoint of the sandbox:
```sed -i "/^helm upgrade/ s/$/ --timeout 20m0s/" /flyteorg/bin/flyte-entrypoint.sh &amp;&amp; tini flyte-entrypoint.sh```

That’s Great but it’s strange that image pull is taking a lot of time on Windows

Docker on Windows is very unstable... The other day, we were unable to start a task because there was no resources available. After some debugging, we found out that there's a bug on WSL2 that makes it so that it doesn't free resources; WSL2 was using 12Gb of RAM and not freeing up any of it...