A way to enumerate/inspect port forwarding from within the dev container.

[modulozero]

I'd like a method to find out what the host-side of port forwarding looks like, from within the container. Even a JSON dump of [host_side_port,remote_side_host:remote_side_port] would be pretty great. As far as I can tell, short of developing an extension from scratch, there's no way to do it, at least short of exposing the docker socket to the inside of the container (awkward, as I'm already running docker-inside-docker).

The use case is as follows:

• I set up a dev container that is supposed to work with the "clone repository in a container" feature.
• I set up port forwarding.
• I do not force specific localhost ports
  Perhaps I want to be able to run several instances of the container in parallel, or to not worry that the user's host will happen to have something on the same port.
• The application wants to generate absolute links at certain times.
• I want to be able to:
  • Print a message like "Reach the front-end at https://localhost:port".
  • The absolute links generated in the application to work correctly.

I generally have a method to programmatically alter the host:port part of the absolute links, but for that to work, I need to know what the port will be on the outside.

[chrmarti]

If you print the message in a terminal, the port will be rewritten before opening when the user clicks on it. Also the openExternal extension API rewrites the port.

[vs-code-engineering]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!