Ten simple rules for writing Dockerfiles for reproducible data science.
editorial · Level V
Where this comes from
- Record sourced from PubMed, PMID 33170857.
- Also identified by DOI 10.1371/journal.pcbi.1008316 and PMC identifier 7654784.
- Licence recorded as CC BY.
- The licence permits redistribution, so the abstract is shown in full and the full text is available from the publisher.
Abstract
Computational science has been greatly improved by the use of containers for packaging software and data dependencies. In a scholarly context, the main drivers for using these containers are transparency and support of reproducibility; in turn, a workflow's reproducibility can be greatly affected by the choices that are made with respect to building containers. In many cases, the build process for the container's image is created from instructions provided in a Dockerfile format. In support of this approach, we present a set of rules to help researchers write understandable Dockerfiles for typical data science workflows. By following the rules in this article, researchers can create containers suitable for sharing with fellow scientists, for including in scholarly communication such as education or scientific papers, and for effective and sustainable personal workflows.
Medical subject headings
- Data Science
- Guidelines as Topic
- Programming Languages
- Software