How can I forward localhost port on my container to localhost on my host?

前端 未结 4 1527
遇见更好的自我
遇见更好的自我 2020-12-05 13:39

I have a daemon on my host running on some port (i.e. 8008) and my code normally interacts with the daemon by contacting localhost:8008 for instance.

I\'ve now conta

相关标签:
4条回答
  • 2020-12-05 13:46

    After checked the answers and did some investigation, I believe there are 2 ways of doing that and these 2 only work in Linux environment.

    The first is in this post How to access host port from docker container

    The second should be set your --network=host when you docker run or docker container create. In this case, your docker will use the same network interface you use in Mac.

    However, both ways above cannot be used in Mac, so I think it is not possible to forward from the container to host in Mac environment. Correct me if I am wrong.

    0 讨论(0)
  • 2020-12-05 14:01

    docker run -d --name <NAME OF YOUR CONTAINER> -p 8008:8008 <YOUR IMAGE>

    That will publish port 8008 in your container to 8008 on your host.

    0 讨论(0)
  • 2020-12-05 14:02

    So the way you need to think about this is that Docker containers have their own network stack (unless you explicitly tell it to share the host's stack with --net=host). This means ports need to be exposed both inside the docker container and also on the outside (documentation), when linked with host ports. The ports exposed on the container need to be bound to the host ports explicitly (with -p xxxx:yyyy in your docker run command) or implicitly (using EXPOSE in your Dockerfile and using -P on the command line), like it says here. If your Dockerfile does not contain EXPOSE 8008, or you do not specify --expose 8008 in your docker run command, your container can't talk to the outside world, even if you then use -p 8008:8008 in your docker run command!

    So to get tcp/8008 on the host linked with tcp/8008 on the container, you need EXPOSE 8008 inside your Dockerfile (and then docker build your container) OR --expose 8008 in your docker run command. In addition, you need to either use -P to implicitly or -p 8008:8008 to explicitly link that exposed container port to the host port. An example docker run command to do this might look like:

    docker run -it --expose 8008 -p 8008:8008 myContainer

    It's handy to remember that in the -p 8008:8008 command line option, the order for this operation is -p HOST_PORT:CONTAINER_PORT. Also, don't forget that you won't be able to SSH into your container from another machine on the internet unless you also have this port unblocked in iptables on the host. I always end up forgetting about that and waste half an hour before I remember I forgot to iptables -A INPUT ... for that specific tcp port on the host machine. But you should be able to SSH from your host into the container without the iptables rule, since it uses loopback for local connections. Good luck!

    0 讨论(0)
  • 2020-12-05 14:05

    I'm not sure if you can do that just with docker's settings. If my under standing is correct, expose port is not what you looking for. Instead, establish ssh port forwarding from container to host mightbe the answer.

    0 讨论(0)
提交回复
热议问题