Open pj-simpson opened 2 years ago
Hey @pj-simpson - glad to see you here, albeit I didn't see this issue when it was originally raised many months ago! I'll certainly take a look as why a fresh creation isn't recreating the rebuilt container as I'd expect to run into the exact same issue.
@pj-simpson I think with this issue, I'll resolve it in the same way you have - I'll remove the blackstone references and build a separate module to perform legislation extraction from text.
Sounds good @ryanmcdonough! All the best and have a Merry Xmas! 🎄
@pj-simpson and you too! Also, removal of blackstone and adding legislation replacement gets it down from 6gb to 1.5gb image and 150mb RAM usage on load so not bad at all!
Description
Whilst I can build and run the ready-made Docker image, as per the projects README, I cannot build the Dockerfile locally without some kind of incompatible requirements error.
To Reproduce
Attempt to build the project's Dockerfile. A sample of the console output:
I've chopped and changed versions and wrangled the order of what gets installed as much as I can, but I just cant get them to work together. My suspicion is that because libraries like Pandas and Numpy use C-extensions, there is an added layer of complexity here. I've even tried running a linux container and installing Python and all the C dependancies needed from scratch, but to no avail, I always come up against this dependancy hell!
Current Workaround
Given that there are fewer endpoints dependant on Blackstone, I've just stripped Blackstone out of my branch. This loses me the 'abbreviation' , 'legislation' and 'named-entity' endpoints, but means I can reliably build and run the container.
my requirements.txt post-removing blackstone
Dockerfile
Possible resolutions