RECORD
Towards a More Reliable and Available Docker-based Container Cloud
Distributed, Parallel, and Cluster Computing · Submitted 28 Aug 2017
abstract compiled · 2026-09-23 · no language-model review
The authors' main claim Our evaluation shows that HYDRA imposes only moderate overheads even under load, while achieving much higher container availability.
The compiled record
The paper's own sentences, arranged. Each label is drawn from a closed vocabulary; the number beside it is the probability the classifier gave that label. Numbers in the tables are the authors', checked by code. No sentence in this record was written by a model.
Open the compiled record
The abstract, sentence by sentence
Operating System-level virtualization technology, or containers as they are commonly known, represents the next generation of light-weight virtualization, and is primarily represented by Docker. However, Docker's current design does not complement the SLAs from Docker-based container cloud offerings promising both reliability and high availability. The tight coupling between the containers and the Docker daemon proves fatal for the containers' uptime during daemon's unavailability due to either failure or upgrade. We present the design and implementation of HYDRA, which fundamentally isolates the containers from the running daemon. Our evaluation shows that HYDRA imposes only moderate overheads even under load, while achieving much higher container availability.
background contribution method result interpretation main claim
| # | sentence | role | the authors' own work | states the main conclusion | strength |
|---|---|---|---|---|---|
| s0 | Operating System-level virtualization technology, or containers as they are commonly known, represents the next generation of light-weight virtualization, and is primarily represented by Docker. | background 1.00 | 0.04 | 0.03 | asserted 1.00 |
| s1 | However, Docker's current design does not complement the SLAs from Docker-based container cloud offerings promising both reliability and high availability. | gap 0.52 | 0.10 | 0.05 | asserted 1.00 |
| s2 | The tight coupling between the containers and the Docker daemon proves fatal for the containers' uptime during daemon's unavailability due to either failure or upgrade. | background 0.81 | 0.12 | 0.05 | asserted 1.00 |
| s3 | We present the design and implementation of HYDRA, which fundamentally isolates the containers from the running daemon. | contribution 0.98 | 0.93 | 0.20 | asserted 0.99 |
| s4 | Our evaluation shows that HYDRA imposes only moderate overheads even under load, while achieving much higher container availability. | result 1.00 | 0.96 | 0.76 | asserted 1.00 |
What was examined, and what was not
- arXiv listing abstract v1
- full text
- figures and tables
- references and citing sentences
- relations to other papers
- P abstract
- S sections
- T body sentences
- C citations
- R cross-paper relations
The paper
Original abstract
Operating System-level virtualization technology, or containers as they are commonly known, represents the next generation of light-weight virtualization, and is primarily represented by Docker. However, Docker's current design does not complement the SLAs from Docker-based container cloud offerings promising both reliability and high availability. The tight coupling between the containers and the Docker daemon proves fatal for the containers' uptime during daemon's unavailability due to either failure or upgrade. We present the design and implementation of HYDRA, which fundamentally isolates the containers from the running daemon. Our evaluation shows that HYDRA imposes only moderate overheads even under load, while achieving much higher container availability.
Human review
Discussion
Know something about this paper? Leave a comment, or highlight any passage above to comment on it.