fix(ci): expand DinD loopback for tracer-release system tests - #3871
Merged
Conversation
System Tests jobs running on docker-in-docker µVM runners hit "no space left on device" with the default 20G loopback (especially the parametric scenario, which builds many container images). Set the gbi-dind env vars to grow the volume to 50G and back it on the kubefs root device instead of the tmpfs-backed /tmp, freeing the volume from the pod's memory budget. See https://datadoghq.atlassian.net/wiki/spaces/K8S/pages/2874901299/How+to+use+Micro+VMs#DinD-in-CI
|
✨ Fix all issues with BitsAI or with Cursor
|
The previous commit applied DOCKER_LOOPBACK_SIZE=50G + DOCKER_LOOPBACK_PATH=/ to the shared .system_tests template, which broke every system-tests job: mkfs.ext4 on the µVM root FS (virtiofs) takes longer than the runner's hardcoded 60s wait-for-docker:2375 timeout, so dockerd never becomes reachable. Move the size bump to tracer-release only (the original failing job) and drop the PATH override — /tmp on these runners is real disk, not tmpfs, so a 50G loopback there works without changing the daemon-ready timing.
Leiyks
force-pushed
the
leiyks/fix-system-tests-dind-disk-space
branch
from
May 11, 2026 13:01
e7ffa3f to
2268a3f
Compare
Leiyks
changed the title
bwoebi
approved these changes
May 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
System Tests: [tracer-release]job has been consistently failing withno space left on device, always during the parametric scenario, on the DinD µVM runners (e.g. this run). The tracer-release job runs every system-tests scenario in sequence and the parametric one exhausts the default 20G Docker-in-Docker loopback volume on Kata-based runners.DOCKER_LOOPBACK_SIZEto50Gonly onSystem Tests: [tracer-release]. The default/tmppath on these runners is real disk (not tmpfs), so a larger loopback there works without changing dockerd startup timing.