-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
ensembl-vep=103.1 won't install into miniconda3 #29069
Comments
Why not use the biocontainers version? These images are built in essentially the same way as you're trying to to. |
This is part of a workflow and our container strategy is to create one image per workflow version. That way we version the whole shebang in parallel and only need to distribute the workflow and the associated image. VEP is only one tool of many in the workflow. |
Heads up, I was able to create an environment
|
@alanhoyle this part at least should now be resolved. (#32576) |
Thanks for letting me know @0xaf1f. I tested this with a simplified Dockerfile that uses FROM mambaorg/micromamba:latest
RUN micromamba install -n base -c conda-forge -c bioconda -c defaults ensembl-vep=103.1 |
I'm trying to install ensembl-vep=103.1 into a Docker image. I'd like to be using
continuumio/miniconda3
to stay future-proof with Python3, but if I do that, it won't work.If I run
docker build
on this I get the following error:However, if I change to
continuumio/miniconda
(i.e. the older Python2 version) it works.With more complex Dockerfiles, I've seen some other issues related to
perl-bioperl>=1.7.2
andt_coffee
vst-coffee
needing a Python < 3.8 and >= 3.7 (default is 3.8.5). (see #20459 for more examples of that)The text was updated successfully, but these errors were encountered: