Bugs in pods: Understanding bugs in container runtime systems

Container Runtime Systems (CRSs), which form the foundational infrastructure of container clouds, are critically important due to their impact on the quality of container cloud implementations. However, a comprehensive understanding of the quality issues present in CRS implementations remains lackin...

Full description

Saved in:
Bibliographic Details
Main Authors: YU, Jiongchi, XIE, Xiaofei, ZHANG, Ceng, CHEN, Sen
Format: text
Language:English
Published: Institutional Knowledge at Singapore Management University 2024
Subjects:
Online Access:https://ink.library.smu.edu.sg/sis_research/9445
https://ink.library.smu.edu.sg/context/sis_research/article/10445/viewcontent/Bugs_in_Pods__Understanding_Bugs_in_Container_Runtime_Systems.pdf
Tags: Add Tag
No Tags, Be the first to tag this record!
Institution: Singapore Management University
Language: English
id sg-smu-ink.sis_research-10445
record_format dspace
spelling sg-smu-ink.sis_research-104452024-11-11T08:05:47Z Bugs in pods: Understanding bugs in container runtime systems YU, Jiongchi XIE, Xiaofei ZHANG, Ceng CHEN, Sen Container Runtime Systems (CRSs), which form the foundational infrastructure of container clouds, are critically important due to their impact on the quality of container cloud implementations. However, a comprehensive understanding of the quality issues present in CRS implementations remains lacking. To bridge this gap, we conduct the first comprehensive empirical study of CRS bugs. Specifically, we gather 429 bugs from 8,271 commits across dominant CRS projects, including runc, gvisor, containerd, and cri-o. Through manual analysis, we develop taxonomies of CRS bug symptoms and root causes, comprising 16 and 13 categories, respectively. Furthermore, we evaluate the capability of popular testing approaches, including unit testing, integration testing, and fuzz testing in detecting these bugs. The results show that 78.79% of the bugs cannot be detected due to the lack of test drivers, oracles, and effective test cases. Based on the findings of our study, we present implications and future research directions for various stakeholders in the domain of CRSs. We hope that our work can lay the groundwork for future research on CRS bug detection. 2024-09-01T07:00:00Z text application/pdf https://ink.library.smu.edu.sg/sis_research/9445 info:doi/10.1145/3650212.3680366 https://ink.library.smu.edu.sg/context/sis_research/article/10445/viewcontent/Bugs_in_Pods__Understanding_Bugs_in_Container_Runtime_Systems.pdf http://creativecommons.org/licenses/by-nc-nd/4.0/ Research Collection School Of Computing and Information Systems eng Institutional Knowledge at Singapore Management University Container runtime Empirical studies Manual analysis Quality issues Root cause Run-time systems Runtimes Software testing Systems implementation Unit testing Computer Engineering Software Engineering
institution Singapore Management University
building SMU Libraries
continent Asia
country Singapore
Singapore
content_provider SMU Libraries
collection InK@SMU
language English
topic Container runtime
Empirical studies
Manual analysis
Quality issues
Root cause
Run-time systems
Runtimes
Software testing
Systems implementation
Unit testing
Computer Engineering
Software Engineering
spellingShingle Container runtime
Empirical studies
Manual analysis
Quality issues
Root cause
Run-time systems
Runtimes
Software testing
Systems implementation
Unit testing
Computer Engineering
Software Engineering
YU, Jiongchi
XIE, Xiaofei
ZHANG, Ceng
CHEN, Sen
Bugs in pods: Understanding bugs in container runtime systems
description Container Runtime Systems (CRSs), which form the foundational infrastructure of container clouds, are critically important due to their impact on the quality of container cloud implementations. However, a comprehensive understanding of the quality issues present in CRS implementations remains lacking. To bridge this gap, we conduct the first comprehensive empirical study of CRS bugs. Specifically, we gather 429 bugs from 8,271 commits across dominant CRS projects, including runc, gvisor, containerd, and cri-o. Through manual analysis, we develop taxonomies of CRS bug symptoms and root causes, comprising 16 and 13 categories, respectively. Furthermore, we evaluate the capability of popular testing approaches, including unit testing, integration testing, and fuzz testing in detecting these bugs. The results show that 78.79% of the bugs cannot be detected due to the lack of test drivers, oracles, and effective test cases. Based on the findings of our study, we present implications and future research directions for various stakeholders in the domain of CRSs. We hope that our work can lay the groundwork for future research on CRS bug detection.
format text
author YU, Jiongchi
XIE, Xiaofei
ZHANG, Ceng
CHEN, Sen
author_facet YU, Jiongchi
XIE, Xiaofei
ZHANG, Ceng
CHEN, Sen
author_sort YU, Jiongchi
title Bugs in pods: Understanding bugs in container runtime systems
title_short Bugs in pods: Understanding bugs in container runtime systems
title_full Bugs in pods: Understanding bugs in container runtime systems
title_fullStr Bugs in pods: Understanding bugs in container runtime systems
title_full_unstemmed Bugs in pods: Understanding bugs in container runtime systems
title_sort bugs in pods: understanding bugs in container runtime systems
publisher Institutional Knowledge at Singapore Management University
publishDate 2024
url https://ink.library.smu.edu.sg/sis_research/9445
https://ink.library.smu.edu.sg/context/sis_research/article/10445/viewcontent/Bugs_in_Pods__Understanding_Bugs_in_Container_Runtime_Systems.pdf
_version_ 1816859075780018176