-
Notifications
You must be signed in to change notification settings - Fork 463
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
Building container image failes due to missing files #51
Comments
Hi @serverhorror, I don't think you need these Otherwise we could always make a |
Hm, good point. Thanks for raising this. The content of the two files is actually quite basic, however it might help to just add them to this repo as well for completeness. For now, you can just create them yourself:
|
@le-ander do you want to make a new docker folder in the repo in a PR so you're credited for code contribution, or shall I just create these files and do that quickly? |
Hi, I'm just reporting this because it seems pretty unreliable to "pull code from a repo that is broken in the first place". I'm not in the bio* domain at all. Just needed to use it a while ago as a component that would "just work". So I can't comment about the quality of the results. I'm on the software development end and it seems strange to me having to pull in "untrusted" code that is in a random docker repository on the internet or even something where I (the client) doesn't control availability of image. |
I'm not quite sure I understand what you mean. I don't know if you're aware, but the code you are pulling is a workflow in a Jupyter notebook that goes with a tutorial for scRNA-seq analysis. The workflow is extensively documented so that people trying to update their pipelines or learn how to perform the analysis can adapt this to their own needs. None of this is an out-of-the-box pipeline that "just works" on any data and is immediately ready to use. The provision of the docker image is a work-around for people who don't want to install the environment manually (instructions in the README). And the code for this image is primarily there for adaptation purposes. There are plenty of ways in which you can get around the issue you are facing here (including just quickly creating the files that were missing yourself, or removing the relevant lines in the Dockerfile). We are working on updating the workflow now and are adding the missing files. However, none of these changes will make the notebooks here any more of a production level tool that "just works". |
@LuckyMD I am aware what I'm working with. Let me try and rephrase: Usually when dealing with software projects one of the expectations is that the code is able to build succsessfully from source. There are quite a lot of environments where container images are not a workaround but the norm. Even more so, a requirement. So when a As I said. I come from the engineering side. All I'm trying to do is report the findings that I see that make it irreproducible. At least they make it hard to reproduce. |
Yes, thanks for reporting this. We are working to not only make this docker image build from source in #54 but also to update the jupyter notebook so it runs with the newest versions of several dependencies. |
Cleaning up old issues on my profile |
There are at least 2 files missing.
I just did a clean checkout of the repository and wanted to build the image (yes, I'm on Windows -- not all of us have a choice here).
It fails with the following message:
The text was updated successfully, but these errors were encountered: