BioContainers

BioContainers is a curated registry of standardised, pre-built containers for bioinformatics and biological research software.

  • Development
  • Infrastructure
  • Tools & Utilities
BioContainers is a curated registry of standardised, pre-built containers for bioinformatics and biological research software. It lets scientists run complex analysis tools on any computer without managing dependencies or wrestling with installation steps, ensuring scientific results are easy to share and reproduce.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

58/100 Fair

Maintained
69last commit 137 days ago
Popular
58814 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
67no serious findings, 2 minor, CI, tests, OpenSSF Scorecard 4.4/10

Based on 4 of 5 factors.

GitHub stars
814
Open issues
44
Last commit
2026-07-07
Latest release
Crux
License
Apache-2.0
Activity
stale

Checked 15 days ago - source: GitHub (BioContainers/containers)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Download InterProScan data first Get the InterProScan data package, check its MD5 (a file-checksum), and unpack it before running the container. This gives the tool the large biological database it needs; without it, scans can fail or produce no results. source
  • Mount reference folders into the container Point the container mount option at your local reference-data folder, using -v for Docker or -B for Singularity/Apptainer. This makes your files visible inside the container; if it is missing or wrong, the tool will look for data in the wrong place and fail. source
  • Show GUI containers on your screen For graphical tools like denovoGUI, pass your DISPLAY variable (the computer screen setting) and mount /tmp/.X11-unix (the X11 window-system folder) into the container. This lets the app draw its window on your computer; without it, the container may start but you won't see the interface. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why can BioContainers be used to run many bioinformatic applications on clusters?

They are based on popular container technology, which makes deployment and portability easier.

How can BioContainers help add newer bioinformatic application versions?

They are based on container technology, which allows RCAC to keep adding newer versions of bioinformatic applications.

How many BioContainers images are available for scientific tools?

BioContainers maintains more than 100,000 containers for over 12,000 tools.

What reproducibility goal does BioContainers state for scientific software?

BioContainers aims to make scientific software easy to discover, install, and run reproducibly.

Answers sourced from biocontainer-doc.readthedocs.io, github.com

Community

Collected 48 days ago - public community threads