This message was deleted.

bentoml serve

seems to work just fine after killing a hanging

bentoml build

call.

This is a problem we've encountered due to the python APIs being incredibly slow at moving large numbers of files; do you have something like that (a venv, for example) that you're including in the bento?

Interesting. I'm thinking no in this case. My makefile is in the root folder. The venv is in the root as well. The makefile runs:

build-bento-service:
    #!/bin/bash -e
    BUILD_CONTEXT="./api/"
    bentoml build --bentofile ./api/bentofile.yaml $BUILD_CONTEXT

Hm, ok. I'll take a quick look at what's run after that print.

No! You were right! I did have an extra venv in that folder. Fixed! Thanks @sauyon

Oh awesome! Something we've been considering is adding common venv folder names to the default exclude, but really we should figure out a way around the python APIs eventually...

Is there a

.bentoignore

file? I'd probably use that by default.

There's an

exclude

inside the

bentofile.yaml

, I think, let me just double check.

there is a

.bentoignore

file.

Ah, forgot to come back to this. Yep, you can specify it both in the

.bentoignore

and with the

exclude

parameter of the

bentofile.yaml

.

Thanks!