Docker and Docker compose

[cyberspice82]

Morning all,

I am seeing more and more need to learn some basic Docker skills.

I am following the Hacking APIs book and all the hacking labs are built with Docker and Docker compose.

I am really struggling with a basic concept…

• I install Docker and Docker compose.
• I then install OWASP Juice Shop as a Docker container.
• I can browse to the OWASP Juice Shop locally using http://localhost:8000
• However, I cannot browse to the OWASP Juice Shop from another computer on my network, for example, from my Kali VM where all the hacking tools are installed such as Burp Suite and Postman.

The docker container running OWASP Juice Shop is getting an IP address on its own subnet, for example 172.16. Whereas my network is using 192.168.

Is there a way to force the Docker container running OWASP Juice Shop to use the same physical NIC that is connected to my LAN rather than using some wacky private subnet I cannot route to from a remote device?

Thanks in advance

[furicle]

Yes ?

Docker networking is surprisingly complicated (to me anyway)
Like everything else, it gets specified when you start up the container.

Lots of documentation on line, like Networking overview | Docker Docs

[dougs-gt]

Your local machine running the container is blocking incoming access to that port. Add a firewall exception to that port on your local firewall. Then, you can browse to http://192.168.1.50:8000 and access the interface (assuming that your machine is running on 1.50 in your network).