Closed kgoderis closed 3 years ago
Hey @kgoderis!
What am I missing here, or what it the docker image on Docker Hub containing that is different from what the Dockerfile ought to build ? (Because, everything runs ok if I used the pre-built image on Docker Hub instead of trying to build one myself)
How are you building the binaries (OS/builder version)? One of the reasons could be that Windows pythonNet isn't the same binary than the one used in Linux, there's a ForceLinuxBuild
cross build flag for windows you could try using.
This is why we created the docker hub images and recommend using them instead.
@Martin-Molinero MacOS X 10.15 with Visual Studio. Is that flag also for MacOS
The reason I want to build my own container is that I need TensorFlow 2.3 and TF-agents for my project. And maybe some other more recent ML libs that are not in the image, or that are due for an upgrade
Hey @kgoderis, Foundation docker image is building again and has been udpated, we will slowly keep updating it to keep up with requests. Suggest directly working on top of the image adding any desired changes/packages, instead of building it from scratch, would this work for you?
Is that flag also for MacOS
yes, it will be required because you are building binaries that are going to be executed by the linux docker image, right? Based on the provided stack exception I can't tell what's wrong, haven't seen it before I believe, but the flag will be a must I think
Closing for now since this isn't a Lean bug. Hope the previous comment solved the issue seen 👍
In https://github.com/QuantConnect/Lean/issues/4930 I already flagged that a docker image can not be build out of the box. I now have managed to do so by moving some packages from conda to pip for installation, as well as change the order of installation a bit. It relates to mlfinlab and fastai basically
The foundation docker looks like
Following the remainder of the instructions I tried to run a python algorithm, it fails when the Python.Runtime is initialised. I get the following output:
Still, in order to get things going, I have changed Python.Runtime.dll.config file to
with a direct reference to the .so in /usr/lib (did not bother creating a virtual env)
What am I missing here, or what it the docker image on Docker Hub containing that is different from what the Dockerfile ought to build ? (Because, everything runs ok if I used the pre-built image on Docker Hub instead of trying to build one myself)