New RunLLM response generated: >>>*# Question* 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 do 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 which seems to solve it (no idea if it is the one expected) but the config file is in

~/.flyte/config.yaml

Am I misunderstanding anything or should I open a GitHub issue? Thanks for your help :) # Answer The issue you're encountering is known and has been reported by other users. The

flytectl

command requires a configuration file, and if it is missing, it can cause a segmentation fault. Running

flytectl config init

to generate the configuration file is indeed the correct approach. However, the generated config file is placed in

~/.flyte/config.yaml

by default, not

~/.flyte/config-sandbox.yaml

. You can manually move or copy the file to the expected location or set the

FLYTECTL_CONFIG

environment variable to point to the correct file.

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

Alternatively, you can directly export the path to the generated config file:

export FLYTECTL_CONFIG=~/.flyte/config.yaml

For further clarity, you may consider opening a GitHub issue to suggest updating the documentation to include this step. Would you like more details on this? Sources: - Flytectl config init - Segfault when config file is missing Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1718782536.566099 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.