You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened?
When using forwardPorts in devcontainer.json, the ports do not appear in the Ports section of VSCode. The ports do successfully forward though.
What did you expect to happen instead?
Manually specified forward ports should appear in the forwarded ports sections of VSCode.
How can we reproduce the bug? (as minimally and precisely as possible)
Use the listed example python repo and uncomment out the forwardPorts line in its devcontainer.json. Rebuild and launch the python webserver. It will auto forward port 9001 as it couldn't get 9000. The webserver will then be available locally on both 9000 and 9001 while only 9001 shows up in the Ports section.
Local Environment:
DevPod Version: v0.5.21
Operating System: windows
ARCH of the OS: AMD64
DevPod Provider:
Local/remote provider: docker
Anything else we need to know?
I have seen this issue with a k8s provider as well.
The text was updated successfully, but these errors were encountered:
Hey @Benjamin-Etheredge, thanks for reporting this issue. That's an issue we've faced for a while now and will need to figure out how to tell VSCode we're already forwarding the port. The issue is that DevPod does have it's own forwarding mechanism which doesn't get picked up by VSCode
What happened?
When using
forwardPorts
indevcontainer.json
, the ports do not appear in thePorts
section of VSCode. The ports do successfully forward though.What did you expect to happen instead?
Manually specified forward ports should appear in the forwarded ports sections of VSCode.
How can we reproduce the bug? (as minimally and precisely as possible)
Use the listed example python repo and uncomment out the
forwardPorts
line in itsdevcontainer.json
. Rebuild and launch the python webserver. It will auto forward port 9001 as it couldn't get 9000. The webserver will then be available locally on both 9000 and 9001 while only 9001 shows up in thePorts
section.Local Environment:
DevPod Provider:
Anything else we need to know?
I have seen this issue with a k8s provider as well.
The text was updated successfully, but these errors were encountered: