8000 Reduce laava Docker image size · Issue #76 · formbio/laava · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Reduce laava Docker image size #76

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.

Sign up for GitHub

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 8000 GitHub? Sign in to your account

Jump to bottom
Open
etal opened this issue Jan 30, 2025 · 5 comments
Open

Reduce laava Docker image size #76

etal opened this issue Jan 30, 2025 · 5 comments
Labels
good first issue Good for newcomers

Comments

@etal
Copy link
Contributor
etal commented Jan 30, 2025

The laava Docker image is simple, yet currently builds to over 4GB in size. The majority of that capacity seems to be unused. Keeping it under 1GB would be ideal.

A likely suspect for the bloat is the TexLive documentation pulled in via texlive-latex-extra and texlive-latex-recommended.

There may be other opportunities to streamline the container.
@etal etal added this to the v3.x milestone Jan 30, 2025
@etal etal added the good first issue Good for newcomers label Jan 30, 2025
@etal etal removed this from the v3.x milestone Mar 10, 2025
@mahyarmirrashed
Copy link

Can I try my hand at this @etal ?

@etal
Copy link
Contributor Author
etal commented Apr 9, 2025

@mahyarmirrashed That would be great, thanks!

@mahyarmirrashed
Copy link

@etal Would you be open to moving away from Conda? My suspicion is that it is making the image quite large. I'm going to try my hand at a different packaging tool in the meantime to see how small I can get it.

@mahyarmirrashed
Copy link

I was able to get the image size down to about 2.8GB. Anymore than that will be quite tough. openjdk, gfortran, and gcc seem to be underlying dependencies taking up about 35% of that total usage.

Could you discuss more about your use case for the Docker image? Is it for developers? Is it for shipping to others? Depending on the answer, there might be a better way to go about this.

@etal
Copy link
Contributor Author
etal commented Apr 22, 2025

Good to know, thanks! The docker container creates the execution environment for the Nextflow processes, so it is important. It's also usable for development and standalone execution, but the main purpose is to serve as a reproducible environment for executing the standardized pipeline.

FYI, @dougnukem is the primary maintainer of this repo now and should be able to provide further guidance on landing any improvements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@etal @mahyarmirrashed
0