Devcontainer users lack reliable cross-platform port forwarding
Developers want to reach services running in development containers from local clients, but the available forwarding approaches are tied to particular tooling, behave differently across host platforms, or require utilities inside the container. Port publishing can also fall short when a service listens only on localhost. One signal concerns Mosh rather than devcontainers, but the other five describe the same devcontainer workflow.
For developers using devcontainers. Mentioned from Sep 2015 to Mar 2023 on GitHub.
5 different people described this problem in 2 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 6.7/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
This is the single feature that is preventing me from moving to devcontainers as a standard. Without this, using devcontainers without any specific tooling is simply impossible
For Linux to Container or Container to Container, I had a Response Time which was 50 Times faster than the one of VS Code. Due to the missing support for Unix Sockets on the other platforms, I'm considering using one static Port and Multiplexing all the other ports through it
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 4 more quotes from people who have this problem
- Current workarounds, existing solutions and risks