Error [BentoctlDockerException]: Failed to tag Docker image, google-compute-engine-iris_classifier:6rqjqqbhbsscvnjh not found.
math-sasso opened this issue · comments
*Describe the bug
When I call bentoctl build as the command below to push an image to my container registry I am always getting this same error.
bentoctl build -b iris_classifier:6rqjqqbhbsscvnjh -f deployment_config.yaml
Created the repository outside-venv-test
Error [BentoctlDockerException]: Failed to tag Docker image, google-compute-engine-iris_classifier:6rqjqqbhbsscvnjh not found.
To Reproduce
What is curios is that my teammates can run it in their computers. My machine is a Ubuntu 20.04.
I installed docker, gcloud and terraform according to those tools documentation
Follow the bentoml tutorial runnning those steps.
- bentoml build
- git clone https://github.com/bentoml/google-compute-engine-deploy.git
- bentoctl operator install google-compute-engine-deploy
- bentoctl build -b iris_classifier:6rqjqqbhbsscvnjh -f deployment_config.yaml
- see error
Environment:
- OS: [Ubuntu 30.04]
- Python Version [e.g. Python 3.8.10]
- BentoML Version [e.g. BentoML-1.0.4]
- Bentoctl Version [e.g. bentoctl-0..3.3]
- google-compute-engine-deploy [v.1.0.2]
My work around is to first call docker containerize to create a docker image and after tag the image in the format expected by bentoctl. This should be done automatically by bentoctl, I still dont know the reason it fails on my machine.
bentoml containerize iris_classifier:6rqjqqbhbsscvnjh
docker tag iris_classifier:6rqjqqbhbsscvnjh google-compute-engine-iris_classifier:6rqjqqbhbsscvnjh
I found the same problem today in Mac using https://github.com/bentoml/aws-ec2-deploy and fixed it by using the same workaround.
This issue should now be fixed in the main branch. @math-sasso @dbuades can you try it out and verify if that works for you? The installation instructions are mentioned here https://github.com/bentoml/bentoctl/blob/main/DEVELOPMENT.md#install-bentoctl-from-source
and thank you for reporting this issue. if this fixes your issue we will cut a new release for this fix.
PR #187 should have fixed this
@jjmachan I confirm this fixes the issue, thanks! Sorry for the delay
thanks for confirming @dbuades. Closing this issue now