-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Cannot complete a Docker build using v.3.8.2 #13649
Comments
What's the platform tag within your docker container? The spacy-3.8.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl wheel built successfully for the release. Regarding the ubuntu test, that was cancelled due to the unrelated failure on Windows (the CI has fail fast enabled). The CI is green on master, which is the same state. |
I have a similar error, building a docker container on Amazon Linux 2023 Python 3.12 base image (i.e. It might be the required thinc version that it can't get a built wheel for, not spacy itself? Downgrading to spacy 3.7.5 also succeeded for me as a workaround.
|
Hi @honnibal , We run this particular job in a "Large" GitHub runner. From the run in question, here is some additional detail:
And our app is currently using this Python image in the Dockerfile, in case that factors in as well: Is this helpful, or are you asking for something different from the run outputs? Thanks again, |
Hi @honnibal ,
Curious if an upcoming version might address this, or if there is anything we could do on our end? Thanks, |
It looks like this problem still exists in the newest release, @honnibal :
Issue #13606
The Docker image build hangs in the same place...
It looks like the specific test run for Python 3.12.5 on the latest Ubuntu was canceled...here:
https://github.com/explosion/spaCy/actions/runs/11127868506/job/30921252535
How to reproduce the behaviour
Make sure your project pulls the latest spaCy (3.8.2 as of now), then attmept to build a Docker image. In our case, this happens withing a GitHub workflow, and we build them on latest Ubuntu.
Your Environment
Our workaround will be to revert back to a hard pin of spaCy 3.7.5 for now, but we'd certainly like to get back to the latest releases once this issue is sorted. Thanks!
The text was updated successfully, but these errors were encountered: