Docker image is broken #198
Comments
|
I should point out that the issue is very likely not with the Dockerfile or the Docker installation per se, but rather with the |
|
Hi @oathbound01 ! I am not really sure what may be causing your installation issue. Are you using the correct branch ( There is a CI workflow that tries to build and test all containers here https://github.com/cavalab/srbench/blob/docker-compose/.github/workflows/ci-docker.yml. You can also check the logs when trying to build AFP, which seems to be the first algorithm that fails in your local machine https://github.com/cavalab/srbench/actions/runs/11374625817/job/31643734527 |
|
I also noticed that Python 3.13 was released earlier this month, with led to building errors with some algorithms. I had to fix python to 3.12 for one algorithm in order to install it, but the pipeline worked for the others. |
No, I was not using that branch, since it's not mentioned anywhere, and the Having said that, not even that branch seems to work: the standard Dockerfile not only uses broken/dead proxies but also fails to create the mamba environment: Commenting that line, the Dockerfile STILL fails since it's looking for Even switching to the (intended?) Also using the Also, I don't see how Actions has much of anything to do with this, I just want to test out the algorithms inside of a Docker container. At this point, I'm not sure if I'm doing something wrong or if the whole process is just very broken, but in any case a more detailed guide on what I'm REALLY supposed to do wouldn't hurt |
|
Hi @oathbound01 we're sorry for this inconvenience. We're now in the middle of setting things up for a new version of srbench (the docker images is meant to be part of that new version) so things may not yet be working as intended. Notice that this project is being maintained by very few volunteers with limited time (at this point I would say only @gAldeia is actively working on that) so things may not run as fast as we wish! We will look into this issue and let you know when we figure it out what's going on. In the meantime I ask you for your patience and, if you figure things out on your end, please let us know and prepare a PR. The success of such projects depend on the whole community working together as a team :-) |
|
Hey @oathbound01, If you're looking for a stable version of the If you want to use the Docker images, you'll need to switch to the As @folivetti mentioned, it is still a WIP. |
|
There is a small guide on how to use the docker here https://github.com/cavalab/srbench/blob/docker-compose/docs/user_guide.md#for-docker-users |
Unfortunately, switching to that branch has not solved my issues, as you can see with the error above. And I don't really know what is causing this, especially when Actions seems to be working fine, especially considering that I've tried following its workflow (which is the same as the guide you linked me) as closely as I could, yet the build just fails.
The stable release is also giving me issues, but to be fair I think it's just conda being conda and refusing to cooperate on my Fedora machine. I might try it on Arch to see if I can get things moving again, although at this point I'm pretty disheartened and might just wait for the Docker image to be done |
|
I haven't tested it on other operating systems yet. So far, I've managed to get it running in my WSL environment (which can be a bit tricky at times) and on an Ubuntu machine. A last resource: instead of building it, try to pull it from docherhub. I know the CI handles DockerHub uploads, but it's tied to William's account, so I don't have the credentials. This means it's not fully up to date, though some algorithms are available: SRBench on DockerHub. In the meantime, I'll look into the micromamba issue you mentioned. Thanks for bringing it up! |
When trying to install the benchmark through Docker, the process fails when trying to install the first algorithm
For some reason it looks like it's trying to pull from a release candidate version of Python, breaking the entire thing in the process.
I've tried running
to no avail. I've also tried manually updating some dependencies, both in the
base_environment.ymland the specificenvironment.yml, but every time I fix something, I end up breaking something else.It would seem that the fix is simpler than I imagine, yet any combination I try doesn't work.
The text was updated successfully, but these errors were encountered: