Nagraj, V.; Turner, S. D.; Magee, N.

Containerization enables portable, reproducible, and scalable scientific computing. However, container development, documentation, and deployment practices can vary widely, even within a single domain. Understanding patterns of how containers are implemented in real-world settings can inform community guidelines, quality scoring rubrics, and systems to automate software review. Focusing on bioinformatics as an exemplar domain, we surveyed published software tools to find applied containerization examples. After identifying >250 tools to review, we annotated metadata regarding version control, asset provenance, and general container image health and tested the ability to build and pull the container images in a purpose-built evaluation platform (https://github.com/vpnagraj/socr8s). The majority of images tested did not build successfully in our environment. Of the tool characteristics we tracked, the strongest predictor of build success was version control activity. Tools with commits in the preceding two years were roughly twice as likely to build. Deeper assessment of failures identified a variety of issues, including missing assets and broken dependency chains. While many tools had published images accessible in open registries, 24% could neither be built nor pulled. Images tended to be large, with median size of 1.57GB for those that were able to be built. Where image specification files were available, we found that more advanced container orchestration and build techniques were uncommon. Our results highlight areas of improvement in how containerized tools are built and maintained in bioinformatics and scientific computing software in general.