Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Ports are not open to external/public interface
See original GitHub issueDescription of the new feature/enhancement
It seems that container-desktop not opens the per docker-compose-file estimated ports to a public interface of the host machine (e.g. 192.168.0.1).
The following command currently provides a remedy:
netsh interface portproxy add v4tov4 listenport=80 listenaddress=192.168.0.1 connectport=80 connectaddress=127.0.0.1 netsh interface portproxy add v4tov4 listenport=443 listenaddress=192.168.0.1 connectport=443 connectaddress=127.0.0.1
But the command does not survive a reboot of the host machine for example. So it would be better to implement it in container-desktop.
By the way: great respect for this lightweight and free “Docker Desktop” replacement!
Proposed technical implementation details (optional)
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:17 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
container-desktop does not open ports on the firewall automatically. container-desktop runs under the user’s account. You need to select the interface where you want the port forward on from the tray context menu. If you select a public interface and your account is not elevated then Windows Firewall will ask if you want to allow the port to be opened.
Issue is fixed in v1.0.0-beta.12 closing issue