Skip to content

Conversation

@thaJeztah
Copy link
Contributor

The top-level IPAddress field is deprecated in the API, so instead, the IP-address should be obtained from the container's primary network.

The top-level IPAddress field is deprecated in the API, so instead,
the IP-address should be obtained from the container's primary network.

Signed-off-by: Sebastiaan van Stijn <[email protected]>
@thaJeztah
Copy link
Contributor Author

Opening separate, because I don't know if PodMan returns the Networks the same as Docker. This information is a bit ambiguous overall, as the original design assumption a container would have a single IP-address, but the IP-address of the container can differ per network.

I think this rewrite is closest to the old behavior.

cc @robmry @haircommander

@dims
Copy link
Collaborator

dims commented Dec 5, 2025

@robmry @haircommander please let me know when this is ready

@robmry
Copy link

robmry commented Dec 7, 2025

LGTM - but I don't know about Podman either.

@haircommander
Copy link
Contributor

lemme dig around for someone who's more active in podman to review

@thaJeztah
Copy link
Contributor Author

Thanks! Yes, I wasn't sure who was best to ping for this, and I wasn't sure how close the API implementation of podman was on this front 🤗

@dims
Copy link
Collaborator

dims commented Dec 16, 2025

let's merge and iterate. folks can file follow up PRs

@dims dims enabled auto-merge December 16, 2025 12:17
@dims dims added this pull request to the merge queue Dec 16, 2025
Merged via the queue into google:master with commit 5d993f4 Dec 16, 2025
7 checks passed
@thaJeztah thaJeztah deleted the update_ipaddress branch December 16, 2025 12:30
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.

4 participants