Hello everyone! I am new to Flyte and love it already 🙂 While getting through the Getting started guide, I noticed that some of the commands did not work for me. I could not find anyone else having this issue on GitHub or the web. In the First Step of "Running a workflow locally": https://docs.flyte.org/en/latest/getting_started_with_workflow_development/running_a_workflow_locally.html#id2 I export the env variable pointing to a config file for `flytectl`:

export FLYTECTL_CONFIG=~/.flyte/config-sandbox.yaml

Problem is that this config file was not previously created and does not exist. As a result Step 4 of the same guide fails

flytectl create project [..]

raises a seg fault. Running

flytectl config init

creates such a config file for me (no idea if it is the one expected) but the config file is in

~/.flyte/config.yaml

Setting

FLYTECTL_CONFIG

to this new file seemingly solves this issue and allow me to finish this tutorial. Am I misunderstanding anything or should I open a GitHub issue? Thanks for your help :)

The

config-sandbox

should be created when you run

flytectl demo start

Did you find issues running that step?

Thanks @average-finland-92144 That steps ran fine but at the end of it I do not have the

config-sandbox

(flyte-example) ➜  my_project git:(main) ✗ export FLYTECTL_CONFIG=~/.flyte/config-sandbox.yaml
(flyte-example) ➜  my_project git:(main) ✗ sudo systemctl start docker                        
(flyte-example) ➜  my_project git:(main) ✗ sudo 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... 🔨 🔧
⏳ Waiting for cluster to come up... ⏳
🧑‍🏭 Activated context "flyte-sandbox"!
+-----------------------------------------------------+---------------+-----------+
|                       SERVICE                       |    STATUS     | NAMESPACE |
+-----------------------------------------------------+---------------+-----------+
| flyte-sandbox-docker-registry-8648675c45-t4qqv      | Running       | flyte     |
+-----------------------------------------------------+---------------+-----------+
| flyte-sandbox-kubernetes-dashboard-6757db879c-m4xhn | Running       | flyte     |
+-----------------------------------------------------+---------------+-----------+
| flyte-sandbox-postgresql-0                          | Running       | flyte     |
+-----------------------------------------------------+---------------+-----------+
| flyte-sandbox-minio-85dc5446b6-rwzkk                | Running       | flyte     |
+-----------------------------------------------------+---------------+-----------+
| flyte-sandbox-buildkit-675bff7bd9-nnzrq             | Running       | flyte     |
+-----------------------------------------------------+---------------+-----------+
| flyte-sandbox-proxy-8f4f7fd9b-dspqq                 | Running       | flyte     |
+-----------------------------------------------------+---------------+-----------+
| flyteagent-798cc9846-r76gr                          | Running       | flyte     |
+-----------------------------------------------------+---------------+-----------+
| flyte-sandbox-64f5656c8f-2r8np                      | Running       | flyte     |
+-----------------------------------------------------+---------------+-----------+
👨‍💻 Flyte is ready! Flyte UI is available at <http://localhost:30080/console> 🚀 🚀 🎉 
❇️ Run the following command to export demo environment variables for accessing flytectl
        export FLYTECTL_CONFIG=/root/.flyte/config-sandbox.yaml 
🐋 Flyte sandbox ships with a Docker registry. Tag and push custom workflow images to localhost:30000
📂 The Minio API is hosted on localhost:30002. Use <http://localhost:30080/minio/login> for Minio console, default credentials - username: minio, password: miniostorage
(flyte-example) ➜  my_project git:(main) ✗ ls ~/.flyte/config-sandbox.yaml
ls: cannot access '/home/guillaume/.flyte/config-sandbox.yaml': No such file or directory

What about

/root/.flyte/config-sandbox.yaml

?

Indeed, it is there! Why is that? I also had to run

flytectl demo start

with

sudo

. As otherwise, I had permission denied.

I think the $HOME folder when you sudo is effectively

/root

Regarding the docker build file, not sure if it's a permissions problem too

Hey @ancient-account-54527 can you share the error you get with

flytectl demo start

without sudo?

Hey @brief-window-55364 I just did and realized it was due to docker. I had to go through some post-linux install tutorial https://docs.docker.com/engine/install/linux-postinstall/ and this is fixed!

I just reproduced your issue using flytekit 1.10.2. The contents of the script are here but in previous versions it was created automatically when creating the project

Perfect, I will use that one. Thanks @average-finland-92144