revert: Bollard update rolled back, closes #66

Using Bollard 0.19.x meant that network stats weren't being recorded correctly. Updated local unhealthy container to use a speed test in order to check for network IO.
This commit is contained in:
Jack Wills
2025-06-19 20:36:54 +00:00
parent c48465f536
commit aac9c6b598
8 changed files with 256 additions and 256 deletions
+2 -3
View File
@@ -149,7 +149,7 @@ async fn main() {
#[allow(clippy::unwrap_used)]
mod tests {
use std::{str::FromStr, sync::Arc};
use std::sync::Arc;
use bollard::service::{ContainerSummary, Port};
@@ -228,7 +228,6 @@ mod tests {
pub fn gen_container_summary(index: usize, state: &str) -> ContainerSummary {
ContainerSummary {
image_manifest_descriptor: None,
id: Some(format!("{index}")),
names: Some(vec![format!("container_{}", index)]),
image: Some(format!("image_{index}")),
@@ -244,7 +243,7 @@ mod tests {
size_rw: None,
size_root_fs: None,
labels: None,
state: Some(bollard::secret::ContainerSummaryStateEnum::from_str(state).unwrap()),
state: Some(state.to_owned()),
status: Some(format!("Up {index} hour")),
host_config: None,
network_settings: None,