Repository navigation
fix: forward configured devcontainer ports - #60
Merged
Merged
Conversation
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
1 participant
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.
Opening a devcontainer now forwards its configured
forwardPortsto host loopback, including servers bound to container localhost. Forwarding reuses listeners on reopening, releases them on Stop/Remove/disconnect, restores saved configuration on reconnect, and reports host-port conflicts.Add active Docker coverage through the packaged Dev Containers RPC process for Node and Python images, with host HTTP assertions and lifecycle cleanup. The relay uses socat, Node.js, or Python 3 in the container; the existing browser suite and five-platform PR matrix remain enabled.