Fix handling of container ports for MacOS Docker API#2380
Merged
pablomendezroyo merged 1 commit intodevelopfrom Feb 20, 2026
Merged
Fix handling of container ports for MacOS Docker API#2380pablomendezroyo merged 1 commit intodevelopfrom
pablomendezroyo merged 1 commit intodevelopfrom
Conversation
…null values from Docker API on MacOS
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
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.
Context
This pull request addresses the issue of handling null values for container ports returned by the Docker API on MacOS. It ensures that the application can gracefully manage scenarios where the ports information is not available.
Approach
The solution modifies the
parseContainerInfofunction to check for null values in the container ports before processing them, preventing potential errors and ensuring stability.Test instructions