feat: support falling back to docker inspect data for gleaning mgmt bridge gw address #1482
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.
title!
similar issue reported in discord here a while back.
tl;dr -- that commit we snag the bridge address so ceos (or presumably others) can set gateway, buuuuuut if you are docker in docker (like me and my little weird launcher tool so i can run this on my mac) then the bridge is not mounted in the "launcher" container so trying to get that bridges address fails.
we already have the output of docker inspect network from earlier on in this func, so this just falls back to attempting to iterate over the ipam section to set v4/v6 addresses. if we still dont get any we just return the original error.
tested this in my dind setup (basically mount docker sock to debian container and launch clab from there but all in docker desktop on Mac) and it worked nicely whereas before it was bombing out due to the error returned from FirstLinkIPs.
lemme know if this makes sense or any changes are needed!