Skip to content

fix(podman): route local clients to the primary listener - #3429

Closed
krishicks wants to merge 1 commit into
mainfrom
hicks/push-xlpssxomqwtt
Closed

krishicks wants to merge 1 commit into
mainfrom
hicks/push-xlpssxomqwtt

Conversation

@krishicks

Copy link
Copy Markdown
Collaborator

Summary

As part of the RFC-0012 changes, Podman Machine uses the IPv4 loopback listener for compute-driver callbacks while the local gateway launcher binds the primary listener to IPv6. The launcher still registered that primary endpoint using localhost.

This meant hostname resolution could direct CLI requests to the IPv4 callback-only listener instead of the primary gateway listener.

Now, we register the literal IPv6 loopback address when using the macOS default while preserving explicit bind-address overrides.

Related Issue

#2942

Changes

Testing

  • mise run pre-commit passes
  • Unit tests added/updated
  • E2E tests added/updated (if applicable)

Checklist

  • Follows Conventional Commits
  • Commits are signed off (DCO)
  • Architecture docs updated (if applicable)

As part of the RFC-0012 changes, Podman Machine uses the IPv4 loopback listener
for compute-driver callbacks while the local gateway launcher binds the primary
listener to IPv6. The launcher still registered that primary endpoint using
localhost.

This meant hostname resolution could direct CLI requests to the IPv4
callback-only listener instead of the primary gateway listener.

Now, we register the literal IPv6 loopback address when using the macOS default
while preserving explicit bind-address overrides.

Signed-off-by: Kris Hicks <khicks@nvidia.com>
@johntmyers johntmyers closed this Sep 17, 2026
@krishicks

Copy link
Copy Markdown
Collaborator Author

This was closed in favor of #3365

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants