This message was deleted.
# ask-for-help
s
This message was deleted.
b
Try bentoml build and push again
f
I just did, it's a different error but without any change to the built bentos, the build containers run until
Copy code
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: <https://pip.pypa.io/warnings/venv>
INFO[0213] Taking snapshot of full filesystem...
After which the build container restarts.
I'm investigating if that is caused by OOMKilled for the builder. Maybe the push+build would have fixed it.
That seems to have been it, @Benjamin Tan is there any way how I can recover my existing deployments from having a "Image Build Failed" badge without having to redo pushing and building for all of them?
b
You can actually build locally and push to the registry that Bento expects
So in my case, I'm using GCR, so you could build locally, tag it in the format and tag that Yatai expects, and push it there
in that case, it would skip the image building step since the image already exists
🙏 1