Pretty simple! Slack commands (or your use case) are now flowing to your local service no policy exceptions are required.By default, most Java web application servers are listening on port 8080, and it can easily cause the popular 8080 port conflict error. The only limitation I found with this solution was the inability to connect to the ngrok HTTP inspector from the browser. When used in combination with -p, the port mappings are ignored.

Rather than binding the ports individually, you can use the host network directly via the -net=host flag.Start your service before the docker container, which should mitigate the issue. You may run into a port conflict with your service when using explicit port binding.Free accounts will generate a random CNAME each time you initialize a tunnel. The NGROK_AUTH and NGROK_SUBDOMAIN env args are optional and are primarily used with a paid account.On Mac, the host address changes, so you need to utilize the reserved DNS name in your port binding.e NGROK_AUTH='' -e NGROK_SUBDOMAIN=mycname wernight/ngrok NOTES AND CONSIDERATIONS I also want to access the Ngrok request inspector running inside the container on port: 4040. On the host, I'm exposing a local rest API on port: 5000, which Ngrok will expose on the internet. Update Started a fork to support some additional Ngrok arguments until they are merged in sirkirby/ngrok docker pull wernight/ngrok:latest Starting your tunnel I recommend wernight/ngrok, it's well-documented and easy to configure. You could roll your own however, there are already several popular options on Docker Hub to get you up and running immediately. Install Docker Desktop via Homebrew brew install docker Container I've found the following Docker-based method to be a reliable workaround to those typical corporate or public network restrictions while still having the full functionality of Ngrok.

Corporate policy restrictions got you down? Me too! I've struggled to find a reliable solution for local Slack, Github, or cloud development when Ngrok, the most commonly used tool for exposing services locally, is restricted by either a local execution policy or via OpenDNS (or similar).

Docker for mac localhost port conflicts