Fix slow serverless wake with stable container MACs#130
Merged
Conversation
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
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
--mac-addresswhen creating static-IP containers.Root cause
Podman generated a different MAC whenever a stopped serverless container rejoined the bridge. The proxy retained the old IP-to-MAC neighbor entry, so Linux waited for neighbor discovery to fail before resolving the new MAC. This produced the repeatable
attempts=12, roughly 8.9-second wake latency.Impact
New and redeployed static-IP containers retain the same MAC across sleep/wake cycles, removing the stale-neighbor delay. Existing containers need one controlled redeploy to receive the creation-time MAC. Health-check and readiness behavior are unchanged.
Validation
go test ./...FAILED