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
Port is open, but can't access it via external IP address
You need RavenDB running on 192.168.0.101:8080 (or 0.0.0.0:8080). If it's running on localhost, it's not accessible from outside the machine.
Read more >What to do if port forwarding does not work - Keenetic
1. When setting up port forwarding, it is necessary to have a public IP address on the router's WAN interface through which it...
Read more >Port in Public IP can't be accessed [closed]
So, the first thing to do is figure out which of those is not working. Go to another Internet access point, outside your...
Read more >Port forwarding not work when behind the public IP
Forget trying to use port forwards and stick to the DNAT. It's an easy two step procedure. 1) Open the firewall up for...
Read more >Understanding Port Forwarding- Beginners Guide
In this tutorial you will learn what port forwarding is,and how it is used to provide internet based devices to access Internal resources....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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