![docker ip forwarding inside container docker ip forwarding inside container](https://linuxconfig.org/wp-content/uploads/2018/11/docker_interacting_php.png)
Here are a few use cases to run docker inside a docker container. I feel like I’m missing a step with the docker configuration or something which passes it through to the container.It definitely works on my network since I can run Soulseek with ports forwarded on my laptop. In this blog, I will walk you through the steps required to run docker in docker using three different methods. Being in host mode should mean that forwarding ports 6081-6082 to that IP should mean they go to Soulseek but they don’t. Looking at Soulseeks diagnostics it does have the right IP, the same as my NAS which is 192.168.0.25. So if I were running Soulseek as a normal application natively, not in docker, I’d choose whatever port I wanted there and then forward those ports to the computer Soulseek was running on.
#DOCKER IP FORWARDING INSIDE CONTAINER HOW TO#
The “Server port” does not need to be opened. In this course, you will learn how to work with Docker images and volumes, configure the Docker daemon and environment variables, forward ports inside a container, and much more. It looks like this, where you select the “listening” ports. I hope this is enough information I can attach some screenshot or whatever if need be, thanks!Ħ0 are the ports I chose in the actual Soulseek application, not in the docker configuration.
![docker ip forwarding inside container docker ip forwarding inside container](https://yqintl.alicdn.com/3e597ac22ada1a7e37a304e35b122e4781c408f0.png)
I have tried doing this via SSH, via the GUI built into synology and of course with Portainer and it’s all the same. Is there something else I need to configure to get the port from the router > synology device > docker > soulseek container? IP addresses () and because of the forwarding rules that are dynamically added in the DOCKER. Port checkers online say those ports are indeed open, but somewhere along the way they aren’t getting to the container. .a container, it exposes it to the entire world, breaking. My understanding is that since the container is on the host network, any port forwarded to the synology device goes straight to the container, right? So I forwarded ports 60 on my router to the Syno device. you will have to use docker run -network host IMAGE:TAG for achieving the desired connection further read here example:- docker run -network host -name CONTAINER1 IMAGE:tag docker run -network. Now within the container itself using Soulseeksown configuration I have selected 60 as my listening ports. I can access soulseek by going to my synology devices IP at the default port for the soulseek container which is 192.168.0.25:6080. I used Portainer to set it up on the same network as my synology device, in host mode, rather than bridge. Soulseek is a P2P application so it needs to have 2 listening ports open in order to work. The docker image I’m having trouble with is realies/soulseek:latest
![docker ip forwarding inside container docker ip forwarding inside container](https://image.slidesharecdn.com/dockertechnologyv18e-140709023642-phpapp01/85/inside-docker-for-fedora20rhel7-12-320.jpg)
I’m currently using a Synology device, so docker is the ideal way to run applications I otherwise couldn’t such as Pihole.