@ancient-wolf-19325 I am just getting started with flyte and I am working on setting up a dev environment that uses vs code dev containers. When I run flytectl demo start I can see it download the image but it errors out like this

flytectl demo start
INFO[0000] [0] Couldn't find a config file []. Relying on env vars and pflags. 
🧑‍🏭 Bootstrapping a brand new Flyte cluster... 🔨 🔧
🐋 Going to use Flyte v1.12.0 release with image <http://cr.flyte.org/flyteorg/flyte-sandbox-bundled:sha-bd3ed0d2684bddbc8fad1c26d4bc39a86e91077f|cr.flyte.org/flyteorg/flyte-sandbox-bundled:sha-bd3ed0d2684bddbc8fad1c26d4bc39a86e91077f> 
🧑‍🏭 Starting container... 🔨 🔧
😬 Something went wrong: Failed to start Sandbox container 🐋, Please check your docker client and try again. 
Error: Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /home/vscode/.flyte
{"json":{},"level":"error","msg":"Error response from daemon: invalid mount config for type \"bind\": bind source path does not exist: /home/vscode/.flyte","ts":"2024-05-19T19:21:46Z"}

The error indicates that the bind source path

/home/vscode/.flyte

does not exist. This path is required for Flyte to mount necessary configurations. You need to create this directory before running

flytectl demo start

.

mkdir -p /home/vscode/.flyte

Would you like more details on setting up Flyte with VS Code dev containers? Sources: - Flyte Community Discussion 1 - Flyte Community Discussion 2 - Flyte Community Discussion 3 👍 0 button 👎 1 button 💡 Hint: Mention @ancient-wolf-19325 in the thread for followups.

that path does exist

@bitter-book-65639 what version are you using?

I believe this is the issue @freezing-airport-6809 https://flyte-org.slack.com/archives/C01P3B761A6/p1716154476595279