![]() ![]() Then I can access the service from the outside: $ curl :465 In other words, when I run on the host: $ docker run -rm -it -p 465:465 python:3.6 python3 -m rver 465 ![]() However, and here comes the interesting part, I do manage to access the service if the port on the host maps to the same port in the container. My problem is that I cannot access port 465 on my server from the outside: $ curl :465Ĭurl: (7) Failed to connect to port 465: No route to host Here's how to simulate such a service: $ docker run -rm -it -p 465:25 python:3.6 python3 -m rver 25 Port 465 maps to port 25 in the container. I am running a docker container that exposes a service on port 465 on the host. The configuration described in this blog post has served me well for a long time, but I'm now facing a problem I never had before. Iptables rules are notoriously difficult to set up when Docker is running on the host, and I thought I had a definitive solution in this fantastic blog post:
0 Comments
Leave a Reply. |