-
Notifications
You must be signed in to change notification settings - Fork 11
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
pip install of fasttext package is failing #249
Comments
I can reproduce both sides of this - the failure to build via buildpacks and the successful build via the Dockerfile. I also validated that using I'm not sure what the difference is. I assume that the version of To explore this further, we could see if pre-downloading I tried to look at The next thing I'd like to explore is if it's possible to provide build-time/system dependencies in the |
Thanks @robdimsdale for spending time.
Do you refer here to the requirements.txt of the project that is being built? I remember that I tried things in that area like adding |
This simple project, https://github.com/src2img/e2e/tree/python-pip-fasttext, is containing a Python project with just one library in its requirements.txt, fastText.
The sample also contains a Dockerfile that mimics the steps that Paketo imo performs = it uses Python 3.10, pip is updated so that it is at version 23.1.2, it runs as non-root then a
pip install
command with the same arguments that Paketo uses. The Dockerfile succeeds, Paketo does not.Expected Behavior
pip install
succeedsCurrent Behavior
It fails like this:
Possible Solution
Steps to Reproduce
git clone https://github.com/src2img/e2e
cd e2e
git checkout python-pip-fasttext
pack build --builder paketobuildpacks/builder-jammy-full myimage
Motivations
Additional Information
There is a pull request open against fastText that aims to resolve exactly the error from above (facebookresearch/fastText#1331). Though, I am not a Python/Pip expert to assess if it is applicable. So wondering why it works without that fix in the Dockerfile approach.
The text was updated successfully, but these errors were encountered: