feat: Add systemd socket activation for dstack-guest-agent #478
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
Changes
dstack-guest-agent.socketwith both sockets (dstack.sock at index 0, tappd.sock at index 1)dstack-socket.{socket,service}andtappd-socket.{socket,service}listenfddependency for receiving sockets from systemdActivatedUnixListenerwrapper implementing rocket'sListenertraitrun_internal/run_internal_v0to use activated sockets when available, with fallbackdstack-guest-agent.serviceto require the socket unitTest plan
Test Results (TDX enabled on teepod2.kvin.wang)
Socket Activation
No /var/run Warning
Boot logs show no warnings about legacy /var/run path.
Socket Persistence After Restart
/var/run Backward Compatibility