fix: make ddev describe work correctly with new Docker Desktop, for docker/for-mac#7742 #7531
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 Issue
Docker Desktop changed their internal inspect format, breaking
ddev describe
and TestCmdDescribeHow This PR Solves The Issue
Use the (appropriate) ExposedPorts to get the full set of exposed ports, instead of inferring it from Ports.
This affects only
ddev describe
and any other usages of app.Describe(), probably unlikely. It works on all the other Docker providers without problems.We probably can't update our Docker Desktop runners (macOS and Windows) until this goes in, so manual testing is required with DD.
Manual Testing Instructions
With Docker Desktop 4.44.0:
docker-compose.extra.yaml
like this andddev describe
should show the 11111 ports etc.TestCmdDescribe
and it should succeedAutomated Testing Overview
No changes required as the original tests caught this problem in the first place.
Release/Deployment Notes