Hi 🙂 I am seeing that bentoml serve asks for a built bento rather than a path or other such inputs

BENTO is the serving target, it can be the import as:
- the import path of a 'bentoml.Service' instance
- a tag to a Bento in local Bento store
- a folder containing a valid 'bentofile.yaml' build file with a 'service' field, which provides the import path of a 'bentoml.Service' instance
- a path to a built Bento (for internal & debug use only)

Serve from a bentoml.Service instance source code (for development use only): 'bentoml serve fraud_detector.py:svc'

What is the risk of serving from an import path to a bentoml.Service when the app is properly containerized in a dockerfile ? Thanks for your help

It is fine. you can also check the generated

dockerfile

for how we run the

bentoml serve

in a docker container