Use host networking for populator container to fix DNS in nested podman#16
Merged
Conversation
alicefr
force-pushed
the
investigating-dns-flake
branch
4 times, most recently
from
May 26, 2026 11:52
16e2255 to
57685b4
Compare
alicefr
force-pushed
the
investigating-dns-flake
branch
from
May 26, 2026 13:36
57685b4 to
61aee7c
Compare
The image populator container runs podman pull inside a bridge network, routing DNS through aardvark-dns. In nested podman scenarios this multi-hop forwarding is unreliable, causing intermittent name resolution failures. Add a --host-network-populator flag (default off) that switches the populator to --network=host, bypassing aardvark-dns. The flag is available on both 'cluster start' and 'node add'. The nested test in hack/test-container-image.sh passes it automatically. Assisted-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
alicefr
force-pushed
the
investigating-dns-flake
branch
from
May 26, 2026 14:31
61aee7c to
944daaf
Compare
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.
The image populator container runs podman pull inside a bridge network, routing DNS through aardvark-dns. In nested podman scenarios this multi-hop forwarding is unreliable, causing intermittent name resolution failures. Switching the populator to --network=host lets it use the host's resolv.conf directly, bypassing aardvark-dns.