-
Notifications
You must be signed in to change notification settings - Fork 820
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: containerize filed #4117
Comments
Can you send the whole stack trace here? |
|
Can you try docker builder prune --filter type=exec.cachemount |
I tried this and also prune --all, but nothing changed. The same error happens in the same step |
can you send your |
|
I also tried with the example from website and I am getting the same error |
Can you send |
|
What is that warning on L1? |
I didn't understand what you mean |
py:216: UserWarning: resource_tracker: There appear to be 1 leaked semaphore objects to clean up at shutdown
warnings.warn('resource_tracker: There appear to be %d ' |
this not happened again but here full tracelog again:
|
I assume you are using conda? |
yes |
I created new enviroment and followed this guide and i am getting same error |
Can you try this in a virtualenv or non-conda environment? |
tried with virtualenv. same error happens in same step
|
How about your |
I did it with deploy-a-transformer-model-with-bentoml tutorial from docks. So there is no requirments txt file but here is bentofile.yaml:
|
Can you try containerize with |
I tried and added --debug option. I guess same error?
|
Sorry but I tried on both M1 and EC2 with x64 and arm, cannot reproduce this bug with virtualenv |
What version of docker is this? |
I am using a Macbook with an intel chip. I followed the quickstart example project, thinking my model had problems. Here is my docker version:
|
@aarnphm I tried with my friend m1 and it worked. The problem may be related to the Intel chip. Is there any idea about solving this problem? |
@FahriBilici, is this issue resolved? |
For me it was resolved by removing my snap installation of docker and reinstall docker according to the docker documentation. I used the convenience-script for Ubuntu. You might also need the post-installation steps for your docker installation. In the original post the docker installation was not done via snap, however as I face the same trace back except the docker path, your docker installation is likely to cause this issue.
|
Describe the bug
I am trying to containerize a classification model from huggingface. I followed guide from docs and it was working until the containerize step. when I was trying to containerize it in
>>> RUN --mount=type=cache,target=/root/.cache/pip bash -euxo pipefail /home/bentoml/bento/env/python/install.sh
part it throw this errorERROR: failed to solve: process "/bin/sh -c bash -euxo pipefail /home/bentoml/bento/env/python/install.sh" did not complete successfully: exit code: 2
here is the explanation log:
Encountered exception while trying to building image: Command '['/usr/local/bin/docker', 'build', '--tag', 'test:at4eqcbyj2weflg6', '--file', '/private/var/folders/yc/wf15jqy94h32mzth0h_hdw_r0000gn/T/tmpb83n2mw1fsTempFS/env/docker/Dockerfile', '/var/folders/yc/wf15jqy94h32mzth0h_hdw_r0000gn/T/tmpb83n2mw1fsTempFS/']' returned non-zero exit status 1. Traceback (most recent call last): File "/Users/-/opt/anaconda3/envs/solity/lib/python3.10/site-packages/bentoml/_internal/container/__init__.py", line 234, in build return builder.build(**kwargs) File "/Users/-/opt/anaconda3/envs/solity/lib/python3.10/site-packages/bentoml/_internal/container/base.py", line 190, in build raise BentoMLException(str(e)) from None bentoml.exceptions.BentoMLException: Command '['/usr/local/bin/docker', 'build', '--tag', 'test:at4eqcbyj2weflg6', '--file', '/private/var/folders/yc/wf15jqy94h32mzth0h_hdw_r0000gn/T/tmpb83n2mw1fsTempFS/env/docker/Dockerfile', '/var/folders/yc/wf15jqy94h32mzth0h_hdw_r0000gn/T/tmpb83n2mw1fsTempFS/']' returned non-zero exit status 1.
To reproduce
No response
Expected behavior
No response
Environment
bentoml:1.1.1
python:3.10.12
The text was updated successfully, but these errors were encountered: