Papers › Aristotle Cloud Federation: Container Runtimes Technical Report

Aristotle Cloud Federation: Container Runtimes Technical Report

24 Sep 2021arXiv:2109.12186links table onlyarchive 2025-07-28

Peter Z. Vaillancourt, Bennett Wineholt, Tristan J. Shepherd, Sara C. Pryor, Jeffrey Lantz, Richard Knepper, Rich Wolski, Christopher R. Myers, Ben Trumbore, Resa Reynolds, Jodie Sprouse, David Lifka

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

A National Science Foundation-sponsored container runtimes investigation was conducted by the Aristotle Cloud Federation to better understand the challenges of selecting and using Docker, Singularity, and X-Containers. The main goal of this investigation was to identify the "pain points" experienced by users when selecting and using containers for scientific research and to share lessons learned. Application performance characteristics are included in this report as well as user experiences with Kubernetes and container orchestration on cloud and HPC platforms. Scientists, research computing practitioners, and educators may find value in this report when considering the use and/or deployment of containers or when preparing students to meet the unique challenges of using containers in scientific research.

PaperPDFCode

Code

federatedcloud/kubernetes-mpi-clusters officialmentioned in paper report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

Not run by Syntology. Nothing on this page verifies that the listed code works.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections