-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Unable to start Label Studio from latest docker image due to OpenBLAS Operation not permitted error #3070
Comments
OpenMathLib/OpenBLAS#3403 (comment) Try to use this command: |
Unfortunately that doesn't work either:
|
Updating to a newer docker version (20.10.12 in my case) has resolved the issue. It may be beneficial to add a note to the install docs with a minimum supported version |
In my case, the docker update didn't solve the problem. I have to add this in the docker compose:
The problem was about the glibc version. see=>Forum |
下面的命令解决了这个问题,启动docker 容器时 增加选项 :--security-opt seccomp:unconfined docker run -it -p 8080:8080 -v /data:/label-studio/data --security-opt seccomp:unconfined heartexlabs/label-studio:latest bash 然后进到容器里面 用 “label-studio start” 启动 |
牛逼Plus |
I've managed to resolve this issue by changing the Python base image to older Debian release. I think it is better to upgrade OS version to latest or use base image that compatibles older OS version rather than disabling default seccomp profile for security. |
need to upgrade docker version to > 20.10.9, https://medium.com/nttlabs/ubuntu-21-10-and-fedora-35-do-not-work-on-docker-20-10-9-1cd439d9921 |
Describe the bug
When attempting to run the latest docker image, it fails to build due to an OpenBLAS error with operation not permitted. It was previously working on 1.5.0.post0.
To Reproduce
Steps to reproduce the behavior:
docker run -it -p 8080:8080 heartexlabs/label-studio:latest
Expected behavior
Docker image should start up Label Studio as usual
Environment (please complete the following information):
Latest docker tag, 914038b9316d
Docker setup:
ulimit -a from host system:
The text was updated successfully, but these errors were encountered: