fix(action): ensure dbus is running before cluster creation#4
Merged
Conversation
vCluster standalone mode requires dbus on the host. GitHub Actions runners (ubuntu-24.04) don't always have dbus active when the job starts, causing intermittent "Failed to connect to bus" failures that the existing retry logic can't recover from when the socket never appears. Start dbus explicitly during host preparation, with systemctl fallback to dbus-daemon --fork, and poll for readiness up to 10s before proceeding.
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
1 participant
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
vcluster createsystemctl start dbuswith fallback todbus-daemon --system --forkWhy
vCluster standalone (docker driver) requires dbus on the host. GitHub Actions ubuntu-24.04 runners don't always have dbus active at job start, causing intermittent
Failed to connect to bus: No such file or directoryfailures.The existing retry logic (linear backoff: 10s, 20s, 30s) works when dbus starts on its own within the first retry window, but fails completely when it doesn't. This was seen in run 22570359727 where all 3 attempts failed, vs run 22483375240 where attempt 2 succeeded after a 10s wait.
Runner image is the same (
20260224.36.1) in both cases — the issue is timing, not a runner update.Test plan
custom-namejob