From c987c2c7a04f15b31ee1fafc9beff59f4f56d2b9 Mon Sep 17 00:00:00 2001 From: raphgm Date: Thu, 24 Sep 2026 20:31:23 +0100 Subject: [PATCH] Cite the Zenodo DOI in the paper and README --- README.md | 2 ++ paper/main.tex | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index a896c72..ce0fe17 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,7 @@ # Container Preflight ✈️ +[![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.22941382.svg)](https://doi.org/10.5281/zenodo.22941382) + **Predict container failures before you run, and diagnose them at the root cause when they happen.** `container-preflight` predicts whether a container project will build and run on a machine **before you run it**, and explains each predicted failure once, at its root cause. diff --git a/paper/main.tex b/paper/main.tex index 181085a..055fa7f 100644 --- a/paper/main.tex +++ b/paper/main.tex @@ -253,7 +253,7 @@ \section{Conclusion} Container failures that ``work on my machine'' are relational: they arise between a project and a host. By analyzing both together, grouping unknowns under root causes and learning from observed failures, \tool{} predicted a third of held-out local Docker failures fully and more than half at least partially, before anything ran, and its predictions held up on two real engines. The same join applies to Kubernetes: manifests against a specific cluster's node architectures, allocatable resources, quotas, storage classes, served APIs and admission policies, predicting events such as \texttt{FailedScheduling}, \texttt{ImagePullBackOff} and \texttt{no matches for kind} before deployment, with root-cause grouping and learned rules unchanged. Other future work: runtime-oriented checks such as health checks and container DNS, and a study with developers measuring time to a working setup. \section*{Data availability} -The tool, rules, mined data, samples, labels and scripts are available at \url{https://github.com/raphgm/container-preflight} \todo{archive with a DOI on Zenodo}. +The tool, rules, mined data, samples, labels and scripts are archived on Zenodo at \url{https://doi.org/10.5281/zenodo.22941382} and developed at \url{https://github.com/raphgm/container-preflight}. The rules used for the held-out evaluation are tagged \texttt{eval-frozen}. \bibliographystyle{elsarticle-num} \bibliography{refs}