Closed ChristianMarzahl closed 1 year ago
Thanks for reporting this bug. We will need to handle path-like objects separately for this.
I notice that you are using a bento_config.yaml
. I suggest you not include this inside the bento, rather mounting this into the container as BENTOML_CONFIG
content is subject to change in the future with newer versions.
docker run -e BENTOML_CONFIG=/home/bentoml/bentoml_config.yaml -v /path/to/your_config_file_locally.yaml:/home/bentoml/bentoml_config.yaml ...
Dear @aarnphm,
Thank you very much for your quick response and pointing out this solution.
@aarnphm
do you have a plan support DEFAULT_BENTO_CONFIG?
like a
# dockerfile
DEFAULT_BENTO_CONFIG = "configuration.yaml"
if exists("$BENTO_PATH/configuration.yaml"): # check file exists
export BENTO_CONFIG="$BENTO_PATH/configuration.yaml"
This is an anti-pattern to include the bento_config into the bento, and we won't do anything special check for the config namespace yet.
BENTOML_CONFIG
should always be mounted into the container rather than being included in the container. The reason why I have already covered above.
So the answer is No 😃
Describe the bug
Setting environment variables with path characters result in an error, this prohibits a large range of valid environment variables from being set without a custom build. #3268
results in:
To reproduce
Expected behavior
Behaviour like a standard script export:
Environment
bentoml: >1.0.5 python: 3.8.13 os: UBUNTU 20.04