Martin
11/11/2024, 11:37 AMDEBUG: Tracking Error: No cloud context default found when I pass the --debug flag. Now the problem happens when I try to build/serve/containerize a service that I wrote I get almost the same but this time as an error Error: [bentos] build failed: No cloud context default found which bricks the CLI command, I can bypass this for serving by passing the --development flag but this doesn't feel like a proper solution because I can't containerize anything or use the full extent of the framework. Suggestions are appreciated 🙇Xipeng Guan
11/11/2024, 12:33 PMbentoml cloud login to log in to bentocloud.Martin
11/11/2024, 1:35 PMbentoml cloud login - am I wrong in that assumption? 🙂Chaoyu
11/11/2024, 6:17 PMserve, build or containerize locally. Login is only needed for push/pull Bentos or managing/scaling deployments with BentoCloud.Chaoyu
11/11/2024, 6:17 PMChaoyu
11/11/2024, 6:18 PMMartin
11/11/2024, 6:57 PMBentoModel - I've also done some depends - I can send minimal code that probably won't wor kbut can help get you the gist? 🙂 Also thank you for the help - it is very appreciatedChaoyu
11/11/2024, 7:04 PMMartin
11/11/2024, 7:27 PMMartin
11/11/2024, 7:28 PMBentofile.yaml is quite simple.Martin
11/11/2024, 7:29 PMpipenv for virtual environments so I rely on that for local testing & I dump them into the requirements.txt later onFrost Ming
11/12/2024, 12:32 AMMartin
11/12/2024, 6:57 AMlocal flag somewhere because I am unsure how to get the bento in that case to package the model file? 🤔Chaoyu
11/12/2024, 7:14 AMFrost Ming
11/12/2024, 10:25 AMBentoModel() to bentoml.models.get() , although there will be a warning message since we don’t recommending doing so