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

Flyte

Hi <@U055NEU23DG>
Thanks for the reply!
That’s how we replace it with our file. However, we always face the problem like the following, when running the setp3 (*3. Run all Flyte components (flyteadmin, flytepropeller, datacatalog, flyteconsole, etc) in a single binary.*) in  <https://docs.flyte.org/en/latest/community/contribute.html#how-to-setup-dev-environment-for-flyteidl-flyteadmin-flyteplugins-flytepropeller-datacatalog-and-flytestdlib|guide>

with command
```POD_NAMESPACE=flyte ./flyte start --config flyte-single-binary-local.yaml```
We will see.
```{"json":{"src":"controller.go:602"},"level":"warning","msg":"Failed to create cluster resources for namespace [flytesnacks-staging] with err: Failed to read config template dir [flytesnacks-staging] for namespace [/root/.flyte/cluster-resource-templates] with err: open /root/.flyte/cluster-resource-templates: no such file or directory","ts":"2023-07-23T21:48:22+08:00"}```

Seems we miss some context or setting to start our command.

any good suggestion?

```(dev) root@googler:/mnt/c/code/dev/flyte# echo $HOME
/root```

I see, <@U055NEU23DG> Thanks for your time.

```(dev) root@googler:~/.flyte# tree .
.
├── config-sandbox.yaml
├── k3s
│   └── k3s.yaml -&gt; /var/lib/flyte/config/kubeconfig
├── node
│   └── password
├── sandbox
│   └── kubeconfig
└── webhook-certs
    ├── ca.crt
    ├── tls.crt
    └── tls.key

4 directories, 7 files```