nestybox / nestybox/sysbox

High disk usage during docker:dind scenarios with Testcontainers

Open
#875 3 comments 0 reactions 1 assignee View on GitHub

@ctalledo is already working on this.

Since Dec 9, 2024.

bug question
Dominant language
Shell
Stars
3.9k
Forks
230
Avg merge
7h 48m
Merged PRs (30d)
3

Description

Environment:
Rancher: v2.9.3
sysbox: registry.nestybox.com/nestybox/sysbox-deploy-k8s:v0.6.5

Container Runtime Version: cri-o://1.30.4
Image: Ubuntu 22.04.5 LTS
Kernel Version: 5.15.0-124-generic
Kube Proxy Version: v1.30.5+rke2r1
Kubelet Version: v1.30.5+rke2r1
vCPUs: 16
RAM: 36GB

Hey,

We're seeing high disk usage and defective CI jobs on rancher worker nodes once or twice a week, mainly in docker-dind scenarios using Testcontainers. An update to Sysbox v0.6.5 doesn't fix this.

image

sudo journalctl -eu crio

Nov 25 12:47:28 ranchernode crio[1642137]: time="2024-11-25 12:47:28.516519173Z" level=warning msg="Stopping container ad738e20887bad39204cd6106c7d16308a1f8a53a5f21d54cf26ca3714938edb with stop signal timed out. Killing..."
Nov 25 12:47:28 ranchernode crio[1642137]: time="2024-11-25 12:47:28.517333181Z" level=warning msg="Stopping container 68095211d7cb09101f5ad415e7f160f8298c9d5c232068553ce10ebbd64a8ce1 with stop signal timed out. Killing..."

Thanks for any help in advance.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.