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

wave conda: always installing procps in containers #3615

Closed

Conversation

marcodelapierre
Copy link
Member

Signed-off-by: Marco De La Pierre [email protected]

@marcodelapierre
Copy link
Member Author

Would close nextflow-io/nf-wave#6

@marcodelapierre
Copy link
Member Author

@pditommaso the test fail is a rate limit being hit.
if you think this is worthwile we can rerun

@pditommaso
Copy link
Member

It would be better to rely on the Conda recipe to install this to avoid depending on distro specific command

https://anaconda.org/conda-forge/procps-ng

@marcodelapierre
Copy link
Member Author

marcodelapierre commented Feb 9, 2023

Do you know whether procps-ng has the same API/CLI than standard ps?

Or otherwise would you share privately the ps calls you are using in the Tower backend, and expected outputs?

@marcodelapierre
Copy link
Member Author

Ok, just did some checks on base images for ubuntu, debian, opensuse, alpine, amazonlinux.
I am a bit ignorant on official naming for ubuntu tools, but turns out these folks actually use procps-ng as the provider for ps. So the conda installation should be fine.
Soon I am going to update the PR accordingly.

@marcodelapierre
Copy link
Member Author

Done, please have a look when you get the chance.

@@ -397,6 +397,7 @@ class WaveClient {
FROM ${config.condaOpts().mambaImage}
COPY --chown=\$MAMBA_USER:\$MAMBA_USER conda.yml /tmp/conda.yml
RUN micromamba install -y -n base -f /tmp/conda.yml && \\
micromamba install -y -n base conda-forge::procps-ng && \\
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking that instead of automagically adding dependencies in the container build it could be added an option to provide one or packages that should be a added in the resulting container e.g.

wave.conda.basePackages = 'conda-forge::procps-ng'

or

wave.conda.addPackages = 'conda-forge::procps-ng'

WDT?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like wave.conda.basePackages, I think it conveys the message.
Will implement as soon as I am finished with this week's duties.

@pditommaso
Copy link
Member

pditommaso commented Mar 1, 2023

Ok, I went ahead with this. Have a look at 7e82781. Thanks Marco!

@pditommaso pditommaso closed this Mar 1, 2023
@marcodelapierre
Copy link
Member Author

cool!

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

Successfully merging this pull request may close these issues.

2 participants