Closed acesnik closed 2 years ago
Part of the issue with conda
runs in docker
is that they're done without initializing conda
like in a normal commandline setup. Plus, the dependability of containerization can be defeated by changes in conda
.
I found that the mamba version changed between the unbroken and broken versions. Fixing that didn't fix the issue, apparently. https://github.com/smith-chem-wisc/Spritz/pull/223
The Docker build has been working pretty consistently, but without any change in dotnet version, openssl version, or seemingly miniconda Docker image version, it stopped recently. https://github.com/smith-chem-wisc/Spritz/actions
I tracked this down to the issue of
No usable version of the libssl was found
starting to pop up for runningdotnet SpritzModifications.dll
.I confirmed this is also an issue with smithlab/spritz:0.3.4 from DockerHub, which is downloaded by the GUI. This eliminates the possibility that this is due to a change in Docker images. Therefore, it's likely that
conda
has changed slightly that makesdotnet
not detectopenssl
in the same wayThe correct version of
openssl
does show up:Here's an attempt of fixing this, but to no avail yet: https://github.com/smith-chem-wisc/Spritz/compare/dockerfix?expand=1.