Skip to content
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

Update envs #36

Open
KateSakharova opened this issue Dec 15, 2020 · 2 comments
Open

Update envs #36

KateSakharova opened this issue Dec 15, 2020 · 2 comments
Assignees

Comments

@KateSakharova
Copy link
Contributor

Package libtiff conflicts for: ( - libtiff=4.1.0 )
antismash=4.2.0 -> perl-bioperl -> perl-bioperl-core -> perl-gd -> libgd[version='>=2.2.5,<2.3.0a0'] -> libwebp[version='>=1.0.0,<1.1.0a0'] -> libtiff
....
2)
Package libffi conflicts for: ( - libffi=3.3 )
subprocess32=3.5.4 -> python[version='>=2.7,<2.8.0a0'] -> libffi[version='3.2.*|>=3.2.1,<3.3.0a0|>=3.2.1,<3.3a0|>=3.3,<3.4.0a0']

@caballero
Copy link
Contributor

The issues are in the conda envs, however, docker images can isolate deps and avoid these conflicts.

@mberacochea mberacochea self-assigned this Jan 11, 2022
@mberacochea
Copy link
Member

IMO, we should try to rely on Toil ability to use conda envs. We could specify the tools in the CWL and use the conda resolver in Toil + CWL.

Running the pipeline with containers is the best way but there could be users that can't use containers, the next best thing is conda.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants